torchvision[cuda10] installs default pytorch build, instead of cuda10 build

torchvision and pytorch are required to be built in similar environment.
Currently, when calling pip-install on cuda10 build of torchvision, (if torch is not already installed) it implicitly installs the default Pytorch build, which - as of today - is built against cuda9, resulting in raising an error during run-time.
e.g.
pip install torchvision[cuda10_package] torch[cuda10_package] - will work
but:
pip install torchvision[cuda10_package]; pip install torch[cuda10_package]
or similarily, pip install torch[cuda10_package] torchvision; pip install --force torchvision[cuda10_package]
will not. (order matters)
Can the requirements of each build be specified in such a way that pip will automatically look for the matching build of pytorch?
Alternatively, is it possible for pip to independently decide the correct build based on environment variables?

Good question. I think that with conda everything should work out fine, given that we have separated out the CUDA version into a different package.
I don't know how to solve the pip issue though. @soumith do you have an idea?

@barrh can you say what EXACT commands you are using in each case. It's not clear to me what you have tried, so getting clarity on that will help me understand what's going on.

@soumith The following installation scenarios will fail to run on cuda10 system:
1.
pip install https://download.pytorch.org/whl/cu100/torchvision-0.3.0-cp36-cp36m-linux_x86_64.whl; pip install https://download.pytorch.org/whl/cu100/torch-1.1.0-cp36-cp36m-linux_x86_64.whl
2.
pip install https://download.pytorch.org/whl/cu100/torch-1.1.0-cp36-cp36m-linux_x86_64.whl torchvision; pip install --force https://download.pytorch.org/whl/cu100/torch-1.1.0-cp36-cp36m-linux_x86_64.whl

hmmm, yea there isn't a easy pip fix to it, but there is a way to fix this. I opened an issue on PyTorch to address it, but it will take a bit of effort from my side https://github.com/pytorch/pytorch/issues/19990

I ran into this issue over the weekend.  It does have some consequences, as it causes some of the example PyTorch models (like the fast style transfer code sample) to fail to train.  Unfortunately, I don't have the exact error message at hand, but it was a runtime error related to the CUBLAS library.  It triggers on the features.bmm call in the gram_matrix function of the utils.py file (line 25).
However, I did find a temporary workaround.  The official PyTorch site says to install torch first, then torchvision.  If you reverse the install commands, then the incorrect version of torch will be installed with torchvision.  Running the torch install command then overwrites the wrong torch version with the correct one.  I haven't tested it thoroughly, but it does cause torch.version.cuda to report the correct version number (10.0.130) and the fast style transfer code starts to train.

I just ran into (mostly) the same problem, although the versions are different since it's been three years . When I used the command given in pytorch's instructions for Linux (Ubuntu 22.10), Stable (1.12.1), and CUDA 11.6:
pip3 install torch torchvision torchaudio --extra-index-url https://download.pytorch.org/whl/cu116
it installed the right version of torchvision (0.31.1+cu116) to get CUDA 11.6 but the older CUDA version for torch (1.12.1+cu102). @tyrian411's solution of re-installing torch by itself fixed it. Perhaps the documentation should be annotated in case people run into this again.


optimize readUntilPrompt

As discussed in #16, this PR tries to optimize the function reading from the ssh stdout until a prompt is detected.
Compared to what I posted in #16 I was able to further reduce the allocations (and overall performance)  by doubling the number of bytes read if the previous Read filled the buffer (bytes slice), meaning that there is probably more bytes to read.
The doubling is capped at 10MB.
goos: linux
goarch: amd64
pkg: github.com/networklore/netrasp/pkg/netrasp
BenchmarkReaderOriginal100Lines            89144             13693 ns/op           51681 B/op         20 allocs/op
BenchmarkReaderStringsBuilder100Lines      77240             14421 ns/op           37649 B/op         16 allocs/op
BenchmarkReaderBytesBuffer100Lines        118660             10312 ns/op           42993 B/op         16 allocs/op

BenchmarkReaderOriginal1KLines              2932            411502 ns/op         1412229 B/op         85 allocs/op
BenchmarkReaderStringsBuilder1KLines        6068            200693 ns/op          496834 B/op         36 allocs/op
BenchmarkReaderBytesBuffer1KLines           8080            150125 ns/op          603238 B/op         34 allocs/op

BenchmarkReaderOriginal10KLines               40          29014998 ns/op        82506028 B/op        761 allocs/op
BenchmarkReaderStringsBuilder10KLines<PHONE_NUMBER> ns/op         5192044 B/op         69 allocs/op
BenchmarkReaderBytesBuffer10KLines<PHONE_NUMBER> ns/op         5806319 B/op         63 allocs/op

BenchmarkReaderOriginal50KLines                2         717873436 ns/op<PHONE_NUMBER> B/op     3955 allocs/op
BenchmarkReaderStringsBuilder50KLines         64          18521338 ns/op        31493692 B/op        102 allocs/op
BenchmarkReaderBytesBuffer50KLines            94          12372473 ns/op        37513008 B/op         94 allocs/op

BenchmarkReaderOriginal100KLines               1<PHONE_NUMBER> ns/op<PHONE_NUMBER> B/op     8220 allocs/op
BenchmarkReaderStringsBuilder100KLines        34          34133189 ns/op        62915612 B/op        112 allocs/op
BenchmarkReaderBytesBuffer100KLines           54          22204790 ns/op        68265700 B/op        102 allocs/op
PASS
ok      github.com/networklore/netrasp/pkg/netrasp      21.662s

I left the original function, the one using strings.Builder and the related benchmarks for reference. Let me know if you want me to clean them up.

Thanks for the PR, looks good! Yes, please go a head and clean up the reference functions and benchmarks.

done

Thanks again!


Refactoring/type hints

This PR solves #95
Development environment
3.8.10 (default, Jan  5 2024, 09:18:58)
[Clang 15.0.0 (clang-15<IP_ADDRESS>.5)] darwin

[x] Ran mypy
[x] Ran tests
[x] Ran pre-commit

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

I developed and tested successfully on Python 3.8.10.
Upon opening this PR, the tests seem to have failed for Python 3.9. When running mypy it finds 25 errors in 20 files (checked 297 source files).
So, I ran mypy also on the latest commit that is not part of this PR and the same number of errors were found. Can it be that the source code on main has not yet been tested on Python 3.9?
If so, I think it's best to resolve these 25 issues in a different PR and block the current PR until the other one has successfully been merged. Thoughts?

I'll have a look into the mypy issue :smile:

My pleasure. I thought it's a good first issue.
I see that you opened PR https://github.com/instadeepai/jumanji/pull/216. Once that is approved, hopefully the linting is gonna pass here too and we can merge.


When auto generating the join syntax, message[] should be changed to map

When auto generating the join syntax in fork-join, message[] should be changed to map as only map is supported
        fork{

        }join () (message[] ) {

        }

This is already fixed in https://github.com/ballerinalang/plugin-intellij/commit/b4cf7fd2f0daed3fb119580b0537e5954153c445.


Problem building fabric-ca-client on arm64

It appears that there are some architecture conflicts here:
% make fabric-ca-client
# golang.org/x/sys/unix
vendor/golang.org/x/sys/unix/syscall_darwin.1_13.go:29:3: //go:linkname must refer to declared function or variable
vendor/golang.org/x/sys/unix/zsyscall_darwin_arm64.1_13.go:27:3: //go:linkname must refer to declared function or variable
vendor/golang.org/x/sys/unix/zsyscall_darwin_arm64.1_13.go:40:3: //go:linkname must refer to declared function or variable
vendor/golang.org/x/sys/unix/zsyscall_darwin_arm64.go:28:3: //go:linkname must refer to declared function or variable
vendor/golang.org/x/sys/unix/zsyscall_darwin_arm64.go:43:3: //go:linkname must refer to declared function or variable
vendor/golang.org/x/sys/unix/zsyscall_darwin_arm64.go:59:3: //go:linkname must refer to declared function or variable
vendor/golang.org/x/sys/unix/zsyscall_darwin_arm64.go:75:3: //go:linkname must refer to declared function or variable
vendor/golang.org/x/sys/unix/zsyscall_darwin_arm64.go:90:3: //go:linkname must refer to declared function or variable
vendor/golang.org/x/sys/unix/zsyscall_darwin_arm64.go:105:3: //go:linkname must refer to declared function or variable
vendor/golang.org/x/sys/unix/zsyscall_darwin_arm64.go:121:3: //go:linkname must refer to declared function or variable
vendor/golang.org/x/sys/unix/zsyscall_darwin_arm64.go:121:3: too many errors

I can definitely help resolve these, but would need some help to get into the code here. Can you advise as to why these arch dependencies would exist?
My environment:
GOARCH="arm64"
GOOS="darwin"
GOVERSION="go1.18.2"
CGO_ENABLED="1"

I was able to get it to build by doing the following:
go get -u golang.org/x/sys
go mod vendor
make fabric-ca-client

It appears recent work was done to upgrade golang to v1.18. Would it be acceptable to update the vendored sys/unix package in a PR?


Differences between braintree.data.setup and braintree.setup

Hello there,
we are using advanced fraud tools for detect fraud. Up till now we had used braintree.data.setup
for collecting data:

getDeviceData() {
    return new Promise((resolve) => {
      const config = getMarketConfig();

      let dataCollector = braintree.data.setup({
        kount: {
          environment: config.kount.environment,
          merchantId: config.brainTree.merchantId,
        }
      });

      resolve(dataCollector.deviceData);
    });
  }

Some time later we switched our getDeviceData method work via braintree.setup:
getDeviceData(braintreeClientToken) {
    return new Promise((resolve) => {
      const config = getMarketConfig();
      braintree.setup(braintreeClientToken, 'custom', {
        dataCollector: {
          kount: {
            environment: config.kount.environment,
            merchantId: config.brainTree.merchantId,
          },
        },
        onReady(braintreeInstance) {
          resolve(braintreeInstance.deviceData);
        },
      });
    });
  }

As we noticed there is no any differences in deviceData from braintree.setup and braintree.data.setup, it is looks the same but after switching to implementation via braintree.setup all our users start getting error : 2000, Do Not Honor.
Unfortunately I didn't found any explanation about differences of this two approaches except that , but I'm still does not understand what does it mean Standalone usage.
Really appreciate you if you can explain what is the differences between this two methods, and why moving to braintree.setup occur Do not honor error to all our users.
SDK version we are using - 2.24.0.

Hi @sashakru,
We think the two setup methods should behave similarly, but we are currently investigating what might be the cause. Thanks for your patience.

Hi @sashakru, we are not certain if the DataCollector setup method causes the 2000 Do Not Honor transaction decline errors from your bank. Do you mind contacting our support team at<EMAIL_ADDRESS>They will help you drill down into the issue.

Closing due to inactivity. Please reopen if more information is available.


Be more honest about effects

Added EXCEPTION to functions that can throw.

@zudov What do you think?

Makes sense, thanks. Let's release it together with other unmerged changes.


Convert Tensor to Vec

Hi,
I've been using your awesome lib for a few days now and I've been wondering what's the most efficient way to convert a Tensor of several dimensions Tensor[n, m] into a Vec<Vec<f32>>, or a similar form.
For reference, my use-case involves computing embeddings stored as Tensors using my library rust-sbert and then converting them into a more raw form to be able to send them through the network, for example using gRPC.

Thanks for your feedback, your rust-sbert crate seems pretty cool.
Re converting a tensor to Vec<Vec<f32>>, this should work with Vec::<Vec::<f32>>::from(tensor), let me know if you have some issues using this.
Fwiw I just added a test to illustrate this in this commit.
Note that we also support conversion to/from ndarray which may be more efficient depending on your use case.

Thanks for the feedback and the quick reply, this worked perfectly. I'll have to stick with Vecs for the library that I am using for now though


Telling a Story with Outcomes Examples

Added samples and writeup from this post to the primer.

cc @lillismith


usm: kafka: test: Group split tests to avoid flakiness

What does this PR do?
The split tests tests a lot of transactions and this causes the event flushing to sometimes fail with tests generating multiple events per transaction like the "with different error codes" test because there is no room in the perf buffer.  Split the test into groups to reduce the risk of this happening.
The grouping is a compromise between running each split index test individually (which would increase the test time) and running everything together (increasing the risk for overflowing buffers). The grouping also increases the test time so the PR includes various things to reduce it to keep it around the same level as before.

Motivation
https://datadoghq.atlassian.net/browse/USMON-1078

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/merge


Documentation site's SSL cert is invalid

Not exactly a repo "issue" but it's blocking me from being able to try out this tool with a work project.
https://gha-cache-server.falcondev.io/getting-started

That's weird, it works for me. What certificate does it show in your browser?


Missing or more than one assembly archive file *.zip in /tmp/src/target

Hello
I am trying to build using the s2i builder fuse-karaf-openshift but I get the below error.  I see that there was similar issue#157 dated May 2018 marked as closed but no solution is described. Can someone help?
I run the following command:
s2i build ~/workspace/fuse-camel-cbr registry.redhat.io/fuse7/fuse-karaf-openshift s2i-cbr2 --loglevel=5
I0111 18:03:04.337063  195642 sti.go:711] [INFO] Writing OBR metadata
I0111 18:03:04.339963  195642 sti.go:711] [INFO] ------------------------------------------------------------------------
I0111 18:03:04.340001  195642 sti.go:711] [INFO] BUILD SUCCESS
I0111 18:03:04.340015  195642 sti.go:711] [INFO] ------------------------------------------------------------------------
I0111 18:03:04.340330  195642 sti.go:711] [INFO] Total time: 03:19 min
I0111 18:03:04.340366  195642 sti.go:711] [INFO] Finished at: 2021-01-11T23:03:04Z
I0111 18:03:04.548154  195642 sti.go:711] [INFO] Final Memory: 30M/106M
I0111 18:03:04.548364  195642 sti.go:711] [INFO] ------------------------------------------------------------------------
I0111 18:03:04.594352  195642 sti.go:711] Copying built artifacts from /tmp/src/target into /deployments...
I0111 18:03:04.691604  195642 sti.go:711] Directory /tmp/src/target contains bundles
I0111 18:03:04.691677  195642 sti.go:711] camel-blueprint-cbr-1.0.0-SNAPSHOT.jar
I0111 18:03:04.691707  195642 sti.go:711] classes
I0111 18:03:04.691732  195642 sti.go:711] generated-test-sources
I0111 18:03:04.691768  195642 sti.go:711] maven-status
I0111 18:03:04.691794  195642 sti.go:711] surefire-reports
I0111 18:03:04.691814  195642 sti.go:711] test-bundles
I0111 18:03:04.691834  195642 sti.go:711] test-classes
I0111 18:03:04.691900  195642 sti.go:711] Missing, or more than one, assembly or archive file *.zip in /tmp/src/target
I0111 18:03:04.804617  195642 docker.go:1044] Waiting for container "7e365380b58ac5f7621c2ece90361ab636bbc7ea66803b91d639b14e54b98e0c" to stop ...
I0111 18:03:07.251446  195642 docker.go:980] Removing container "7e365380b58ac5f7621c2ece90361ab636bbc7ea66803b91d639b14e54b98e0c" ...
I0111 18:03:07.542361  195642 docker.go:990] Removed container "7e365380b58ac5f7621c2ece90361ab636bbc7ea66803b91d639b14e54b98e0c"
I0111 18:03:07.542587  195642 cleanup.go:33] Removing temporary directory /tmp/s2i039059575
I0111 18:03:07.542599  195642 fs.go:313] Removing directory '/tmp/s2i039059575'
I0111 18:03:07.546440  195642 build.go:170] Build failed
E0111 18:03:07.546470  195642 errors.go:296] An error occurred: non-zero (13) exit code from registry.redhat.io/fuse7/fuse-karaf-openshift

@dhirajsb any idea ?

@dhirajsb any idea ?

@rhuss looks like the s2i build didn't build a karaf assembly for some reason. Basically the karaf maven plugin's assembly goal should have been invoked and an assembly zip archive should have been created. Maybe an issue with the project's pom.xml??
The resolution not mentioned in the older ticket is to print the contents of the /tmp/src/target directory, which shows that no assembly was created.
@kkdavidwong, can you verify that the output from the following line:
Running 'mvn ${maven_env_args} ${MAVEN_ARGS} ${MAVEN_ARGS_APPEND}'"

has the default maven opts:
install -DskipTests -e -Dfabric8.skip=true -B

Also, try running maven with those options locally to see whether the assembly archive is being created in the target directory. If it isn't try and investigate the cause for that.
The way it works is that the pom packaging should be <packaging>karaf-assembly</packaging>, which automatically adds karaf:assembly goal to the build to create the assembly.

@rhuss looks like the s2i build didn't build a karaf assembly for some reason. Basically the karaf maven plugin's assembly goal should have been invoked and an assembly zip archive should have been created. Maybe an issue with the project's pom.xml??
The resolution not mentioned in the older ticket is to print the contents of the /tmp/src/target directory, which shows that no assembly was created.
@kkdavidwong, can you verify that the output from the following line:
Running 'mvn ${maven_env_args} ${MAVEN_ARGS} ${MAVEN_ARGS_APPEND}'"

has the default maven opts:
install -DskipTests -e -Dfabric8.skip=true -B

Also, try running maven with those options locally to see whether the assembly archive is being created in the target directory. If it isn't try and investigate the cause for that.
The way it works is that the pom packaging should be <packaging>karaf-assembly</packaging>, which automatically adds karaf:assembly goal to the build to create the assembly.

Thank you for looking into this problem.
there is maven goal assembly and install...
  <plugin>
    <groupId>org.jboss.redhat-fuse</groupId>
    <artifactId>karaf-maven-plugin</artifactId>
    <version>${fuse.bom.version}</version>
    <extensions>true</extensions>
    <executions>
      <execution>
        <id>karaf-assembly</id>
        <goals>
          <goal>assembly</goal>
        </goals>
        <phase>install</phase>
      </execution>
    </executions>
    <configuration>
      <javase>1.8</javase>
      <karafVersion>v4x</karafVersion>
      <framework>framework</framework>
      <useReferenceUrls>true</useReferenceUrls>
      <archiveTarGz>false</archiveTarGz>
      <includeBuildOutputDirectory>false</includeBuildOutputDirectory>
      <startupFeatures>
        <feature>framework</feature>
        <feature>jaas</feature>
        <feature>log</feature>
        <feature>shell</feature>
        <feature>management</feature>
        <feature>aries-blueprint</feature>
        <feature>camel-blueprint</feature>
        <feature>fabric8-karaf-blueprint</feature>
        <feature>fabric8-karaf-checks</feature>
      </startupFeatures>
      <startupBundles>

mvn:${project.groupId}/${project.artifactId}/${project.version}

Maven arguments:
I0118 10:46:10.371356   71316 sti.go:711] Starting S2I Karaf Build .....
I0118 10:46:10.371413   71316 sti.go:711] Maven build detected
I0118 10:46:10.371426   71316 sti.go:711] Using custom maven settings from
/tmp/src/configuration/settings.xml
I0118 10:46:10.593765   71316 sti.go:711] Using MAVEN_OPTS
'-XX:+UseParallelGC -XX:GCTimeRatio=4 -XX:AdaptiveSizePolicyWeight=90
-XX:MinHeapFreeRatio=20 -XX:MaxHeapFreeRatio=40 -XX:+ExitOnOutOfMemoryError'
I0118 10:46:10.593786   71316 sti.go:711] Found pom.xml ...
I0118 10:46:10.593793   71316 sti.go:711] Running 'mvn
-Dmaven.repo.local=/tmp/artifacts/m2 -s /tmp/src/configuration/settings.xml
install -DskipTests -e -Dfabric8.skip=true -B '
I0118 10:46:11.395585   71316 sti.go:711] [1mApache Maven 3.5.0 (Red Hat
3.5.0-4.3) [m
I0118 10:46:11.395610   71316 sti.go:711] Maven home:
/opt/rh/rh-maven35/root/usr/share/maven
I0118 10:46:11.395644   71316 sti.go:711] Java version: 1.8.0_272, vendor:
Red Hat, Inc.
I0118 10:46:11.395659   71316 sti.go:711] Java home:
/usr/lib/jvm/java-1.8.0-openjdk-<IP_ADDRESS>2.b10-1.el7_9.x86_64/jre
I0118 10:46:11.395676   71316 sti.go:711] Default locale: en_US, platform
encoding: ANSI_X3.4-1968
On Thu, Jan 14, 2021 at 2:17 PM Dhiraj Bokde<EMAIL_ADDRESS>wrote:

@rhuss https://github.com/rhuss looks like the s2i build didn't build a
karaf assembly for some reason. Basically the karaf maven plugin's
assembly goal should have been invoked and an assembly zip archive should
have been created. Maybe an issue with the project's pom.xml??
The resolution not mentioned in the older ticket is to print the
contents of the /tmp/src/target directory, which shows that no assembly
was created.
@kkdavidwong https://github.com/kkdavidwong, can you verify that the
output from the following line:
Running 'mvn ${maven_env_args} ${MAVEN_ARGS} ${MAVEN_ARGS_APPEND}'"
has the default maven opts:
install -DskipTests -e -Dfabric8.skip=true -B
Also, try running maven with those options locally to see whether the
assembly archive is being created in the target directory. If it isn't
try and investigate the cause for that.
The way it works is that the pom packaging should be
karaf-assembly, which automatically adds
karaf:assembly goal to the build to create the assembly.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/fabric8io-images/s2i/issues/260#issuecomment-760411934,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASCBU7SN77CDKOOSP23OOKTSZ47N3ANCNFSM4V6MKNFQ
.

Thank you for looking into this problem.
there is maven goal assembly and install...
  <plugin>
    <groupId>org.jboss.redhat-fuse</groupId>
    <artifactId>karaf-maven-plugin</artifactId>
    <version>${fuse.bom.version}</version>
    <extensions>true</extensions>
    <executions>
      <execution>
        <id>karaf-assembly</id>
        <goals>
          <goal>assembly</goal>
        </goals>
        <phase>install</phase>
      </execution>
    </executions>
    <configuration>
      <javase>1.8</javase>
      <karafVersion>v4x</karafVersion>
      <framework>framework</framework>
      <useReferenceUrls>true</useReferenceUrls>
      <archiveTarGz>false</archiveTarGz>
      <includeBuildOutputDirectory>false</includeBuildOutputDirectory>
      <startupFeatures>
        <feature>framework</feature>
        <feature>jaas</feature>
        <feature>log</feature>
        <feature>shell</feature>
        <feature>management</feature>
        <feature>aries-blueprint</feature>
        <feature>camel-blueprint</feature>
        <feature>fabric8-karaf-blueprint</feature>
        <feature>fabric8-karaf-checks</feature>
      </startupFeatures>
      <startupBundles>

mvn:${project.groupId}/${project.artifactId}/${project.version}

Maven arguments:
I0118 10:46:10.371356   71316 sti.go:711] Starting S2I Karaf Build .....
I0118 10:46:10.371413   71316 sti.go:711] Maven build detected
I0118 10:46:10.371426   71316 sti.go:711] Using custom maven settings from
/tmp/src/configuration/settings.xml
I0118 10:46:10.593765   71316 sti.go:711] Using MAVEN_OPTS
'-XX:+UseParallelGC -XX:GCTimeRatio=4 -XX:AdaptiveSizePolicyWeight=90
-XX:MinHeapFreeRatio=20 -XX:MaxHeapFreeRatio=40 -XX:+ExitOnOutOfMemoryError'
I0118 10:46:10.593786   71316 sti.go:711] Found pom.xml ...
I0118 10:46:10.593793   71316 sti.go:711] Running 'mvn
-Dmaven.repo.local=/tmp/artifacts/m2 -s /tmp/src/configuration/settings.xml
install -DskipTests -e -Dfabric8.skip=true -B '
I0118 10:46:11.395585   71316 sti.go:711] [1mApache Maven 3.5.0 (Red Hat
3.5.0-4.3) [m
I0118 10:46:11.395610   71316 sti.go:711] Maven home:
/opt/rh/rh-maven35/root/usr/share/maven
I0118 10:46:11.395644   71316 sti.go:711] Java version: 1.8.0_272, vendor:
Red Hat, Inc.
I0118 10:46:11.395659   71316 sti.go:711] Java home:
/usr/lib/jvm/java-1.8.0-openjdk-<IP_ADDRESS>2.b10-1.el7_9.x86_64/jre
I0118 10:46:11.395676   71316 sti.go:711] Default locale: en_US, platform
encoding: ANSI_X3.4-1968
On Thu, Jan 14, 2021 at 2:17 PM Dhiraj Bokde<EMAIL_ADDRESS>wrote:

@rhuss https://github.com/rhuss looks like the s2i build didn't build a
karaf assembly for some reason. Basically the karaf maven plugin's
assembly goal should have been invoked and an assembly zip archive should
have been created. Maybe an issue with the project's pom.xml??
The resolution not mentioned in the older ticket is to print the
contents of the /tmp/src/target directory, which shows that no assembly
was created.
@kkdavidwong https://github.com/kkdavidwong, can you verify that the
output from the following line:
Running 'mvn ${maven_env_args} ${MAVEN_ARGS} ${MAVEN_ARGS_APPEND}'"
has the default maven opts:
install -DskipTests -e -Dfabric8.skip=true -B
Also, try running maven with those options locally to see whether the
assembly archive is being created in the target directory. If it isn't
try and investigate the cause for that.
The way it works is that the pom packaging should be
karaf-assembly, which automatically adds
karaf:assembly goal to the build to create the assembly.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/fabric8io-images/s2i/issues/260#issuecomment-760411934,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASCBU7SN77CDKOOSP23OOKTSZ47N3ANCNFSM4V6MKNFQ
.


Stubs for extended form types

When form types are created from controller like this:
public function __invoke()
{
	  $form = $this->createForm(SearchType::class);
	  $form->handleRequest($request);
	  if ($form->isSubmitted() && $form->isValid()) {

		  $code = $form->getData(); // <--- mixed

	  }
}

psalm thinks it is mixed.
These 3 stubs fixes cases that all work with string. In few weeks, I will add other types after I confirm returned data.

I see tests are failing only on Symfony4, but I can't see the reason for that. Any help?


Add pagination on get user logs service

modified -
route file
controller
service
dao
repository

Closing due to lack of progress.


AST: Requestify unique underlying type substitutions

Introduce a request that computes the unique underlying type substitution of an opaque type declaration. This ensures that the type substitution is available on-demand when generating SIL in lazy typechecking mode.
Resolves rdar://117439760

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test


Respect umask settings in Transmission config

Accidentally closed old pull request #10050 when trying to rebase it. Here is a new one.
In NixOS/nixpkgs@da6bc44 @thoughtpolice
made the Transmission NixOS module override the umask setting in the
Transmission config. This commit removes that override.
I want a different umask setting and I guess it is possible that other
people might want it to. Thus I think it is a good idea to respect the
umask settings in the Transmission config.

It occurred to me: one way to retain the old behavior but still respect the user would be to switch the original statement around, so that the user config overrides the module instead of the other way around wrt. umask. Something like
fullSettings = {
  umask = 2; download-dir = downloadDir; incomplete-dir = incompleteDir;
} // cfg.settings

What do you think? This would mean that people who don't care to set the umask get the old behavior (transmission defaults to 18 aka 022 in octal).

Looks good. Just updated the pull request.

Great, thanks


add Flush method

This pull request is related to https://github.com/basicrum/front_basicrum_go/pull/53
cc: @ceckoslab

@eapache Could you please check the pull request?

Thanks!

Release in v1.4.0


XLSX package Download as Excel in Desktop App

I am developing a desktop app which is an Electron js App.I am having a problem with exporting excel file using xlsx package. It works properly (i can download the file and it shows in project directory folder) however, the app doesn't show directory or not giving any alerts like in google chrome because its a desktop app. So client can't understand the export button works or not. What are your solution suggestions for this situation?
Code Example:
function exportReport(e){
       e.preventDefault();
       let ws_name = "MySheet";
       if(!Lodash.isEmpty(props.dataSource)){
           let ws = XLSX.utils.json_to_sheet(props.dataSource);
           console.log(ws)
           let wb = XLSX.utils.book_new();
           XLSX.utils.book_append_sheet(wb, ws, ws_name);
           XLSX.writeFile(wb, 'out.xlsx');

       }
   }

https://github.com/SheetJS/sheetjs/tree/master/demos/electron#reading-and-writing-files
/* from app code, require('electron').remote calls back to main process */
var dialog = require('electron').remote.dialog;

/* show a file-save dialog and write the workbook */
var o = dialog.showSaveDialog();
XLSX.writeFile(workbook, o);

Depending on the electron version, you may need to use dialog.showSaveDialogSync and pass the nodeIntegration option.  For more info, see https://github.com/SheetJS/sheetjs/issues/1994


Fix Linux build.  Remove #include <sys/sysctl.h>

It doesn't appear that the sysctl call was used, and the call has been deprecated in Linux for some time. On Ubuntu 20.10 this include header is not found and breaks the library from building.

Joey, we need to verify if this will still build on macOS without systcl. We may have to surround this include with an # ifdef __APPLE__ or similar.

Confirmed that this is also unnecessary on macOS. Merged.


Harmonic LFOs Update (again, sorry...)

Just an extra bit of functionality I realised would be very useful as I was playing with the new ability to change the divisions on the fly: mode per LFO.
This is incredibly useful in practice because it means you can use LFO 1 as a master clock for example, sending square waves, and then use the others as any other waveform with any other division.
The wave form of the current LFO is now shown as a little symbol underneath its division when it is selected, so it's very easy to see which LFO is using which waveform.  The individual LFO waveforms are now saved to the file in a list the same way as the dviisions list, rather than a global mode variable.
This also will make it easier in future to add different or more complex waveforms, or even things like swing per LFO.
p.s. sorry for not thinking of this before I requested the review of the previous PR!

I've just noticed that the drawing of the sine symbol results in a noticeable slowing down of the system speed so I'm going to see if I can use the bytearray method of drawing images instead, or only draw it once when the mode is changed

I've fixed this by just drawing the sine symbol pixel by pixel. Bytearray seemed to have the same performance issues and was also very awkward to generate from an image

There is one a new wave shape - random - which is sort of random, it's actually just the sum of 3 sine waves so it's relatively unpredictable but also computationally non-intensive compared to some kind of actual random generator.
There is also a wave shape mode of 'off' allowing any LFO to be turned off easily

All changes you suggested have been made! I also used your handy one line increment for the selected LFO, as well as the mode of the currently selected LFO


.NET Core application name does not change in taskbar?

.NET Core application name does not change in taskbar?
Even after the self contained publishing the process name doesn't change, the assembly name property seems to work only on changing the .dll file name.
I have four applications running, but for each process it shows dotnet as shown in the picture

I think this is a duplicate of https://github.com/dotnet/core-setup/issues/2007.

@steveharter @nguerrera is this something for the host or something that needs to be fixed in publish. Host doesn't know the name of the app until publish.

I think the different here is that for a self-contained application or any application where the host is renamed to match the program name, we should be able to give something better in task manager.

@nguerrera @livarcocc I'm going to move this to the CLI repo because I think this is about what happens when the apphost exe is renamed and updated to "look like the app".

Issue moved to dotnet/cli #8832 via ZenHub


Add a fact for installed postgres version

Summary
There is sometimes a need to handle versions differently.  (The last exampel for us being deciding whether to monitor the stats collector process.)  This fact provides a basis for writing such code.
Checklist

[X] 🟢 pdk validate
[X] 🟢 pdk test unit

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Magnus Gustavsson seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

There might be multiple PostgreSQL clusters installed with different versions. Debian has pg_lsclusters script.

RHEL doesn't unfortunately, do we can't depend on it for this. A quick Google search indicates that pg_lsclusters` is a Debian specific thing.

@maggu Yes, it's Debian specific. It's fairly simple Perl script. AFAIK postgresql doesn't ship any tool to manage/list clusters. You could try to parsing $confdir but that can be in very different locations. You could export clusters managed by Pupppet to a text/JSON file and then load it as a fact.

I think in this case it's fine to only have a 80% solution. If it works for the common setups and the edge cases are documented, that is fine in my opinion.

I think in this case it's fine to only have a 80% solution. If it works for the common setups and the edge cases are documented, that is fine in my opinion.

I agree. If there's a need for the rest, a second hierarchical fact confined by and using pg_lsclusters could always be added in the future.

Fedora 40 has already moved to parallel installable packages for PostgreSQL (by creating postgresqlXX packages) and I expect future RHEL versions to follow. It sounds to me that tooling like pg_lsclusters should be included.

There is sometimes a need to handle versions differently. (The last exampel for us being deciding whether to monitor the stats collector process.) This fact provides a basis for writing such code.

The version is already available in the globals as $postgresql::globals::version. By default detected rather statically but if you need a non-standard version then you modify it. The further code sets up the right repositories or in case of RHEL 8 & 9 OS packages the right DNF module. I don't see a need for a fact here.

Debian appears to have pg_config --version as part of the standard installation. I believe that could perhaps solve the problem of making this work on the major Linux platforms. I don't currently plan to put more work into it though unless the consensus is that a version fact would indeed be useful.

It has worked reasonably well sometimes. Other times though, when the version value is undef and the fallback used, the result has turned out to not be what we wanted. I would be interested to hear how this approach has worked out for others though. Switching to using a fact to determine the actual version so far at least seems to be more consistent over time.

I think it should be the other way around: you specify the version you want and the module makes it so.
Fundamentally the problem is that until you install the package, you don't have the version. So it can never be idempotent.

Run 1

Install package with some configuration

Run 2

Fact is available
Modifications may be made

In addition to that, we have multi instance mode where I think even one instance may run a different version than another and I question how this fact is going to be useful in the generic case.

I don't see us going back to using the globals parameter, even though I suppose to could be made to work with enough effort. We have a lot of people working with Puppet code in multiple departments and can't depend on it being explicitly set everywhere. Perhaps we're special enough though, that it's better that we just use a local fact instead of trying to merge this upstream.

Perhaps other maintainers have a different opinion, but as a maintainer of this module I'd say that you're not using the module correctly. It is designed that you pass in the version you want.

Fundamentally the problem is that until you install the package, you don't have the version. So it can never be idempotent.

It would indeed require two runs to reach a final state. Isn't that the case for any fact except for the core facts? While I agree that in general fewer runs are better than more, there are also other aspects to consider. In this case, first and foremost the amount of work required to keep explicit versions updated.

In addition to that, we have multi instance mode where I think even one instance may run a different version than another and I question how this fact is going to be useful in the generic case.

That would be a limitiation to this PR, yes (as discussed above). Unless the scope is changed, and that is of course a possibility.

Perhaps other maintainers have a different opinion, but as a maintainer of this module I'd say that you're not using the module correctly. It is designed that you pass in the version you want.

I personally don't think the documentation currently reflects that indention very well, and perhaps ought to be updated. (Also, for reasons stated above I don't believe this approach would work very well for us.)

It would indeed require two runs to reach a final state. Isn't that the case for any fact except for the core facts? While I agree that in general fewer runs are better than more, there are also other aspects to consider. In this case, first and foremost the amount of work required to keep explicit versions updated.

That is why I think detecting the version via a fact is considered unreliable. You can query the repositories for the available version and use that, but what if the manifests set up the repositories?
We have this in https://github.com/voxpupuli/puppet-nginx and there it's only causing problems.

I personally don't think the documentation currently reflects that intention very well, and perhaps ought to be updated.

That may be true. I see https://github.com/puppetlabs/puppetlabs-postgresql?tab=readme-ov-file#override-defaults is there, but it could be promoted to its own chapter so I opened https://github.com/puppetlabs/puppetlabs-postgresql/pull/1610
(Also, for reasons stated above I don't believe this approach would work very well for us.)
Could you elaborate on that? Because I'm inclined to consider it unsupported. This module takes great care of minimizing the amount of changes to a database server because restarting a database server is considered undesirable. Anything that can risk that should be treated with great caution.


Experimental worker-to-worker bindings support

Adds support for experimental worker-to-worker bindings, letting you call a worker from another worker. The Wrangler config field looks like follows:
services = [{ name = "foo", script_name = "foo-service", env = "production" }]

Where:

name is the name of the binding in your worker code
script_name is the script to reference
env (optional) is the environment of the script to reference (e.g. production, staging, etc)

Updated based on feedback, PR should be more simpler now

Closed in favor of #166


Lead with 0BSD

Reword #7 because Github's license detector didn't recognize that way as 0BSD

This change did enable Github to detect 0BSD


[pagination] Remove children prop

[x] I have followed (at least) the PR section of the contributing guide.

@eps1lon Sorry, missed that one of the tests you added is using children...


Proposition of improvement: add Feature Dataset

Not an issue, rather a proposition of improvement for a future release.
In a case of a ESRI geodatabase, I think it would be really useful to have a column in the Excel file for the feature dataset. Like that it would be easier to look for a particular feature class and to filter the Exel file.

Not accepted by GDAL / OGR team, so for now, the re is no way to achieve it.


Rails app only using Parse: how to configure  database.yml ?

Hi Alan,
Sorry for the slightly out of subject question : my my rails app only use Parse as database so in this case how do you configure database.yml on so on?
Many thanks,
Philippe

I mean, how to avoid to configure with useless sqlite3 or pg database


Fix audit online release variable

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.

[x] Have you successfully run brew tests with your changes locally?

#7685 changed the release variable but not the following lines leading to this error currently when using brew audit --online:
Error: undefined local variable or method `release' for #<Homebrew::FormulaAuditor:0x00007fb5c7b89a28>

Thanks!


Barcode Items can have nil for the organization_id field

[ ] Make BarcodeItem.organization_id nullable
[ ] Make the lookup queries for doing BarcodeItem lookups pull the union of records with the Org's ID and those with nil for that field
[ ] Allow users to create custom barcode item entries that are just for them
[ ] BarcodeItem#index only shows in-house barcodes (those with the orgID set to the current org)

I'm still thinking about this one and the best way to approach it -- from both a code and UX perspective.
Some specific concerns are:
Do want to lookup items scoped to other organizations -- if no, how about if it doesn't exist on the organization or globally (nil)?

@seanmarcia The way I had imagined it (and feel free to disagree here if you have different ideas):

"Global" barcodes have an organization_id set to nil
"Private" barcodes (ones created internally) have an organization_id set

Whenever the app needs to query for BarcodeItem, it would do something like: BarcodeItem.where(organization_id: nil).or(where(organization_id: current_organization.id)).
The thing that keeps popping up in my mind is that, while we expect users to only enter in custom barcodes (like, only known to that org), they might enter in barcodes for national brands that aren't in the global DB -- maybe (and this is likely out of scope for this issue) there's some way for users to submit or flag their barcode as "this is a brand".
Also if we're going to push the "Create your own barcode" thing, we should probably have some way to generate barcodes that the users can print out?

It is pretty simple to print out a barcode, it is just a font you have to install. This is something we may need to make a screencast about. (or find one on youtube!)

I think an easier way to handle this would be to just create a new organization, call it BarCodeOrg or something and put all the EAN13 codes on it. That way we could just do BarcodeItem.where(organization_id: Organization.find_by_name("BarCodeOrg").id).or(where(organization_id: current_organization.id))
We probably wouldn't need that find_by_name, we could probably just hardcode it once we had it created since it won't change after that.

This approach will also require a fair bit less refactoring :)

I'm going to do a few things with this to start with. Need to get some PRs in and this is a good opportunity!

Instead of the task Allow users to create custom barcode item entries that are just for them how about Allow users to set barcode item entries as unique to them or global (nil)
I also wonder if we are going with this approach of having universal barcodes if we should have removed the ability to see bar codes. I think one of the strong advantages of the system is being able to create custom barcodes.

how about Allow users to set barcode item entries as unique to them or global (nil)

I like it. That sounds good :) We could add some validation that just checks to see if that particular UPC has already been made global. Or maybe a DB unique constraint on UPC + organization_id? Would that fly for NULL values in organization_id?
As it was (the BarcodeItems#index view and all that) I think it was superfluous information as it was displayed. I definitely do agree creating custom barcodes should be something we do, but maybe we can streamline the UX a bit more so it's more intuitive? I don't have any specific ideas in mind yet -- brainstorm?
I'm going to work on the next TODO item for this.

@seanmarcia Any thoughts on the UX for adding barcodes?
My current thinking (and this may be overcomplicating) is to use the existing barcode_items routes. Those will automatically scope down for regular users. Same with the other CRUD actions. May need to write tests that verify access control is respected. I also think the UI needs to be improved a little bit. The numerical value really doesn't need to be a column, maybe just have it as text is either a hover attribute, title property, or some "show" link type thing?
I think we may need to add an administrative area that can do management tasks (site-wide CRUD for all resources).
Your thoughts?

I thought the easiest solution is just keep what we have now and just add in a radio button or something like that for setting it as global (org_id: nil) or local (org_id: current_org.id)
I think this might also require checking in on issue #20 for consistency. Or we can just back-port whatever you do to what valerie adds to her PR.

That's a good point -- right now we just need the feature to work. we can worry about access control and stuff later.

THIS IS DONE FINALLY AND CAN BE REVIEWED !!!!!


Integrate with types from 3rd party bindings

The binding generator should be able to both integrate with bindings for the standard library as provided by Scala Native as well as bindings provided by 3rd party libraries.
For example, one package provides bindings for gtk and another package bindings for a new gtk component. The component package should ideally just declare a dependency on the gtk binding and not have to include bindings for all of gtk.
One idea would be to have the binding generator create a file with types and information similar to the stdHeader.config file which can be packaged together with a binding and then loaded from the JAR.

LLVM modulemaps look interesting: https://clang.llvm.org/docs/Modules.html#module-map-language

The current std-header configuration has one limitation because it uses basename whereby it doesn't allow multiple libraries to have a file with the same name. This limitation should only be an issue if we map 1:1 files to extern objects.
If we instead can trace the entry point of the library this should not be an issue. Libraries may have multiple entrypoints (header files) but then they are usually grouped in a nested directory. It looks like rust-bindgen gets around solves this by requiring that users provide a wrapper header file which includes all header files of the library. This automatically allows to blacklist all other headers.
We still need to keep track of which header file declares which type so that we can reference types correctly. For example, if bzip2 includes stdio.h to use FILE in a method then the generated code should use stdio.FILE in the method signature. For this to work we should use a file similar to std-header to maintain a namespace context for the current header file being parsed and add this information as an annotation in the generated types and declarations. Filtering by this annotation will make it quite simple to prune methods from external headers.

Sorry, I do not fully understand what do you mean by fully qualified name of a header file? Library name + path to the file?

As an example the fully qualified name of bzip2 could be org.scalanative.bindings.bzip2.

Okay, but we can get this name without a file similar to std-header by simply concatenating package name and lib name, am I right?

So, will we generate one scala object from multiple headers of a library? Then we should mark each generated binding with information on where it came from. Will it look like this?:
@extern
object mylib {
  @location("header1.h")
  type union_myUnion = native.CArray[Byte, native.Nat._8]

  @location("header2.h")
  def setIntValue(v: native.Ptr[union_myUnion]): Unit = native.extern
}

But I suppose it is not necessary if std-headers contain this info:
mylib {
  object org.scalanative.bindings.mylib
  headers {
    header1.h
    header2.h
  }
}

So if parsed library includes header1.h then we can check which library contains this header and include corresponding scala object. But what if two libraries contain header file with the same name?
mylib1 {
  object org.scalanative.bindings.mylib1
  headers {
    header1.h
  }
}
mylib2 {
  object org.scalanative.bindings.mylib2
  headers {
    header1.h
  }
}

@jonas, I wrote my thought about this issue here, what do you think about it?
I suggested there new format of config file, but I think that it is too complicated and we should use existing format.


V-38671 Remove sendmail package will also remove cronie from CentOS 6 distros.

Version: 0.9
I'm running STIG categories 1 and 2 on a webserver running CentOS 6.7. I'm running into this error:
Traceback (most recent call last):                                                                                │ * updates: mirror.web-ster.com
  File "/home/centos/.ansible/tmp/ansible-tmp-1440039562.82-112125137340434/cron", line 2117, in <module>              │Resolving Dependencies
    main()                                                                                │--> Running transaction check
  File "/home/centos/.ansible/tmp/ansible-tmp-1440039562.82-112125137340434/cron", line 440, in main                   │---> Package cronie.x86_64 0:1.4.4-15.el6 will be installed
    crontab = CronTab(module, user, cron_file)                                                                         │--> Processing Dependency: dailyjobs for package: cronie-1.4.4-15.el6.x86_64
  File "/home/centos/.ansible/tmp/ansible-tmp-1440039562.82-112125137340434/cron", line 178, in __init__               │--> Processing Dependency: /usr/sbin/sendmail for package: cronie-1.4.4-15.el6.x86_64
    self.read()                                                                                │--> Running transaction check
  File "/home/centos/.ansible/tmp/ansible-tmp-1440039562.82-112125137340434/cron", line 199, in read                   │---> Package cronie-anacron.x86_64 0:1.4.4-15.el6 will be installed
    raise CronTabError("Unable to read crontab")                                                                       │--> Processing Dependency: crontabs for package: cronie-anacron-1.4.4-15.el6.x86_64
__main__.CronTabError: Unable to read crontab

I've discovered that the CentOS crontab package cronie is getting uninstalled when running task V-38671 Medium  The sendmail package must be removed because cronie has a dependency on sendmail. However, cronie is required for the task beginning with V-38670, which fails because cronie is no longer installed. Reinstalling cronie and then running this role fixes the issue but it is undesirable to have to run the role, reinstall cronie, then run the roll again.

My initial thought is to implement a check for the removal of sendmail, and subsequently install postfix as per STIG guidance. Postfix being  present should allow cronie to work I think.
Does reinstalling cronie also reinstall sendmail?

I can verify your initial thoughts. The way I’m getting around this now is by uninstalling sendmail then reinstalling cronie and postfix. Reinstalling cronie does not install sendmail. Installing cronie installed exim instead. I don’t know if installing postfix  and then cronie would also install exim.

On Aug 24, 2015, at 16:40, Jonathan Davila<EMAIL_ADDRESS>wrote:
My initial thought is to implement a check for the removal of sendmail, and subsequently install postfix as per STIG guidance. Postfix being present should allow cronie to work I think.
Does reinstalling cronie also reinstall sendmail?
—
Reply to this email directly or view it on GitHub https://github.com/MindPointGroup/RHEL6-STIG/issues/27#issuecomment-134373242.

I'll need to do some experimentation with this.

Need to check to see if exim gets installed if postfix is installed prior to reinstalling cronie
Will evaluate the possibility of using rpm with --no-deps

Thanks for bringing this up

I just dug into this a bit and I think I've nailed down the behavior. cronie requires either sendmail or postfix since the postfix package also installs /usr/sbin/sendmail. Here is cronie's deplist:
sdoran@stigtest-cos6 ~> yum deplist cronie
Loaded plugins: fastestmirror
Finding dependencies:
Loading mirror speeds from cached hostfile
 * base: mirror.vtti.vt.edu
 * extras: mirror.atlanticmetro.net
 * updates: mirror.ash.fastserv.com
package: cronie.x86_64 1.4.4-15.el6
...
  dependency: /usr/sbin/sendmail
   provider: sendmail.x86_64 8.14.4-9.el6
   provider: postfix.x86_64 2:2.6.6-6.el6_5
...

If neither sendmail nor cronie are installed, installing cronie will install postfix to satisfy the dependency (exim comes from EPEL; this was run without EPEL configured as another repo) :
sdoran@stigtest-cos6 ~> sudo yum install cronie
Loaded plugins: fastestmirror
Setting up Install Process
Loading mirror speeds from cached hostfile
 * base: mirror.vtti.vt.edu
 * extras: mirror.atlanticmetro.net
 * updates: mirror.ash.fastserv.com
Resolving Dependencies
--> Running transaction check
---> Package cronie.x86_64 0:1.4.4-15.el6 will be installed
--> Processing Dependency: dailyjobs for package: cronie-1.4.4-15.el6.x86_64
--> Processing Dependency: /usr/sbin/sendmail for package: cronie-1.4.4-15.el6.x86_64
--> Running transaction check
---> Package cronie-anacron.x86_64 0:1.4.4-15.el6 will be installed
--> Processing Dependency: crontabs for package: cronie-anacron-1.4.4-15.el6.x86_64
---> Package postfix.x86_64 2:2.6.6-6.el6_5 will be installed
--> Running transaction check
---> Package crontabs.noarch 0:1.10-33.el6 will be installed
--> Finished Dependency Resolution

If sendmail and cronie were explicitly installed (not postfix), then removing sendmail will remove cronie. This is the situation @mliudev is reporting.
sdoran@stigtest-cos6 ~> rpm -qa | grep -E "(postfix|cronie|sendmail)"
cronie-1.4.4-15.el6.x86_64
cronie-anacron-1.4.4-15.el6.x86_64
sendmail-8.14.4-9.el6.x86_64

sdoran@stigtest-cos6 ~> sudo yum erase sendmail
Loaded plugins: fastestmirror
Setting up Remove Process
Resolving Dependencies
--> Running transaction check
---> Package sendmail.x86_64 0:8.14.4-9.el6 will be erased
--> Processing Dependency: /usr/sbin/sendmail for package: cronie-1.4.4-15.el6.x86_64
--> Running transaction check
---> Package cronie.x86_64 0:1.4.4-15.el6 will be erased
--> Processing Dependency: cronie = 1.4.4-15.el6 for package: cronie-anacron-1.4.4-15.el6.x86_64
--> Running transaction check
---> Package cronie-anacron.x86_64 0:1.4.4-15.el6 will be erased
--> Processing Dependency: /etc/cron.d for package: crontabs-1.10-33.el6.noarch
--> Restarting Dependency Resolution with new changes.
--> Running transaction check
---> Package crontabs.noarch 0:1.10-33.el6 will be erased
--> Finished Dependency Resolution

If cronie, postfix, and sendmail are all installed, then removing sendmail does not remove cronie. I believe this is the most desirable situation:
sdoran@stigtest-cos6 ~> rpm -qa | grep -E "(postfix|cronie|sendmail)"
cronie-1.4.4-15.el6.x86_64
cronie-anacron-1.4.4-15.el6.x86_64
sendmail-8.14.4-9.el6.x86_64
postfix-2.6.6-6.el6_5.x86_64

sdoran@stigtest-cos6 ~> sudo yum erase sendmail
Loaded plugins: fastestmirror
Setting up Remove Process
Resolving Dependencies
--> Running transaction check
---> Package sendmail.x86_64 0:8.14.4-9.el6 will be erased
--> Finished Dependency Resolution

I believe the best way to fix this is to ensure postfix is installed prior to hitting this task. The question then becomes where should postfix be installed? Prelim tasks, or immediately prior to V-38671? Immediately prior to V-38671 will work, currently and after the refactor when tasks are ordered by vuln ID. I'll submit a PR that has the task immediately before V-38671 unless I hear otherwise.

Thanks for looking into this. Your findings are consistent with mine. I have been working around this by installing postfix prior to running this role. Thanks for fixing this.


Add option to add error breadcrumb in sentry log

When using pkg/errors a problem we keep encountering is that sentry truncates the error message, which removes relevant information that has been annotated on the error via Wrapf. I looked into adding this into the StackTraceFrame but it would include a mountain of changes including ones upstream in raven-go.
This instead adds a new option IncludeErrorBreadcrumb which when true will add a breadcrumb to the sentry report that includes the verbose print of the error. When using pkg/errors this gives you a full trace including the annotations.
Totally understand if this isn't something you want to merge but leaving this here as maybe it will be useful to others. The "right" way to do this is to annotate each StackTraceFrame with vars in the cases where there is an annotation. This would require tweaking pkg/errors to get at the error message at that level (and not only the recursive error message) and tweaking getsentry/raven-go to let us set vars on a StackTraceFrame.

Thanks! 🍞
Note: https://github.com/evalphobia/logrus_sentry/releases/tag/v0.8.2


Bump GraphQL.NET to 8.0.2

Pull Request Test Coverage Report for Build<PHONE_NUMBER>6
Details

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

Totals

Change from base Build<PHONE_NUMBER>5:
0.0%

Covered Lines:
1875

Relevant Lines:
1934

💛  - Coveralls


add sql server (T-SQL) support

Codecov Report
Patch coverage: 45.90% and project coverage change: -0.33% :warning:

Comparison is base (029da8d) 81.21% compared to head (32eed38) 80.88%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##           master     #112      +/-   ##
==========================================
- Coverage   81.21%   80.88%   -0.33%
==========================================
  Files          46       46
  Lines        5520     5567      +47
  Branches     1357     1368      +11
==========================================
+ Hits         4483     4503      +20
- Misses        792      818      +26
- Partials      245      246       +1

Files Changed
Coverage Δ

metrics_layer/core/sql/query_design.py
87.19% <ø> (-0.07%)
:arrow_down:

metrics_layer/core/parse/connections.py
43.75% <17.24%> (-5.23%)
:arrow_down:

metrics_layer/core/model/field.py
82.97% <46.15%> (-0.39%)
:arrow_down:

metrics_layer/cli/seeding.py
56.95% <71.42%> (+0.42%)
:arrow_up:

metrics_layer/core/model/definitions.py
100.00% <100.00%> (ø)

metrics_layer/core/sql/query_dialect.py
100.00% <100.00%> (ø)

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


zooming with scroll-wheel

https://stackoverflow.com/questions/11551049/matplotlib-plot-zooming-with-scroll-wheel

Done with v10


Version catalog prevents locking of settings plugins

Summary
--write-locks does not write the classpath configuration to settings-gradle.lockfile when a version catalog is defined (either implicit gradle/libs.versions.toml or explicit).
Expected behavior
gradle --write-locks should write the classpath configuration (plugin dependencies) to settings-gradle.lockfile.
A subsequent execution without --write-locks/--update-locks should happily run as versions are expected to be locked (even with LockMode.STRICT).
Actual behavior
gradle --write-locks does not write the classpath configuration (plugin dependencies) to settings-gradle.lockfile, and instead produces the output described at #21101 which does not contain the classpath configuration.
A subsequent execution without --write-locks/--update-locks will complain (because we run with LockMode.STRICT).
Reproduction steps

In a separate prerequisite build, publish a Plugin<Settings> plugin with maven-publish

Prerequisite Settings plugin
// corporate-plugin-project/build.gradle.kts
plugins {
    `java-gradle-plugin`
    `maven-publish`
}
group = "corporate"
version = "0.0.1-SNAPSHOT"
publishing {
    repositories {
        maven("file:///c:/Temp/repo")
    }
}
gradlePlugin {
    plugins {
        register("foo") {
            id = "corporate.settings"
            implementationClass = "corporate.SettingsPlugin"
        }
    }
}

// corporate-plugin-project/src/main/java/corporate/SettingsPlugin.java
package corporate;

import org.gradle.api.Plugin;
import org.gradle.api.initialization.Settings;
import org.gradle.api.logging.Logger;
import org.gradle.api.logging.Logging;

public class SettingsPlugin implements Plugin<Settings> {

    private final Logger logger = Logging.getLogger(SettingsPlugin.class);

    @Override
    public void apply(Settings target) {
        logger.lifecycle("Applied {}", SettingsPlugin.class.getName());
    }
}

Create a new build using the above plugin and strict locking:

settings.gradle.kts
// settings.gradle.kts
pluginManagement {
    repositories {
        gradlePluginPortal()
        maven("file:///c:/Temp/repo") {
            name = "corporate"
        }
    }
}
buildscript {
    configurations.classpath {
        resolutionStrategy.activateDependencyLocking()
    }
    dependencyLocking.lockMode.set(LockMode.STRICT)
}
plugins {
    id("corporate.settings") version "0.0.1-SNAPSHOT"
}

rootProject.name = "gradle-settings-locking"

Create an empty gradle/libs.versions.toml file
Execute gradle --write-locks to create settings-gradle.lockfile
Execute gradle

Note: the symptom appears also when using a non-default version catalog (i.e. with explicit declaration)
Environment

Gradle 7.6 (this also happens with 8.0-rc-2)

Thank you for providing a valid reproducer.
The issue is in the backlog of the relevant team but this area of Gradle is currently not a focus one so it might take a while before a fix is made.


Sort imports using isort

Imports are currently ordered somewhat haphazardly: they are not always grouped by type (system, third-party, cvxpy), they are not always in alphabetical order, multiple from imports from the same library are not grouped, &c.
This PR applies isort to the entire cvxpy project to produce a consistent import ordering.
Though large, the PR consists entirely of auto-generated changes achieved by running
isort --up --tc .

in the project root.

Can we try to get this merged? I fixed the merge conflicts but probably still needs work.

@SteveDiamond @r-barnes I have made some fixes to this branch. What's the best way to bring these in? For now, I have created a PR in @r-barnes' fork: https://github.com/r-barnes/cvxpy/pull/1/files

Ok I kind of screwed up this PR by merging in the typing PR, now there are conflicts everywhere. Maybe we can close this and just rerun isort --up --tc .?


[No QA] Improve network test to use Onyx values

Details
Following up on an older follow up issue / promise I created to improve the Network tests. Basically, we should be testing Onyx data and not only how many times a method has been called.
Fixed Issues
Fixes https://github.com/Expensify/Expensify/issues/154745
Tests
Automated
QA Steps
No QA
Tested On

[x] Web
[x] Mobile Web
[x] Desktop
[x] iOS
[x] Android

Screenshots

Web

Mobile Web

Desktop

iOS

Android

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.


ng2TelInputOptions isn't passed along

Why did you stop passing along ng2TelInputOptions to intl-tel-input on the last commit? Makes it pretty hard to work with this wrapper.

Any updates on this? There's no way of setting the initial options for intl-tel-input.

Has this been fixed?

@gauravsoni119  any updates on the pull request?

Can you please merge? I need this feature as well!


Topic icon: fa-balance-scale

Unable to get fa-balance-scale to display as a topic icon:
http://fortawesome.github.io/Font-Awesome/icon/balance-scale/

are you setting the value to "fa fa-balance-scale" ? you need that extra "fa" in there.

That is what it's set to right now, but still no scales. http://aashe-hub-dev.herokuapp.com/admin/metadata/sustainabilitytopic/6/

Ok, I'm seeing the issue. fa-balance-scale was created in Font Awesome version 4.4 and Unity v1.8 uses 4.2
I'll work on updating to Unity 1.9 to get this in there.

Ok, I've updated the theme, so it's in there now;


[4.0] Filter out 0-length tokens when generating syntax model nodes.

swift::tokenize() with TokenizeInterpolatedString set to true produces an empty string literal token between directly adjacent interpolations, e.g. in "\(1)\(1)". The syntax model relies upon it to determine whether the next left paren is a string interpolation anchor or not, but there is no need to to include a corresponding empty SyntaxNode in the syntax model. 0-length syntax nodes don't really make sense and may break assumptions in client SyntaxModelWalkers.

Resolves rdar://problem/33601932.

@swift-ci Please test


Update

Coverage remained the same at 85.863% when pulling 576182e4e7d6fd19a7f22336521eec473919e47a on fix/travis_yaml into c861575bf6844919ec06cf3d3eb998ee81f99108 on master.


Example code allows port set to 0, but precondition in publishPhaseTwo requires port > 0

The example code specifies .listenForConnections which makes NetService listen on a port assigned by the OS. That port is then used for the advertisements. You can't specify port 0 without .listenForConnections, as you've discovered.

Thanks.  I backed away from that configuration because when I try to use BlueSocket to listen on the assigned port, it gives me an "Address already in use" error.  I'm following up with the author of that package.


bounding box information

Hello,
Thanks for open-sourcing the dataset. May I ask a few questions about the bounding box information?
First, in the json files, what does height, width, x and y stand for? E.g., does x and y stand for the middle point of the bounding box or the left upper corner?
Second, how can I find the overall width and height of the document? (This information is to normalize the bounding box coordinates between [0, 1])
Thanks.

For the first question, the (x, y) is the left upper corner. For the second question, the overall width and height can be found by looking at the root element (the element with the smallest id).


Code re-organization and registry improvements

https://github.com/alan-turing-institute/MLJBase.jl/issues/495
#355

waiting on https://github.com/JuliaRegistries/General/pull/28937

waiting on https://github.com/JuliaRegistries/General/pull/28937


Add extra classes to the main layout and sidebar components

This PR adds some additional classes to the main layout and sidebar components where there were a few gaps, I think due to the elements not being their own components so not receiving classes in the previous PR?
For example there's a filament-sidebar-footer class, but no filament-sidebar-header, and none of the main elements within filament-app-layout have a class, which leaves them quite tricky to target still.
The additional classes (in bold) are:

filament-app-layout

filament-sidebar-close
filament-main

filament-main-header

filament-sidebar-open
filament-breadcrumbs

filament-main-content
filament-main-footer

filament-sidebar

filament-sidebar-header
filament-sidebar-nav
filament-sidebar-footer

I'm sure you'll want to tweak some of the naming.

Cool, only a couple of tweaks. Thanks!


Finding assoc. With type1 query

Type1 query needs to be sth more than just 'bout gaining knowledge.

Just looks for more phrases containing the keywords (not synonyme-like) and 'OH. And I suppose (with nsyn) that snow is white, also' or 'Didn't know that, but I know it's [something here] also.'. Or 'Wow, that's interesting. Didn't know about it.   '.


Alpine for ARM

I'm using alpine:latest as base image, and run container on Raspberry Pi 2(armv7l). But error occured when trying to shell into container,
$ sudo docker exec -it myalpine sh
exec format error

it's due to /bin/sh is built for Linux x86_64 I guess.
So, any idea on supporting alpine for ARM?

There is a docker hub image at armhf/alpine.

It would be nice if the hub supported multi-arch registries.  I made some comments in that direction, but nothing close to filing a bug yet.
Ideally, something like the below would allow an armhf and x86_64 architecture to both build from the same Dockerfile, in some imaginary future version of the Docker registry:
FROM scratch
ENV ALPINE_VERSION 3.5.0
ADD alpine-minirootfs-${ALPINE_VERSION}-${DOCKER_ARCH}.tar.gz /

Right now, the Hub only knows images by name and tag--it doesn't know about architecture--so no such thing will work, unfortunately.

I'll leave this open for now. But I think the limitations have already been mentioned before:

Docker Hub (and other registries as far as I know) don't provide a way to distinguish architecture for a single repository (though, we could just as well have a special tag for arm).
There aren't any arm builders for either Docker Hub or CircleCI. We'd need some way to automate the building of arm images.

+1 for official alpine image multi-arch support.
Debian and Ubuntu both already have this.

Docker Hub provides a system for official docker-library maintainers to distribute multi-arch images. When we submit an update to the docker-library repo, we can specify alternate architectures which will then get pushed to the appropriate organization on Docker Hub.
See https://github.com/docker-library/official-images#multiple-architectures
For example, the debian image specifies multiple architectures in this file, which then get pushed to the docker hub organizations amd64, armv7, armv5, i386, etc
The amd64 organization on Docker Hub is effectively the same as the regular library org, which is why Alpine is currently in both.

As far as actually building the images, all you need to do is change the --arch flag on apk fetch alpine-base to the arch you are building. See builder/scripts/mkimage-alpine.bash
Since we're not actually compiling anything, just downloading some files, it seems fairly simple to add multi-arch to the build proccess, if I'm not mistaken. I think this should also work on any builder architecture (even an x86_64 based CircleCI or Docker Hub builder).
The last step would be to change the library spec file generator here to include the architectures we support.
@andyshinn If this sounds good to you, I'll start working on a PR
The last decision would probably be whether the gliderlabs images would want multiarch. This would probably be more complicated because there isn't a great place to put them.

We've completed the first release for multi-arch alpine. See #352.


move to react 16.14.0

fixes builds on node 16.x due to nivo issue

addressed in https://github.com/hyperledger-labs/firefly-ui/pull/37


jsonnet: add output with html documentation

Motivation for this change
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Relase notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

@ofborg eval
(Sorry, ofborg's certs recently had an issue, meaning that it was unable to
react to PRs. This has been fixed, but all PRs filed in this period will need
ofborg to be manually kicked off.)

Just curious, can I order @ofborg too?

Yep, everybody can, whether or not they're part of the NixOS organization. https://github.com/NixOS/ofborg#commands


S3 Async Errors

When calling the async version of several functions in S3, I get a "pure virtual function called" error. I get this from PutObject, DeleteObject, and ListObjects. There might be more, as these are the only functions I have tested. The synchronous versions work fine for me.

We've just tested this on latest. What platform are you using? Can we see build output?

I'm building on a EC2 t2.small ubuntu instance.
-- Found Git: /usr/bin/git (found version "1.9.1")
-- TARGET_ARCH not specified; inferring host OS to be platform compilation target
-- Generating linux build config
-- Building AWS libraries as static objects
-- Http client: Curl
-- Encryption: Openssl
-- The C compiler identification is GNU 4.8.4
-- The CXX compiler identification is GNU 4.8.4
-- 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
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Install binary prefix: linux/intel64
-- Considering ec2
-- Considering elasticloadbalancing
-- Considering s3
-- Considering rds
-- Considering route53
-- Considering cloudfront
-- Considering rds
-- Considering logs
Updating version info to 0.13.14
-- Custom memory management disabled
-- Configuring done
-- Generating done
-- Build files have been written to: /home/ubuntu/colossi-servers/cpp/aws-sdk-cpp/build

Can you try building with gcc 4.9?

Just built with 4.9.3. The pure virtual function error is gone, but is replaced by a segfault, similar to my other issues:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffee7ae700 (LWP 15538)]
0x0000000000000000 in ?? ()
(gdb) bt
#0  0x0000000000000000 in ?? ()
#1  0x0000000000ffcd1d in Aws::S3::S3Client::ListObjectsAsyncHelper(Aws::S3::Model::ListObjectsRequest const&, std::function<void (Aws::S3::S3Client const*, Aws::S3::Model::ListObjectsRequest const&, Aws::Utils::Outcome<Aws::S3::Model::ListObjectsResult, Aws::Client::AWSErrorAws::S3::S3Errors > const&, std::shared_ptr<Aws::Client::AsyncCallerContext const> const&)> const&, std::shared_ptr<Aws::Client::AsyncCallerContext const> const&) const ()
#2  0x00007ffff5b36350 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#3  0x00007ffff724f182 in start_thread (arg=0x7fffee7ae700) at pthread_create.c:312
#4  0x00007ffff52be47d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Looks like it might be a null object.  Any further gdb info you can give?

What's the easiest way to compile with debugging symbols?

-DCMAKE_BUILD_TYPE=Debug

After compiling with debug symbols, here is a more complete stack trace:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffee7ae700 (LWP 29366)]
0x00007ffff5b691b6 in std::string::compare(std::string const&) const () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
(gdb) bt
#0  0x00007ffff5b691b6 in std::string::compare(std::string const&) const () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#1  0x00000000016e91f9 in std::operator< <char, std::char_traits, std::allocator > (__lhs=..., __rhs=...) at /usr/include/c++/4.9/bits/basic_string.h:2590
#2  0x0000000001ae462d in std::lessstd::string::operator() (this=0x7fffee7adcd8, __x=<error reading variable: Cannot access memory at address 0x20>, __y="")
at /usr/include/c++/4.9/bits/stl_function.h:371
#3  0x0000000002094e45 in std::_Rb_tree<std::string, std::pair<std::string const, std::string>, std::_Select1st<std::pair<std::string const, std::string> >, std::lessstd::string, std::allocator<std::pair<std::string const, std::string> > >::_M_get_insert_hint_unique_pos (this=0x7fffee7adcd8, __position=..., __k="")
at /usr/include/c++/4.9/bits/stl_tree.h:1543
#4  0x00000000022d29ac in std::_Rb_tree<std::string, std::pair<std::string const, std::string>, std::_Select1st<std::pair<std::string const, std::string> >, std::lessstd::string, std::allocator<std::pair<std::string const, std::string> > >::_M_emplace_hint_unique<std::piecewise_construct_t const&, std::tuplestd::string&&, std::tuple<> >(std::_Rb_tree_const_iterator<std::pair<std::string const, std::string> >, std::piecewise_construct_t const&, std::tuplestd::string&&&&, std::tuple<>&&) (
this=0x7fffee7adcd8, __pos=...) at /usr/include/c++/4.9/bits/stl_tree.h:1794
#5  0x00000000022d2861 in std::map<std::string, std::string, std::lessstd::string, std::allocator<std::pair<std::string const, std::string> > >::operator (this=0x7fffee7adcd8, __k=<unknown type in /home/ubuntu/colossi-servers/cpp/worker/Worker.exe, CU 0x5f60b72, DIE 0x5f6c842>) at /usr/include/c++/4.9/bits/stl_map.h:519
#6  0x000000000230c5db in Aws::Http::Standard::StandardHttpRequest::SetHeaderValue (this=0x7fffee7adc60, headerName="", headerValue="")
at /home/ubuntu/colossi-servers/cpp/aws-sdk-cpp/aws-cpp-sdk-core/source/http/standard/StandardHttpRequest.cpp:59
#7  0x00000000021b04f0 in Aws::S3::S3Client::ListObjectsAsyncHelper(Aws::S3::Model::ListObjectsRequest const&, std::function<void (Aws::S3::S3Client const*, Aws::S3::Model::ListObjectsRequest const&, Aws::Utils::Outcome<Aws::S3::Model::ListObjectsResult, Aws::Client::AWSErrorAws::S3::S3Errors > const&, std::shared_ptr<Aws::Client::AsyncCallerContext const> const&)> const&, std::shared_ptr<Aws::Client::AsyncCallerContext const> const&) const (this=0x7fffffffdfd0, request=..., handler=...,
context=std::shared_ptr (empty) 0x0) at /home/ubuntu/colossi-servers/cpp/aws-sdk-cpp/aws-cpp-sdk-s3/source/S3Client.cpp:1307
#8  0x00000000021b0367 in Aws::S3::S3Client::<lambda()>::operator()(void) const (__closure=0x3092ab0)
at /home/ubuntu/colossi-servers/cpp/aws-sdk-cpp/aws-cpp-sdk-s3/source/S3Client.cpp:1302
#9  0x00000000021ea354 in std::_Bind<Aws::S3::S3Client::ListObjectsAsync(const Aws::S3::Model::ListObjectsRequest&, const ListObjectsResponseReceivedHandler&, const std::shared_ptr&) const::<lambda()>()>::__call(<unknown type in /home/ubuntu/colossi-servers/cpp/worker/Worker.exe, CU 0x58d9e13, DIE 0x5b397f8>, std::_Index_tuple<>) (this=0x3092ab0, __args=<unknown type in /home/ubuntu/colossi-servers/cpp/worker/Worker.exe, CU 0x58d9e13, DIE 0x5b397f8>)
at /usr/include/c++/4.9/functional:1264
#10 0x00000000021e3c68 in std::_Bind<Aws::S3::S3Client::ListObjectsAsync(const Aws::S3::Model::ListObjectsRequest&, const ListObjectsResponseReceivedHandler&, const std::shared_ptr&) const::<lambda()>()>::operator()<, void>(void) (this=0x3092ab0) at /usr/include/c++/4.9/functional:1323
#11 0x00000000021d7bb5 in std::_Function_handler<void(), std::_Bind<Aws::S3::S3Client::ListObjectsAsync(const Aws::S3::Model::ListObjectsRequest&, const ListObjectsResponseReceivedHandler&, const std::shared_ptr&) const::<lambda()>()> >::_M_invoke(const std::_Any_data &) (__functor=...)
at /usr/include/c++/4.9/functional:2039
#12 0x0000000002319a26 in std::_Bind_simple<std::function<void ()> ()>::_M_invoke<>(std::_Index_tuple<>) (this=0x3092c98) at /usr/include/c++/4.9/functional:1700
#13 0x000000000231996b in std::_Bind_simple<std::function<void ()> ()>::operator()() (this=0x3092c98) at /usr/include/c++/4.9/functional:1688
#14 0x00000000023198e8 in std::thread::_Impl<std::_Bind_simple<std::function<void ()> ()> >::_M_run() (this=0x3092c80) at /usr/include/c++/4.9/thread:115
#15 0x00007ffff5b36350 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#16 0x00007ffff724f182 in start_thread (arg=0x7fffee7ae700) at pthread_create.c:312
#17 0x00007ffff52be47d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111
The lowest level that is still in Aws is #6, which corresponds to the following line:
headerMap[StringUtils::ToLower(headerName.c_str())] = StringUtils::Trim(headerValue.c_str());
both headerName and headerValue are empty strings.

I also just tried printing headerMap in gdb, and it responded with:
$6 = std::map with<PHONE_NUMBER>17440 elements<error reading variable: Cannot access memory at address 0x18>

Encounter a similar "rb_tree" related error building with g++ 6.2


Update Composer dependencies (2021-02-05-00-06)

Visual regression test passed!
View the visual regression test report


Allow choosing a protocol for Serverless NEGs

It is possible to enable HTTP/2 between GLB and serverless network endpoints. This PR makes the necessary change that allows setting protocol, so HTTP/2 can be chosen for GLB <> Serverless NEG communication.

@cagataygurturk Would you mind fixing the formatting error?

@cagataygurturk Are you sure setting the protocol is actually required for serverless NEGs?
In the documentation, it says the "protocol" parameter is ignored for serverless NEGs and some internal investigation seems to confirm that.

@cagataygurturk Are you sure setting the protocol is actually required for serverless NEGs?
In the documentation, it says the "protocol" parameter is ignored for serverless NEGs and some internal investigation seems to confirm that.

Can you point out exactly where in that document it is stated that protocol is ignored? Both the API and Console allows protocol selection with NEGs and I couldn't find any information about protocol being ignored, hence I sent this PR.

Then this PR goes to trash :) Thanks!

@cagataygurturk Thanks for contributing though and sorry for not catching this earlier.


Example task 2

Description
Duration: 2
Dependencies:

#1

⚠ This task is in the critical path
🎉 The task has no delays


From Ed Lavender on gear types (4)

"Temporal variation. There are some surveys for which gear types have changed through time. For example, in the NS-IBTS data, I think various gears were used until the early 1980s before the GOV 36/47 gradually became standard. But all data for the NS-IBTS (1967–2020) is simply listed as GOV. Looking at your code, I think this is because you have focused on GOV trawls or the most common gear type. Is this also the case for the other surveys (e.g, GSL-N where only ‘Chalut de font’ is recorded)? "

I indeed constrained to GOV because it's the most standard for NS-IBTS, but I don't think this is the case for GSL. I'll let others respond @mpinsky @zoekitchel

For GSL-N, see comments under #10

Info was included for GSL-N. Is the info the same for GSL-S?

GSL-S is separate. I believe it already has gear recorded?

Hmmmmmm, you are right, the info is in the PDF but, the gsl-s.pdf does not match the gsl-s.Rmd file. Anyone knows why this is? I can just update one with the other, but wanna make sure before doing it

GSL-S and GSL-N are different trawl surveys, one is North and the other one is South, and I believe we have to even sub-separate one of the two regions because of separate sub-surveys with different levels of taxonomic identifications, @zoekitchel ?

Nevermind. I didn't realize the gsl-s.Rmd file of the summary folder called the cleaning script get_gsl-s.R before rendering. Is all good.


No custom scope for template literal tags

TS and JS Grammar Extension version:  0.0.49 / latest
Code
// Please include a code snippet that demonstrates the issue
styled.div``

div here has scope
variable.other.property.ts
meta.var.expr.tsx
source.tsx

It would be nice if it had a custom scope similar to a function call which has the scope
entity.name.function.ts
meta.function-call.ts
meta.var.expr.tsx
source.tsx

I just discovered that
div``

do get a custom scope, it's just when having a member access that this fails


fix: explicitely execute the npm scripts with node

This fixes the issue that the scripts can not be run on Windows.

Bump.


Remove the obsolete, prefix-based CODEOWNERS matcher & related tests

A follow-up to:

https://github.com/Azure/azure-sdk-tools/pull/5088

With this PR, now only the new, regex-based, wildcard-supporting CODEOWNERS matcher is present in the codebase.
This PR also:

removes the obsolete ProgramSimplePathTests class;
renames ProgramGlobPathTests to RetrieveCodeOwnersProgramTests;
updates comments to remove mentions of the old, prefix-based matcher;
makes few comment improvements to classes testing the new matcher;
removes obsolete tests from get-codeowners.ps1.
Related PR:
https://github.com/Azure/azure-sdk-tools/pull/5103

This PR contributes to:

https://github.com/Azure/azure-sdk-tools/issues/2770

The following pipelines have been queued for testing:java - templatejava - template - testsjs - templatenet - templatenet - template - testspython - templatepython - template - tests You can sign off on the approval gate to test the release stage of each pipeline. See eng/common workflow

Note to self: revert deletion of simple path tests; instead, update/refactor. This is because glob path and simple path are two separate execution path in codebase. Current glob path tests always use target path of /**.

The following pipelines have been queued for testing:java - templatejava - template - testsjs - templatenet - templatenet - template - testspython - templatepython - template - tests You can sign off on the approval gate to test the release stage of each pipeline. See eng/common workflow

/check-enforcer override


Session refactoring

replaces #934 by making possible to override the default bags, but more importantly, it removes the storage definition from the inside of the session one to the outside.

:+1:  thanks!


Add support for InternLM

add support for https://github.com/InternLM/InternLM
generate result in cczhong/internlm-chat-7b-4bit-gptq and we can use as expected.

so when I use safetensor to save, I met ValueError: QuantLinear() does not have a parameter or a buffer named weight. problem when I load them, do you have idea why?


ProductAttributeValue._set_value fails with unicode value and attribute.type == OPTION

AbstractProductAttributeValue._set_value has faulty logic.
The block in question
    def _set_value(self, new_value):
        if self.attribute.is_option and isinstance(new_value, str):
            # Need to look up instance of AttributeOption
            new_value = self.attribute.option_group.options.get(
                option=new_value)

isinstance(u'Test', str) == False
We need to use
from django.utils.six import string_types
...
    def _set_value(self, new_value):
        if self.attribute.is_option and isinstance(new_value, string_types):
            # Need to look up instance of AttributeOption
            new_value = self.attribute.option_group.options.get(
                option=new_value)

Got bit by this. :(

I searched the code base for isinstance\([^,]+, ?str\) and didn't find any other matches, so that's good at least.
Is there already an automated tool to look for these sorts of errors? Lint?


describe a programming workflow for ADRS (6h)

goal: describe a first draft functional workflow for ADRS similar to ADVS
2h meeting
1h review
1h finalize in a flow chart
the workflow should address:
functionality
order of variables

hi all, this can be closed as it will move to {admiral.onco} TA package extension which we'll be working on 1H22.


Add buffer mode to MatSlider

Feature Description
Introduce a buffer mode to MatSlider, similar to the one already available in MatProgressBar
Use Case
In most video or audio streaming players it may be required to show the amount of buffer being downloaded during the playback. Adopting a progress bar isn't enough because the user needs to be able to seek back and forth in the media, which requires a slider. I'm suggesting a slider bar with the ability to draw a buffer line, with a customizable color.

I don't see us adding this feature unless it were added to the Material Design spec.


Does Atom have an opinion on the future of Coffeescript?

Hi guys,
A quick heads up that there's a pretty active discussion going on over at coffeescript6/discuss about possible next steps for Coffeescript.
Thought you might want to comment, given Atom is a heavy Coffeescript user. Discussed issues are here.
There's also a survey that's relevant to you: Survey for devs/teams with maintained Coffescript codebases: happy with CS, or considering migrating?

I am not an official member of the Atom team.
However, the current strategy appears to be that when new files are checked into the codebase, those should be written in ES6.  No more Coffeescript files should be added.
Existing coffeescript files may be converted to ES6 when they undergo a major rewrite.
/cc @lee-dohm
Also, we're trying to control the amount of Issues that we have to triage and track. For general questions, the Atom message board is where you'll probably be able to find answers faster.

Only suggestion I'll make is that you swap the freakin' of and in operators the other way around so devs won't keep confusing the two when flipping between CoffeeScript and ES6.
Ｐ Ｌ Ｅ Ａ Ｓ Ｅ

@Alhadis You can use for...of in ES6: for...of

@Haggus That's my point. for...of does something different in CoffeeScript, which is what for...in does in JavaScript. It drives me insane.

What @50Wliu said was right on the nose. 👍


remove response

closes https://github.com/Azure/azure-sdk-for-cpp/issues/1343
Pull Request Checklist
Please leverage this checklist as a reminder to address commonly occurring feedback when submitting a pull request to make sure your PR can be reviewed quickly:
See the detailed list in the contributing guide.

[x] C++ Guidelines
[x] Doxygen docs
[x] Unit tests
[x] No unwanted commits/changes
[x] Descriptive title/description

[x] PR is single purpose
[x] Related issue listed

[x] Comments in source
[x] No typos
[x] Update changelog
[x] Not work-in-progress
[x] External references or docs updated
[x] Self review of PR done
[x] Any breaking changes?

/azp run cpp - storage


Update dune_radiological_model.fcl

radiological modules for produnevd added: protodunevd_39ar, protodunevd_42ar, protodunevd_85kr and protodunevd_222rn

I checked the geometrical coordinates and it looks good to me.


Update eslint and lint all existing files

Todo

Use Airbnb eslint config
Use next/core-web-vitals
Use react/recommended
Plugins for React and typescript-eslint
After the setup run yarn lint-fix
Fix all eslint errors and push all the updated files to a new refactor branch

Can i work on this?


Fix prefix issue as pointed out by @jakirkham

fixes issue #1 on this feedstock

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

The recipe must have some tests.


Update EPOCHS_DONE in training trace after every epoch

closes #171

I do not think so, it is not really an epoch. What should be the value anyways? 0, 1? Next, the model is not modified yet so I do not want to list this training unless -a is specified.

Is it ready to be merged then?


run and build error in orangepi 3B

devices:  orangepi 3B
os: ubuntu 22.04
After I install flutter-elinux and create a sample flutter project.
And Got error when run  flutter-elinux build elinux --target-backend-type=x11  or  flutter-elinux run -d  elinux-x11

And my OS only support x11
env | grep -E "DISPLAY|SWAY|XDG_SESSION_TYPE"
XDG_SESSION_TYPE=x11 DISPLAY=:0.0
And flutter-elinux devices shows elinux-x11  device.
Flutter assets will be downloaded from https://storage.flutter-io.cn. Make sure you trust this source!
Found 3 connected devices:
  Linux (desktop)  • linux          • linux-arm64    • Orange Pi 1.0.4 Jammy 5.10.160-rockchip-rk356x
  eLinux (desktop) • elinux-wayland • flutter-tester • Orange Pi 1.0.4 Jammy 5.10.160-rockchip-rk356x
  eLinux (desktop) • elinux-x11     • flutter-tester • Orange Pi 1.0.4 Jammy 5.10.160-rockchip-rk356x

Run "flutter emulators" to list and start any available device emulators.

If you expected another device to be detected, please run "flutter doctor" to diagnose potential issues. You may also try increasing the time to wait for connected devices
with the "--device-timeout" flag. Visit https://flutter.dev/setup/ for troubleshooting tips.

You are lacking libstd++ for clang14
'sudo apt install libstdc++-12-dev`


Typo in introduction section

[Enter feedback here]
Typo in introduction section -> "It can help your in understanding if your..."

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

ID: 878f02f6-0a9a-a7c2-0ec6-afad85e2c2a4
Version Independent ID: 16344e53-0446-6081-fad8-d07d87a512a6
Content: Introduction to Network Configuration Diagnostics in Azure Network Watcher
Content Source: articles/network-watcher/network-watcher-network-configuration-diagnostics-overview.md
Service: network-watcher
GitHub Login: @damendo
Microsoft Alias: damendo

@DarkKnightAnk, Appreciate your patience. The doc has been edited accordingly and it would take some time for the changes to get reflect over the doc.
We are closing this issue for now. If there are further questions regarding this matter, please reply and we will gladly continue the discussion.


fix: rename NumKeyColumns to PrimaryKeyIndexes

Which issue does this PR close?
Closes #419
Rationale for this change
NumKeyColumns is no longer useful anymore, and should be removed.
What changes are included in this PR?
I add a new struct Indexes  to hold the primary key indexes.
Are there any user-facing changes?

none
How does this change test

use unit test. in test_build_from_arrow_schema

@dust1 Please update PR's description to tell us how you test this, and if there are any user changes.

@dust1 I realize this is a breaking change, you need update target branch to https://github.com/CeresDB/ceresdb/tree/breaking-changes.
Main doesn't accept breaking change now.

ok

Oops. I can't find the Settings in this pr to modify the target branch, I may need to recreate a pr

I think this PR is ready for merge, I will push some minor changes.
Thanks @dust1