docker -D info does not include debug information

(docker version: 1.8.1)
According to the info documentation

The global -D option tells all docker commands to output debug information.

When I use the -D option, I get the same result as without -D:
$ docker -D info
Containers: 8
Images: 140
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 156
 Dirperm1 Supported: false
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 3.13.0-24-generic
Operating System: Ubuntu 14.04.2 LTS
CPUs: 2
Total Memory: 1.955 GiB
Name: test-VirtualBox
ID: YHUO:K2OX:K6UA:UEBP:RQYK:F2K7:SWDJ:IH67:TWO4:MQ5J:IAFJ:3XCH
WARNING: No swap limit support

$ docker info
Containers: 8
Images: 140
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 156
 Dirperm1 Supported: false
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 3.13.0-24-generic
Operating System: Ubuntu 14.04.2 LTS
CPUs: 2
Total Memory: 1.955 GiB
Name: test-VirtualBox
ID: YHUO:K2OX:K6UA:UEBP:RQYK:F2K7:SWDJ:IH67:TWO4:MQ5J:IAFJ:3XCH
WARNING: No swap limit support

Not sure if the -D option has been deprecated, and documentation simply needs to be updated?
(I also have a question about the Images: 140, what does this number corresponds to? It doesn't appears to match up with the output from docker images : 18)

Hi!
Please read this important information about creating issues.
If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.
This is an automated, informational response.
Thank you.
For more information about reporting issues, see https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues

BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
docker version:
docker info:
uname -a:
Provide additional environment details (AWS, VirtualBox, physical, etc.):
List the steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Provide additional info you think is important:
----------END REPORT ---------
#ENEEDMOREINFO

what does this number corresponds to? It doesn't appears to match up with the output from docker images : 18)

I think it includes all intermediate images, so should match docker images -a

When I use the -D option, I get the same result as without -D:

Hm, good point, I know it's still used for the daemon to output more log messages, but it could be that the client doesn't use it anymore (previously docker info did show more info when used with -D)

I think it includes all intermediate images, so should match docker images -a

I see!

Old(?) Gordon bot asks for docker -D info
https://github.com/docker/docker/blob/634a848b8e3bdd8aed834559f3b2e0dfc7f5ae3a/contrib/report-issue.sh#L39
New(?) Gordon bot asks for docker info
https://github.com/docker/leeroy/blob/a3fb0f9f89e99bc5663435265fec361c4eca9200/github/comments.go#L60

From what I can tell in info.go, it looks like the debug is only shown if the daemon is started with -D:
https://github.com/docker/docker/blob/634a848b8e3bdd8aed834559f3b2e0dfc7f5ae3a/api/client/info.go#L54
So, I tried to start the docker daemon manually with -D: docker daemon -D. When I issued docker info again, I can see the extra debug info:
$ docker info
Containers: 9
Images: 157
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 175
 Dirperm1 Supported: false
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 3.13.0-24-generic
Operating System: Ubuntu 14.04.2 LTS
CPUs: 2
Total Memory: 1.955 GiB
Name: test-VirtualBox
ID: YHUO:K2OX:K6UA:UEBP:RQYK:F2K7:SWDJ:IH67:TWO4:MQ5J:IAFJ:3XCH
Debug mode (server): true
File Descriptors: 11
Goroutines: 18
System Time: 2015-09-13T13:22:20.604492352-07:00
EventsListeners: 0
Init SHA1: f03be8ef95c082e1e68bfb533064420fcfd161eb
Init Path: /usr/lib/docker/dockerinit
Docker Root Dir: /var/lib/docker
WARNING: No swap limit support

So I guess the documentation could be updated with both examples. One example would show the output of info when daemon is started as normal, and the other example when daemon is started with -D. Finally, remove the description of -D from info command itself.

#dibs

Thanks for doing the research. Looking at some PRs that could be related here; https://github.com/docker/docker/pull/11965 which removed coupling of -D and the "Debug" env-var, and https://github.com/docker/docker/pull/13221 brought it back in, and this line seems to tell if the extra should be output or not; https://github.com/docker/docker/pull/11965/files#diff-9ee0ca443f464cd85f2e1339c2c204d9R47
@duglin any ideas? Should this output be dependent on the daemon being in debug?

@tiborvass as @thaJeztah mentioned, the issue is here:
https://github.com/docker/docker/blob/master/api/client/info.go#L53
we only check the daemon's debug flag, not the client's or the "common" flags:
https://github.com/docker/docker/blob/master/docker/common.go#L40
I wasn't sure if the way you want this solved is to pull in those 'common' flags into the CLI code or if there was some other way you wanted people to get access to them.  Adding a check for the "DEBUG" env var does work but I'd really prefer to not use that if we can avoid it.

ping @tiborvass

I think #19893 fixes this but keep in mind that not all commands will generate debug info - some just don't have anything to say  :-)   Once that PR is in, try "docker -D run ubuntu echo hi" and you should see some output.  "docker -D info" though is just a quiet one.

I can confirm that #19893 fixed this issue:

I'm also adding a regression test to make sure this doesn't break again: #19901

@calavera I'm not seeing that debug line when I do docker -D info from master? Anything needed?

@duglin the debug flag must be set on the server to see that:

right, that's what I figured, so to his scenario the only way we'll see more info is if he gets lucky on the particular command. e.g. docker info doesn't have any debug info, but "docker run" does.


The layout function cannot be used after the upgrade

Is the layout function canceled? Or am I not using the right method?

readme，use id_photo workflow


Credits don't work when updates are suspended

Most of the cesium-native integrations have a "Suspend Update" feature. When enabled, they don't call Tileset::updateView, so the current set of loaded and selected tiles is frozen in place. This is useful for debugging.
But this doesn't work well with credits. If updateView isn't called in a frame, then none of that tileset's credits will be shown in that frame. The credits disappear, rather than being frozen like the tiles are.
One way to solve this is to move the "suspend update" feature into cesium-native, probably in TilesetOptions. Then the integrations would always call updateView, but when updates are suspended it would exit early without loading or selecting tiles. It would apply the previously-selected credits to the current frame, though, fixing this bug.

I ran into this issue in Cesium for Omniverse yesterday as well.


Update s3, sdk-core, sqs to 2.17.263

Updates

software.amazon.awssdk:s3
software.amazon.awssdk:sdk-core
software.amazon.awssdk:sqs

from 2.17.191 to 2.17.263.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "software.amazon.awssdk" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "software.amazon.awssdk" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #540.


[CI] Test builds from zip files

Description
Although config.ts is added at the top level of the plugin, it is not included in the construction artifact when using the command yarn plugin-helpers build. The current github testing workflows always get the source code through checkout.  (see examples https://github.com/opensearch-project/dashboards-search-relevance/blob/main/.github/workflows/remote-integ-tests-workflow.yml#L72-L75 and https://github.com/opensearch-project/dashboards-search-relevance/blob/main/.github/workflows/test-and-build.yml#L22-L25). We should instead utilize build artifacts for integration testing.

Is this a problem for all plugins? Could we please open a meta issue in OpenSearch-Dashboards and do this for all plugins? cc: @kavilla

Is this a problem for all plugins? Could we please open a meta issue in OpenSearch-Dashboards and do this for all plugins? cc: @kavilla

Opened this:
https://github.com/opensearch-project/OpenSearch-Dashboards/issues/3918

Current progress is being worked on and monitored here.


mzXML/mzML to mzMLb converter for Python?

Hi,
I really appreciate your efforts in creating the mzMLb data format. I wonder how difficult it would be to integrate this format into an existing Python program that is made for large scale MS data processing. The program runs on Linux and Windows and currently uses its own high-performance data format. In that case, I could adopt the file format right away. We are currently using the Apache Arror based .feather format.
https://mint.resistancedb.org/

from psims.transform.mzml import MzMLToMzMLb

for fn in tqdm(fn_mzML):
    fn_out = fn.replace('mzML', 'mzMLb')
    print(fn, '-->', fn_out)
    MzMLToMzMLb(fn, fn_out).write()


experiment attribute not present in data retrieved from database service

Informations

Qiskit Experiments version: 53c3d218c552ad4aaf40da4c6ff5122b71e052e8
Python version: 3.9.10
Operating system: Arch Linux

What is the current behavior?
experiment attribute not present in data retrieved from database service. It survives local serialization and deserialization, so it should also survive database storage and retrieval.
Steps to reproduce the problem
import json
from qiskit import IBMQ
from qiskit_experiments.framework import ExperimentEncoder, ExperimentDecoder, ExperimentData
from qiskit_experiments.library import StandardRB

IBMQ.load_account()
provider = IBMQ.get_provider(hub='ibm-q-internal', group='deployed', project='default')
backend = provider.get_backend('ibmq_belem')

exp = StandardRB(
    qubits=(0,),
    lengths=list(range(1, 5)),
    seed=123,
    backend=backend,
)
data = exp.run()
data.save()
data.block_for_results()

deserialized = json.loads(json.dumps(data, cls=ExperimentEncoder), cls=ExperimentDecoder)
print('Experiment present after local deserialization:')
print(deserialized.experiment is not None)
print()

retrieved_data = ExperimentData.load(data.experiment_id, provider.service('experiment'))
print('Experiment present after database retrieval:')
print(retrieved_data.experiment is not None)

...
(Warning about backend not being serializable omitted)
...

Experiment present after local deserialization:
True

Experiment present after database retrieval:
False

What is the expected behavior?
experiment attribute should be present in data retrieved from database service.
Suggested solutions
Serialize the experiment and store it in the database when data.save is called. Deserialize and return it when data is retrieved.

The intent is to actually remove having the experiment instance in ExperimentData at all, and instead store the config that can be used to recover the experiment later if needed (#694), but there are some database issues that need to be resolved first before this can be done (See issue #691 for example)


Android Background service

Hello.
I am beginner android developer.
I want to know where is background service in code.
Regards.

EngineService.java


Added screenshot to readme (gif)

Uses interface after cosmetic changes in #2
Fixes #4

thanks @tabacitu


Rename spawn-frontend-material to spawn-frontend

and current spawn-frontend repository to spawn-frontend-old.

Old repo changed name to spawn-frontend-draft-1 , there is also a note about depreciation.
This repo won't be changed, I think this name is ok.


Potential issue in the KNN calculation

Thank you for your fascinating work.
I encountered several issues related to DDP while using the knn_eval.py script, but the major problem lies in line 261:
https://github.com/rezaakb/peft-vit/blob/5095e75ef45018baef7ccf935ba6095b6d030d9b/src/eval_knn.py#L261
The data loader is returning the image and the index (not the label), but the KNN calculation requires the label. Could you please clarify this? I have been unable to reproduce the ImageNet1k accuracy using the trained model on CIFAR-100 with block expansion.
I was able to reproduce the results on CIFAR-100:

But the results on ImagetNet1k:

Thank you.

Thank you so much for using our code and reporting this issue. Yes, we need to modify the k-NN code and write documentation for it.
Regarding your issue, I believe the indexes should be fine. We used the k-NN evaluation from here. Can you check if the model initialized correctly with expanded blocks? You need to pass the arguments that you used for expansion (e.g., split) to this code.

Thank you for your response. I also couldn't reproduce the results using just the pretrained model. I believe there are numerous issues in the knn_eval script.

Yes, I think there may have some problems loading the checkpoint, I will check it. Thank you.


[ko] Update the multi tenancy docs to remove reference to archived pr…

https://github.com/kubernetes/website/pull/48178/files

/approve


Switching to a "comparison" tab always puts the cursor back to the start of the file

VSCode Version: 1.5.3
OS Version: Windows 8.1 Enterprise

Steps to Reproduce:

Right click on a working file and choose "Select to compare"
Right click on another working file and choose "Compare with...". This will open a tab showing the comparison.
Scroll down to a position.
Open another file / switch to another tab.
Go back to the comparison tab - the cursor is back at the start of the document and the scroll position is lost.

https://github.com/Microsoft/vscode/issues/10663


Roll Flutter Engine from 67a7fe18c014 to 1a2360f77b36 (2 revisions)

https://github.com/flutter/engine/compare/67a7fe18c014...1a2360f77b36
2024-08-22<EMAIL_ADDRESS>Roll Skia from 4c66b7e42027 to 7611984dc27b (1 revision) (flutter/engine#54710)
2024-08-22<EMAIL_ADDRESS>Roll Dart SDK from 025bf8d376d3 to ce160bf13347 (1 revision) (flutter/engine#54709)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC jimgraham@google.com,rmistry<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


Themes

Theme basics for light/dark mode.
Unfortunately Bootstrap v5 still does not offer support for implementing this easily, so we will either need to add overrides for our customizations or generate a separate Bootstrap version, like I did for BTCPay.
Will think about this some more :)
Closes #9.
Preview

Rebased and adapted the settings view:

There are still minor kinks like the loading indicator not showing properly on dark mode, but I'd say let's bring this in as we are about to change the loading animation anyways.


Aleo deploy command

Motivation
We need to have a CLI command to deploy Aleo projects. During Testnet3's life cycle all program deployments will be sent to the blockchain by Aleo Explorer (https://aleo.network.com/testnet3/deploy) on behalf of the user 🚀
Related PRs

This feature will be used by https://github.com/AleoHQ/snarkOS-beacon/pull/13

Cc https://github.com/AleoHQ/snarkVM/issues/986


client.get_community_info(cid); issue

When I'm trying to write information from community in variable, it throws me an exception:
The JSON value could not be converted to System.String. Path: $.themePack.themePackRevision | LineNumber: 0 | BytePositionInLine: 945."
Example:
Amino.Client client = new Amino.Client();
await client.login(email, password);
await client.join_community(cid);
var community = client.get_community_info(cid); // exception, cid is correct, because join works perfectly.

fixed in #41 and availave in 1.7.0-dev0.2.3


Autocomplete IntelliSense only showing options for first options overload, missing the rest

Suppose I create a function that can take multiple overload types.  For example:
function getElement(reference: { name: string });
function getElement(reference: { index: number });
function getElement(reference: { id: string });
function getElement(reference: any) {
    // do something with reference
}

When I go to use the function, IntelliSense correctly shows me that there are three possible overloads:

Etc.

However, when I type a curly bracket and then press ctrl-space to get the autocomplete list, it only shows me the first type (“name”), and not any of the other overloads (“index” and “id”)

This works as expected now


Fix: 58 Timeframe bugs for last-7days & last week

Fix for issue #58
1st bug, last 7 days line/bar chart is showing 8 days
TEST:

add a bar/line chart widget to a dashboard with a timeframe of Last 7 Days
the chart should only show the last 7 days (and not the last 8 days)

2nd bug, when selected week start is Monday and you have a single line/bar widget on the dashboard with a timeframe of Last Week, the last Sunday was not shown in the chart.
TEST:

make sure that in 'settings' you have selected to start the week on Monday
create an empty dashboard
add a line/chart widget to this dashboard with a timeframe of Last Week
the chart should show the values for all the days of last week, including the last Sunday

Solution tested on Netlify by the the user reported the issue, see #58


Refactor chi-squared distribution

Ok, this is a larger one:
Mode
Fix formula for the mode. Math.NET implementation has an error for freedom < 2 and faulty unit tests as well.
Pdf and log density
When investigating this unit test:
// TODO: figure out why this test fails:
test::check_continuous_distribution(&try_create(1.0), 0.0, 10.0);

I realised the problem two-fold: First, the old pdf implementation returned Inf at 0 instead of 0. Second, for freedom == 1.0 the pdf is very steep around 0 and cannot be integrated with the hard-coded step size. So I implemented a branching in the pdf and log density (also see Wikipedia) and changed freedom to 1.5.
Actually, Math.NET has a little bit more branching in the chi-squared pdf, but the bulk of it is covered in statrs's gamma.rs implementation. I'm not sure if we want to cover the case of freedom = Inf. @boxtown What's your opinion on this? If yay, I'll add this branching to pdf() and ln_pdf() and uncomment the unit tests. If nay, I'll just delete the commented unit tests.
Misc
And of course added more unit tests, but this is kind of self-explanatory.

Yup, I think being consistent with scipy is probably a good thing
On Oct 30, 2017 11:52 AM, "Mikhail Pak"<EMAIL_ADDRESS>wrote:

@mp4096 commented on this pull request.
In src/distribution/chi_squared.rs
https://github.com/boxtown/statrs/pull/77#discussion_r147747017:

@@ -310,7 +310,11 @@ impl Continuous<f64, f64> for ChiSquared {
///
/// where k is the degrees of freedom and Γ is the gamma function
fn pdf(&self, x: f64) -> f64 {

   self.g.pdf(x)

   if x > 0.0 {

Ok! Just to make sure: You prefer to return +∞ when 0 < freedom < 2 and
pdf is evaluated at 0.
Then I'll rewrite the unit tests and update the docs.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/boxtown/statrs/pull/77#discussion_r147747017, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACwkvpSBpFsyFbCHnZeBEr1mygWosyVlks5sxfDagaJpZM4P_MEl
.


Split Remaining Charge Time into Hours/Mins

I think this is a bit more understandable at quick glance.

Loving the new updates to the widget. Hope we aren't locked out soon...

@niklasvieth Thoughts?


Enhance test for GitHub support

Github support is experimental feature. I will enhance the tests for this feature for practical usage.

I've made a project for integration tests of Walter. https://github.com/walter-cd/walter-github-sample-for-test


admin: Getting a missing mapbox access token for the interview map

This is the case for all recent surveys. Could it be one of the recent package migration? It previously worked. Doing a bisect should find the commit that broke the map.

This is a bug since webpack 5. I'm totally puzzled by this, the code is the same, the token is there. Maybe some incompatibility? We could try to debug this, but react-mapbox-gl hasn't been updated in 4 years.
I propose we just upgrade to deck-gl for these maps. See https://github.com/chairemobilite/transition/pull/773/commits/b361dacf5252d85f67b38d96266db507bd717531 for a simple implementation of deck-gl with our code base in Transition.


rofi plugins and rofi-wayland

menu application rofi has a dozen plugins on nixpkgs, but using Wayland port rofi-wayland package instead the plugins appear not to work yet.
as per https://discourse.nixos.org/t/rofi-on-wayland-and-plugins/17354, a workaround that may work is this:
nixpkgs.overlays = [(final: prev: {
  rofi-calc = prev.rofi-calc.override { rofi-unwrapped = prev.rofi-wayland-unwrapped; };
})];

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/rofi-on-wayland-and-plugins/17354/6

hm seems like rofi -show calc works

I am having same issue with rofimoji, download it with nixpkgs -p rofimoji and then it uses XWayland version :/

@justinlovinger am I just using your package wrong or something? Only way I could get it working nicely, at least should be documented somewhere or something idk

@justinlovinger am I just using your package wrong or something? Only way I could get it working nicely, at least should be documented somewhere or something idk

That is correct. rofimoji differentiates between Wayland-clipboard support and Wayland-rofi support, so we do too.
Actually, now that rofimoji supports many different selectors, there is an argument to be made for not wrapping rofi with the binary and instead relying on selectors in your environment.

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/rofi-emoji-plugin-instructions-dont-work-need-help/49696/9


"Never show this again on" notification disables ability to change largeFileOptimization

Issue Type: Bug
This is related to large files tokenization
I started facing this After the fix made in https://github.com/Microsoft/vscode/issues/44206.
If the user clicks "never show this again" when they are informed certain features have been turned off, the user can never have the notification show again via changing settings.
Additionally, all of the settings related to large files are now ignored ('editor.largeFileOptimizations'), as vscode checks to see if the notification was dismissed and returns if it is, then checks settings if it isnt dismissed.
This means if the user wants to have the notification not display due to not needing it for most files, but be able to force optimizations on later for a particular file, it is now not possible to do so.
Version: 1.29.1
Commit: bc24f98b5f70467bc689abf41cc5550ca637088e
Date: 2018-11-15T19:13:36.375Z
Electron: 2.0.12
Chrome: 61.0.3163.100
Node.js: 8.9.3
V8: 6.1.534.41
Architecture: x64
Steps to Reproduce

Open large file (vscode definition of large file)
Click "Never show this again" on disabled tokenization notification
Attempt to word wrap large file (disabled due to disabled tokenization)
Open Settings
Change User setting 'editor.largeFileOptimizations' to true
Attempt to word wrap large file (still disabled)

editor.largeFileOptimizations is true by default. It must be changed to false in order to get wrapping working in large files.


Add support for password resets

I'd be interested to see what you suggest for password resets, since uberauth/guardian don't seem to have something built in. Or do you recommend using sentinel which seems to provide some of this functionality out of the box. Thanks @hassox!

I'm working on this for my own project right now. Should have something to report back soon.


In OSX do not search for GL headers

It appears that in recent versions of OSX, the GL headers are removed and not needed anymore. @jbmouret @Aneoshun  can you verify that this is working OK in your Mac PCs?

It works but the master was working before (with the narrowing patch).

In the master, I get this result:
Magnum: Checking for OpenGL includes           : /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/OpenGL.framework/Versions/A/Headers
but yes, this does not seem to be mandatory.

Yes in recent M1 laptops (a few of my students have them), it seems that there is no GL.h header. I'll merge this. Seems harmless.


Add error handling for cache connection errors

One thing to note is that if the cache isn't available, Strider will get a new registry of kps for every single query. This is very suboptimal, but would allow us to respond in real time until we could get the redis back up.

Hmm. I think I can make it better. An in-memory registry that is just loaded on startup. Cause getting it in real time takes about 20 seconds, and that's just cutting into our lookup time.


Report: 500 Server Error in Elixir Live Book

Enum.concat([0, 0, 0, 0, 0], [{0, 0}])
I received a 500 Server Error response. It seems that this code is causing an issue within the Live Book environment.
Please investigate this error and provide assistance in resolving it? It appears that the Enum.concat/2 function, when called with the arguments [0, 0, 0, 0, 0] and [{0, 0}], is triggering the server error.
I have been utilizing the Elixir Live Book platform for my development work, and it has been an excellent tool thus far. I appreciate the convenience it offers for interactive Elixir coding and experimentation. However, encountering this error has hindered my progress, and I would greatly appreciate your prompt assistance in resolving it.
If you require any additional information or code samples to assist in troubleshooting this issue, please let me know, and I will be more than happy to provide them.
Thank you for your attention to this matter. I look forward to hearing from you soon and having this issue resolved, allowing me to continue utilizing the Elixir Live Book platform effectively.

This code works fine for me. Livebook v0.9.2

Which livebook version are you on?

This code works fine for me. Livebook v0.9.2
Which livebook version are you on?

The same version with you I am using on Cloud also.

Hey @aungmyooo2k17, are you able to access any logs from the application? Does it happen only for this specific code?

Hey @aungmyooo2k17, are you able to access any logs from the application? Does it happen only for this specific code?

Only for this specific code that I provide above. I don't think I can get any logs because I thought the function make the server long running processing and then I cannot able to see my notes again (only showing 500 server error). And then I click on the menu shown below.

Are you running using Docker? I was thinking maybe you could access the container logs.
If you create a new notebook and have just that code, does it also break?

At that time I am now using docker I was on live book on the fly my link was https://alex.fly.dev.
but now I am using on docker it's working fine.

You can go to the dashboard on fly.io and look at the monitoring tab, perhaps there are some logs there.
That said, a likely explanation would be that you run out of memory (especially if that's the default fly instance size). It's surprising that the Enum.concat would push it over the edge, but once the memory usage was close to maximum, it could be any code.

Actually see on Dashboard tab also showing 500 server error. That is why I can do nothing.

@aungmyooo2k17 I mean https://fly.io/dashboard, not the Livebook dashboard :)

I'm gonna assume this was related to the fly instance and close this. If you run into this again and it's not out of memory crash, feel free to reopen :)


[BUG]  Cannot read properties of undefined (reading 'options')

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
Following the documentation on Shopware Frontends, it says to add @shopware-pwa/cms-base to the extends: [ ] section of nuxt.config.ts, however whenever I do that and start up my nuxt project I get the following error message.
 ERROR  Cannot read properties of undefined (reading 'options')

 ERROR  Cannot read properties of undefined (reading 'options')

Once I remove the extends my nuxt project is able to startup properly.
Expected Behavior
Following the documention here https://frontends.shopware.com/framework/shopping-experiences.html#install-the-package it doesn't mention to do that, however the templates have it in the extend section and not in the module section. What is the correct way of adding this module to the nuxt.config.ts file?
Steps To Reproduce
Create Nuxt Project
install @shopware-pwa/cms-base module
Add it to the extends: ["@shopware-pwa/cms-base"] section of your nuxt.config.ts(.js) file
Start up the project
Environment
- OS: Windows 11
- Node: 21.1.0
- pnpm: N/A

Anything else?
N/A

CMS Base package as a layer is available only in canary version currently. Once the maturity of the setup is enough, the documentation will be updated for this option as well.
You mentioned the docs, and there is no work about using layers yet, so if you are using the latest or a specific stable version, please don't use layers. We are working on that 🙌🏼


[Backport 2.14] Fix negative requestStats memory_size issue (#13553)

Description
Backports https://github.com/opensearch-project/OpenSearch/pull/13553
Related Issues
Check List

[x] New functionality includes testing.

[x] All tests pass

[x] New functionality has been documented.

[x] New functionality has javadoc added

[x] Failing checks are inspected and point to the corresponding known issue(s) (See: Troubleshooting Failing Builds)
[x] Commits are signed per the DCO using --signoff
[x] Commit changes are listed out in CHANGELOG.md file (See: Changelog)
~[ ] Public documentation issue/PR created~

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

Seems like all the changelog entries were removed recently. Maybe add a skip changelog tag in that case?

Seems like all the changelog entries were removed recently. Maybe add a skip changelog tag in that case?

The change log for a release branch is the release notes. You should add this to the 2.14 release notes instead. (Actually, it should be removed from the Unreleased 2.x sections in the 2.x and main branches, since it will be released in 2.14.)

@msfroh Added in the release notes. I thought it was already picked, my bad.

@sgup432 Can you fix up the changelog and release notes on the 2.x and main branches for this change now?


TEST_TMPDIR not set for sh_tests

It doesn't look like TEST_TMPDIR is being set. Here's what I see if I add an env to the top of my test script:
TEST_SRCDIR=/absolute-path-to/b89de19a538f272d8732af51d9c5c7fb/kythe-trunk/bazel-out/local_linux-fastbuild/bin/kythe/extractors/cmake/compilation_database.runfiles
TEST_TIMEOUT=300
_=/usr/bin/env
PWD=/absolute-path-to/b89de19a538f272d8732af51d9c5c7fb/kythe-trunk/bazel-out/local_linux-fastbuild/bin/kythe/extractors/cmake/compilation_database.runfiles
TZ=UTC
SHLVL=2
TEST_SIZE=medium

This is also not being set for cc_test in Mac OS X:
exec ${PAGER:-/usr/bin/less} "$0" || exit 1
E0418 20:24:17.488983<PHONE_NUMBER> gtest_main.cc:50] TEST_SRCDIR=/private/var/tmp/_bazel_trevorgray/390dfa3fb96187fc2bcda1f7756632a6/code/bazel-out/local_darwin-fastbuild/bin/sample_test.runfiles
E0418 20:24:17.490394<PHONE_NUMBER> gtest_main.cc:50] TEST_TIMEOUT=300
E0418 20:24:17.490414<PHONE_NUMBER> gtest_main.cc:50] PWD=/private/var/tmp/_bazel_trevorgray/390dfa3fb96187fc2bcda1f7756632a6/code/bazel-out/local_darwin-fastbuild/bin/sample_test.runfiles
E0418 20:24:17.490428<PHONE_NUMBER> gtest_main.cc:50] TZ=UTC
E0418 20:24:17.490442<PHONE_NUMBER> gtest_main.cc:50] SHLVL=1
E0418 20:24:17.490455<PHONE_NUMBER> gtest_main.cc:50] TEST_SIZE=medium
E0418 20:24:17.490470<PHONE_NUMBER> gtest_main.cc:50] OLDPWD=/private/var/tmp/_bazel_trevorgray/390dfa3fb96187fc2bcda1f7756632a6/code
E0418 20:24:17.490483<PHONE_NUMBER> gtest_main.cc:50] _=./sample_test
F0418 20:24:17.490499<PHONE_NUMBER> gtest_main.cc:53] Check failed: getenv("TEST_TMPDIR") != NULL
*** Check failure stack trace: ***
    @        0x107c8c51a  google::LogMessage::Fail()
    @        0x107c8b4ab  google::LogMessage::SendToLog()
    @        0x107c8c1c0  google::LogMessage::Flush()
    @        0x107c932a8  google::LogMessageFatal::~LogMessageFatal()
    @        0x107c8c965  google::LogMessageFatal::~LogMessageFatal()
    @        0x107c84b7f  main
tools/test/test-setup.sh: line 16: 20787 Abort trap: 6           "./$@"

Known issue - it's not set for any test.


ARROW-14634: [Flatbuffers] introduction of ColumnBag

This Draft PR is the proposed flatbuffer change referenced on the mailing list with subject "[DISCUSS] next iteration of flatbuffer structures"
I wrote a small document with some details of the proposal: https://docs.google.com/document/d/1jsmmqLTyJkU8fx0sUGIqd6yu72N4v9uHFsuGSgB_DfE
This is the non-documentation side of the proposal.

@alamb FYI

Thank you for the writeup and PR @nbauernfeind  -- I added a link to the mailing list discussion and left a question on the context for this change in the google doc.

I've updated the PR based on feedback so far. I had to move FieldNode to Schema.fbs -- to avoid a cyclical dependency between Schema, Message, and ColumnBag.


project_folder variable is never created and initialized. Code won't run.

project_folder variable is never created and initialized. Code won't run.
if not os.path.exists(project_folder):
os.makedirs(project_folder)

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

ID: a086a867-60ff-3f45-702d-2ea0ce0f4f0c
Version Independent ID: 38c9cb40-e4ed-1849-d7ca-9e5c9e51a94d
Content: Automated ML remote compute targets - Azure Machine Learning
Content Source: articles/machine-learning/how-to-auto-train-remote.md
Service: machine-learning
Sub-service: core
GitHub Login: @cartacioS
Microsoft Alias: sacartac

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

#assign:@sdgilley

@CESARDELATORRE - thanks for noticing this.  The project_folder should be a string, so the easiest way to fix is to simply add quotes around 'project_folder'.  I've made this change to the document.  The updated version will be available later today.
#please-close


Fix erroneous behaviors of missing discriminator fields on bundling.

Fix #114

Codecov Report

Merging #115 into master will increase coverage by 0.17%.
The diff coverage is 90%.

@@            Coverage Diff             @@
##           master     #115      +/-   ##
==========================================
+ Coverage   92.27%   92.45%   +0.17%
==========================================
  Files          11       11
  Lines        1282     1286       +4
  Branches      257      259       +2
==========================================
+ Hits         1183     1189       +6
+ Misses         99       97       -2

Impacted Files
Coverage Δ

lib/bundling.js
96.68% <90%> (+1.03%)
:white_check_mark:

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 2dedafe...cbbd555. Read the comment docs.

@landrito -- friendly ping

Sorry looking over it right now!

ping


[BUG] Unable to server a fileserver with hauler store serve

Environmental Info:

N/A

Hauler Version:
zackbradys@Zacks-MBP Downloads % hauler version
 __    __       ___       __    __   __       _______ .______
|  |  |  |     /   \     |  |  |  | |  |     |   ____||   _  \
|  |__|  |    /  ^  \    |  |  |  | |  |     |  |__   |  |_)  |
|   __   |   /  /_\  \   |  |  |  | |  |     |   __|  |      /
|  |  |  |  /  _____  \  |  `--'  | |  `----.|  |____ |  |\  \----.
|__|  |__| /__/     \__\  \______/  |_______||_______|| _| `._____|
hauler: Airgap Swiss Army Knife

GitVersion:    0.4.2
GitCommit:     f982f51
GitTreeState:  clean
BuildDate:     2023-12-19T18:10:07Z
GoVersion:     go1.21.5
Compiler:      gc
Platform:      darwin/arm64

System CPU architecture, OS, and Version:
Darwin Zacks-MacBook-Pro.local 23.2.0 Darwin Kernel Version 23.2.0: Wed Nov 15 21:53:18 PST 2023; root:xnu-10002.61.3~2/RELEASE_ARM64_T6000 arm64

Describe the bug:

In hauler store serve there is no option for registry or fileserver. It only shows the commands for the registry and you don't have the ability to use the fileserver. It looks like it never made it over from hauler serve.

Steps To Reproduce:
zackbradys@Zacks-MBP Downloads % hauler serve -h
*** WARNING: Deprecated Command ***
The 'serve' command is deprecated and will be removed in a future release of Hauler.

Usage:
  hauler serve [flags]
  hauler serve [command]

Available Commands:
  files       Start a fileserver
  registry    Start a registry

Flags:
  -h, --help   help for serve

Global Flags:
  -l, --log-level string    (default "info")

zackbradys@Zacks-MBP Downloads % hauler store serve -h
Expose the content of a local store through an OCI compliant server

Usage:
  hauler store serve [flags]

Flags:
  -c, --config string      Path to a config file, will override all other configs
  -d, --daemon             Toggle serving as a daemon
      --directory string   Directory to use for registry backend (defaults to '$PWD/registry') (default "registry")
  -h, --help               help for serve
  -p, --port int           Port to listen on (default 5000)

Global Flags:
      --cache string       Location of where to store cache data (defaults to $XDG_CACHE_DIR/hauler)
  -l, --log-level string    (default "info")
  -s, --store string       Location to create store at (default "store")

Expected behavior:

Ability to use hauler store serve registry for all OCI content and hauler store serve fileserver for all file content.

Actual behavior:

See previous comments

Additional context / logs:

N/A

PR for fileserver.  https://github.com/rancherfederal/hauler/pull/159

Will be included in the next release.


Helm Chart: Allow use of alternative values file from remote chart

Some helm charts include multiple value file options (example: https://github.com/istio/istio/tree/master/install/kubernetes/helm/istio). It would be valuable to be able to select a specific values file to use rather than the default. If a user were to download the preferred file and add it to a secret, it could become stale.

I don't think I understand what's going on with all those values files. How would you use them if you were just using the Helm command line tool?

Here's how I selected the values-production.yaml file for redis:
helm install stable/redis --values https://raw.githubusercontent.com/helm/charts/master/stable/redis/values-production.yaml

@squaremo another example:  helm install istio --name istio --values install/kubernetes/helm/istio/values-istio-demo.yaml --namespace istio-system

I'm all for making the Helm-operator more widely useful. I would ask this though: are you sure you want your deployed chart to depend on a resource that can change arbitrarily?

That's a fair question. The motivation here, though, is to use a "standard" package without having to worry about getting out-of-date if you pull your own copy in order to apply a different values file... I think there can be valid reasons to go either way.

It would be even better if helm allowed packaging multiple values files in the packaged and versioned chart, and then you could install the chart and specify -f values-production.yaml and it would look for a values file named that packaged with the chart. This gives an easy way for the creators of charts to provide several different default configurations.


Add ICD11 lex_exact alignments

Spreadsheet at: https://docs.google.com/spreadsheets/d/1WyyJwlubS9OYJl-zS6E03NNf6p2oDSA2du_CWa410RQ/edit?gid=849840827#gid=849840827

Closing - too many conflicts to address now


Toggle buttons in CSD expand header bar height

I've checked in gnome-tweaks. On any page where toggle buttons aren't found the header bar remains the same height. However, the extensions page does have a toggle button and the header bar increases in height by 4 or 5 pixels.
gnome settings also appears to have the same bug but to a lesser extent.

Thanks @SaucySauce. I did notice that but wasn't sure if anyone used the thicker theme. I'll take a look this weekend :+1:

I've just pushed an update that reduces the size of the sliders in all themes (should have done this a while ago). I'm no longer seeing the headerbar size change when switching between tabs in gnome-tweaks; let me know if it's fixed for you as well.

Sorry for the late reply, was fixing the wifi on Fedora 30. The new update fixed the bug. Thank you. Sorry if I'm being picky, I'm a stickler for detail.


Fix typo in troubleshooting guide

Fix LIBS to LIBGS
Thanks at @kilacoda for pointing it out.

Actually the RTD build did not really fail: https://readthedocs.org/api/v2/build/12251294.txt
copying static files... ... done
copying extra files... done
dumping search index in English (code: en)... done
dumping object inventory... done
build succeeded, 11 warnings.

The HTML pages are in _build/html.
Updating searchtools for Read the Docs search...```

Also, it would have been strange that these two single-letter changes could make the build fail.


Drop implicit dependencies from go.mod

As per title and similarly to the recent pkg changes.
/assign @dprotaso

/lgtm
/approve


Modified generateRandom() method to accommodate character length

Modified the generateRandom() method to accommodate providing character length, this will give more flexibility for specific character length scenarios.  The characterLength  parameter is optional and defaults to 12 max.

Hey @alome007 looks great, can you also add and update the tests to match the new argument that you have added?

sure thing! @prikeshsavla


buildContext attribute is relative to what?

Hi guys,
in the description we've got this:
buildContextBuild context | (Optional) Path to the build contextDefault value: **
So my question is - this path is relative to repo root / to Dockerfile or whatever else? Please make it clear in description.

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

ID: 0d9dbf88-7e55-d427-145e-d36b04fb197f
Version Independent ID: a3f30c00-817c-9c05-7a57-3f2bf618821e
Content: Docker task - Azure Pipelines
Content Source: docs/pipelines/tasks/build/docker.md
Product: devops
Technology: devops-cicd-tasks
GitHub Login: @azooinmyluggage
Microsoft Alias: atulmal

@VerdonTrigance Thanks for your question. We're looking into it as a doc enhancement. In the meantime, consider these resources:

Azure DevOps Services
Azure DevOps Support Bot
Azure DevOps on Stack Overflow


Add logging

There now should be a stream of data coming in to this channel. Try online at https://alignmentsearch.up.railway.app/ to test it out (I'm keeping our McGill team jam-version in sync for the moment since we haven't set up our deployment pipeline with stampy yet - once that happens I'll let it slide gracefully into the night.)
I feel like this closes #4, though there's probably further work to do here since we'd ideally like to have some posthumous way to view a full prompt (exact source chunks, history, etc). Just throwing it all in the mix as-is is trips discord's rate limit, and is a bit unwieldy to view.

Yes, I was about to respond to your message on Discord but it looks like you've already dealt with it here. I would say for the #ask-log channel, preferably B (questions and answers, no sources or context) but if rate-limiting is still an issue then C (just questions). And we'll still want full logging by some other mechanism.
As for the deployment pipeline, TJ (@tayler6000) offered to help, once he has a chance to familiarize himself with the repo. TJ has extensive experience doing that kind of stuff with Stampy and other AED projects. I can also switch chat.stampy.ai and chat.aisafety.info to point to this deployed project too.


Why python(2) instead of python3?

As the project is still relatively small, it is easier to port. Why start in python2 if the '__future__' is already here?

Worry not, my friend. We're using Python 3. In the CONTRIBUTING.md when we create the environment from Conda, we especify the version 3 ; )

Oh, great! But shouldn't the shebang line specify python3 as the interpreter? (on line 1 of the setup file: #!/usr/bin/env python I believe it should be #!/usr/bin/env python3)
In my system, specifying only python ends up in python2.

Hum… reopening the Issue!
@irio is this a problem? We could change the way we call setup in the instructions (I guess that's the file you're talking about, @Bilkow, am I right), because shebangs really rely on a very unstable stack: how each of us set up our own computers. Maybe say that the recommended way is to run python setup.py with Python 3.
Or (re)write/(re)check setup in a way that is compatible with Python 2 and 3…

Or… /usr/bin/env python within the project environment created (check CONTRIBUTING.md) will always be Python 3? Not sure… gonna check that later (but if anyone knows the answer, save me some minutes).

@cuducos the project environment will always be Python 3
The python path will be like: /home/user/anaconda/envs/serenata_de_amor/python which is Python 3, but I don't know if the setup script will use Python from Anaconda env or #!/usr/bin/env python

I don't know if the setup script will use Python from Anaconda env or #!/usr/bin/env python

That's my doubt too.


Podspec platform is wrong

The SugarRecord Readme said require iOS 7+, but podspec's platform is iOS 8.

Right, I'll change @iblacksun

@pepibumur thanks.


Relabel unused columns to be unique.

Addresses the concern a couple API users have expressed about "unused" API columns being duplicated.

lgtm! thanks for hopping on this 🙏
It might be nice to have an API snapshot/test build with this to verify it, but I trust you've tested it thoroughly so no real need at all.
🚢 🚢

Yeah, I am pretty sure I manually tested this well enough but I'll kick off a snapshot run to sanity-check!


Update mux and demux

Hi. This PR updates the mux and demux modules and adds the following features:

Support multiple outstanding requests
Able to reach 1 request/cycle throughput (i.e. they can handle back-to-back requests without stalls)
Read and write channels now run independently (i.e., they can send data at the same time)

I have created a test program that can generates random axil transactions and random handshakings. Both mux and demux have passed the generated tests from there. Also, with these modules, I am now able to run ZynqParrot on Zedboard with Ethernet and PLIC located outside the top.v module.

Very cool! Can you commit your testbench here as well?

Fixed!


[FEATURE] Create PersistentTaskExtension interface

Is your feature request related to a problem?
Extension points (see https://github.com/opensearch-project/opensearch-sdk-java/issues/315) will be (optionally) implemented on Extensions. Eventually these points may need to be communicated to OpenSearch to be registered in the appropriate service or module.
Allowing extensions to inherit from appropriate interfaces depending on their type will match the current Plugin implementation.
What solution would you like?
Add a new interface PersistentTaskExtension with default implementations for extension points matching PersistentTaskPlugin.java.

Hello @dbwiddis, I would like to take this issue

#562

Done in #562


Config file location should follow "modern" specifications

Writing dotfiles into the root of user's home dir is not really a thing anymore.
For linux, there's the XDG base directory specification. This would make the location by default something like ~/.config/aider/config.yml.  See https://gist.github.com/roalcantara/107ba66dfa3b9d023ac9329e639bc58c#file-xdg-cheat-sheet-md
On a mac ~/.config is probably better for a terminal app than going to the "correct" ~/Library/Application Support/aider/config.yaml. Tools like git, github copilot, gh cli, shells, neovim and many others use it or at least will make a symlink from there to Library.
On windows %APPDATA%\Aider\config.yaml is probably good.

Thanks for trying aider and reporting this issue.
FYI, you can also store the aider config yaml file in the root of your git working directory.

The input and chat history and tag files should also be stored in (I think) $XDG_CACHE_HOME/aider/{repo-name}


[WIP] Add split match

Adds the Split and Match functionality into the topologymodeler

Start and end date:  2018-04-13

Contributor:  Thommy Zelenik, @zelenikty

Supervisor: Lukas Harzenetter, @lharzenetter Karoline Saatkamp, @saatkamp

[x] Ensure that you followed http://eclipse.github.io/winery/dev/ToolChain#github---prepare-pull-request.

[x] Branch name checked. That means, the branch name starts with thesis/, fix/, ...

[ ] Ensure that the commit message is a good commit message

[ ] Ensure to use auto format in all files

[ ] Change in CHANGELOG.md described

[ ] Tests created for changes

[ ] Screenshots added (for UI changes)

Follow up at https://github.com/eclipse/winery/pull/240.


Improve few things for v6

[x] Change react-native.js to native.js.
[x] Add more keywords.
[x] Move plugins and its friends to dependencies.
[x] Improve documents

https://github.com/preco21/eslint-config-prev/commit/6f8143aff222da4ec8a8ae7d5f6e1183543f724c


Fix spacing between error text and component

Pull Request
🤨 Rationale
Fixes #1845
👩💻 Implementation
Moved the error text on controls down 2px to create a 2px margin between the bottom of a control and the error text.
🧪 Testing
Manually tested in storybook and verified that the error text is no longer visible between the select/combobox and the dropdown.
✅ Checklist

[ ] I have updated the project documentation to reflect my changes or determined no changes are needed.

@m-akinc, can you buddy this for me?


Waiting to send SMSG_SET_PROFICIENCY (10026).

Sometimes I get stuck on loading screen while logging in with a repeating message in the console that says:
22:42:34 |  Network | WorldClient     | C<P S | Waiting to send SMSG_SET_PROFICIENCY (10026).
22:42:34 |  Network | WorldClient     | C<P S | Waiting to send SMSG_SET_PROFICIENCY (10026).
22:42:34 |  Network | WorldClient     | C<P S | Waiting to send SMSG_SET_PROFICIENCY (10026).
22:42:34 |  Network | WorldClient     | C<P S | Waiting to send SMSG_SET_PROFICIENCY (10026).
22:42:34 |  Network | WorldClient     | C<P S | Waiting to send SMSG_SET_PROFICIENCY (10026).
22:42:34 |  Network | WorldClient     | C<P S | Waiting to send SMSG_SET_PROFICIENCY (10026).
22:42:34 |  Network | WorldClient     | C<P S | Waiting to send SMSG_SET_PROFICIENCY (10026).
This appears to have started after I installed an addon called Aux: https://www.curseforge.com/wow/addons/aux/files/all?filter-game-version=2020709689%3A8958
When the issue happens, the only way to fix it is to close game and console, and relaunch.

That's a known random bug of HermesProxy itself, you have to restart the launcher.
It most likely has nothing to do with your addons.


Redirect prod subdomains to fightpandemics.com

We want to redirect any random subdomain like thisobviouslyisntarealsubdomain.fightpandemics.com and www.fightpandemics.com to fightpandemics.com.

Oh weird, this is already resolved, wonder why it did not autoclose 🤔


DecalMap: Fix the isReady function

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

Snapshot stored with reference name:
refs/pull/13855/merge
Test environment:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/13855/merge/index.html
To test a playground add it to the URL, for example:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/13855/merge/index.html#WGZLGJ#4600
Links to test babylon tools with this snapshot:
https://playground.babylonjs.com/?snapshot=refs/pull/13855/merge
https://sandbox.babylonjs.com/?snapshot=refs/pull/13855/merge
https://gui.babylonjs.com/?snapshot=refs/pull/13855/merge
https://nme.babylonjs.com/?snapshot=refs/pull/13855/merge
To test the snapshot in the playground with a playground ID add it after the snapshot query string:
https://playground.babylonjs.com/?snapshot=refs/pull/13855/merge#BCU1XR#0


Update bwc test from 2.10 to 2.11

Description
Update bwc test from 2.10 to 2.11
Issues Resolved
N/A
Check List

[X] New functionality includes testing.

[X] All tests pass

[X] New functionality has been documented.

[X] New functionality has javadoc added

[X] Commits are signed as per the DCO using --signoff

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

@heemin32 lets get @ryanbogan changes also ported to main after that all BWC tests should be successful

@heemin32 lets get @ryanbogan changes also ported to main after that all BWC tests should be successful

His change is already in the main. Not sure why it is still failing.

@heemin32 lets get @ryanbogan changes also ported to main after that all BWC tests should be successful

His change is already in the main. Not sure why it is still failing.

This can be a new issue.


Tailwind cli is not processing css

I am using tailwincss ver 0.6.5 and node ver10.7.0. I have followed the installation guide and trying to process my css with tailwind cli but cli is not processing my css just outputting my own css file as it is. I am using these steps.
./node_modules/.bin/tailwind init tailwind.js
I am using the sample css from the guide with tailwind directives to create my css file tailwind.css
then using the following command to process my css.
./node_modules/.bin/tailwind build tailwind.css -c tailwind.js -o devstyles.css
tailwind build command is just copying tailwind.css to devstyles.css and not processing tailwind.css to generate styles.

I've just created a repository to try and replicate this but can't:
https://github.com/adamwathan/tailwind-cli-test
When I run ./node_modules/.bin/tailwind build tailwind.css -c tailwind.js -o devstyles.css from the root of that project, devstyles.css is created with all the replaced CSS like you see in the committed file.
Can you share a repository that reproduces the issue so I can try and troubleshoot what's different?

Cli was working fine in the past, may be not working with Node v 10. Here is the repo https://github.com/ansarizafar/tailwindcss

Ah ok I see the issue, you are trying to use postcss-import as well. The Tailwind CLI doesn't pick up your postcss.config.js file or anything like that, it only does Tailwind's processing.
If you want to use full-blown PostCSS and include other plugins and stuff, you need to use a proper build tool that supports PostCSS like Webpack, Gulp, etc.

Sent you a PR which shows you how to do what you want using postcss-cli:
https://github.com/ansarizafar/tailwindcss/pull/1

@adamwathan Thanks for the help. Its working now.


Lazysizes blocking flexslider and owlcarousel when included in page loading

Hi,
Using the latest version of lazysizes my website users are experiencing all carousels being blocked from loading.
View problem on first load of link to our site!
For the purpose of this ticket I have disabled all lazyloading on the front page of the website. The file is literally just included in the head. I've tried including it via Cloudflare's CDN, same issue.
I've tried disabling initialization and initializing it after the carousel's load. When doing this method it stops working about every 15th page load.
Any help would be appreciated
flexslider first image (hacked to display, should slide and show controls)

Owl Carousel items not displaying:

Refreshing the page 1x will show all missing items

Issue unrelated to lazysizes


make gae module optional

enable gae module only if GAE_INSTANCE environment variable is set.
This could perhaps be renamed to gcp, but such renaming should probably be done separately once the environment variable that identifies all GCP environments is defined.

This PR needs to be updated to used either https://github.com/GoogleCloudPlatform/openjdk-runtime/pull/73 or https://github.com/GoogleCloudPlatform/openjdk-runtime/pull/74 when one of them is merged.

@meltsufin updated this PR to use the update PR previously submitted and implemented the JETTY_MODULES_ENABLED stuff we have discussed (as was kind of related to how gcp module is turned on).

@meltsufin I added unit tests for all the functionality in the setup script... and even found a bug in the unpacking logic!

@aslo Can you take a look at the structure tests @gregw added?

Sure! Tests look good, but I think there's an issue with the use of the --workspace argument for the structure_tests local run. When the structure tests are run via Cloud Builder, the project root is automatically mounted at the /workspace directory in the container - I don't believe it's actually configurable.
So, in short, the workspace needs to refer to the project root - it would need to look like this:
https://github.com/GoogleCloudPlatform/jetty-runtime/compare/master-gae-optional...master-gae-optional--structure-test-config?expand=1

@meltsufin @aslo I cherry picked Alex's change into this PR.


Handle parallel queries

The PR (https://github.com/logstash-plugins/logstash-input-jdbc/pull/70) sets max_work_threads to 1 to prevent consistency issues - which means that the scheduler will not process parallel queries.  There are additional code changes in order to support parallel queries.  This ticket tracks parallel queries support as an enhancement request.

@talevy @suyograo I think this is a valuable enhancement to get in sooner rather than later. How difficult would this be to implement?

@acchen97 I will have to take a look at how other safely do this. With how the plugin works today, I see some ways users can shoot themselves in the foot.

+1

Hey @guyboertje, since you've worked on this plugin a bit, think you can take this investigation on? It is one of those things that maybe would be better handled by running two separate jdbc inputs in the pipeline


[VL] Fix broken memory limit used for Velox spilling (patch 2)

the previous one https://github.com/oap-project/gluten/pull/1356 doesn't fix the issue

Looks you just add a config, how it fix the spill limit?

It's to pass config spark.gluten.memory.task.offHeap.size.in.bytes to native code. Otherwise facebook::velox::memory::kMaxMemory will be used.
Some relevant C++ codes you can refer to:
https://github.com/oap-project/gluten/blob/0af5406edf7431e902532660ef46f662fafbe4f6/cpp/core/config/GlutenConfig.h#L30
https://github.com/oap-project/gluten/blob/b45967480068970960a30917092277e59bab41cf/cpp/velox/compute/VeloxBackend.cc#L56-L65


Support newer versions of dependencies

Newer versions of dependencies could also be supported. This would allow better integration with distribution native package managers as they normally only install the newest appropriate version. I have it running fine on Arch Linux with  requests 2.4.3 and markdown 2.5.
While at it, transitive dependencies could also be removed to clean up. Flask already pulls in itsdangerous, Werkzeug and Jinja, which in turn requires markupsafe.

Just fixed this locally. I didn't want to remove the transitive dependencies that the project is actually using, because a dependency's dependencies is an implementation detail that has no guarantee that they'll still be there in future versions.
Closing this, but thank you for

And that is just enough to simplify building the package for Arch Linux. Thank you.

Oh, awesome! Thank you! Glad that change helped.

FYI, I just released 3.1.0 with the unpinned dependencies.


Sublayer

We have subLayers
Yaml parsing

Recursive addition of sublayers to layers

Filtering layers, style paramater mixing, style paramater caching

Does a BFS layer graph traversal to determine appropriate style parameter for a feature.

NOTES:
Because of how unique set of layer match IDs are determined, this puts a cap on the number of layers in the scene file (64 aka 64 bit key for the cache).

Reviewing now

@tallytalwar You overwrote a commit I made, it was small so no big deal this time but do try to be careful when rewriting history

@blair1618 oops... so sorry about that :|.

The tile construction process is going to need some radical changes. Currently we have no way to change the base style from within a sublayer or even to use different data sources among top-level layers. I have some ideas on this that I can start implementing ASAP.
I think it might make the most sense to just merge these changes with the understanding that many things in here will be substantially altered soon.

@blair1618 I agree ... We have already discussed that this branch is not addressing such refactors.
I have comments in the code stating the limitations you mentioned above.
Also I am currently working on multiple datasource for the uber layer.

I am generally not a fan of rewriting history on any shared branches for
this reason. I've seen it cause confusion many times. I prefer merge
commits, they are not as pretty, but IMO more likely to "just work".
(I regularly alter history on local changes before pushing, or on a branch
only I am working on.)
On Monday, July 13, 2015, Varun<EMAIL_ADDRESS>wrote:

@blair1618 https://github.com/blair1618 oops... so sorry about that :|.
—
Reply to this email directly or view it on GitHub
https://github.com/tangrams/tangram-es/pull/166#issuecomment-121045866.

@bcamper I just learnt altering history so I was doing that a lot here, but I was the only one working on this branch, but unfortunately missed a small commit from Matt. Will take care of this in the future.

@tallytalwar right, the point is that such mistakes are much less likely if the mechanism that enables them isn't used in the first place.

Any more suggestions or improvements on this?
Good to be merged?


Not working with WoW 11.0 (TWW)

No overlay is shown on default raid frames. No errors thrown in bugsack.

Looks like the Blizz unit frames have changed in TWW. This will take some time to investigate.

I tested this with Raid Style unit frames in a follower dungeon and the Overshields are showing on the Raid Frames. Disabling the addon hides the overshields (just the normal glow).
Looks like it's working as expected. I'll update the version so you don't need to load outdated addons.

I'll re-check tomorrow. There might be something broken on the toon I used if that's the case.

Can confirm it's working fine now. I assume there was some issue on the character I initially tested on.


ZMap build is requiring libnuma-dev

This issue supersedes this pull request: https://github.com/zmap/zmap/pull/446. This was originally reported by @azet.
One some systems, ZMap incidentally tries to build with with PF_RING support. I believe that PF_RING does require libnuma, but the default should not be trying to build with PF_RING support.
I'm specifically noting:
[ 20%] Building C object src/CMakeFiles/ztests.dir/socket-pfring.c.o
[ 20%] Building C object src/CMakeFiles/ztests.dir/recv-pfring.c.o
But if you look at the CMake configuration, you'll see
Handle various versions of socket
if(WITH_PFRING)
set(SOURCES ${SOURCES} socket-pfring.c)
set(ZTESTSOURCES ${ZTESTSOURCES} socket-pfring.c)
elseif (APPLE OR BSD)
set(SOURCES ${SOURCES} socket-bsd.c)
set(ZTESTSOURCES ${ZTESTSOURCES} socket-bsd.c)
else()
set(SOURCES ${SOURCES} socket-linux.c)
set(ZTESTSOURCES ${ZTESTSOURCES} socket-linux.c)
endif()
So I think this issue should really be: Why is @azet's system think WITH_PFRING is set when it's not.
@azet just to confirm that this isn't something leftover, can you try to clone to a fresh directory and rebuild and see if you're trying to build with PF_RING support?

ZMap incidentally tries to build with with PF_RING support

This wasn't what I was reporting! I was building with PF_RING ZeroCache support on purpose. I don't think ZMap will build without the special cmake flags set. I may be missing something?

OK. Got it. Unfortunately, this is contrary to what you posted in the issue :) :
azet@scan-sha2017:~/software/zmap/v2.1.1$ cmake .
-- Checking for module 'json-c'
--   Found json-c, version 0.12.1
-- Default ZMap configuration file location is /etc/zmap
-- Checking if blacklist.conf exists there...
-- Checking if zmap.conf exists there...
-- Configuring done
-- Generating done
-- Build files have been written to: /home/azet/software/zmap/v2.1.1

If this is indeed the problem, then we just need to add this as a documented dependency for 10gigE scanning at: https://github.com/zmap/zmap/blob/master/10gigE.md

@zakird
Verified:
azet@scan-sha2017:~/software$ git clone https://github.com/zmap/zmap zmap-2
Cloning into 'zmap-2'...
remote: Counting objects: 5880, done.
remote: Compressing objects: 100% (53/53), done.
remote: Total 5880 (delta 48), reused 15 (delta 8), pack-reused 5819
Receiving objects: 100% (5880/5880), 5.53 MiB | 5.58 MiB/s, done.
Resolving deltas: 100% (4135/4135), done.
azet@scan-sha2017:~/software$ cd zmap-2/
azet@scan-sha2017:~/software/zmap-2$ cmake .
-- The C compiler identification is GNU 6.4.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Found PkgConfig: /usr/bin/pkg-config (found version "0.29")
-- Checking for module 'json-c'
--   Found json-c, version 0.12.1
-- Default ZMap configuration file location is /etc/zmap
-- Checking if blacklist.conf exists there...
CMake Warning at CMakeLists.txt:156 (message):
  Existing configuration file detected at /etc/zmap/blacklist.conf,
  blacklist.conf from sources will NOT be installed.  Please check and
  install manually!

-- Checking if zmap.conf exists there...
CMake Warning at CMakeLists.txt:156 (message):
  Existing configuration file detected at /etc/zmap/zmap.conf, zmap.conf from
  sources will NOT be installed.  Please check and install manually!

-- Configuring done
-- Generating done
-- Build files have been written to: /home/azet/software/zmap-2
azet@scan-sha2017:~/software/zmap-2$ make -j4
Scanning dependencies of target git_versioning
Scanning dependencies of target zmaplib
[  1%] Building C object lib/CMakeFiles/zmaplib.dir/blacklist.c.o
[  1%] Building C object lib/CMakeFiles/zmaplib.dir/constraint.c.o
[  1%] Built target git_versioning
[  2%] Building C object lib/CMakeFiles/zmaplib.dir/logger.c.o
[  3%] Building C object lib/CMakeFiles/zmaplib.dir/pbm.c.o
[  4%] Building C object lib/CMakeFiles/zmaplib.dir/rijndael-alg-fst.c.o
[  5%] Building C object lib/CMakeFiles/zmaplib.dir/random.c.o
[  6%] Building C object lib/CMakeFiles/zmaplib.dir/xalloc.c.o
[  7%] Building C object lib/CMakeFiles/zmaplib.dir/lockfd.c.o
[  8%] Building C object lib/CMakeFiles/zmaplib.dir/util.c.o
[  9%] Building C object lib/CMakeFiles/zmaplib.dir/queue.c.o
[ 10%] Building C object lib/CMakeFiles/zmaplib.dir/csv.c.o
[ 11%] Linking C static library libzmaplib.a
[ 11%] Built target zmaplib
[ 11%] Generating zbopt.h
[ 12%] Generating parser.c
[ 13%] Generating parser.c
[ 14%] Generating zitopt.h
[ 16%] Generating zopt.h
[ 16%] Generating ztopt.h
Scanning dependencies of target zblacklist
[ 17%] Generating lexer.c
Scanning dependencies of target ziterate
[ 18%] Generating lexer.c
[ 19%] Building C object src/CMakeFiles/zblacklist.dir/zblacklist.c.o
[ 20%] Building C object src/CMakeFiles/ziterate.dir/aesrand.c.o
Scanning dependencies of target zmap
[ 21%] Building C object src/CMakeFiles/ziterate.dir/cyclic.c.o
Scanning dependencies of target ztests
[ 22%] Building C object src/CMakeFiles/zmap.dir/aesrand.c.o
[ 24%] Building C object src/CMakeFiles/ztests.dir/aesrand.c.o
[ 24%] Building C object src/CMakeFiles/zblacklist.dir/zbopt_compat.c.o
In file included from /home/azet/software/zmap-2/src/zbopt_compat.c:15:0:
/home/azet/software/zmap-2/src/zbopt.c: In function 'cmdline_parser_internal':
/home/azet/software/zmap-2/src/zbopt.c:505:7: warning: variable 'check_required' set but not used [-Wunused-but-set-variable]
   int check_required;
       ^~~~~~~~~~~~~~
[ 25%] Building C object src/CMakeFiles/zmap.dir/cyclic.c.o
[ 26%] Building C object src/CMakeFiles/ztests.dir/cyclic.c.o
[ 27%] Building C object src/CMakeFiles/ziterate.dir/iterator.c.o
[ 28%] Building C object src/CMakeFiles/zmap.dir/expression.c.o
[ 29%] Building C object src/CMakeFiles/ztests.dir/expression.c.o
[ 30%] Linking C executable zblacklist
[ 31%] Building C object src/CMakeFiles/ziterate.dir/shard.c.o
[ 32%] Building C object src/CMakeFiles/ztests.dir/fieldset.c.o
[ 33%] Building C object src/CMakeFiles/zmap.dir/fieldset.c.o
[ 33%] Built target zblacklist
[ 34%] Building C object src/CMakeFiles/zmap.dir/filter.c.o
[ 35%] Building C object src/CMakeFiles/ziterate.dir/state.c.o
[ 36%] Building C object src/CMakeFiles/ziterate.dir/validate.c.o
[ 37%] Building C object src/CMakeFiles/zmap.dir/get_gateway.c.o
[ 38%] Building C object src/CMakeFiles/ziterate.dir/zitopt_compat.c.o
In file included from /home/azet/software/zmap-2/src/zitopt_compat.c:15:0:
/home/azet/software/zmap-2/src/zitopt.c: In function 'cmdline_parser_internal':
/home/azet/software/zmap-2/src/zitopt.c:545:7: warning: variable 'check_require' set but not used [-Wunused-but-set-variable]
   int check_required;
       ^~~~~~~~~~~~~~
[ 39%] Building C object src/CMakeFiles/ziterate.dir/ziterate.c.o
[ 40%] Building C object src/CMakeFiles/ztests.dir/filter.c.o
[ 41%] Building C object src/CMakeFiles/ztests.dir/get_gateway.c.o
[ 42%] Building C object src/CMakeFiles/ztests.dir/iterator.c.o
[ 43%] Building C object src/CMakeFiles/zmap.dir/iterator.c.o
[ 43%] Linking C executable ziterate
[ 44%] Building C object src/CMakeFiles/zmap.dir/monitor.c.o
[ 45%] Generating topt.h
[ 46%] Building C object src/CMakeFiles/ztests.dir/monitor.c.o
Scanning dependencies of target ztee
[ 46%] Built target ziterate
[ 47%] Building C object src/CMakeFiles/ztee.dir/ztee.c.o
[ 48%] Building C object src/CMakeFiles/zmap.dir/recv.c.o
[ 48%] Building C object src/CMakeFiles/ztee.dir/topt_compat.c.o
[ 49%] Building C object src/CMakeFiles/zmap.dir/send.c.o
In file included from /home/azet/software/zmap-2/src/topt_compat.c:7:0:
/home/azet/software/zmap-2/src/topt.c: In function 'update_arg':
/home/azet/software/zmap-2/src/topt.c:397:9: warning: variable 'stop_char' set but not used [-Wunused-but-set-variable]
   char *stop_char = 0;
         ^~~~~~~~~
/home/azet/software/zmap-2/src/topt.c: In function 'cmdline_parser_internal':
/home/azet/software/zmap-2/src/topt.c:476:7: warning: variable 'check_required' set but not used [-Wunused-but-set-variable]
   int check_required;
       ^~~~~~~~~~~~~~
[ 50%] Building C object src/CMakeFiles/ztests.dir/recv.c.o
[ 50%] Building C object src/CMakeFiles/zmap.dir/shard.c.o
[ 50%] Building C object src/CMakeFiles/ztests.dir/send.c.o
[ 51%] Building C object src/CMakeFiles/ztests.dir/shard.c.o
[ 52%] Linking C executable ztee
[ 53%] Building C object src/CMakeFiles/zmap.dir/socket.c.o
[ 53%] Built target ztee
[ 54%] Building C object src/CMakeFiles/zmap.dir/state.c.o
[ 55%] Building C object src/CMakeFiles/zmap.dir/summary.c.o
[ 56%] Building C object src/CMakeFiles/ztests.dir/socket.c.o
[ 57%] Building C object src/CMakeFiles/zmap.dir/validate.c.o
[ 58%] Building C object src/CMakeFiles/zmap.dir/zmap.c.o
[ 59%] Building C object src/CMakeFiles/ztests.dir/state.c.o
[ 60%] Building C object src/CMakeFiles/ztests.dir/summary.c.o
[ 61%] Building C object src/CMakeFiles/ztests.dir/validate.c.o
[ 62%] Building C object src/CMakeFiles/ztests.dir/ztopt_compat.c.o
[ 63%] Building C object src/CMakeFiles/ztests.dir/probe_modules/module_icmp_echo.c.o
In file included from /home/azet/software/zmap-2/src/ztopt_compat.c:15:0:
/home/azet/software/zmap-2/src/ztopt.c: In function 'update_arg':
/home/azet/software/zmap-2/src/ztopt.c:345:15: warning: variable 'val' set but not used [-Wunused-but-set-variable]
   const char *val = value;
               ^~~
/home/azet/software/zmap-2/src/ztopt.c:344:9: warning: variable 'stop_char' set but not used [-Wunused-but-set-variable]
   char *stop_char = 0;
         ^~~~~~~~~
/home/azet/software/zmap-2/src/ztopt.c: In function 'cmdline_parser_internal':
/home/azet/software/zmap-2/src/ztopt.c:414:7: warning: variable 'check_required' set but not used [-Wunused-but-set-variable]
   int check_required;
       ^~~~~~~~~~~~~~
[ 64%] Building C object src/CMakeFiles/zmap.dir/zopt_compat.c.o
In file included from /home/azet/software/zmap-2/src/zopt_compat.c:15:0:
/home/azet/software/zmap-2/src/zopt.c: In function 'cmdline_parser_internal':
/home/azet/software/zmap-2/src/zopt.c:854:7: warning: variable 'check_required' set but not used [-Wunused-but-set-variable]
   int check_required;
       ^~~~~~~~~~~~~~
[ 65%] Building C object src/CMakeFiles/zmap.dir/lexer.c.o
/home/azet/software/zmap-2/src/lexer.c: In function 'yy_get_next_buffer':
/home/azet/software/zmap-2/src/lexer.c:586:18: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
   for ( n = 0; n < max_size && \
                  ^
/home/azet/software/zmap-2/src/lexer.c:1060:3: note: in expansion of macro 'YY_INPUT'
   YY_INPUT( (&YY_CURRENT_BUFFER_LVALUE->yy_ch_buf[number_to_move]),
   ^~~~~~~~
[ 66%] Building C object src/CMakeFiles/zmap.dir/parser.c.o
[ 67%] Building C object src/CMakeFiles/ztests.dir/probe_modules/module_icmp_echo_time.c.o
[ 68%] Building C object src/CMakeFiles/ztests.dir/probe_modules/module_tcp_synscan.c.o
[ 69%] Building C object src/CMakeFiles/zmap.dir/probe_modules/module_icmp_echo.c.o
[ 70%] Building C object src/CMakeFiles/ztests.dir/probe_modules/module_udp.c.o
[ 71%] Building C object src/CMakeFiles/ztests.dir/probe_modules/module_tcp_synackscan.c.o
[ 72%] Building C object src/CMakeFiles/ztests.dir/probe_modules/packet.c.o
[ 73%] Building C object src/CMakeFiles/zmap.dir/probe_modules/module_icmp_echo_time.c.o
[ 74%] Building C object src/CMakeFiles/zmap.dir/probe_modules/module_tcp_synscan.c.o
[ 75%] Building C object src/CMakeFiles/zmap.dir/probe_modules/module_tcp_synackscan.c.o
[ 75%] Building C object src/CMakeFiles/ztests.dir/probe_modules/probe_modules.c.o
[ 75%] Building C object src/CMakeFiles/zmap.dir/probe_modules/module_udp.c.o
[ 76%] Building C object src/CMakeFiles/zmap.dir/probe_modules/packet.c.o
[ 77%] Building C object src/CMakeFiles/ztests.dir/probe_modules/module_ntp.c.o
[ 78%] Building C object src/CMakeFiles/zmap.dir/probe_modules/probe_modules.c.o
[ 79%] Building C object src/CMakeFiles/zmap.dir/probe_modules/module_ntp.c.o
[ 80%] Building C object src/CMakeFiles/zmap.dir/probe_modules/module_upnp.c.o
[ 81%] Building C object src/CMakeFiles/ztests.dir/probe_modules/module_upnp.c.o
[ 82%] Building C object src/CMakeFiles/zmap.dir/probe_modules/module_dns.c.o
[ 83%] Building C object src/CMakeFiles/ztests.dir/probe_modules/module_dns.c.o
[ 84%] Building C object src/CMakeFiles/zmap.dir/probe_modules/module_bacnet.c.o
[ 85%] Building C object src/CMakeFiles/ztests.dir/probe_modules/module_bacnet.c.o
[ 86%] Building C object src/CMakeFiles/ztests.dir/output_modules/module_csv.c.o
[ 87%] Building C object src/CMakeFiles/ztests.dir/output_modules/module_json.c.o
/home/azet/software/zmap-2/src/probe_modules/module_dns.c: In function 'dns_global_initialize':
/home/azet/software/zmap-2/src/probe_modules/module_dns.c:527:12: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector]
 static int dns_global_initialize(struct state_conf *conf)
            ^~~~~~~~~~~~~~~~~~~~~
/home/azet/software/zmap-2/src/probe_modules/module_dns.c: In function 'dns_global_initialize':
/home/azet/software/zmap-2/src/probe_modules/module_dns.c:527:12: warning: stack protector not protecting local variables: variable length buffer [-Wstack-protector]
 static int dns_global_initialize(struct state_conf *conf)
            ^~~~~~~~~~~~~~~~~~~~~
[ 88%] Building C object src/CMakeFiles/zmap.dir/output_modules/module_csv.c.o
[ 89%] Building C object src/CMakeFiles/zmap.dir/output_modules/module_json.c.o
[ 90%] Building C object src/CMakeFiles/ztests.dir/output_modules/output_modules.c.o
[ 91%] Building C object src/CMakeFiles/ztests.dir/tests/test_harness.c.o
[ 92%] Building C object src/CMakeFiles/zmap.dir/socket-linux.c.o
[ 93%] Building C object src/CMakeFiles/zmap.dir/output_modules/output_modules.c.o
[ 94%] Building C object src/CMakeFiles/zmap.dir/recv-pcap.c.o
[ 95%] Building C object src/CMakeFiles/ztests.dir/lexer.c.o
[ 96%] Building C object src/CMakeFiles/ztests.dir/socket-linux.c.o
/home/azet/software/zmap-2/src/lexer.c: In function 'yy_get_next_buffer':
/home/azet/software/zmap-2/src/lexer.c:586:18: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
   for ( n = 0; n < max_size && \
                  ^
/home/azet/software/zmap-2/src/lexer.c:1060:3: note: in expansion of macro 'YY_INPUT'
   YY_INPUT( (&YY_CURRENT_BUFFER_LVALUE->yy_ch_buf[number_to_move]),
   ^~~~~~~~
[ 97%] Building C object src/CMakeFiles/ztests.dir/parser.c.o
[ 98%] Building C object src/CMakeFiles/ztests.dir/recv-pcap.c.o
[ 99%] Linking C executable zmap
[ 99%] Built target zmap
[100%] Linking C executable ztests
[100%] Built target ztests
azet@scan-sha2017:~/software/zmap-2$ dpkg -l libnuma-dev
dpkg-query: no packages found matching libnuma-dev
azet@scan-sha2017:~/software/zmap-2$

Unfortunately, this is contrary to what you posted in the issue :) :

Well, yes and no (it was very late already). So I was trying to re-build without 10GE support afterwards, but running cmake like for a usual installation was using the previous options (I think because of the cmake cache, and no proper cmake clean command).

If you want to start over, your best bet is going to be something like running git clean -dfx to take care of old CMake files. CMake doesn't have a great clean option, but this would have been the source of your problems.

This drives me nuts about cmake. It might be good idea to include a shell script in the repo that does the right thing given that running git clean isn't very reasoanble.

@zakird

If you want to start over, your best bet is going to be something like running git clean -dfx to take care of old CMake files. CMake doesn't have a great clean option, but this would have been the source of your problems.

Yea, this is what I did in the end. Well, rm -rf zmap/ && git clone .. is what I did. :)
Why are you depending on cmake anyway? I don't see an urgent reason to use it for the build process here. In my experiencecmake causes more troubles than it solves (especially when used with [poor or old] scientific software, your project - of course - excluded)..

OS distribution. We don't love it, but it seems to make the folks who distribute ZMap much happier, and we want to make their lives as easy as possible.

@zakird

This drives me nuts about cmake. It might be good idea to include a shell script in the repo that does the right thing given that running git clean isn't very reasoanble.

Many projects ship a simple shell or bash script called bootstrap that takes care of initial bootstrapping, checking for missing dependencies et cetera. Maybe that's an option for developers trying to build from source?

Realistically, almost everyone should be installing this through a package manager not building from source. We don't particularly want to be encouraging folks to be installing from source unless they're developers, in which case, having strong and correct documentation seems appropriate.

@zakird
Sure, and that's what your README / Install documents say. I totally agree that distro packages are the best way to go. But some people will need to build from source (e.g. for fixing bugs, improving parts of the code or benchmarking/testing as in my case).

I added documentation to 10GigE in commit 624e19d.

@azet Yep, absolutely agree.
Out of curiosity, were you able to get 10gigE scanning working? Given the the large packet drop at destination networks seen when performing seen doing scans >3gbps, we've somewhat neglected the 10gigE scanning portion of ZMap the last few years.

We'll I'm dependent on hardware from other people and a quite spontaneous (i.e. non-datacenter) networking / NOC at sha2017.org - the server isn't mine and I had little time for network tuning nor any influence on the 10GE swithes, BGP info etc.
I'm currently having an issue with the specific Intel card we've borrowed and PF_RING zerocopy kernel modules, in addition, the server only has 8GB of RAM (for ~20 scans in parallel), a single 8core Xeon E5v3 @ 3.2GHZ and no out of band management. I'm doing my best, but this isn't what I'd call a proper lab setup nor would I usually benchmark in such an environment. But we've got a lot of free upstream bandwidth, so why not grab as much as we can as best as we can improvise on site? People came up with cool ideas here out of the blue. I'm also scanning iWARP, RoCEv2 and SCTP for the first time.
see:

https://gist.github.com/azet/54862407b7af1c2813e590ead83f7553
https://wiki.sha2017.org/index.php?title=Internet-wide_Scanning
scan-sha2017.external.meta.southbound.io:8080 (public:guest)

If you've got any ideas and want to try them out send me a ssh public key to<EMAIL_ADDRESS>and a submission proposal (which we'll accept right away from you guys anyways, it's intended for people with little to no experience in internet measurement). Attribution and data-sets go to the original authors.
We've also a few custom scans I cannot tell much about at the moment that we'd like to re-run or test.


Build errors on Mac

Darwin Piotrs-MacBook-Pro.local 19.6.0 Darwin Kernel Version 19.6.0: Thu Jun 18 20:49:00 PDT 2020; root:xnu-6153.141.1~1/RELEASE_X86_64 x86_6
Makefile.am:16: but option 'subdir-objects' is disabled
Makefile.am: installing './depcomp'
/usr/local/Cellar/automake/1.16.2_1/share/automake-1.16/am/depend2.am: error: am__fastdepCC does not appear in AM_CONDITIONAL
/usr/local/Cellar/automake/1.16.2_1/share/automake-1.16/am/depend2.am:   The usual way to define 'am__fastdepCC' is to add 'AC_PROG_CC'
/usr/local/Cellar/automake/1.16.2_1/share/automake-1.16/am/depend2.am:   to 'configure.ac' and run 'aclocal' and 'autoconf' again
/usr/local/Cellar/automake/1.16.2_1/share/automake-1.16/am/depend2.am: error: AMDEP does not appear in AM_CONDITIONAL
/usr/local/Cellar/automake/1.16.2_1/share/automake-1.16/am/depend2.am:   The usual way to define 'AMDEP' is to add one of the compiler tests
/usr/local/Cellar/automake/1.16.2_1/share/automake-1.16/am/depend2.am:     AC_PROG_CC, AC_PROG_CXX, AC_PROG_OBJC, AC_PROG_OBJCXX,
/usr/local/Cellar/automake/1.16.2_1/share/automake-1.16/am/depend2.am:     AM_PROG_AS, AM_PROG_GCJ, AM_PROG_UPC
/usr/local/Cellar/automake/1.16.2_1/share/automake-1.16/am/depend2.am:   to 'configure.ac' and run 'aclocal' and 'autoconf' again
Makefile.am: error: C source seen but 'CC' is undefined
Makefile.am:   The usual way to define 'CC' is to add 'AC_PROG_CC'
Makefile.am:   to 'configure.ac' and run 'autoconf' again.

Fixed by running all steps, deps, bootstrap, configure, make. Updated readme with that: https://github.com/signalwire/libstirshaken/pull/51/commits/49e029e509a63e64cc92a64754e749a5dfbce1a7


Ollam build error wih  CUDA on Jetson Orin  (CUDA v12.6)

What is the issue?
Error: llama runner process has terminated: CUDA error: the provided PTX was compiled with an unsupported toolchain.
current device: 0, in function ggml_cuda_compute_forward at /ollama/llm/llama.cpp/ggml/src/ggml-cuda.cu:2326
err
/ollama/llm/llama.cpp/ggml/src/ggml-cuda.cu:102: CUDA error
CUDA version 12.6.68
OS
Linux
GPU
Nvidia
CPU
Other
Ollama version
0.3.11

Dup of #2408 - we're working towards supporting this in the official builds, but until then, you can build from source locally and it should work.  The CUDA libraries we link against in our arm builds are for servers with discrete GPUs which unfortunately are incompatible with Jetsons.


Modification proposal. Do you think can be merged to your origin branch?

Modifications on library:

Fixed CS5490::calibrate - |= vs &= on bitwise operations

Added /RESET pin management (constructor overloading)

Added not blocking register reading with check on operation result

Added internal voltage reference checkInternalVoltageReference (according to "Errata: CS5490 Rev B2 Silicon (Mar'13) - Erratum 2 "On chip reference reset state")

Added sendCalibrationCommand method (with no settle time delay)

Added some not fundamental methods

Enriched "keywords.txt"

Modification on examples:

Added "CS5490_AC_Current_Gain_Tuning_demo.ino" example - a practical application built on CDB5490U evaluation board for sensing on AC line with current gain calibration

First, I'll thank you a lot for the proposal.

Fixed CS5490::calibrate - |= vs &= on bitwise operations

As you may have notice by fixing this. I could not test the calibration methods.
There are many methods and code that I can't do many tests. I'm reading everything to understand what you made, but I'll trust your tests

Added /RESET pin management (constructor overloading)
Enriched "keywords.txt"
Added not blocking register reading with check on operation result

Nice changes.

Added "CS5490_AC_Current_Gain_Tuning_demo.ino" example - a practical application built on CDB5490U evaluation board for sensing on AC line with current gain calibration

I still don't like this kind of operation like the code below, but I have no other ideas. Arduino unfortunately don't support try..catch operations :/
  double rmsV = line.getRmsV();
  if (!line.isLastReadingOperationSucceeded()) registerReadingOperationIsOK = false;
  double freq = line.getFreq();

I'll merge everything and make some other changes before next release. I just need some time.
Thanks again

It's a pleasure to contribute your project!
I can assure all is properly working here on my testbench. In every case I'll send you new pull request in case some bug to fix will arise (together with the related fixes, naturally!).

I still don't like this kind of operation like the code below, but I have no other ideas. Arduino unfortunately don't support try..catch operations :/

 double rmsV = line.getRmsV();
  if (!line.isLastReadingOperationSucceeded()) registerReadingOperationIsOK = false;
  double freq = line.getFreq();

Yes, that was just a "poor programmer"'s solution in order not to modify your base code ;-)
A cleaner way to write the code could be something as what follow, by defining methods that get a reference to the output parameter (Arduino staff advices not to use pointers, because error prones) and return the result of the operation (i.e. a bool, despite I know Arduino staff deprecates the use of boolean variables):
bool getRmsV(double &retVal); // method declaration in header file
and use it as follow:
double rmsV; if(line.getRmsV(&rmsV)) {         // reading of the rmsV succeeded --> perform operations on it } else {         // reading operation failed... --> retry or in general handle the exception (catch) action }

I can assure all is properly working here on my testbench. In every case I'll send you new pull request in case some bug to fix will arise (together with the related fixes, naturally!).

Great!
I had an idea. What about something like this:
Removing this line from CS5490::read()
  this->_readOperationResult = true;

Then adding another method like
CS5490::resolve(){
  this->hardwareReset(void);
  this->_readOperationResult = true;
}

You do similar in your code. It also gives the possibility to not use the operation result boolean. And you can check whether you want.

Hi Tiago,
ok for the "resolve" method. It could be useful but consider that a reset operation will apply all the default values to the internal registers set --> another setup will be necessary.
It's not so clear to me how you would use the modified code... could you please me send an usage example together with the modified "CS5490::read()" ?
Thank you!

a reset operation will apply all the default values to the internal registers set --> another setup will be necessary.
True. another setup means calling CS5490_SendConfiguration() again?

I think once we don't have CS5490::sendConfiguration() yet, we can use as follows:
Before:
double PF = line.getPF();
if (!line.isLastReadingOperationSucceeded()) registerReadingOperationIsOK = false;
uint32_t Igain = line.readReg(16, 33);
if (!line.isLastReadingOperationSucceeded()) registerReadingOperationIsOK = false;
if(registerReadingOperationIsOK)
{
  //Do something
}
else
{
   Serial.println("Critical registes checksum error - CS5490 hardware reset required!");
   resetRequired = true;
}
if(resetRequired)
{
  resetRequired = false;
  measureErrorDetectionCounter = 10;
  communicationMaxRetries = 5;
  line.resolve();
  CS5490_SendConfiguration();
  Serial.println("RESET PERFORMED");
}

After adding resolve method
The new methods:
void CS5490::read(int page, int address){

	unsigned long startMillis;

	this->clearSerialBuffer();

	uint8_t buffer;
	//Select page and address
	if(this->selectedPage != page){
		buffer = (pageByte | (uint8_t)page);
		cSerial->write(buffer);
		this->selectedPage = page;
	}
	buffer = (readByte | (uint8_t)address);
	cSerial->write(buffer);

	startMillis = millis();
	//Wait for 3 bytes to arrive
	while( (cSerial->available() < 3) && ( (millis()-startMillis) < 500));
	if(cSerial->available() >= 3)
	{
		for(int i=0; i<3; i++){
			data[i] = cSerial->read();
		}
                // this->_readOperationResult = true; // (Removing this line)
	}
	else
	{
		this->_readOperationResult = false;
	}

	this->clearSerialBuffer();
}

CS5490::resolve(){
  this->hardwareReset(void);
  this->_readOperationResult = true;
  // this->sendConfiguration(); //Future method?
}

The Example:
double PF = line.getPF();
uint32_t Igain = line.readReg(16, 33);
if(line.isLastReadingOperationSucceeded())
{
  //Do something
}
else
{
  resetRequired = true;
}
if(resetRequired)
{
  resetRequired = false;
  measureErrorDetectionCounter = 10;
  communicationMaxRetries = 5;
  line.resolve();
  CS5490_SendConfiguration();
  Serial.println("RESET PERFORMED");
}

This avoids multiple "if (!line.isLastReadingOperationSucceeded()) registerReadingOperationIsOK = false;" operations.

Hi Tiago,
crystalline explaination: for me it's OK.
Forget the "CS5490::sendConfiguration()" function or  other callback schemes: simplicity is the best approach and is the aim of Arduino.
I've just committed the modified files (tested on my bench).
I changed "isLastReadingOperationSucceeded" into "areLastReadingOperationsSucceeded" because the method now check a cumulative result of the communication between two line.resolve() calls, in general (take a look to my comments over both the "resolve" and "areLastReadingOperationsSucceeded" methods in teh .cpp).
Let me know if now is ok.
Thank you,
Maurizio

Forget the "CS5490::sendConfiguration()" function or other callback schemes: simplicity is the best approach and is the aim of Arduino.

True. That's also why we're trying to avoid pointers, etc...
Your request is good to go now.

Thank you for merging Tiago!


DISREGARD - Entities fail to load - Unavailable

Problem/Motivation

All uptime kuma entities fail to load. State is Unavailable

Expected behavior

Uptime Kuma entities expected to load and reflect proper state of associated uptime kuma entry

Actual behavior

All uptime entities failed to load after updating to Home Assistant 2023.3.1. Updating to 2023.3.2 did not resolve the issue.

Steps to reproduce

On startup, Uptime Kuma entities fail to load. However, uptime kuma is accessible via web UI and entities/data appear normal there. Logs show:

2023-03-08 16:21:37.616 ERROR (SyncWorker_0) [homeassistant.util.package] Unable to install package pyuptimekuma==0.0.6: ERROR: Cannot install pyuptimekuma==0.0.6 because these package versions have conflicting dependencies.
ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts
Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

Uptime Kuma logs report no issues.
Uptime Kuma
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting
Add-on: Uptime Kuma
It is a self-hosted monitoring tool like "Uptime Robot"
Add-on version: 0.6.1
You are running the latest version of this add-on.
System: Home Assistant OS 9.5  (amd64 / generic-x86-64)
Home Assistant Core: 2023.3.1
Home Assistant Supervisor: 2023.03.1
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service uptime-kuma: starting
s6-rc: info: service uptime-kuma successfully started
s6-rc: info: service legacy-services: starting
[16:14:40] INFO: Starting Uptime Kuma...
Welcome to Uptime Kuma
s6-rc: info: service legacy-services successfully started
Your Node.js version: 18
2023-03-08T16:14:40-06:00 [SERVER] INFO: Welcome to Uptime Kuma
2023-03-08T16:14:40-06:00 [SERVER] INFO: Node Env: production
2023-03-08T16:14:40-06:00 [SERVER] INFO: Importing Node libraries
2023-03-08T16:14:40-06:00 [SERVER] INFO: Importing 3rd-party libraries
2023-03-08T16:14:41-06:00 [SERVER] INFO: Creating express and socket.io instance
2023-03-08T16:14:41-06:00 [SERVER] INFO: Server Type: HTTP
2023-03-08T16:14:41-06:00 [SERVER] INFO: Importing this project modules
2023-03-08T16:14:41-06:00 [NOTIFICATION] INFO: Prepare Notification Providers
2023-03-08T16:14:41-06:00 [SERVER] INFO: Version: 1.20.1
2023-03-08T16:14:41-06:00 [PLUGIN] WARN: Warning: In order to enable plugin feature, you need to use the default data directory: ./data/
2023-03-08T16:14:41-06:00 [DB] INFO: Data Dir: /data/
2023-03-08T16:14:41-06:00 [SERVER] INFO: Connecting to the Database
2023-03-08T16:14:41-06:00 [DB] INFO: SQLite config:
[ { journal_mode: 'wal' } ]
[ { cache_size: -12000 } ]
2023-03-08T16:14:41-06:00 [DB] INFO: SQLite Version: 3.39.4
2023-03-08T16:14:41-06:00 [SERVER] INFO: Connected
2023-03-08T16:14:41-06:00 [DB] INFO: Your database version: 10
2023-03-08T16:14:41-06:00 [DB] INFO: Latest database version: 10
2023-03-08T16:14:41-06:00 [DB] INFO: Database patch not needed
2023-03-08T16:14:41-06:00 [DB] INFO: Database Patch 2.0 Process
2023-03-08T16:14:41-06:00 [SERVER] INFO: Load JWT secret from database.
2023-03-08T16:14:41-06:00 [PLUGIN] WARN: Skip scanning plugin directory
2023-03-08T16:14:41-06:00 [SERVER] INFO: Adding route
2023-03-08T16:14:41-06:00 [SERVER] INFO: Adding socket handler
2023-03-08T16:14:41-06:00 [SERVER] INFO: Init the server
2023-03-08T16:14:41-06:00 [SERVER] INFO: Listening on 3001

Please check previously logged issues before creating a new one, your issue is with the custom integration you have installed rather than the addon.

#57
#56
#53
#52
#51
#49

My apologies


Volar misbehaves after creating new folder on VS Code

This is when Volar works correctly. NuxtWelcome is identified as a component (in blue color). Autocompletion and IntelliSense all function as intended.

After creating a new folder assets and a file assets/main.scss, Volar becomes irresponsive (NuxtWelcome is no longer blue, which indicates that code analysis has stopped working). IntelliSense and auto-completion work neither in .vue files or .ts files.

This is not bound to happen, but VS Code then creates infinite pop-up windows asking to access other programs' data. From Activity Monitor we can see there are numerous Code Helper processes, presumably created by Volar, and they resulted in increased memory usage.

My specs:

VS Code: 1.85.1 (Universal)
OS: Darwin arm64 23.2.0
Node: 21.5.0
TypeScript Vue Plugin (Volar): 1.8.27, takeover mode
Vue Language Features (Volar): 1.8.27

I have found similar issues like https://github.com/vuejs/language-tools/issues/3801 and #3816. This glitch can seriously damage user experience and I would appreciate it if the cause could be found and fixed.

Could you please try https://github.com/vuejs/language-tools/discussions/3789?

Could you please try #3789?

Still, it cannot detect components and infers their types as (property) any. The autocompletion works but imports components, which 1) is not needed in Nuxt; 2) inserts import statements in the wrong place; 3) still cannot correctly identifies components as they are.
Performance issue is solved and .ts files are no longer affected, as I observe.

Duplicate of https://github.com/vuejs/language-tools/issues/3832?

Duplicate of #3832?

Actually, I edited the project with WebStorm and then when I open it in VS Code, it's the same old issue again.

Using the dev version in #3789 now.

Also have this issue, if I create a new folder I have to reload my editor with Volar/Vue Extension.

Please track in https://github.com/vuejs/language-tools/issues/4424