text:
chore(deps): update module github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper to v1.42.6

This PR contains the following updates:

Package
Type
Update
Change

github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper
require
patch
v1.42.5 -> v1.42.6

Release Notes

terraform-ibm-modules/ibmcloud-terratest-wrapper (github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper)
v1.42.6
Compare Source
Bug Fixes

deps: update module github.com/gruntwork-io/terratest to v0.48.1 (#905) (511dc17)

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

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

This PR has been generated by Renovate Bot.

ℹ Artifact update notice
File name: tests/go.mod
In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

1 additional dependency was updated

Details:

Package
Change

github.com/gruntwork-io/terratest
v0.48.0 -> v0.48.1

/run pipeline


text:
go mod tidy

The update was made by the renovate bot, but in reality that version was never used, because no import paths were updated.
I turned off the renovate bot for that reason, to prevent similar messy upgrades in the future. We can turn it back on at some point, but someone will need to investigate configuration and whether it's even possible for the bot to update import paths.

@radeksimko should we run go mod vendor?

@appilon  go mod vendor doesn't really change anything - I tried.

source: gharchive/pull-request

authors: appilon radeksimko

license: MIT

license_type: permissive

license_source: github-api


text:
Request: Defining Custom material properties in the blueprints

When using the custom isotopics within the blueprints file it allows a user to specify number densities or mass fractions with some specified density for defining the initial composition of the material. In this case, a user can choose to use material: Custom or choose to use material: X, where X can be something like SS316 or UO2 as an example.
When specifying material: X, the ARMI framework will initialize the component to have material X and then it will default to using the Python methods for getting different material properties that are implemented (e.g., density, linear expansion coefficient, heat capacity, etc.). Although when a user specifies Custom as the material then there is limited functionality to specify these types of material properties.
blocks:
    inner fuel:
        clad: &component_fuel_clad
            shape: Circle
            material: SS316
            Tinput: 20.0
            Thot: 20.0
            id: 0.64
            od: 0.77
            mult: 271
        fuel:
            shape: Circle
            material: Custom
            isotopics: InnerFuel
            Tinput: 20.0
            Thot: 100.0
            id: 0.0
            mult: clad.mult
            od: clad.id

Sometimes when doing benchmark analyses it is useful to specify the number densities of a material using custom isotopics while still maintaining the use of the Custom material so that the density is not inherited from a given material, but instead use the number densities that are specified by the user. In this case, it would be nice if a user could inherit some methods from an existing material (i.e., linear expansion coefficient), but not all of them.
I could imagine a section in the blueprints that could allow a Custom material object to be built. Maybe this means allowing the user to import custom material definitions from a separate Python script (similar to shuffleLogic.py) or maybe this means just providing something like:
materials:
    CustomFuel:
        isotopics: InnerFuel
        linearExpansion: UZr.linearExpansion
        heatCapacity: SS316.heatCapacity
blocks:
    inner fuel:
        clad: &component_fuel_clad
            shape: Circle
            material: SS316
            Tinput: 20.0
            Thot: 20.0
            id: 0.64
            od: 0.77
            mult: 271
        fuel:
            shape: Circle
            material: CustomFuel
            Tinput: 20.0
            Thot: 100.0
            id: 0.0
            mult: clad.mult
            od: clad.id

In this scenario, the isotopics are now a child of the CustomFuel material that is defined in the materials section (rather than it being its own section on the component definition) and then the linearExpansion and heatCapacity functionalities are tied to the pre-existing UZr and SS316 methods that are already implemented in the code base.
This would allow me as the user to circumvent the warning in https://github.com/terrapower/armi/pull/496 and have more control over this behavior without having to implement a new Material class in the application I am working off of to handle both the correct treatment of a custom number density input along with the allowing the material to thermally expand, etc.
Please let me know what you think about this @ntouran / @john-science. The specific use case for this is when a benchmark specifies the number densities of a component/block and when we would like to have linear expansion defined to support a reactivity coefficient calculation.

Hmm. I'm sympathetic but want to hear more. We do allow users to provide fresh or subclass materials in plugins that can be named whatever they want. For a benchmark, it might be most expressive and safest and easiest to maintain to have the specific materials of the benchmark defined as regular old ARMI materials in Python code. Making more ways to make or point to material properties in blueprints doesn't seem necessary at first glance given plugin materials.
But clearly you have a request, and that's legit. I guess I want to hear more about why just doing materials in a plugin isn't better. It seems like you want to have user input rather than developer input (kinda like shuffleLogic, as you say). But maybe we could allow "user input" to be used using the plugin framework? Then the user would just bring a my-materials.py and we'd point to it during app configuration.

I think that the challenge that I am trying to find a balance with is being able to implement "one-off" materials for benchmark/validation efforts without necessarily extending the code base of the ARMI application unnecessarily. In a sense I am trying to see how much of the existing framework/material plugin(s) can be leveraged to get the capabilities of still using a Custom material but with user-defined (or predefined) material properties to treat thermal expansion.
Using a material class that is not Custom with number densities set does not seem to be working as I would like (as in the number densities that are specified are seemly being scaled(?) by the actual density of the material class that is set) and if I switch to Custom to get the intended behavior that I am looking for then the ability to run calculations that rely on thermal expansion sort of go out the door.
One thing that could be done is to implement a base material class that accepts number densities and derives the mass density from the custom isotopics that are provided and then just subclass specific benchmark materials from that. I guess what I am really looking for with this issue/ticket is a discussion on what the best approach could be for treating benchmarks when number densities are a given and when I want to leverage material properties on a material class (not something that Custom currently offers). Totally up to suggestions from you though!

I personally have taken the approach of piece-mealing a custom material class for situations like this.
I am working off of some documents that specify the  isotopics in MOX fuel in a very specific way that is different than how the MOX material class expects them. So I made a new material class of my own that accepts the isotopics in the way that aligns with my references, but then just derives all the material properties from existing material classes in ARMI.
I have found this to be an acceptable approach, but depending on how many times you need to do this for a given modeling effort, it could easily be quite annoying.

I guess I am cheating a little bit because what I am doing will only work for programmatically-defined models...
I have given my model into its own python entry point. So Python actually runs from the directory in which my input files live. I put my custom material classes in this same directory, so when Python runs it recognizes the modules. And ARMI automatically registers any material classes in the run directory, so their names are recognized from within the blueprints file.
This is a little different than if you were to run your model through the ARMI entry point directly. In that case, you would have to put your custom material classes into the ARMI directory for them to be recognized and registered. That's probably not something you'd want to do, though, because then the material class would likely be outside the repo that your are using to version control your model.
This does bring up an alternative option, though. We could have ARMI look in the directory of the blueprints file for any custom material classes to register, in the same way that it already does in the ARMI directory. Then you could just plop your custom material classes in a module that sites next to your blueprints file, and everything would work great.
Eh?

I would like the idea of importing custom materials from a custom Python script, if @ntouran is OK with that.

After talking with @ntouran offline, it's not unreasonable to expand the API functionality of the framework to allow for discovery of a material plugin. I am thinking that it makes sense for this discovery feature to be optional for applications and in order to enable it, the application will have to explicitly provide a directory path to search for these custom scripts.
This differs a bit from the fuel management / shuffle logic because we probably need the materials data to be configured with the app rather than being loaded based on case settings.
I like the idea of by default (if this feature is enabled) that the app will always just search in the current working directory for a python file that meets the criteria (e.g., implements a plugin class that inherits from the ARMI plugin and the file meets some application-defined naming convention).
If a custom materials plugin is configured then it will be added to the materials namespace list. Likely, if a custom material library is being loaded in, then it should probably take priority over the other material packages, but maybe this can also be configurable for the application? We either need to prevent custom materials from having the same name as another material that is imported or make it clear which one is taking priority and where the use is from.
Additionally, we should notify the user when any custom material library is discovered and imported.

Sorry, @jakehader let me just check in to make sure I understand.

...discovery of a material plugin...

What do you mean by "discovery" here?  So far, the user always carefully defines which plugins they want in their run in the ARMI ecosystem. This is how they gain fine control over their simulations.
Also, and not for nothing, I am not a fan of "just searching in a folder for a Python file that includes a subclass of something". If every single thing in an ARMI simulation is carefully defined by the user except this one thing, that'll be hard to explain to the user who will want to just know "Why can't I define everything in my YAML file? Why is this one thing different?" It breaks the paradigm users will have for how to define a run.
Also also, right now you can look at a settings file and a database file and you know everything about the run that created the database file.  So now your settings file won't full define the run? You will also need a full copy of whatever folder includes these input files?
I don't want to be a wet blank, but I am not entirely convinced.

Thanks for the feedback @john-science. I definitely think that this warren's further discussion between you, me, and @ntouran. Let's take it offline and report back here with a proposed solution or maybe alternate way to frame the problem I am looking to solve.

@john-science, would you be able to schedule some time to talk about this with me? I am looking for something to help our benchmark modeling where not just density is important, but when we also need to consider temperature effects on material properties, but using a custom material definition for number densities.

@john-science I assume you closed this by accident?

@keckler Hmm... I didn't close this. Yet. I just referenced it in a PR and GitHub decided they must be connected and closed this ticket.
But @ntouran and I aren't hugely interested in this PR. We already have three ways to define materials for ARMI, and I'm not sure this one adds a lot of value.

The linked issue above will be how we actually solve this issue.

Hmm, while implementing that it occurred to me that plugins don't really do too much in terms of registering materials that they bring in other than setting the material resolution order to know about them (as @john-science was trying to remind me earlier).
This leads me to the supported path.to.module:MaterialClassName syntax supported by ARMI already. If you specified your material name in blueprints as, e.g. jakesCustomMaterials:Milkshake then the system would try to import jakesCustomMaterials.py and look for the Milkshake material class in there.
This can and does currently provide user-supply-able material classes in the run's input directory, provided that the input directory is in the module resolution path (e.g. PYTHONPATH).
I tried this out and it works. But it's kind of a pain to always be updating your PYTHONPATH. One thing we could consider doing to make this happen is having ARMI add the input directory directly to the sys.path variable at runtime. Then imports by name would work no problem.
Thoughts on that?

source: gharchive/issue

authors: jakehader john-science keckler ntouran

repo: terrapower/armi


text:
with default nCycles (nCycles=1) database writes at cycle 0 are suppressed in snapshots

The setting nCycles has very little meaning for a snapshots run, so many users delete the line which reverts to default value of 1. this suppress the database write for snapshots operator because it thinks it is at EOL during this if statement when cycle = 0:
https://github.com/terrapower/armi/blob/f6bf598525efaac72f0391296af832b556d415ad/armi/bookkeeping/db/database3.py#L264-L268
https://github.com/terrapower/armi/blob/f6bf598525efaac72f0391296af832b556d415ad/armi/operators/operator.py#L260-L269
Also, the snapshots operator does some big backflips to get ARMI to write to the database at just the right times. See exclusions/logic in code below
https://github.com/terrapower/armi/blob/f6bf598525efaac72f0391296af832b556d415ad/armi/operators/snapshots.py#L64-L80
It might be more clear/obvious to just disable the database interface during snapshots and explicitly call a to-be-created "writeToDb" public method on databaseInterface.

@ntouran
Tell me if I'm wrong.
But since class OperatorSnapshots(operatorMPI.OperatorMPI): and class OperatorMPI(Operator):, could we just override the def atEOL method to fix this problem for him?

class OperatorSnapshots(operatorMPI.OperatorMPI):
    # ...
    @property
    def atEOL(self):
        return self.r.p.cycle == self.cs["nCycles"]     # ditch the "- 1"

It looks like we would want to delete the first 2 of these 3 lines as well:
https://github.com/terrapower/armi/blob/f6bf598525efaac72f0391296af832b556d415ad/armi/operators/snapshots.py#L78-L80
Though... I'm sure those were there for a reason, I'm not sure I see it.

We should definitely override atEOL for the snapshot operator. The proposal from John is fine, but is till dependent on the setting always being in the default time. Maybe it'd be better to just always return False for snapshots?

authors: john-science ntouran onufer


text:
Consolidate getDominantMaterial methods into one

There were quasi-independent implementations of getDominantMaterial
on three separate objects. Now they are all unified into the same
implementation. The special needs of various clients have been handled
by refactoring the functionality into two functions at the composite
module level. A warning was added indicating the high likelihood of these
functions being moved to something more topical of composition in the
near future.
In addition, several calls to getComponents were changed to iterComponents
mostly as an indication of where it's appropriate to use one over the other.
The performance enhancement of this is not expected to be large.

I'm gonna send this one too and will need a post-push audit from @youngmit  for cleanups and whatnot.


text:
toml files using wrong commentstring

toml files seem to use /* */ pattern when the should use #

Hey, neovim doesn't seem to have a toml filetype in the runtime: https://github.com/neovim/neovim/tree/master/runtime/ftplugin
So it seems to default to /* */
As this plugin doesn't set the commentstring value but uses what is set, you'll have to set this your self. If you look under the Configure section of the readme there are a few ways sepcified this can be set (Changing/Setting commentstring).
Personnaly I would create a local ftplugin/toml.lua file and have it set there (the last example).
Closing as this isn't a big of the plugin.
Please re-open if you are still having issues.

authors: ChristianChiarulli terrortylor

repo: terrortylor/nvim-comment


text:
Feature request - erase over background image

Hi,
Wondering if the following case would be possible to implement with this lib:

I want to implement something like 'scratch to reveal content underneath'.
I'm using background image with localSourceImage
If I set stroke color to erases (#00000000) I still can't erase the background image. The use case would be to have another view with content under SketchCanvas view, and you just scratch/erase on the background image and this content will reveal.

Help would be appreciated.

any update ? I am facing the same case.

repo: terrylinla/react-native-sketch-canvas

license: mit

license_source: bigquery


text:
Need Python on Node 4.x on Windows

https://github.com/tessel/start.tessel.io/blob/master/views/FRE-cmd.jade and https://github.com/tessel/start.tessel.io/blob/master/views/FRE-install.jade should note that users should install Node 0.12.x on Windows as there isn't a precompiled usb_bindings for Node 4.x yet.  Would you like a PR for this?

@robrich that would be great! Thanks.

Here ya go: https://github.com/tessel/start.tessel.io/pull/84


text:
Select which Tessel to use

From comments on the T2 CLI spec.
The CLI should select a tessel based on this list in order of priority:

using the --name flag
a config file in the directory you're using the T2 CLI from (what should this config file look like?)
an environment variable in the terminal, set as export TESSEL=Bulbasaur
if there is a single tessel connected over USB, prefer that one
if there is only one tessel visible, use that one
if none of the above are found run tessel list automatically and prompt selection

@kevinmehall @nplus11 @ekolker

The config file is under debate here: https://github.com/tessel/t2-cli/issues/94

[Cross posting from #93]
I still think this is a bad idea. Folks would have to look up how to select a particular Tessel anyway so showing them how to set an environment variable is just as much effort (but more useful down the road).
I have rarely seen people want to set a project to a specific Tessel. This could cause confusion if they ever try to do a demo with a different Tessel than they built the project with.
In addition, project configuration files already exist (like package.json) and adding another file is more of a headache.

I agree. I think we need a clear picture of env vars rather than project mapped tessels

Any more opinions on this or should I close it? @Frijol

I think the listing in the top comment is correct– unless there was a decision re config files that changes that?
Is the listed order implemented in code?

I feel strongly that there should be no config file option for the reasons listed in my comment from May 5.

@Frijol if there are no other opinions on this, I think we should remove the config file option. Sound good?

Sure, removing now.

Partially fixed with #151. We just need to implement the selection mechanism if you have multiple USB or LAN Tessels.


text:
Q&A: Unclear document for retrain(tunefine) Tesseract LSTM model for box/tiff with hand made created boxes file from image.

Hi,
I don't see any part of in this document (https://github.com/tesseract-ocr/tesseract/wiki/TrainingTesseract-4.00#creating-starter-traineddata)  for create .trainneddata from hand made boxes file.
I want to retrain tesseract 4 for recognize some special characters for my situation. In my case I want recognize some characters like: Φ, φ etc ...
So I create my training data (tiff image + box file) from my images.
I generated its via this command line: tesseract [lang].[fontname].exp[num].tif [lang].[fontname].exp[num] batch.nochop makebox, then after I edit manually by Qt-box-editor.
(I done with this link: https://github.com/tesseract-ocr/tesseract/wiki/Training-Tesseract-–-Make-Box-Files)
So now I files:

.tif file
.box file
.tr file (generated by command: tesseract [lang].[fontname].exp[num].tif [lang].[fontname].exp[num] box.train
unicharset file ( I don't set properties for unicharset file and don't generate font properties file)

My question is: How can I create .trainneddata and tunefine training ltsm for my case from them.
Thank you !

I read tesstrain.sh, seems it use text2image to automatically generate box file from text. But I want to generate box file from my image.
Thank you

See here:
https://github.com/tesseract-ocr/tesseract/wiki/TrainingTesseract-4.00#making-box-files

@amitdo Thank you for replying me
But I have read this part and now I have files:
.tif file
.box file
.tr file (generated by command: tesseract [lang].[fontname].exp[num].tif [lang].[fontname].exp[num] box.train
unicharset file ( I don't set properties for unicharset file and don't generate font properties file)
My question is: How can I create .trainneddata from them ?
Currently, I'm using combine_lang_model to generate .trainneddata but I get an error like:

I downloaded langdata from here: https://github.com/tesseract-ocr/langdata

I find 2 repo contain langdata:
What should I choose, I'm using LSTM in tesseract
1: https://github.com/tesseract-ocr/langdata_lstm
2:  https://github.com/tesseract-ocr/langdata

I find 2 repo contain langdata:
What should I choose, I'm using LSTM in tesseract
1: https://github.com/tesseract-ocr/langdata_lstm
2:  https://github.com/tesseract-ocr/langdata

I find 2 repo contain langdata:
What should I choose, I'm using LSTM in tesseract
1: https://github.com/tesseract-ocr/langdata_lstm
2:  https://github.com/tesseract-ocr/langdata

lease respect guidelines for posting issue: use tesseract user forum for asking questions/support.

authors: amitdo tonquangtu zdenop

repo: tesseract-ocr/tesseract


text:
Code alignment desired

The following code should be aligned a little bit:
if bJsonSchema:
    try:
        validate(instance=oJsonCfgData, schema=oJsonSchemaCfg)
    except Exception as error:
        if error.validator == 'additionalProperties':
            logger.error(f"Verification against JSON schema failed: '{error.message}'\n" + \
                         "          Additional properties are not allowed! Please put the additional params into 'params': { 'global': {...} \n")
            BuiltIn().unknown('JSON schema validation failed!')
        elif error.validator == 'required':
            logger.error(f"The parameter {error.message}, but it's not set in JSON configuration file.\n")
            BuiltIn().unknown('JSON schema validation failed!')
        else:
            errParam = error.path.pop()
            logger.error(f"Parameter '{errParam}' with invalid value found in JSON configuration file! \n" + \
                         f"          {error.message}\n")
            BuiltIn().unknown('JSON schema validation failed!')

This is redundant: BuiltIn().unknown('JSON schema validation failed!'). You should put this as common final feedback at end of except, but outside all if/elif.
The error message in first case is:
[ ERROR ] Verification against JSON schema failed: 'Additional properties are not allowed ('Minimum_versionXYZ' was unexpected)'
          Additional properties are not allowed! Please put the additional params into 'params': { 'global': {...}

Seems that "Additional properties are not allowed" is already part of 'error.message' - and therefore should be removed from second line in logger.error().

Hello Holger,
I created the pull-request #129 for this ticket.
Thank you,
Son

solved and already merged with #129

authors: HolQue namsonx test-fullautomation


text:
[Mirror] IpGroups Changes

Mirror from https://github.com/Azure/azure-rest-api-specs/pull/7397

/azp run

repo: test-repo-tih/azure-rest-api-specs


text:
Updated to use Node20

Updated action to use Node.js 20 to close #23.
Also updated README to use latest checkout & setup-node versions and workflows to use Node 20.
Note: Though it should work, this PR is untested. Please do so before merging.

@alexesprit can you merge this one?

It's better late than never :D
Sorry for ignoring this.

authors: BhavyeMathur alexesprit danielnetop


text:
Errors on Kubernetes 1.23 (with containerd as container runtime)

Hi there!
Since Kubernetes 1.20, Docker support is deprecated and will be totally removed from 1.24. We use GKE to manage Kubernetes so the upgrade will be done automatically.
As far as I've read, developers should not have been impacted but we made tests in Kubernetes 1.23 to check that all is OK and it seems we have some issues with a microservice using Testcontainers :
09:59:44.578 [testcontainers-ryuk] WARN org.testcontainers.utility.ResourceReaper - Can not connect to Ryuk at localhost:49153
java.net.ConnectException: Connection refused (Connection refused)
	at java.base/java.net.PlainSocketImpl.socketConnect(Native Method)
	at java.base/java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:399)
	at java.base/java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:242)
	at java.base/java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:224)
	at java.base/java.net.SocksSocketImpl.connect(SocksSocketImpl.java:403)
	at java.base/java.net.Socket.connect(Socket.java:591)
	at org.testcontainers.utility.ResourceReaper.lambda$null$3(ResourceReaper.java:194)
	at org.rnorth.ducttape.ratelimits.RateLimiter.doWhenReady(RateLimiter.java:27)
	at org.testcontainers.utility.ResourceReaper.lambda$start$4(ResourceReaper.java:190)
	at java.base/java.lang.Thread.run(Thread.java:835)

This is not reproductible on a Kubernetes 1.19 where Docker is not deprecated nor removed.
We tried to disable Ryuk in pom.xml (as indicated for this error this issue) but it has no effect :
<plugin>
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-failsafe-plugin</artifactId>
    <executions>
        <execution>
            <goals>
                <goal>verify</goal>
                <goal>integration-test</goal>
            </goals>
            <configuration>
                <environmentVariables>
                    <TESTCONTAINERS_RYUK_DISABLED>true</TESTCONTAINERS_RYUK_DISABLED>
                </environmentVariables>
            </configuration>
        </execution>
    </executions>
</plugin>

Is anyone have an idea please?
Thank you by advance!

We tried to launch IT with testcontainers in a local Minikube with Kubernetes 1.23 and Containerd as container runtime:
minikube start --kubernetes-version v1.23.0
--network-plugin=cni
--enable-default-cni
--container-runtime=containerd
--bootstrapper=kubeadm

But it leads to this error when launching mvn -T 2 failsafe:integration-test failsafe:verify :
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.87 s <<< FAILURE! - in com.ggl.merch.kafka.it.MerchandisingConsumerIT
[ERROR] should_consume_merchandising_message_and_process_record  Time elapsed: 0.012 s  <<< ERROR!
java.lang.IllegalStateException: Could not find a valid Docker environment. Please see logs and check configuration
        at com.ggl.merch.kafka.it.MerchandisingConsumerIT.<init>(MerchandisingConsumerIT.java:91)

Anyone already had the same problem? Thank you!

Exactly the same problem here. I'm using Rancher Desktop 1.1.1 on MacOS.

We are running into the same problem with Amazon EKS

@nadworny @atooni Do you have similar errors in your logs?

@nadworny @atooni Do you have similar errors in your logs?

Yes

I had the message container startup failed. We have now decided to use the socket based communication as we are using separate clusters for dev / staging and prod. That works quite well.

@atooni What do you mean by use the socked based communication? At which level?

It might be the case that we see very different issues here, so we should be careful to not mix things up.
Testcontainers interacts with Docker using the Docker Engine RESTful API. If another container engine is used, an appropriate API needs to be configured and made accessible for Testcontainers, if it is running in a location that differs from the default Docker location.
Here is the part from our docs, that explains how to manually configure Testcontainers to interact with a Docker Engine-like RESTful API that does not get automatically detected:
https://www.testcontainers.org/features/configuration/#customizing-docker-host-detection
So to everyone observing problems with their setups, how is your API accessible from the process that is running the tests?

Solved by putting this in our configuration:
- name: "TESTCONTAINERS_HOST_OVERRIDE"
  valueFrom:
    fieldRef:
      fieldPath: status.hostIP

Following this doc:
    TESTCONTAINERS_HOST_OVERRIDE
    Docker's host on which ports are exposed.
    Example: docker.svc.local

Sorry for the question @fdelbrayelle , which configuration are you referring to ? I'm running with a similar issue in EKS and I would like to know if I could do the same thing you did. Thanks in advance.

@vinniehg This is about setting the environment variable TESTCONTAINERS_HOST_OVERRIDE. See the docs: https://www.testcontainers.org/features/configuration/#customizing-docker-host-detection

authors: atooni fdelbrayelle kiview nadworny vinniehg

repo: testcontainers/testcontainers-java


text:
TestNG test suites are executed multiple times when run with maven test

TestNG test suite are executed multiple times if run in Maven test. Here is what I have in pom.xml
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-surefire-plugin</artifactId>
                <version>2.8.1</version>
                <configuration>
                    <forkMode>pertest</forkMode>
                    <encoding>UTF-8</encoding>
                    <inputEncoding>UTF-8</inputEncoding>
                    <outputEncoding>UTF-8</outputEncoding>
                    <argLine>-Xms256m -Xmx1024m -ea -Dfile.encoding=UTF-8</argLine> <!-- -ea: assertions enabled   file.encoding: setting the platform default character set -->
                    <suiteXmlFiles>
                        <suiteXmlFile>testngA.xml</suiteXmlFile>
                        <suiteXmlFile>testngB.xml</suiteXmlFile>
                        <suiteXmlFile>testngC.xml</suiteXmlFile>
                        <suiteXmlFile>testngD.xml</suiteXmlFile>
                    </suiteXmlFiles>
                    <testFailureIgnore>true</testFailureIgnore>
                </configuration>
            </plugin>

Here is the result and you can see that the test suite were executed multiple times
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building TestNGParallelTest 0.0.1-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-resources-plugin:2.4.3:resources (default-resources) @ TestNGParallelTest ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory C:\Users\U0020941\Documents\Projects\Miscellaneous\TestNGParallelTest\src\main\resources\beans
[INFO] skip non existing resourceDirectory C:\Users\U0020941\Documents\Projects\Miscellaneous\TestNGParallelTest\src\main\config
[INFO] skip non existing resourceDirectory C:\Users\U0020941\Documents\Projects\Miscellaneous\TestNGParallelTest\src\main\resources\schema
[INFO] skip non existing resourceDirectory C:\Users\U0020941\Documents\Projects\Miscellaneous\TestNGParallelTest\data
[INFO]
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ TestNGParallelTest ---
[INFO] Nothing to compile - all classes are up to date
[INFO]
[INFO] --- maven-resources-plugin:2.4.3:testResources (default-testResources) @ TestNGParallelTest ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 0 resource
[INFO]
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ TestNGParallelTest ---
[INFO] Nothing to compile - all classes are up to date
[INFO]
[INFO] --- maven-surefire-plugin:2.8.1:test (default-test) @ TestNGParallelTest ---
[INFO] Surefire report directory: C:\Users\U0020941\Documents\Projects\Miscellaneous\TestNGParallelTest\target\surefire-reports

T E S T S
Running TestSuite
2014-04-08 08:33:20.782 Thread-16   TestA.class --- 7
2014-04-08 08:33:20.783 Thread-18   TestA.class --- 9
2014-04-08 08:33:20.782 Thread-11   TestA.class --- 2
2014-04-08 08:33:20.782 Thread-14   TestA.class --- 5
2014-04-08 08:33:20.783 Thread-9    TestA.class --- 0
2014-04-08 08:33:20.783 Thread-10   TestA.class --- 1
2014-04-08 08:33:20.783 Thread-12   TestA.class --- 3
2014-04-08 08:33:20.782 Thread-13   TestA.class --- 4
2014-04-08 08:33:20.782 Thread-15   TestA.class --- 6
2014-04-08 08:33:20.783 Thread-17   TestA.class --- 8
2014-04-08 08:33:20.854 Thread-21   TestB.class --- 2
2014-04-08 08:33:20.854 Thread-22   TestB.class --- 3
2014-04-08 08:33:20.854 Thread-20   TestB.class --- 1
2014-04-08 08:33:20.855 Thread-23   TestB.class --- 4
2014-04-08 08:33:20.854 Thread-19   TestB.class --- 0
2014-04-08 08:33:20.855 Thread-25   TestB.class --- 6
2014-04-08 08:33:20.855 Thread-27   TestB.class --- 8
2014-04-08 08:33:20.855 Thread-24   TestB.class --- 5
2014-04-08 08:33:20.855 Thread-28   TestB.class --- 9
2014-04-08 08:33:20.855 Thread-26   TestB.class --- 7
2014-04-08 08:33:20.868 Thread-30   TestC.class --- 1
2014-04-08 08:33:20.868 Thread-29   TestC.class --- 0
2014-04-08 08:33:20.868 Thread-32   TestC.class --- 3
2014-04-08 08:33:20.869 Thread-34   TestC.class --- 5
2014-04-08 08:33:20.869 Thread-37   TestC.class --- 8
2014-04-08 08:33:20.869 Thread-36   TestC.class --- 7
2014-04-08 08:33:20.868 Thread-31   TestC.class --- 2
2014-04-08 08:33:20.869 Thread-38   TestC.class --- 9
2014-04-08 08:33:20.868 Thread-33   TestC.class --- 4
2014-04-08 08:33:20.87  Thread-35   TestC.class --- 6
2014-04-08 08:33:20.925 Thread-39   TestD.class --- 0
2014-04-08 08:33:20.925 Thread-41   TestD.class --- 2
2014-04-08 08:33:20.925 Thread-42   TestD.class --- 3
2014-04-08 08:33:20.926 Thread-43   TestD.class --- 4
2014-04-08 08:33:20.925 Thread-40   TestD.class --- 1
2014-04-08 08:33:20.926 Thread-44   TestD.class --- 5
2014-04-08 08:33:20.926 Thread-46   TestD.class --- 7
2014-04-08 08:33:20.926 Thread-45   TestD.class --- 6
2014-04-08 08:33:20.932 Thread-48   TestD.class --- 9
2014-04-08 08:33:20.932 Thread-47   TestD.class --- 8
Tests run: 40, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.119 sec
Running TestSuite
2014-04-08 08:33:23.129 Thread-11   TestA.class --- 2
2014-04-08 08:33:23.129 Thread-16   TestA.class --- 7
2014-04-08 08:33:23.129 Thread-14   TestA.class --- 5
2014-04-08 08:33:23.129 Thread-15   TestA.class --- 6
2014-04-08 08:33:23.129 Thread-13   TestA.class --- 4
2014-04-08 08:33:23.129 Thread-18   TestA.class --- 9
2014-04-08 08:33:23.129 Thread-10   TestA.class --- 1
2014-04-08 08:33:23.129 Thread-9    TestA.class --- 0
2014-04-08 08:33:23.129 Thread-12   TestA.class --- 3
2014-04-08 08:33:23.129 Thread-17   TestA.class --- 8
2014-04-08 08:33:23.158 Thread-20   TestB.class --- 1
2014-04-08 08:33:23.158 Thread-19   TestB.class --- 0
2014-04-08 08:33:23.158 Thread-21   TestB.class --- 2
2014-04-08 08:33:23.158 Thread-22   TestB.class --- 3
2014-04-08 08:33:23.158 Thread-23   TestB.class --- 4
2014-04-08 08:33:23.158 Thread-25   TestB.class --- 6
2014-04-08 08:33:23.159 Thread-26   TestB.class --- 7
2014-04-08 08:33:23.159 Thread-24   TestB.class --- 5
2014-04-08 08:33:23.159 Thread-27   TestB.class --- 8
2014-04-08 08:33:23.159 Thread-28   TestB.class --- 9
2014-04-08 08:33:23.171 Thread-29   TestC.class --- 0
2014-04-08 08:33:23.171 Thread-30   TestC.class --- 1
2014-04-08 08:33:23.171 Thread-31   TestC.class --- 2
2014-04-08 08:33:23.171 Thread-32   TestC.class --- 3
2014-04-08 08:33:23.171 Thread-33   TestC.class --- 4
2014-04-08 08:33:23.171 Thread-34   TestC.class --- 5
2014-04-08 08:33:23.172 Thread-35   TestC.class --- 6
2014-04-08 08:33:23.172 Thread-36   TestC.class --- 7
2014-04-08 08:33:23.172 Thread-37   TestC.class --- 8
2014-04-08 08:33:23.172 Thread-38   TestC.class --- 9
2014-04-08 08:33:23.186 Thread-39   TestD.class --- 0
2014-04-08 08:33:23.186 Thread-41   TestD.class --- 2
2014-04-08 08:33:23.186 Thread-42   TestD.class --- 3
2014-04-08 08:33:23.186 Thread-40   TestD.class --- 1
2014-04-08 08:33:23.187 Thread-43   TestD.class --- 4
2014-04-08 08:33:23.187 Thread-46   TestD.class --- 7
2014-04-08 08:33:23.187 Thread-47   TestD.class --- 8
2014-04-08 08:33:23.187 Thread-44   TestD.class --- 5
2014-04-08 08:33:23.187 Thread-45   TestD.class --- 6
2014-04-08 08:33:23.187 Thread-48   TestD.class --- 9
Tests run: 40, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.23 sec
Running TestSuite
2014-04-08 08:33:25.587 Thread-12   TestA.class --- 3
2014-04-08 08:33:25.587 Thread-17   TestA.class --- 8
2014-04-08 08:33:25.587 Thread-18   TestA.class --- 9
2014-04-08 08:33:25.587 Thread-9    TestA.class --- 0
2014-04-08 08:33:25.587 Thread-11   TestA.class --- 2
2014-04-08 08:33:25.587 Thread-13   TestA.class --- 4
2014-04-08 08:33:25.587 Thread-10   TestA.class --- 1
2014-04-08 08:33:25.587 Thread-15   TestA.class --- 6
2014-04-08 08:33:25.587 Thread-14   TestA.class --- 5
2014-04-08 08:33:25.587 Thread-16   TestA.class --- 7
2014-04-08 08:33:25.62  Thread-20   TestB.class --- 1
2014-04-08 08:33:25.62  Thread-19   TestB.class --- 0
2014-04-08 08:33:25.621 Thread-22   TestB.class --- 3
2014-04-08 08:33:25.621 Thread-23   TestB.class --- 4
2014-04-08 08:33:25.62  Thread-21   TestB.class --- 2
2014-04-08 08:33:25.621 Thread-24   TestB.class --- 5
2014-04-08 08:33:25.621 Thread-26   TestB.class --- 7
2014-04-08 08:33:25.621 Thread-25   TestB.class --- 6
2014-04-08 08:33:25.621 Thread-28   TestB.class --- 9
2014-04-08 08:33:25.621 Thread-27   TestB.class --- 8
2014-04-08 08:33:25.636 Thread-29   TestC.class --- 0
2014-04-08 08:33:25.636 Thread-31   TestC.class --- 2
2014-04-08 08:33:25.636 Thread-30   TestC.class --- 1
2014-04-08 08:33:25.636 Thread-32   TestC.class --- 3
2014-04-08 08:33:25.636 Thread-35   TestC.class --- 6
2014-04-08 08:33:25.636 Thread-33   TestC.class --- 4
2014-04-08 08:33:25.637 Thread-34   TestC.class --- 5
2014-04-08 08:33:25.637 Thread-37   TestC.class --- 8
2014-04-08 08:33:25.637 Thread-36   TestC.class --- 7
2014-04-08 08:33:25.637 Thread-38   TestC.class --- 9
2014-04-08 08:33:25.65  Thread-39   TestD.class --- 0
2014-04-08 08:33:25.65  Thread-41   TestD.class --- 2
2014-04-08 08:33:25.65  Thread-42   TestD.class --- 3
2014-04-08 08:33:25.65  Thread-40   TestD.class --- 1
2014-04-08 08:33:25.65  Thread-43   TestD.class --- 4
2014-04-08 08:33:25.65  Thread-44   TestD.class --- 5
2014-04-08 08:33:25.65  Thread-46   TestD.class --- 7
2014-04-08 08:33:25.651 Thread-48   TestD.class --- 9
2014-04-08 08:33:25.651 Thread-47   TestD.class --- 8
2014-04-08 08:33:25.651 Thread-45   TestD.class --- 6
Tests run: 40, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.21 sec
Running TestSuite
2014-04-08 08:33:28.079 Thread-13   TestA.class --- 4
2014-04-08 08:33:28.079 Thread-10   TestA.class --- 1
2014-04-08 08:33:28.079 Thread-12   TestA.class --- 3
2014-04-08 08:33:28.079 Thread-17   TestA.class --- 8
2014-04-08 08:33:28.079 Thread-14   TestA.class --- 5
2014-04-08 08:33:28.079 Thread-9    TestA.class --- 0
2014-04-08 08:33:28.079 Thread-11   TestA.class --- 2
2014-04-08 08:33:28.079 Thread-15   TestA.class --- 6
2014-04-08 08:33:28.079 Thread-16   TestA.class --- 7
2014-04-08 08:33:28.079 Thread-18   TestA.class --- 9
2014-04-08 08:33:28.113 Thread-19   TestB.class --- 0
2014-04-08 08:33:28.113 Thread-21   TestB.class --- 2
2014-04-08 08:33:28.113 Thread-20   TestB.class --- 1
2014-04-08 08:33:28.113 Thread-22   TestB.class --- 3
2014-04-08 08:33:28.113 Thread-23   TestB.class --- 4
2014-04-08 08:33:28.114 Thread-27   TestB.class --- 8
2014-04-08 08:33:28.114 Thread-28   TestB.class --- 9
2014-04-08 08:33:28.114 Thread-26   TestB.class --- 7
2014-04-08 08:33:28.114 Thread-25   TestB.class --- 6
2014-04-08 08:33:28.114 Thread-24   TestB.class --- 5
2014-04-08 08:33:28.127 Thread-29   TestC.class --- 0
2014-04-08 08:33:28.127 Thread-31   TestC.class --- 2
2014-04-08 08:33:28.127 Thread-32   TestC.class --- 3
2014-04-08 08:33:28.127 Thread-33   TestC.class --- 4
2014-04-08 08:33:28.127 Thread-30   TestC.class --- 1
2014-04-08 08:33:28.128 Thread-34   TestC.class --- 5
2014-04-08 08:33:28.128 Thread-36   TestC.class --- 7
2014-04-08 08:33:28.128 Thread-35   TestC.class --- 6
2014-04-08 08:33:28.128 Thread-37   TestC.class --- 8
2014-04-08 08:33:28.128 Thread-38   TestC.class --- 9
2014-04-08 08:33:28.14  Thread-40   TestD.class --- 1
2014-04-08 08:33:28.14  Thread-39   TestD.class --- 0
2014-04-08 08:33:28.14  Thread-41   TestD.class --- 2
2014-04-08 08:33:28.14  Thread-42   TestD.class --- 3
2014-04-08 08:33:28.141 Thread-43   TestD.class --- 4
2014-04-08 08:33:28.141 Thread-44   TestD.class --- 5
2014-04-08 08:33:28.141 Thread-45   TestD.class --- 6
2014-04-08 08:33:28.141 Thread-46   TestD.class --- 7
2014-04-08 08:33:28.141 Thread-47   TestD.class --- 8
2014-04-08 08:33:28.146 Thread-48   TestD.class --- 9
Tests run: 40, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.271 sec
Results :
Tests run: 160, Failures: 0, Errors: 0, Skipped: 0
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 13.368s
[INFO] Finished at: Tue Apr 08 08:33:30 EDT 2014
[INFO] Final Memory: 7M/121M
[INFO] ------------------------------------------------------------------------
Here is one of the test classes
package com.company.qed;

import java.sql.Timestamp;

import org.testng.annotations.DataProvider;
import org.testng.annotations.Test;

public class TestA
{
    @Test(dataProvider="data", threadPoolSize=5)
    public void methodA(int i)
    {
        java.util.Date date= new java.util.Date();
        System.out.println(new Timestamp(date.getTime()) +
                "\tThread-" + Thread.currentThread().getId() + "\tTestA.class --- " + i);
    }

    @DataProvider(name="data", parallel=true)
    public Object[][] data()
    {
        Object[][] fields = new Object[10][1];

        for (int i = 0; i<10; i++) {
            fields[i][0] = i;
        }

        return fields;
    }

}

Here is one of the testng xml file
<suite name="Suite A">
    <test name="Test Name A">
        <classes>
            <class name="com.company.qed.TestA" />
        </classes>
    </test>
</suite>

My solution is to wrap all testng xml file into one testng xml as follows
<suite name="TestNG.xml" parallel="instances" thread-count="5">
    <suite-files>
        <suite-file path="./testngA.xml" />
        <suite-file path="./testngB.xml" />
        <suite-file path="./testngC.xml" />
        <suite-file path="./testngD.xml" />
    </suite-files>
</suite>

And then reference that in pom.xml. This solution works.

any plans to fix this ?

@jagdeepjain - Is this still a problem with the latest TestNG released version viz., 6.14.3 ? Have you tried ? Can you please help post back your results ?

Please ensure you try with the latest released version of surefire plugin as well, just to ensure you are able to reproduce this in the latest version.

Please ensure you try with the latest released version of surefire plugin as well, just to ensure you are able to reproduce this in the latest version.

Yes this is happening in TestNg 7.0.0

@olexmal - Can you please create a simple standalone project that can be used to recreate this issue ?

I am fasing same issue what was the solutions for this issue?

@kasivisalakshiBorra - My above comment still holds true. Without a reproducible sample, nothing can be said.

@krmahadevan apologies for delay in response, to counter this I have used docker container to run it parallel that is running sequential tests in each docker container but spawning few of docker container in parallel.
I have updated the surefire and testNG version as per your recommendation but still it has problem, the test never runs for me with testNG also the test suite has 3 tests but it shows 4 in test run with 1 failure and 3 skipped, may be something else is going on here.
One more thing to highlight that with test suite I am using
  @Test(priority = 1)
  @BeforeTest(groups = "arquillian", inheritGroups = true)

In GoogleTest1, GoogleTest2, GoogleTest3.
But when this is removed in GoogleTest4 and run with just mvn test -Dtest=GoogleTest4 this works fine.
Error with testNG test suite is as below when run as mvn clean test
Check below:
-------------------------------------------------------------------------------
Test set: TestSuite
-------------------------------------------------------------------------------
Tests run: 4, Failures: 1, Errors: 0, Skipped: 3, Time elapsed: 0.954 s <<< FAILURE! - in TestSuite
org.jagdeep.example.arquillian.google.tests.GoogleTest1.f  Time elapsed: 0.745 s  <<< FAILURE!
java.lang.NullPointerException
	at org.jagdeep.example.arquillian.google.tests.GoogleTest1.f(GoogleTest1.java:21)

Above is the console output.
The project is pushed @ https://github.com/jagdeepjain/webdriver-arquillian-test can you please check it once and let know if there is any issue with the project setup or the versions?

Let me take back above comment and try after removing arquillian.

Ok this works fine for me, code is the branch parallel-test in above mentioned repository.
I forcefully made on test failed and below is the console outout.
INFO: Detected dialect: W3C
Aug 02, 2020 4:03:33 PM org.openqa.selenium.remote.ProtocolHandshake createSession
INFO: Detected dialect: W3C
Test Ran fine.
Test Ran fine.
Test Ran from GoogleTest2.
Test Ran from GoogleTest1.
Test Ran fine.
[ERROR] Tests run: 3, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 10.734 s <<< FAILURE! - in TestSuite
[ERROR] org.jagdeep.example.arquillian.google.tests.GoogleTest3.f  Time elapsed: 10.356 s  <<< FAILURE!
java.lang.AssertionError: expected [Google] but found [Google1]
	at org.jagdeep.example.arquillian.google.tests.GoogleTest3.f(GoogleTest3.java:23)

[INFO]
[INFO] Results:
[INFO]
[ERROR] Failures:
[ERROR]   GoogleTest3.f:23 expected [Google] but found [Google1]
[INFO]
[ERROR] Tests run: 3, Failures: 1, Errors: 0, Skipped: 0
[INFO]
[ERROR] There are test failures.

Please refer to /Users/jagdeepjain/git/webdriver-arquillian-test/test-output for the individual test results.
Please refer to dump files (if any exist) [date].dump, [date]-jvmRun[N].dump and [date].dumpstream.
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 13.563 s
[INFO] Finished at: 2020-08-02T16:03:40+05:30
[INFO] Final Memory: 20M/216M
[INFO] ------------------------------------------------------------------------

Though the build shows success, I have to look into it.
Thanks @krmahadevan for the tip.

@gcosmiano please check with the parallel-test branch @ https://github.com/jagdeepjain/webdriver-arquillian-test later I will move this branch in to separate repo for demonstrating the same.

@jagdeepjain - A bit confused. So are you saying that the issue is not with TestNG but somewhere else ? Or are you saying that the problem persists and needs to be looked at ?

@krmahadevan issue shows up when we use TestNG with arquillian as per my findings.
Refer https://github.com/cbeust/testng/issues/508#issuecomment-667647842

From the above comments, it looks like the problem perhaps could be with arquillian since a plain vanilla project with only TestNG works fine. Closing this issue.

authors: gcosmiano jagdeepjain kasivisalakshiBorra krmahadevan olexmal

repo: testng-team/testng


text:
Rework appendData method in SheetDataClass

At present, appendData can only handle a single kiDataEntry, but it's been proven more reliable to stick things at the bottom than shift and insert data at the top.
Prerequisite to markDuplicatesV2 getting final support, is a big thing that needs to get done.

This has been completed, and is backwards compatible- SheetData.appendData now accepts kiDataEntry and kiDataEntry[] types.

repo: texas-mcallen-mission/sheetCore


text:
show one-time option on monthly form, fix styles

This allows the user to switch to a "one-time" donation from the monthly donation URL — just as they can for the yearly donation. While we don't want to encourage one-time donations, it's better to have a user give one-time than drop off entirely because they don't want to set up a recurring charge and can't figure out how to get to a one-time donation place, which they can't find at all from this URL right now.
I also fixed the dollar sign and input field, so that it expands to fill the available width and doesn't go to two lines when the screen shrinks.
To test:
Go to a monthly donation url /memberform?installmentPeriod=monthly&amount=15 and make sure you can process a one-time donation
Resize and make sure that the amount input looks good on all sizes

Everything WFM. I'd like to check w/ @x110dc to ensure this won't break anything from a Salesforce standpoint.

LGTM.

repo: texastribune/salesforce-stripe


text:
Feature request for "recommended" preset

Many other linting tools have "recommended" presets that catch errors (rather than opinionated things) like:

eslint has eslint:recommended
eslint-plugin-react has react/recommended
eslint-plugin-jsx-a11y has jsx-a11y/recommended

etc.
It would be nice if textlint had a "recommended" preset with language-agnostic plugins that prevent errors like:
textlint-rule-no-dead-link
textlint-rule-spellchecker

So that less manual configuration is needed for a error preventing / non-opinionated setup.

textlint support multiple languages.
It is difficult to define recommended.

authors: azu trevordmiller

repo: textlint/textlint


text:
How to use?

Fatal error: Class 'TextmagicRestClient' not found in "dir" on line

I am using codeinigter and I have facing the same issue Class 'TextmagicRestClient' not found

repo: textmagic/textmagic-rest-php


text:
Consider utility functions that require type arguments

https://downloads.haskell.org/ghc/9.10.1/docs/users_guide/exts/required_type_arguments.html
from Int 1
into Text "x"

Since this would require either conditional compilation or CPP, I'm going to avoid providing this until required type arguments are supported by the three latest versions of GHC. Perhaps someone could implement this as a companion library if they're interested.

repo: tfausak/witch


text:
share the observables

this solves #35

Coverage remained the same at 100.0% when pulling 5eeca6977bdbaf92f8091e96e6aa1dbb89e917ff on fix-observables into c2e37ddedcaca78d680a5bc1e8a5f1540e51f425 on master.

authors: coveralls tflori

repo: tflori/angular-translator


text:
Displays HH:SS instead of HH:MM

My clock displays HH:SS instead of HH:MM.  NumberOfHorizontalDisplays = 4.
Do you have a newer version that displays correctly?  And perhaps has support for an MQTT password?
Thanks

hmm... You are using it with 12h mode?
https://github.com/tg44/mqtt-marquee-scroller/blob/master/marquee/Display.cpp#L218 I think this line has a bug in it, where we show the seconds instead of the minutes...
I have no mqtt password support as I know, I run this on my home network with no need for authentication.


text:
Update Collection#create comment.

Minor wording changes.
Add explanation of create's ability to set foreign keys on related models.
Closes #1062

:+1:

authors: rhys-vdw ricardograca

repo: tgriesser/bookshelf


text:
fix: Cannot find module 'fs-extra-promise’ during install

This change is

Test 89614235b5a16dd(b5a16dd) has failed
See https://github.com/ThaliTester/TestResults/tree/89614235b5a16dd_fix__Cannot_find_module__fs-extra-promise’_during_install_larryonoff/ for the fail logs

@yaronyg please review.
I'm almost sure that you won't like the install.js, line 368, but this's line as a brother to the line npm install --no-optional --production.

Test 896142354fd14d5(4fd14d5) has failed
See https://github.com/ThaliTester/TestResults/tree/896142354fd14d5_fix__Cannot_find_module__fs-extra-promise’_during_install_larryonoff/ for the fail logs

I don't believe this checkin is necessary. Please see the comments.

Review status: 0 of 1 files reviewed at latest revision, 3 unresolved discussions.

thali/install/install.js, line 90 at r1 (raw file):

          return conf.thaliInstall;
        }
        return Promise.reject('Configuration error!');

Shouldn't this return new Error('Configuration error!');?

thali/install/install.js, line 309 at r1 (raw file):

  var thaliProjectName, thaliDepotName, thaliBranchName, btconnectorlib2;

  getReleaseConfig(thaliDontCheckIn)

Why are we passing thaliDontCheckIn to getReleaseConfig when it doesn't actually take an argument?

thali/install/install.js, line 354 at r1 (raw file):

        return uninstallPluginsIfNecessary(weAddedPluginsFile, appRootDirectory)
          .then(function () {
            // this section isn't valid, but it has to be at the moment

This section isn't necessary. What I believe caused the problem is that Rockwell didn't follow the instruction in the readme to 'mkdir -p FooBar/thaliDontCheckIn/localdev'. This instruction tells the install script to just copy the contents of the cloned depot instead of downloading the zip file. If that command had been executed then later on when we call 'jx npm install ../../../Thali_CordovaPlugin/thali/' this would trigger the postInstall script which runs installCordovaPlugin.js which then runs npm on the install directory thus rending this new code unnecessary.

Comments from Reviewable

PR is added to the queue for testing as 1. task. (33949f2)

Test (Success) 89614235 build is completed (33949f2)
See https://github.com/ThaliTester/TestResults/tree/8961423533949f2_fix__Cannot_find_module__fs-extra-promise’_during_install_larryonoff/ for the logs

Test 8961423533949f2(33949f2) has failed
See https://github.com/ThaliTester/TestResults/tree/8961423533949f2_fix__Cannot_find_module__fs-extra-promise’_during_install_larryonoff/ for the fail logs

Review status: 0 of 1 files reviewed at latest revision, 3 unresolved discussions.

thali/install/install.js, line 90 at r1 (raw file):
Previously, yaronyg (Yaron Y Goland) wrote…
> Shouldn't this return new Error('Configuration error!');?

The next `.then` block will receive error as a next value in case of returning `Error('Configuration error!')`, so returning Error isn't valid.

thali/install/install.js, line 309 at r1 (raw file):
Previously, yaronyg (Yaron Y Goland) wrote…
> Why are we passing thaliDontCheckIn to getReleaseConfig when it doesn't actually take an argument?

Looks very reasonable. It looks that it comes from some old logic when this function took arguments.
I'll fix it.

thali/install/install.js, line 354 at r1 (raw file):
Previously, yaronyg (Yaron Y Goland) wrote…
> This section isn't necessary. What I believe caused the problem is that Rockwell didn't follow the instruction in the readme to 'mkdir -p FooBar/thaliDontCheckIn/localdev'. This instruction tells the install script to just copy the contents of the cloned depot instead of downloading the zip file. If that command had been executed then later on when we call 'jx npm install ../../../Thali_CordovaPlugin/thali/' this would trigger the postInstall script which runs installCordovaPlugin.js which then runs npm on the install directory thus rending this new code unnecessary.

I've analysed readme and install.js. As result we have the following scenario.

jx npm install ../../../Thali_CordovaPlugin/thali/ --save --no-optional --autoremove "*.gz" is executed.
thali and thali/install packages are installed for the base directory ../../../Thali_CordovaPlugin/thali/
install.js script downloads Thali from GitHub
install.js runs cordova add for the folder downloaded from GitHub

As result since Cordova hooks depend on installer packages and since we've downloaded clean copy from GitHub packages cannot be found.
So we need somehow install packages for Cordova hooks.

Comments from Reviewable

PR is added to the queue for testing as 3. task. (98e234c)

Review status: 0 of 1 files reviewed at latest revision, 3 unresolved discussions.

thali/install/install.js, line 354 at r1 (raw file):
Previously, larryonoff (larryonoff) wrote…
> I've analysed readme and install.js. As result we have the following scenario.
>
> 1. `jx npm install ../../../Thali_CordovaPlugin/thali/ --save --no-optional --autoremove "*.gz"` is executed.
> 2. `thali` and `thali/install` packages are installed for the base directory `../../../Thali_CordovaPlugin/thali/`
> 3. `install.js` script downloads Thali from GitHub
> 4. `install.js` runs `cordova add` for the folder downloaded from GitHub
>
> As result since Cordova hooks depend on installer packages and since we've downloaded clean copy from GitHub packages cannot be found.
>
> So we need somehow install packages for Cordova hooks.

In addition

"Why it works for build.sh"
Because script created thaliDontCheckIn/localdev directory what means that local thali clone will be used.

When the local folder already has all packages installed.

Comments from Reviewable

Test (Success) 89614235 build is completed (98e234c)
See https://github.com/ThaliTester/TestResults/tree/8961423598e234c_fix__Cannot_find_module__fs-extra-promise’_during_install_larryonoff/ for the logs

Test 8961423598e234c(98e234c) has failed
See https://github.com/ThaliTester/TestResults/tree/8961423598e234c_fix__Cannot_find_module__fs-extra-promise’_during_install_larryonoff/ for the fail logs

PR is added to the queue for testing as 1. task. (8bc729a)

@yaronyg I've analysed the problem deeper. As result I see that README is correct and prepare.sh is correct. The problem occurs since how Cordova runs its hooks. It copies it's hooks into installed plugin directory and then run it's scripts, the hooks folder is for example ThaliTestApp/plugins/org.thaliproject.p2p/thali/install/cordova-hooks, so this folder obviously not having required packages, since it's already installed Cordova plugin folder and not our thali installer folder.

Test (Fail) 89614235 build is completed (8bc729a)
See https://github.com/ThaliTester/TestResults/tree/896142358bc729a_fix__Cannot_find_module__fs-extra-promise’_during_install_larryonoff/ for the logs

PR is added to the queue for testing as 1. task. (77ead0c)

Test (Fail) 89614235 build is completed (77ead0c)
See https://github.com/ThaliTester/TestResults/tree/8961423577ead0c_fix__Cannot_find_module__fs-extra-promise’_during_install_larryonoff/ for the logs

PR is added to the queue for testing as 1. task. (8645e5e)

Test (Success) 89614235 build is completed (8645e5e)
See https://github.com/ThaliTester/TestResults/tree/896142358645e5e_fix__Cannot_find_module__fs-extra-promise’_during_install_larryonoff/ for the logs

Test 896142358645e5e(8645e5e) has failed
See https://github.com/ThaliTester/TestResults/tree/896142358645e5e_fix__Cannot_find_module__fs-extra-promise’_during_install_larryonoff/ for the fail logs

PR is added to the queue for testing as 1. task. (fd4d6ce)

Test (Success) 89614235 build is completed (fd4d6ce)
See https://github.com/ThaliTester/TestResults/tree/89614235fd4d6ce_fix__Cannot_find_module__fs-extra-promise’_during_install_larryonoff/ for the logs

Test 89614235fd4d6ce(fd4d6ce) has failed
See https://github.com/ThaliTester/TestResults/tree/89614235fd4d6ce_fix__Cannot_find_module__fs-extra-promise’_during_install_larryonoff/ for the fail logs

this should be fixed. the fix is just to run setUpDesktop.sh before thali install.

authors: ThaliTester larryonoff yaronyg


text:
Updated getting started docs; mentioned analytic.

Signed-off-by: Bartlomiej Plotka bwplotka@gmail.com

I guess we can consider merging this now with the incubation happening. Text lgtm.

Need to fix links first (:

I guess we still want to have this.

I guess we still want to have this.

authors: bwplotka metalmatze yeya24

repo: thanos-io/thanos


text:
Illuminate Support Version

Hi,
Could you tag your latest dev-master version of the package to 1.0.1, like that I don't need to require the dev master version, and can continue with 1.0.*. And then it will play nice with laravel 4.2. I require it in one of my packages and would prefer not to run it on dev-master.
Thanks

Done!

Thanks, care to do a "Force Update" on Packagist as well?

Yup, done... .need to setup auto update someday.

Thanks! Indeed, quite handy!

@that0n3guy
Been making some modifications to get it working with Laravel 6.0 (and then i'll do 7.0). I managed to use up my 1 force update on packagist as a guest, don't know how long the timeout is. If you could either setup the auto update according to one of the methods here: https://packagist.org/about#how-to-update-packages that would be great.
Otherwise a manual update would work for now. Don't know if there's a different level of access to the repo that you can give me that allows for that integration to be setup.
Thanks


text:
Rename binary to anything other than knife

If this gem is not intended to replace knife, why can't we just rename this gem binary to kinfe_dbag.
ChefDK has a knife binary, knife-solo has a binary with the same name knife

I now understand that this project adds the additional subcommands to existing knife command. Since there is another issue to track it, I am closing this one


text:
Can't update permissions when edit role

Version information

Laravel: v5.7.*
Voyager: v1.3.0 || v1.3.1
PHP: 7.1.30
Database: MySQL 8.0

Description

Can't update permissions when edit role, duplicate route
PUT|PATCH voyager.roles.update TCG\Voyager\Http\Controllers\VoyagerBaseController@update
PUT|PATCH voyager.roles.update TCG\Voyager\Http\Controllers\VoyagerRoleController@update
Steps To Reproduce
Steps to reproduce the behavior:

Edit role
Select permissions (p.e posts)
Send
Instead of executing  VoyagerRoleController@update, VoyagerBaseController@update is executed

A possible solution

Edit Bread Role and add VoyagerRoleController as Main Controller

Can you list exact versions installed not what you are requiring?
Voyager can be 1.3.0 or 1.3.1
Is this happening on a new install or it started after an update?

checked in both versions ( v1.3.0 and v1.3.1 )

i have the same problem in 1.3.1

I was able to reproduce the bug, not really sure yet when this started.
Quick fix without changing any code set in roles BREAD configuration as Controller
TCG\Voyager\Http\Controllers\VoyagerRoleController

@d3turnes v1.3.0 works fine.
The problem is the double declaration of the routes but the second one overrode the first one untill #4605 (merged in 1.3.1) where parameter was changed causing two routes to coesist:
PUT|PATCH | admin/roles/{id}
PUT|PATCH | admin/roles/{role}

Fixed with #4669

Voyager: v1.3.1
Issue still persists
This is NOT fixed yet, i.e. default vanilla installation of voyager still results in erroneous saving of users/roles

@kingIZZZY This bug affects only v.1.3.1, it's fixed in 1.3-dev and next release (v1.3.2) will contain fix.
You can fix it in the way described in my other comment.

How can composer update to the bleeding edge latest commits?
Even as time goes on and more commits happen it would be great if i can keep updating to the latest fixes

NOT fixed for me in 1.4-dev. I can't update the Roles page

That's what's in the upgrade guide for 1.4, yes.

@Hirbod that's because the final fix is setting that in BREAD but if you are updating you need to do that manually.
There was a temporary fix in 1.3.2 that didn't require to set that because it's a breaking change.

authors: Hirbod MrCrayon Parmgy d3turnes emptynick kingIZZZY

repo: the-control-group/voyager


text:
Multiple Files/Images

Hi. Could you add the ability to upload multiple files and images?

I have the same questions. how to modify the upload form with multiple images upload?

It should already be possible to add multiple files add once.

@marktopper what about storing images as an array of String? eg: image galleries.

@uchsarath, this issue has been closed for nearly a month and your question is unrelated to the original.  Please open a new issue if you still have questions/comments

authors: AlexDukachev fletch3555 marktopper uchsarath


text:
Moved factory definitions to config.

Moved factory definitions to config.
Updated old static references to models to use new factory methods.

These changes makes it possible to override stuff in a more consistent way, as far as I've tested the changes does not create any issues. It mostly abstracts stuff to config and makes use of the factory methods where it wasn't before.

I have no idea why all those other commits are showing up... I just checked the actual git branch and it looks fine to me.

I updated the PR and removed policies from the config file, I also deprecated the useModels method as requested.

I will split this into 2 PR's aswell. one containing the bug-fixes with the factory models and one with the change to configs.


text:
"No such file or directory: '/opt/conda/bin/python2.7'"

Do i have install the python ver 2,7 to lean the courses?

Hi @Adsyarif, I'd recommend using the updated course here, which uses many updated libraries, including Python 3.7 and TensorFlow 2. Let me know if there's any reason why that's an issue for you.

authors: Adsyarif jonkrohn


text:
intro + abstract institutionalized organisation

We need a proper abstract and an intro for the institutions that we require. I don't think we have written a lot yet about that in the intro.

recreated the original draft PR as #10

authors: CaptainSifff mhagdorn


text:
npm run <script> error

Running npm run <script> (or npm run compile in my case), on the TestFlight latest build, errors out, while using the run button when the said file is open, works. Please see attached images for more info.

I have tried adding .js as the file extension in the second screenshot, as well, but it outputs the same thing. I can also confirm that the file paths are correct.

Ran into this issue, too. Running the commands for each script directly in the terminal works fine. Running it via npm run xyz fails.

authors: Lukas-Batema brandonsheppard

repo: thebaselab/codeapp


text:
Get User credentials after successful login

After successfully login with the Facebook login dialog, the result doesn't return the actual use credentials.
Instead it returns: {"declinedPermissions": [], "grantedPermissions": ["public_profile", "email"], "is
Cancelled": false}
LoginManager.logInWithPermissions(["public_profile"]).then(
  function(result) {
    console.log(result)
    //I get this in the console: {"declinedPermissions": [], "grantedPermissions": ["public_profile", "email"], "is
Cancelled": false}
    }
  },
);

Maybe related, react-native-firebase auth is having difficulty consuming the output from this module at the moment, that issue could use more triage before saying it is definitely related: https://github.com/invertase/react-native-firebase/issues/5106

@PrincewillIroka thanks for reporting this bug.
Does it happen all the time?
Would you mind to clone this repo and implement some test for it in order to reproduce?
That would help me a lot in order to debug it and specially having your constraints (environment and platform) set to reproduce :)

Be sure to check that you have enabled the facebook auth in the firebase console. I had the same issue, and enabling it fixed the problem

Interesting! That might explain why I have not been able to reproduce it in my project or help (I maintain react-native-firebase and wanted to solve this one...) thanks @zRelux - curious to here from @PrincewillIroka if that was the problem

I've sorted the issue. @zRelux Thanks for your suggestion and @mikehardy thanks for your efforts too.
I also found out that I was making a mistake by trying to access the user credentials from here directly:
const result = await LoginManager.logInWithPermissions([
      'public_profile',
      'email',
    ]);
console.log(result)

I had to get the user AccessToken, pass it unto auth (from  '@react-native-firebase/auth) before gaining access to the user credentials.
import auth from '@react-native-firebase/auth';

    if (result.isCancelled) {
      throw 'User cancelled the login process';
    }

    // Once signed in, get the users AccessToken
    const data = await AccessToken.getCurrentAccessToken();

    if (!data) {
      throw 'Something went wrong obtaining access token';
    }

    // Create a Firebase credential with the AccessToken
    const facebookCredential = auth.FacebookAuthProvider.credential(
      data.accessToken,
    );

    // Sign-in the user with the credential
    auth().signInWithCredential(facebookCredential);
    auth().onAuthStateChanged((user)=>console.log(user));

Glad to see that everything went fine in this issue :)

authors: PrincewillIroka mikehardy thebergamo zRelux

repo: thebergamo/react-native-fbsdk-next


text:
Periodically rebase firebase-cpp-sdk with upstream

Description
This workflow runs thebrowsercompany/gha-sync-fork at 8 am every day.
It can also be triggered manually using:
gh workflow run 'cron-sync-with-upstream.yml' -R thebrowsercompany/firebase-cpp-sdk

Or by clicking the "Sync this Fork" button in the GitHub UI.
Testing
See this workflow run: https://github.com/thebrowsercompany/firebase-cpp-sdk/actions/runs/9104534949

Nice! This seems like the right approach. I still think that there is some value in compressing all the CI changes that we have as their history doesn't actually give us anything.

Agreed! Let's talk about this today: We can either squash the changes periodically, or I can add a parameter to the gha-sync-fork workflow that attempts to do it automatically every time we sync.

What's the flow to handle rebase failures? Once we have one conflicting commit in our history, will all subsequent rebases fail?

Yep, and someone will have to fix the conflict to get this job to succeed again. let's also talk about this today too. We could have some alerting if needed, but I'd like to hear how everyone thinks that alerting should work, and any other ideas we may have.

repo: thebrowsercompany/firebase-cpp-sdk


text:
Have you tried multiple accounts using 1 telegram account?

Hey there)
Have you tried multiple accounts using 1 telegram account? Have you checked if telegram user id is transferred to HERE backend? (in this case they could ban account if they see one tg uses multiple accounts)

Hi! Each claim session operates independently with its own set of cookies: Telegram cookies specifically for web.telegram.org, and game cookies under tgapp.herewallet.app. Consequently, I'm able to run 5 to 6 game sessions per single Telegram login. Regarding data sharing, to the best of my knowledge, Telegram only relays IP addresses and other basic information to HereWallet, as indicated in their notification pop-ups. I haven’t delved deeply into the specifics of what the API transmits.
As for the potential of being banned, it presents an interesting scenario since your rewards are mined directly onto the Near Protocol Blockchain, as can be seen on the blockchain explorer. To my knowledge, there aren't any Terms and Conditions tied to the usage of the HereWallet app, or at least nothing explicitly agreed upon during the signup process.

Based on your question, I have updated the readme documentation:
💡 TIP: While you cannot register more than one wallet to a single Telegram username, this script enables you to manage multiple pre-existing HereWallet accounts using just one Telegram account by initiating multiple individual sessions. For straightforward setup, consider using SCREEN (refer to the quick start guide below). For more advanced users, PM2 is recommended.

Thanks!

Always a pleasure, and a great question by the way.
P.S. Feel free to update to the new version, it's running about 30 seconds per claim faster than the last version, and is more stable in making claims :)

I have 14 accounts running on the same server, and have the setting to allow 4 simultaneous claims at once. I forced PM2 to restart them all to watch the log go crazy initializing them all again.

I have 14 accounts running on the same server, and have the setting to allow 4 simultaneous claims at once. I forced PM2 to restart them all to watch the log go crazy initializing them all again.

Wow, not bad at all)

authors: Wapweb thebrumby

repo: thebrumby/HotWalletClaimer


text:
Optimize the output GIF size.

https://github.com/thec0sm0s/image-processor/blob/513bf2d3d8e96db4893692e3ebfd415fb5e0f0bc/app/api_resources/discord/welcome_banner.py#L104-L110
This is the most obvious way to generate GIFs using Python PIL. However when the input GIF consists of more number of frames or are just of higher resolution, the resulting processed GIF size goes around of size ranging 10-15MB. Maybe use some kind of compression or opimization algorithms for examples drop consecutive frames which look similar or any possible way to optimize the resulting GIF.

Hello! I would like to contribute, may I be assigned to this issue?

Thanks for considering this! I would love to.

You may join Discord community for follow up on this or normal fest discussions, etc


text:
CSS columns? For two-column layout

Should the two column layout use css columns instead of two page objects

Just coming across this project. I've experimented with similar things, and it depends on how you "print" ... In my experience WebKit browsers currently turn CSS columns into 1 column when sent to print. Firefox (and phantom.js) are what I can get to print CSS multi columns correctly.

authors: bjornmeansbear cathschmidt

repo: thedesignoffice/babybindery


text:
navbar not working - android, mobile view

on my android (4.1.2) phone with chrome 43.0.2357.78 (and also with the 'Internet' app) the navbar cannot be toggled, this means the menu items are not visible and navigating a site is impossible.
first experienced on my own site but it actually happens on http://thednp.github.io/bootstrap.native/, too.

only occurs on the actual device; inside the chrome developer tools things work just fine
while loading the page an Uncaught ReferenceError: Popover is not defined(anonymous function) @ scripts.js:5 error occurs (via: Remote Debugging on Android with Chrome)

Hey, can you please do a test like this on your phone
var btn = document.querySelector('.myButtonMenu'); // give the selector a proper value here, create the button
var div = document.querySelector('.myDiv'); // give the selector a proper div, a demo only div, create the div

btn.addEventListener('click',function(){
  div.innerHTML = 'clicked'
},false);

I need to know if the click is triggered, or it's a CSS glitch.
Thanks for reporting.

Closing this until further notice.

for all intents and purposes, this seems to have been solved.
tried with

android 5.1.1 and chrome 47.0.2526.83
android 4.2.2 and native browser app
on http://thednp.github.io/bootstrap.native/
(sorry, for not getting back earlier)

Thanks for the heads up.

authors: iiegn thednp


text:
Add websocket example

A websocket example that takes data from a redis queue and sends it to the browser.

Coverage remained the same at 93.83% when pulling b7971913474066d610655332ecc34540b6f88161 on websocket into 1089c6cb050a9ed6397a5e983a00c554c56535c3 on master.

authors: amarandon coveralls

repo: thefab/tornadis


text:
Issue scraping prices

Searching for prices using the following code
from pypartpicker import Scraper

# creates the scraper object
pcpp = Scraper()
# returns a list of Part objects we can iterate through
print ("Including entries without prices")
parts = pcpp.part_search("AMD Ryzen", region="uk")

# iterates through every part object
for part in parts:
    # prints the name and price of the part
    print(part.name)
    print(part.price)

print("Excluding entries without prices")
for part in parts:
    if part.price is not None:
        # prints the name and price of the part
        print(part.name)
        print(part.price)

Yields the following results

But upon checking the results for the same search on pcpp, you can see that many of these cpus do have prices

Am I missing something or are the prices not being scraped correctly?

Fixed my issue perfectly, Thank you!

repo: thefakequake/pypartpicker


text:
Add guide on working with Effection and TypeScript

One of the gaps in Effection is that it has some idiosyncrasies in working with TypeScript. In particular with the way TS handles generators, there is no way for the right hand side of a yield expression to influence the inferred type of the left hand side. As a result, you need to explicitly annotate your intermediate values, otherwise TS infers them as being of type any
// `bare` is typed as `any`
let bare = yield Promise.resolve(10);

// to get type support you need to explicitly annotate
let num: number = yield Promise.resolve(10);

This can be problematic since you can actually get it wrong and get the compiler out of sync with the actual code which can result in mystifying runtime errors.
// this will type-check just fine
let num: number = yield Promise.resolve('not a number!');

The fact that there is not inference is confusing as seen here and so we should arm folks with the knowledge a) not to be suprised by it and b) how to work with it, because it's something that will likely happen very soon in their journey.

Gotcha thanks, I was asking to figure out the way of explaining the limitation in the guides.

Closed by #599

authors: cowboyd jorgelainfiesta

repo: thefrontside/effection


text:
Collapse does not work

i downloaded the latest version .. put it in a folder main/themes/geekdoc
i started my main project with hugo server -D
added the geekdocCollapseSection: true
but nothing appears

Hi, needs some more input. What browser do you use? hugo server -D runs without errors? What exactly means  "nothing appears"? Do you have content added to your site? How does your content look like? geekdocCollapseSection needs to be added to your page front matter.

You can find an example folder structure here https://github.com/thegeeklab/hugo-geekdoc/tree/master/exampleSite/content/collapse. Thats how the documentation page is deployed https://geekdocs.de/ where you can see collapse in action.

I copied the content towards my application but the collapse does not work .. on the other hand geekdocHidden works fine

the arrows do not appear near the collapse menu

What browser do you use?

I'm not able to reproduce it:
hugo new site demosite
cd demosite
mkdir -p themes/hugo-geekdoc/
curl -L https://github.com/thegeeklab/hugo-geekdoc/releases/latest/download/hugo-geekdoc.tar.gz | tar -xz -C themes/hugo-geekdoc/ --strip-components=1
vi config.toml # add the content from the getting-started guide
cp -r  /tmp/hugo-geekdoc/exampleSite/content/collapse/ content/
hugo server -D

thank you it works now

authors: mahmoudozil xoxys

repo: thegeeklab/hugo-geekdoc


text:
Removes gridworks and safety dependencies to cut down on total dependencies

Removing these removes ~45 dependencies

Removes gridworks and safety dependencies to cut down on total dependencies. Removing these removes ~45 dependencies.

repo: thegridelectric/gridworks-protocol


text:
create footer ui

create footer folder to add new different footer ui component .
till now 3 component are added

Additional footer
link footer
simple footer

Bro, make some quality content, this is a very basic design, and I recommend you add some styles

ok

should i change this and add new ones or what

change it and add styles

@thekavikumar you can assign me this issue . I can make good improvements in footer section

repo: thekavikumar/love-simple-ui


text:
Need to manually interact with spotify first, otherwise returns 404: Not Found

When I open a player and send a play request it returns 404: Not found. After manually starting a song in the player, I can again control it, but if nothing has played for a while the error returns, even though the player has stayed open.

Hi @fartbender. Thanks for opening this issue.
If I understand you correctly, the application you're building using this wrapper doesn't work properly until you've interacted with the official Spotify client. Is this correct?

Hi there - That is correct. I should probably say that I am building it using Node-red

I have the same issues

We encounter the exact same issue for a few weeks now. We have a NodeJS service in our backend which uses the spotify web api to play/stop songs. We always receive a [Error [WebapiError]: Not Found] error until we start/stop a song manually in the Spotify Player. After that the play/stop command works for a few minutes without any issues.

repo: thelinmichael/spotify-web-api-node


text:
Simplify base theme

Tidies it up a little by removing unnecessary borders. All the themes we ship did this, so might as well improve base styles to simplify things.

I'm not too fond of this, really. I don't think we should make all our themes look alike.
The unnecessary borders are actually a nice design choice I think. Sure, they aren't necessary for The Lounge to work, but that's not the point of a theme :-)
They do make it for a nice theme. If a more "pure" version should arise, more flat-UI style, with less borders, etc., then we're talking about a new theme.
However, I do believe you have a point regarding all non-default themes that constantly cancel what the default one does. To solve this, we should start moving all design-specific items from style.css to example.css. I wanted to start this with the nick colors but then forgot.
That way, in the not-so-long term, style.css contains items that are necessary for the app itself, and theme files do contain what's specific to the theme their author has designed. Also, themes having more independence means less risk to break them by changing UI elements for the default theme.
Finally, as @maxpoulin64 keeps saying 😄, doing so will be a step towards theme management.
Now, I'm not saying this should be in one go. For example, when I get to deal with https://github.com/thelounge/lounge/issues/335#issuecomment-219295830, I could move the colors to the theme files instead...

The point of this PR was not only to make it easier for themes to change styles, but also to remove the unnecessary padding. I can hardly agree that it makes for a nice design choice. Take a look at a lot of other chat software, they try to give the chat window as much space as reasonably possible.

I agree with @xPaw on this one. The simpler the base theme the better, as every other theme is based on that. Currently, themes have to fight with every detail we add to the base them to remove them. I'd rather have to use a theme (we could even call it Shout, as that's where it comes from) to keep it than have the default theme be a problem for the other themes.
Plus, it would also help The Lounge set itself further apart from Shout. So personal tastes aside, that's still a 👍 for me.

Moving design-specific stuff away from style.css is a mandatory step anyway if we really want to be serious about theme management. Until we do so, all themes will always have to cancel out what style.css does.
The maintenance burden will not necessarily be more costly as what we have so far (think of all the times we had to ask PR authors "can you add this to other themes too?" or "did you test this with other themes to make sure it doesn't break them?")
I'll test this before merging.

I like the looks.

authors: JustRamon astorije maxpoulin64 xPaw

repo: thelounge/lounge


text:
fix(/components/sidebar): remove Sidebar.Collapse parent Tooltip on child hover

Changes

[x] refactor(/components/dropdown): remove extraneous @ts-expect-error
[x] fix(/components/sidebar): remove SidebarCollapse parent Tooltip o…

Description
In Sidebars with a Sidebar.Collapse, when you hover over a child Sidebar.Item,
the parent's Tooltip is still displayed, erroneously.
Now only the child's Tooltip comes up when you hover over that child.
This new behavior causes a different problem where the parent's Tooltip isn't
visible at all, even when you hover over the parent button. To solve that, we just
add an HTML title attribute to the button.
Fixes #429
Type of change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)

Breaking changes
N/A
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[x] Test A: Navigate to the Sidebar section in Storybook. Select the Multi-level dropdown example. Expand the collapse. Set the Sidebar to collapsed. Hover over the child item inside the collapse to observe the new, correct behavior.

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules
[x] I have checked my code and corrected any misspellings

Weird, I'm not sure why but this issue with my refactor commit is coming up in the CI, but it currently blocks me from running yarn build:lib if I don't remove the @ts-expect-error from my local machine. I'll just remove that for now.

repo: themesberg/flowbite-react


text:
🛑 Image server is down

In e46944d, Image server (https://image.themonetizr.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Image server is back up in ff8e5be.

repo: themonetizr/upptime


text:
🛑 Console is down

In 90e1460, Console (https://api.themonetizr.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Console is back up in 6fcb68e after 9 minutes.


text:
Promise.prototype.finally is not aligned with the most current spec draft

According to draft 4 of the Promise.prototype.finally spec , the callback parameter might not be callable.
Spec: https://tc39.es/proposal-promise-finally/
Similar issues: https://github.com/stefanpenner/es6-promise/issues/336

OMG. We have hundreds of Sentry issues that I've been debugging for weeks and weeks on and off, made so much worse by the really poor unhandled promise rejection stack I was getting in our react-native environment made this immensely difficult to track down. Turns out I was trusting the types too much and thought it was safe to do
myPromiseFn().finally()

Because the types say that the argument to finally is optional. I was doing this throughout my code because I was otherwise getting ESLint warnings saying I needed to await the promise that was returned. Doing this was my way of communicating that I know what I'm doing and do not intend to await this promise (in a useEffect() for example).
tl;dr
This library requires a function to be provided to finally and if not provided it throws with:
TypeError: undefined is not a function

Types Expectation
The types I find when clicking through to the definition of finally() are as follows:
interface Promise<T> {
    finally(onfinally?: (() => void) | undefined | null): Promise<T>
}

These types are provided directly from Typescript.

SEO for others in pain
Warning message I was receiving:
Possible Unhandled Promise Rejection (id: 0): TypeError: undefined is not a function

Sentry polyfills promise to make it nearly identical to the normal react-native promise, but also adds in sentry tracking of unhandled promise exceptions. This was the specific usage of this library I found.
Trying to find the original stack trace of unhandled promise rejections in this particular scenario was gruelingly difficult as the stack never included relevant code, just library code like the following:
(When Sentry was normally polyfilling)
TypeError: undefined is not a function
    at anonymous (http://127.0.0.1:19000/index.bundle?platform=ios&dev=true&hot=false:125276:31)
    at tryCallOne (http://127.0.0.1:19000/index.bundle?platform=ios&dev=true&hot=false:125101:16)
    at anonymous (http://127.0.0.1:19000/index.bundle?platform=ios&dev=true&hot=false:125182:27)
    at apply (native)
    at anonymous (http://127.0.0.1:19000/index.bundle?platform=ios&dev=true&hot=false:26192:26)
    at _callTimer (http://127.0.0.1:19000/index.bundle?platform=ios&dev=true&hot=false:26111:17)
    at _callReactNativeMicrotasksPass (http://127.0.0.1:19000/index.bundle?platform=ios&dev=true&hot=false:26141:17)
    at callReactNativeMicrotasks (http://127.0.0.1:19000/index.bundle?platform=ios&dev=true&hot=false:26304:44)
    at __callReactNativeMicrotasks (http://127.0.0.1:19000/index.bundle?platform=ios&dev=true&hot=false:19761:46)
    at anonymous (http://127.0.0.1:19000/index.bundle?platform=ios&dev=true&hot=false:19573:45)
    at __guard (http://127.0.0.1:19000/index.bundle?platform=ios&dev=true&hot=false:19745:15)
    at flushedQueue (http://127.0.0.1:19000/index.bundle?platform=ios&dev=true&hot=false:19572:21)
    at callFunctionReturnFlushedQueue (http://127.0.0.1:19000/index.bundle?platform=ios&dev=true&hot=false:19557:33)

(When Sentry was set to enabled: false)
WARN  Possible Unhandled Promise Rejection (id: 5):
TypeError: undefined is not a function
TypeError: undefined is not a function
    at anonymous (/Users/distiller/react-native/sdks/hermes/build_iphonesimulator/lib/InternalBytecode/InternalBytecode.js:339:28)
    at tryCallOne (/Users/distiller/react-native/sdks/hermes/build_iphonesimulator/lib/InternalBytecode/InternalBytecode.js:53:16)
    at anonymous (/Users/distiller/react-native/sdks/hermes/build_iphonesimulator/lib/InternalBytecode/InternalBytecode.js:139:27)
    at apply (native)
    at anonymous (http://127.0.0.1:19000/index.bundle?platform=ios&dev=true&hot=false:26192:26)
    at _callTimer (http://127.0.0.1:19000/index.bundle?platform=ios&dev=true&hot=false:26111:17)
    at _callReactNativeMicrotasksPass (http://127.0.0.1:19000/index.bundle?platform=ios&dev=true&hot=false:26141:17)
    at callReactNativeMicrotasks (http://127.0.0.1:19000/index.bundle?platform=ios&dev=true&hot=false:26304:44)
    at __callReactNativeMicrotasks (http://127.0.0.1:19000/index.bundle?platform=ios&dev=true&hot=false:19761:46)
    at anonymous (http://127.0.0.1:19000/index.bundle?platform=ios&dev=true&hot=false:19573:45)
    at __guard (http://127.0.0.1:19000/index.bundle?platform=ios&dev=true&hot=false:19745:15)
    at flushedQueue (http://127.0.0.1:19000/index.bundle?platform=ios&dev=true&hot=false:19572:21)
    at callFunctionReturnFlushedQueue (http://127.0.0.1:19000/index.bundle?platform=ios&dev=true&hot=false:19557:33)

Identifying the offending line of code
I tried a few different StackOverflow answers for trying to find the real stack trace of the promise that was causing the issue I was seeing. As noted the stack trace that is printed does not end up leading to any code I have written, which made it questionable whether it was my fault or potentially some other library causing the issue.
After trying to use bluebird as suggested here I curiously found that the warning went away. Now I know it was because Bluebird promise implementation does not require a finally parameter!
In the end, I did the following to identify the offending line of code (sorry this isn't a patch-package patch as we do not use that lib)
I manually added three lines in two files.
File 1: node_modules/promise/setimmediate/core.js
Add the following line of code in the function Promise(fn) {... function (line 61 for me).
  this._stack = (new Error()).stack;

File 2: node_modules/promise/setimmediate/rejection-tracking.js
Inside the enable function where a setTimeout is called (line 47 for me) with:
onUnhandled.bind(null, promise._51)

Replace it with:
onUnhandled.bind(null, promise._51, promise)

Then in the onUnhandled function just add a 2nd parameter "promise" and console log there and you'll see the _stack field printed out with the original location where the Promise was created.
  function onUnhandled(id, promise) { // line 60 for me
    console.log("rejection-tracking:61 - onUnhandled", id, promise)

Although I got a bundled stack trace I was still able to track it down when the code was not minified.
NOTE: This is NOT performant and SHOULD NOT be included in any production builds as calling (new Error()).stack on every promise constructor will slow things down a lot. For debugging this is not an issue though.
I'd love for someone to tell me how I could have done this an alternative way as I feel it is ridiculous I had to go through these steps.

repo: then/promise


text:
[Feature Request] Add a message option when sending coins

Hi there! Actually, I have a feature request for the software.
When we want to send coins, there are the address fields, amount, and the fees charged...
So, can we have a 'Message' option as well? Like if someone wants to send some coins with a message, how could he do it?
Can we add such a feature?

This has been moved to the Design Repository

repo: thenewboston-developers/Account-Manager


text:
Timesheet - 17/04/2021 - James Pang

Task 1
Reviewed and merged PRs
Proof of Work

https://github.com/thenewboston-developers/Website/pull/1715
https://github.com/thenewboston-developers/Website/pull/1716

Time Spent
1 hours

Task 2
Proofread, add Terms of Service and Privacy Policy pages to website according to figma design
Proof of Work

https://github.com/thenewboston-developers/Website/pull/1726

Time Spent
4.5 hours

Task 3
Reviewed Sanjeev's tutorial PR and added some small changes
Proof of Work

https://github.com/thenewboston-developers/Website/pull/1666

Time Spent
1 hour

Task 4
Investigated on font size issue in website, realised the underlying problem and created a fix
Proof of Work

https://github.com/thenewboston-developers/Website/issues/1722
https://github.com/thenewboston-developers/ui-js/pull/18

Time Spent
2 hour

Task 5
Reviewed PRs in thenewboston/ui
Proof of Work

https://github.com/thenewboston-developers/ui-js/pull/14
https://github.com/thenewboston-developers/ui-js/pull/13

Time Spent
.5 hour

Total Time Spent
9 hours
Account Number
c54c04774efaae20746fd3f29cdd619fea512e119bc1082b863572b2e8844104

Approve

Approved

authors: itsnikhil jamessspanggg manishram


text:
FAQ clicking title issue on homepage

Bug Description
On FAQ on the homepage when clicking the title the page scrolls into the question and it's making the question you clicked to go to the top.
Steps to Reproduce
Steps to reproduce the behavior:

Go to 'https://thenewboston.com/'
Scroll down to 'Bottom until you see the FAQ and click on one of the titles'
See an error

Expected behavior
When I click on the title the position of my screen should be the same. and when the title is clicked it will just open the card. not put the title on the top of my screen.
Actual behavior
The FAQ on the homepage makes the position of title on the top when you clicked it.
Screenshots/Recordings

OS and Browser

Browser Chrome

Account Number
6a25290a1c04252563d286790194bfd341e2656bcad17e9bbf75d7a626946067

Duplicate of #1989

authors: jamessspanggg markmendozadev

repo: thenewboston-developers/Website


text:
Can a second instance be run in a child bridge?

Describe Your Problem:
I am using two Caseta hubs. Can a second instance of the plugin be run, perhaps via a child bridge, to be able to use the plugin with both hubs?

Hi @JoelGit! I've done some poking around and had some discussions about mDNS related to multiple bridges. I expected it to work, but only have one and obviously hadn't tested it. I'd love to get it working. Can you describe what you see when you try?

Will do!

Any chance you have tested this? I still expect it to Just Work.

Please reopen if this is still a problem

authors: JoelGit thenewwazoo