Trouble building argus_camera

I'm trying to build argus_camera on my jetson Nano as I would like to start my project of a wrapper of libargus to be able to setup more settings that gstreamer allows us.
When doing cmake .. at argus_camera/build
/argus_camera/build$ cmake
-- The C compiler identification is GNU 7.5.0
-- The CXX compiler identification is GNU 7.5.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Could not find Tegra Multimedia API
-- Configuring done
-- Generating done
-- Build files have been written to: /home/nicolas/argus_camera/build
You can see the line "Could not find Tegra Multimedia API' comming from the CMakeList.txt
find_package(TegraMM REQUIRED)
if(${TegraMM_FOUND})
message(STATUS "Found Tegra Multimedia API")
else()
message(STATUS "Could not find Tegra Multimedia API")
endif()
Then when triyng make I have the error:
/home/nicolas/argus_camera/src/ArgusCamera.cpp:3:10: fatal error: Argus/Argus.h: No such file or directory
#include "Argus/Argus.h"
I had the source files of the Tegra Multimedia API on my Jetson image at /usr/src/jetson_multimedia_api so I think I have the Tegra Multimedia API included in the flashed image.
I compiled /usr/src/jetson_multimedia_api/argus with succes and can use an executable like /usr/src/jetson_multimedia_api/argus/build/samples/oneShot/argus_oneshot
I also tried with succces:
sudo apt install nvidia-l4t-jetson-multimedia-api
Am I missing something? Can someone explain how to setup libArgus to be used as a package? Or do I have to flash a specific image?

Ok I found the solution myself checking FindTegraMM.cmake
I had to cp /usr/src/jetson_multimedia_api to /home/hostname/tegra_multimedia_api
But now I have a lot of cpp errors like not finding methodes, wrong type, etc
Maybe the API evolved since 2017
Which version of the API were you using with the repo?
Or maybe I'll try to update it myself.


feat(skopeo-sync-gen): Introduce new clustertask

Introduces a new ClusterTask responsible for running new skopeo-sync-gen subcommand of crane.
Also addresses issues with how oc-registry-info ClusterTask was emitting results (ie. remove newlines).
Fixes #55

/hold
May not be necessary to have a dedicated task for this.


Add Tree Maker

Project URL
https://ddddddo.github.io/gtree/
Category
Converters
Description
Added Tree Maker to Converters category.
Why it should be included to awesome-markdown (optional)
Website that converts markdown to tree.
This page calls a function that outputs tree. This function is a Go package compiled as WebAssembly.
You can change the branches.
Also, once loaded, you can enjoy offline!
image
Checklist

[x] Only one project/change is in this pull request
[x] Addition in alphabetical order
[x] Has a commit from less than 2 years ago
[x] Has a clear README in English

@BubuAnabelas
Hi👋!
I think it's a good site, please merge it!

@BubuAnabelas
Hi☀!
How about this pr? Sorry if you're busy!


Add a CONTRIBUTION.md file.

Currently, we lack on documentation on how the beginners should start contributing to the library. We should add a CONTRIBUTION.md file that will contain all the information required by the beginners to start contributing.
The key points on the documentation/file will include -

Development environment required before contributing.
Git principles that should be followed while contributing to the library.
The code style.
How to claim an issue?
How to make a successful Pull Request?

Hey, I'm a beginner though I'd love to help you out with this!

Thank you so much @daniellekush for your interest 🙂  I am assigning this issue to you.
Once a PR is ready we can discuss on what can be added more or removed.

@daniellekush Are you working on this issue?

Closing this issue and creating a new one to attract contributors.


Clicking a link created using an @link JSDoc tag, opens the same file again in a weird state

Initial checklist

[X] I read the support docs
[X] I read the contributing guide
[X] I agree to follow the code of conduct
[X] I searched issues and couldn’t find anything (or linked relevant results below)

Affected packages and versions
unifiedjs.vscode-mdx
Link to runnable example
No response
Steps to reproduce

Create an MDX file with the following content:{/** {@link Component} */}
export function Component() {}

Hover the Component function identifier.
Click the Component link.

Expected behavior
The user is taken to the Component, which happens to be in the same place in this example. Within JavaScript files, this works as expected.
Actual behavior
The same file is opened in a new tab a weird state. The breadcrumbs show the full file path instead of a relative one.

Runtime
No response
Package manager
No response
OS
No response
Build and bundle tools
No response

This was solves upstream in Volar 2.3.0.

This was solved for hover info, but not completion items.


Example shows confusing use of strings vs. generator

jsc.forall accepts generators. However, the first thing a newbie user sees is the following:
jsc.forall("bool -> bool", "bool", function (f, b) {
    return f(f(f(b))) === f(b);
  });

I'm led to think that you're actually supposed to put the string "bool -> bool" as the first argument. Is there any way we can clarify this?

That is what you put as the first argument, yes.
To clarify this, try it, and see that it works.

There is: https://github.com/jsverify/jsverify#dsl-for-input-parameters

@fatuhoku does that documentation section helps at all, or should we try to improve it.
At least I should expand it with a bit more examples.

@phadej it may just be me being new to Javascript — the documentation calls the use of strings in place of the actual expected values a 'DSL' but I didn't really think it was one.
What I understand as a (e)DSL is something like https://github.com/Masonry/Masonry.

@fatuhoku DSL (domain specific language) is a broader term then EDSL (embedded domain specific language). The latter inherits the syntax and constructs of the host language, e.g. Masonry is EDSL, a library in objective-c. The former (DSL) can be anything.
In jsverify case we can construct generators using JavaScript, .e.g jsc.array(jsc.nat). One could say that is EDSL. Or than you can use a bit different language: "array nat", which isn't embedded anymore.

There is possibility of confusion, but I don't know how to explain this more clearly; I can put the text above in a footnote of README if it does clarifies even a bit.

@fatuhoku A "domain specific language" is just a language which is purposed to a task, rather than a language whose usage is open ended (a "general purpose language.")
CSS is a DSL.  Javascript is not.

In general, the useful cutting criterion is "do whole chunks of software not make sense in this language?"
It doesn't make sense to implement a database or an operating system kernel under CSS; it doesn't make sense to implement an eReader in SQL; it doesn't make sense to implement an email parser in a computer algebra system; it doesn't make sense to implement a BIOS in Hypercard; it doesn't make sense to implement a chess UI in an expert systems language; et cetera.
Not "this would be a bad choice."  It would be a bad choice to write a web browser in Erlang because Erlang's access to UI controls is so painful.  But it can be done.
I mean "this literally isn't a goal that can be considered."
If that's a common outcome, then you're almost certainly looking at a DSL.
POV-Ray is a DSL.  Prolog is not.

Point well made.


Auto Count Fixed #5510

Issue Reference
Link: https://github.com/bagisto/bagisto/issues/5510

@devansh-webkul
This is working fine


Rule changes so that label files always match viewables; misc bugfixes; all unit tests pass

I don't think these changes will affect the OPUS import. They are mainly for Viewmaster and mostly cosmetic. The main issue is that the rules were inconsistent about whether a "viewable" applies to the label files or just the data files. Now they always apply to the label file as well as the data. BTW, it may be necessary to copy some more GO_0xxx data files into the Dropbox directory for those new unit tests to succeed. (The files needed are scattered all over the volumes, so the easiest way to do this is to create a file listing the new file paths as found in the rules/GO_0xxx.py pytests, and then use "rsync -av --files-from=  ".)

I verified this branch does not break the OPUS import.


Storing Model Metadata

We want the user to be able to view the model's metadata, such as the number of seeds it has been trained to identify, and other pieces of information that might be useful to the user.
We need to store such information in a JSON file somewhere that can be accessed via the backend.
https://learn.microsoft.com/en-us/rest/api/azureml/

@RussellJimmies document an example of the JSON to serve as specification and share with datascience group

Archives from project board on November 14

Archives from project board on November 14


"Bad substitution" errors with updater and prefsCleaner

Hallo!
Both updater.sh and prefsCleaner.sh produce a "Bad substitution" error. Specifically:
./prefsCleaner.sh: 12: ./prefsCleaner.sh: Bad substitution
./prefsCleaner.sh: 15: ./prefsCleaner.sh: Bad substitution

and
./updater.sh: 13: ./updater.sh: Bad substitution
./updater.sh: 14: ./updater.sh: Bad substitution

I use Debian GNU/Linux 10.2. I have both files in my Firefox profiles directory and invoke them in bash via "sh ./prefscleaner.sh" and "sh ./updater.sh".
What am I doing wrong?

https://github.com/ghacksuserjs/ghacks-user.js/blob/8f76d9439f1b7998d100bc0cda316a8f2dcba741/prefsCleaner.sh#L1
The shebang is bash and not sh. Line 12,15 contains ${BASH_SOURCE[0]} where shellcheck --shell=sh prefsCleaner.sh says  ^---------------^ SC2039: In POSIX sh, array references are undefined.. Maybe you need to start with bash prefscleaner.sh

Debian probably uses "dash" as "sh". Call scripts using "bash".

 You are absolutely right. Thank you!


Slow start of Alluxio client in Word Count

Alluxio Version:
2.4.1
Describe the bug
When I test wordcount task using mapreduce on alluxio, I found that it takes longer for map containers which read from alluxio to finish compared with those read from hdfs. More precisely, after the container starts, containers read from alluxio need about more 4~8 seconds to initialize and then read the first record.
It seems a slow start of alluxio client. Then I add some debug logs to figure out which steps alluxio delays. The logs tell that alluxio client takes about 4 seconds to load configurations with meta master.
Since the total cost of each map task is only about 40s, alluxio shortens the time to read data, but spends more time on initialization. So it seems that alluxio can not help with such mapreduce tasks.
Here is the debug code I add:
# alluxio.util.ConfigurationUtils.java
public static GetConfigurationPResponse loadConfiguration(InetSocketAddress address,
      AlluxioConfiguration conf, boolean ignoreClusterConf, boolean ignorePathConf)
      throws AlluxioStatusException {
    GrpcChannel channel = null;
    try {
      LOG.debug("Alluxio client (version {}) is trying to load configuration from meta master {}",
          RuntimeConstants.VERSION, address);

      long start = System.currentTimeMillis();
      channel = GrpcChannelBuilder.newBuilder(GrpcServerAddress.create(address), conf)
          .setClientType("ConfigurationUtils").disableAuthentication().build();
      long stub = System.currentTimeMillis();
      LOG.info("########### build channel cost: " + (stub - start) + " ms");

      start = System.currentTimeMillis();
      MetaMasterConfigurationServiceGrpc.MetaMasterConfigurationServiceBlockingStub client =
          MetaMasterConfigurationServiceGrpc.newBlockingStub(channel);
      stub = System.currentTimeMillis();
      LOG.info("########### acquire client cost: " + (stub - start) + " ms");

      start = System.currentTimeMillis();
      GetConfigurationPResponse response = client.getConfiguration(
          GetConfigurationPOptions.newBuilder().setRawValue(true)
              .setIgnoreClusterConf(ignoreClusterConf).setIgnorePathConf(ignorePathConf).build());
      stub = System.currentTimeMillis();
      LOG.info("########### get configuration cost: " + (stub - start) + " ms");

      LOG.debug("Alluxio client has loaded configuration from meta master {}", address);

      return response;
    } catch (io.grpc.StatusRuntimeException e) {
      throw new UnavailableException(String.format(
          "Failed to handshake with master %s to load cluster default configuration values: %s",
          address, e.getMessage()), e);
    } catch (UnauthenticatedException e) {
      throw new RuntimeException(String.format(
          "Received authentication exception during boot-strap connect with host:%s", address),
          e);
    } finally {
      if (channel != null) {
        long start = System.currentTimeMillis();
        channel.shutdown();
        LOG.info("########### shut down channel cost: " + (System.currentTimeMillis() - start) + " ms");
      }
    }
  }

Here is the log of one map container:
...
2021-03-15 16:31:37,952 INFO [main] alluxio.util.ConfigurationUtils: ########### build channel cost: 220 ms
2021-03-15 16:31:37,958 INFO [main] alluxio.util.ConfigurationUtils: ########### acquire client cost: 6 ms
2021-03-15 16:31:39,666 INFO [main] alluxio.util.ConfigurationUtils: ########### get configuration cost: 1707 ms
2021-03-15 16:31:41,731 INFO [main] alluxio.util.ConfigurationUtils: ########### shut down channel cost: 2065 ms
...
Here are the yarn configuration:

nodemanager: 19 nodes with 256GB memory and 96 processors
maximum 96 containers per node
no other load except test wordcount task
word count size: 210GB
split size is 128MB

Is there anyone who meet this problem before and can give me some suggestions? Thanks.
To Reproduce
Steps to reproduce the behavior (as minimally and precisely as possible)
Expected behavior
Figure out the problem and fix it.
Urgency
HIGH
Additional context
Add any other context about the problem here.

@liupan664021 I think all the costs up until the shutdown are necessary. It's possible they could be optimized, but setting up the channel and retrieving the configuration is necessary for the client in order for all cluster default configuration to be used. Currently this cannot be configured.
Shutting down the channel might arguably be something that can be done off the critical path in order to save those 2000ms or so. If you don't care for cluster defaults, then we could potentially avoid this whole process by adding a configuration flag to skip loading the remote configuration if the performance impact on the tasks is too large. Adding the configuration flag to skip loading cluster default configuration could essentially remove all of this overhead.
Unfortunately, the the client is quite heavyweight and is expected to be long running so that these costs don't add up. It sounds like with your current compute setup clients get created and destroyed frequently which makes the performance seem much worse. I believe there are other frameworks which you could use which don't create and destroy clients so frequently.

we discussed this issue offline and I believe the handshaking process between client and master to sync cluster config contributes to the slow start. @liupan664021  did you try to disable the flag "alluxio.user.conf.cluster.default.enabled" ?
I actually checked the source code and it seems this flag only controls conf sync between workers and master. I think this is a regression. But let us know your finding and it will be helpful


nuxt/kit: ability to configure web components for auto-import

Describe the feature
I have been trying to configure auto-imports for a library of web components, so that i can minimize bundle size without having to manually add imports.
I tried creating a module like this:
import { defineNuxtModule, addComponent } from 'nuxt/kit'

export default defineNuxtModule({
  meta: {
    name: 'my-components',
    compatibility: {
      nuxt: '^3.0.0',
    },
  },

  setup() {
    // From the runtime directory
    addComponent({
      name: 'MyButton',
      kebabName: 'my-button',
      mode: 'client',
      filePath<EMAIL_ADDRESS>    })
  },
})

However, this does not work as addComponent (or something downstream of it) expects there to be a vue component at the given path. the problem would exist just the same if I had a web component relative to the module (i.e. not from npm)
I am wondering if there is any scope to extend addComponent/component auto-import behavior to support web components. Since web components typically register themselves, the desired output would be a side-effect import wherever usage of my-button was detected. something like this:
// rather than this
import Button from<EMAIL_ADDRESS>// we would have this
import<EMAIL_ADDRESS>
My first thought was to add a sideEffectOnly: boolean option to addComponent as a flag to indicate this is the desired behavior, but i don't think that composes well with other existing options (e.g. what does it mean to have mode: "server" with sideEffectOnly: true?). Therefore perhaps the best option would be a new value for mode, since (right now) web components are implicitly client-side.
I'm sure it's possible to build this behavior outside of nuxt with some custom transforms etc, but i imagine a comprehensive solution would end up recreating most, if not all, of nuxt's existing mechanisms for scanning/importing/tree-shaking components.
Such an addition would be useful not just in my use case, but for all web component libraries. Additionally, many WC libraries publish a manifest of components they contain,  meaning a generic nuxt module could be written which accepts the manifest as an input, and dynamically calls addComponent for each web component found.
In summary, my proposal is something like:
addComponent({
  name: 'my-button',
  mode: 'web-component', // the specific value is up for debate
  filePath<EMAIL_ADDRESS>})

Additional information

[X] Would you be willing to help implement this feature?
[X] Could this feature be implemented as a module?

Final checks

[X] Read the contribution guide.
[X] Check existing discussions and issues.

Would welcome thoughts from @prashantpalikhe and @steveworkman.

I agree that adding imports manually is a chore, and in a CSR Vue app it's the only way to split the WC imports effectively due to their inherent side effects. That given, it does work very well.
Assuming that a WC library had a manifest (not all of them do) and the template parser could pick up WCs by their tags as defined in the next config, then it is plausible that they could be auto-imported.
If there is no manifest then I don't see how this can work. One could be supplied in the next config but at that point you may as well have put the imports in the right components.
Thinking of this in relation to the SSR-lit plugin, we had issues with the import order of some of the lit dependencies. The WCs that are detected to be imported would need to be included along with other route/component specific imports so that they are loaded late enough for the SSR plugins to be ready for them.
Happy to test this out if it gets a PR.

Thanks Steve. Appreicate your perspective especially with regards to SSR. I would personally, as a first step, want to keep the scope very narrow so that it only covers client side rendering, and only extends nuxt kit to allow auto imports of web components. Consuming a manifest, adding options to nuxt config, or SSR concerns can be added later/independently.

If there is no manifest then I don't see how this can work. One could be supplied in the next config but at that point you may as well have put the imports in the right components

I'm not sure I agree. The nature of WCs mean that there is no identifier to import. So you get no type errors at build time if you fail to import a WC. And vscode offers no suggestion to add an import. So an import is very easily forgotten. And when you do forget, you get (often silent) failures at runtime.
Worse yet, because web components are in a global registry, you may not get any failures even if you forget an import. Consider ComponentA and ComponentB both depend on a web component my-button. ComponentA correctly imports my-button, whilst ComponentB did not.
In this scenario, ComponentB may render perfectly fine with no errors, simply because ComponentA was also loaded on the current (or a previous) page, meaning my-button is already in the global registry. ComponentB may work only by coincidence, despite its missing imports. This can get confusing and hard to track down, especially as the module graph gets more complex.
So there is still value even if manually defining each web component for auto-import. Which is why I think extending nuxt kit just enough is useful in itself, and it can act as an enabler for better/smarter functionality to be built on top later.


Extract all the lowest P00n for each Maize v5 protein

For the file Zm-B73-REFERENCE-NAM-5.0_Zm00001eb.1.protein.2.fa
please generate a plain text file that is the lowest P00n number for each gene. So it would start:
Zm00001eb093920_P001
Zm00001eb033650_P001
...

They might all just be P001s. But maybe not, I don't know. Perhaps some begin with P0002
As the call, I talked about also a version with the longest isoform. But let's skip that for now. Let's just focus on lowest P00n number.
thanks!

My solution:
My command line:

(program file name, fasta file name)
Results:

And isoforms should be sent to a text file in the same directory.

great, thanks, looks promising! But I don't think it has been pushed to the repo? I see this:
$ git pull
Already up to date.

deutsch@WALDORF G:\Repositories\GitHub\PlantProteomes\SeqComparison\scripts
$ python lowest_pvalue_ML.py ..\proteomes\maize\original\Zm-B73-REFERENCE-NAM-5.0_Zm00001eb.1.protein.2.fa
None

Please make sure that you have a txt file in the same directory as     the program

not what you posted above.

And then I was going to try running the above program to create gene-only FASTA files for B73_v4, B73_v5, and the W22 and then do a table comparison of those 6 files. Can we string together your programs do that?

Thanks for the reminder; I just pushed.
I can work on making that comparison file now!

Great, thanks, I pulled the latest code and it generates the txt file nicely. So the next step is to alter it so that it writes a FASTA file (instead or in addition). And then once it can write FASTA files, then we should be able to do that comparison.
thanks!


Giving undef answer to questions crashes

Pressing a wrong key in the startup questions (like enter or too big/small number) gives Runtime error 201.

On 4/12/2015 11:22 AM, Jari Komppa wrote:

Pressing a wrong key in the startup questions (like enter or too
big/small number) gives Runtime error 201.

Yes, the entire startup part is decidedly un-robust :-)  Optimized for
size, not grace.


Propel is trying to create and persist a new object instead of updating it

I retrieve a record from the database this way
$error_messages = "";
 $filter = FiltersQuery::create()->findPk(1);
if ($filter->validate()) {
            $filter->save();
            echo "SUCCESS";
        } else {
            foreach ($filter->getValidationFailures() as $failure) {
                $error_messages .= $failure->getInvalidValue() . " " . $failure->getPropertyPath() . ": " . $failure->getMessage();
            }
            echo $error_messages;
        }

I get validation errors, like the filter name already exists because it's thinking that I want to create a new object and persist it instead of updating an existing one.

I rather think the validation is buggy and does not exclude itself from the unique constraint check. Please show us your concrete validations and the full stacktrace of the exception.

You're totally right, it was the validation that is causing the probleme of saving on update. But I don't understand why, the validation was working before and is also working for the create (save new record). I just disabled the validation and the update is working again. Here's my validation code in the schema:
  <parameter name="nameUnique"
                       value="{column: name, validator: Unique, options: {message: This filter name already exists in the database}}"/>

So I don't know why the validation is buggy.
Here's the validation method generated by propel in my model:
  public function validate(ValidatorInterface $validator = null)
    {
        if (null === $validator) {
            if(class_exists('Symfony\\Component\\Validator\\Validator\\LegacyValidator')){
                $validator = new LegacyValidator(
                            new ExecutionContextFactory(new DefaultTranslator()),
                            new ClassMetaDataFactory(new StaticMethodLoader()),
                            new ConstraintValidatorFactory()
                );
            }else{
                $validator = new Validator(
                            new ClassMetadataFactory(new StaticMethodLoader()),
                            new ConstraintValidatorFactory(),
                            new DefaultTranslator()
                );
            }
        }

        $failureMap = new ConstraintViolationList();

        if (!$this->alreadyInValidation) {
            $this->alreadyInValidation = true;
            $retval = null;

            $retval = $validator->validate($this);
            if (count($retval) > 0) {
                $failureMap->addAll($retval);
            }

            if (null !== $this->collDisplaySegments) {
                foreach ($this->collDisplaySegments as $referrerFK) {
                    if (method_exists($referrerFK, 'validate')) {
                        if (!$referrerFK->validate($validator)) {
                            $failureMap->addAll($referrerFK->getValidationFailures());
                        }
                    }
                }
            }

            $this->alreadyInValidation = false;
        }

        $this->validationFailures = $failureMap;

        return (Boolean) (!(count($this->validationFailures) > 0));

    }

I've got the same problem ;)
So... I read the code of Propel/Runtime/Validator/Constraints/UniqueValidator.php
    public function validate($value, Constraint $constraint)
    {
        if (null === $value) {
            return;
        }

        $className  = $this->context->getClassName();
        $tableMap   = $className::TABLE_MAP;
        $queryClass = $className . 'Query';
        $filter     = sprintf('filterBy%s', $tableMap::translateFieldName($this->context->getPropertyName(), TableMap::TYPE_FIELDNAME, TableMap::TYPE_PHPNAME));

        if (0 < $queryClass::create()->$filter($value)->count()) {
            $this->context->addViolation($constraint->message);
        }
    }

So, the violation is played when we have at least 1 record in database... even if it's the current record :)
If you have an idea to solve it.. ? :)
Thank !

Shouldnt it be
        if (0 > $queryClass::create()->$filter($value)->count()) {
Instead of
        if (0 < $queryClass::create()->$filter($value)->count()) {

As far as I understand, the comparaison should be

with 0 for new objects
with 0 if the this field is being update
with 1 if the object is being updated but this field unchanged

Does this sound right ?

Something like this seems to work, though it's far from perfect : don't set setFoo($foo) if the value is the same as the previous one
        $className  = $this->context->getClassName();
        $tableMap   = $className::TABLE_MAP;
        $queryClass = $className . 'Query';
        $filter     = sprintf('filterBy%s', $tableMap::translateFieldName($this->context->getPropertyName(), TableMap::TYPE_FIELDNAME, TableMap::TYPE_PHPNAME));

		$referenceValue = (in_array('member.'.$this->context->getPropertyName(),$this->context->getObject()->getModifiedColumns())?0:1);

        if ($referenceValue < $queryClass::create()->$filter($value)->count()) {
            $this->context->addViolation($constraint->message);
        }

Столкнулся с аналогичной проблемой, вот мой вариант решения, похожий на предложение @henrisson
        if (null === $value) {
            return;
        }

        $className  = $this->context->getClassName();
        $tableMap   = $className::TABLE_MAP;
        $queryClass = $className . 'Query';
        $filter     = sprintf('filterBy%s', $tableMap::translateFieldName($this->context->getPropertyName(), TableMap::TYPE_FIELDNAME, TableMap::TYPE_PHPNAME));
        $matches    = $queryClass::create()->$filter($value);

        $columnName = sprintf('%s.%s', $tableMap::TABLE_NAME, $this->context->getPropertyName());

        if ($this->context->getObject()->isNew() && $matches->count() > 0) {
            $this->context->addViolation($constraint->message);
        }

        else if ($this->context->getObject()->isModified() && $matches->count() > (in_array($columnName, $this->context->getObject()->getModifiedColumns()) ? 0 : 1)) {
            $this->context->addViolation($constraint->message);
        }

Только в моём примере наименования колонки формируется автоматически...

@fenric solution seems good.
Just created a unit test to validate the solution.

PR seems merged


Better test runner

A way to run tests that works in browsers and with CI.

We now use karma, travis CI with saucelabs. :)


URL to tag goes to branch if they have the same name

Gitea version (or commit ref): 1.10.0+dev-198-g111d31d68
Git version:
Operating system:
Database (use [x]):

[ ] PostgreSQL
[ ] MySQL
[ ] MSSQL
[x] SQLite

Can you reproduce the bug at https://try.gitea.io:

[x] Yes (provide example URL)
[ ] No
[ ] Not relevant

Description
When a branch and a tag has the same name, entering the URL to the tag shows the branch instead.
Example: https://try.gitea.io/merle_noir/TestName/src/tag/BranchAndTagNameSame is URL to tag but it shows the content of the branch with the same name.

What do you think the proper behaviour?

Expected behavior:

{Repo}/src/branch/{refname}: 404 if branch {refname} doesn't exist. If exist show branch.
{Repo}/src/tag/{refname}: 404 if tag {refname} doesn't exist. If exist show tag.

Actual behavior:

{Repo}/src/branch/{refname}: 404 if branch {refname} doesn't exist. If exist show branch.
{Repo}/src/tag/{refname}: 404 if tag {refname} doesn't exist. If exist show branch (in first case, if it exist) otherwise show tag.

The reason for this is in /modules/context/repo.go, func RepoRefByType, the code first correctly determines if the branch or tag exist (depending on what is requested), but then first check if branch exist (line 610) regardless if branch or tag was requested.


Add functions for symbolic manipulations required in GR

We can use sympy to write functions which can act as utilities, and can return relevant expressions in symbolic form only. It can be nice cool addition to the library.

Similar Issue #70
Closing this


Bulleted lists in move descriptions break the character builder

In GitLab by @Asacolips on Feb 5, 2021, 10:12
Technical Notes

Placing bulleted lists in Move descriptions causes layout issues in the character builder.

Acceptance Criteria

[ ] Layout issues for bulleted lists are resolved

In GitLab by @Asacolips on Apr 1, 2021, 20:09
This was due to overly aggressive layout styling for the character builder. Will be resolved in 0.7.0 when it releases.


It should be possible to interact/comment on each job

Some big problems with the job board at the moment are:

it’s very static, discussion is difficult to start
you don’t know the state of it, if it’s taken already
we don’t know if it’s done

As far as I know it’s possible to embed Discourse thread replies in a website. We could have a category in the Discourse called »Jobs« (you can’t create posts but will be led to the job submission form), and one thread per job. Then on every job there’s the discussion thread below.
@erlend-sh could you point us how to do that maybe? :)
We do have to require that the people have to register at Discourse though and be subscribed to the issue. But maybe that can be automated and will lead to growth.
cc @jdittrich @simonv3 @belenbarrospena @janushead @guiguru @HeikoTietze @bnvk @evalica

This looks like it's what we want:
https://meta.discourse.org/t/embedding-discourse-comments-via-javascript/31963

Okay! This has been implemented but it can use a lot of improvement.
I think a lot of that improvement will come from figuring out the formatting and the markdown, eg.:
https://discourse.opensourcedesign.net/t/jobs-libreoffice-mascot/328
http://opensourcedesign.net/jobs/jobs/2017-06-28-libreoffice-mascot
Yay \o/
cc @bnvk @jancborchardt @evalica

w00t w00t, great @simonv3 great step and progress 👍
For some reason I had to update the ID in your link to Discourse from 328 to 353, not sure why.
How does this currently get created? Is it 100% automated? Is that perhaps why the ID issue happened?

yeah, the ID issue probably happened because I have since deleted and created that thing a couple of times for testing purposes.
This is actually pretty incredible functionality from Discourse. We can set it so that stuff gets automatically gets created when Discourse polls the feed.xml for the jobs (in which case we can only do it for jobs I think, not for, say, articles), or that it gets created when someone views the page (as is the case now).
As some of the old projects gets viewed this might take some curation on the forum, hiding posts etc.

we can only do it for jobs I think, not for, say, articles

Why is this? We can (and should / am working towards) have multiple RSS feeds.

Looks like a limitation on the Discourse side. There's only one input field for where to fetch RSS feed data from and it seems to apply to all embedded Discourse threads.
If we have separate repos we can't do this I think, but isn't it also fairly standard to provide an RSS feed of all updates from a site?

So we could have a unified feed and then a "category" attribute which would tell Discourse where to add the topic?

I think so? I mean, by no means am I an expert on this.

We could have a category in the Discourse called »Jobs« (you can’t create posts but will be led to the job submission form), and one thread per job. Then on every job there’s the discussion thread below.

@marielle-G15 sorry about this outdated issue – this is actually something that is working already exactly as you describe :)

Category in the Discourse: https://discourse.opensourcedesign.net/c/job-postings
Corresponds with the list at https://opensourcedesign.net/jobs/
Discussion from the forum shows in a job posting: https://opensourcedesign.net/jobs/jobs/2019-03-19-design-of-badges-for-different-xmpp-compliance-levels

One thing we could additionally do is show the amount of comments in the list on the job board directly, and highlight ones without comments? Is that something you would be interested in looking into @marielle-G15?

One thing we could additionally do is show the amount of comments in the list on the job board directly, and highlight ones without comments?

I can look at this new aspect of this issue when look at the job page design 🙌


Fix download tool step of the reproducer role.

Given the tags in that task, choose kubectl instead of operator-sdk as
a anchor to check if the task has been done.

As a pull request owner and reviewers, I checked that:

[ ] Appropriate testing is done and actually running
[ ] Appropriate documentation exists and/or is up-to-date:

[ ] README in the role
[ ] Content of the docs/source is reflecting the changes

/approve

/lgtm
thanks @sathlan - I forgot to update the creates back then -.-'


run ./bin/fmt.sh to fix fmt failure

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers: geeknoid, nmittler
If they are not already assigned, you can assign the PR to them by writing /assign @geeknoid @nmittler in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

galley/OWNERS
istioctl/OWNERS
mixer/OWNERS
pilot/OWNERS
pkg/OWNERS
security/OWNERS
tests/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@hzxuzhonghu: PR needs rebase.

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

@hzxuzhonghu: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
29c718bf40666dffd57acf008a2595cefc0d5cca
link
/test istio-unit-tests

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

@hzxuzhonghu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
29c718bf40666dffd57acf008a2595cefc0d5cca
link
/test istio-unit-tests

prow/istio-presubmit.sh
29c718bf40666dffd57acf008a2595cefc0d5cca
link
/test istio-presubmit

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

@hzxuzhonghu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
dfbadff3637c21335b8422fb21118f6e394f0605
link
/test istio-unit-tests

prow/e2e-mixer-no_auth-mcp.sh
dfbadff3637c21335b8422fb21118f6e394f0605
link
/test e2e-mixer-no_auth-mcp

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

is circle and prow already updarted to use go1.11 ?

The linter check has been made temporarily optional until CI is fixed.  See the discussion from yesterday in the oncall channel, starting with https://istio.slack.com/archives/C6RHFVB44/p1539370001000100
There have been several PRs similar to this that have been created in hopes of making CI happy.  I recommend just closing this.


ENV vars are not available in the hooks scripts

It seems that the ENV variables specified in the readme that should exist while the hooks are running are not actually there.
docker run --rm -it --privileged -v $(pwd):/app -v $HOME/.dockercfg:/.dockercfg:ro --volumes-from builder_cache tutum/builder:staging asdf
Here is my hooks/push file:
#!/bin/sh

env
gh-release create fenderton/sqs_worker "$IMAGE_NAME"

And the output:
=> Executing hooks/push hook
HOSTNAME=0cc98cd00027
SHLVL=1
HOME=/root
OLDPWD=/
_=./hooks/push
TERM=xterm
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
PWD=/src

I would expect the IMAGE_NAME env var to be available and be set to asdf.

You need to provide the variables to the tutum/builder container. What Tutum does is to configure a webhook in github in order to deploy a tutum/builder container with the right ENV variables. Therefore, the ENV variables would be available when building from Tutum, but you have to provide them if you want to use the tutum/builder image in your own.

Thanks @pchico83 !


Initial progress toward a collected data schema.

This is a proof-of-concept PR. It's more of a sketch than something intended to be reviewed and merged.
The concept is based on this doc: https://docs.google.com/document/d/1cZMhSaSS4Ckus4KDga3oiTol4iLcZRcc15GguRJCcQ4/edit#heading=h.fa4kckfyfzzf.
The PR has:

schema updates to show how we could easily create a collective schema that's an augmented version of the existing schema (in reality, I think it would be even more understandable to define the collected schema first and then define the API schema as a subset of it)
a convert-formats.ts script that allows converting in between CSV and JSON versions of that schema. In the longer-term, we can export to Google sheets with some of the validations we currently have in place
3 files to show that this works. They're probably not that interesting to look at. schema-friendly-data.csv is a version of the CO data that was already converted to fit the schema, so we don't have to worry about changing names of columns/fields. schema-friendly-data.json is that CSV after it was converted to JSON. back-to-csv.csv is the roundtrip back to CSV. I've checked that they are equivalent (not byte-equivalent – something is off with the newlines or maybe quoting, but they are value-equivalent).

This proof-of-concept has been broken up into a bunch of actual PRs, so closing now.


Android client shortcuts

Hi,
Trying to use device automation apps like Llama, AutomateIT, Macrodroid and e.c.
And the problem is -  shortcuts "Traccar Start" and "Traccar Stop" are not present in automation apps shortcuts list.
The same behavior for my LG G3 (Lollipop) and new one Xiaomi with Android 6.0.
Client's version 3.11 and 3.12.
Thank you.

Have you created the links from the app?

Yes, of course.

Then I'm not sure why they don't show up in the automation app. It might be possible to specify activity and parameters directly, without using shortcuts. Check addShortcuts method for more info about parameters.

OK. I'll try. Thank you.

Same here. Code from app with expected behavior.

Traccar Client already implements this functionality exactly the same way as the code that you pointed to.

But shortcuts from traccar is not visible from any other apps/launchers (

If you can find the difference, you are welcome to point it out. As far as I can tell, they are using same API.

I'll try, but sadly I'm not developer.

Unfortunately I don't have time to investigate it further at the moment, but with Android O release we would have to change shortcuts system anyway, so I'm review the code then.

Thank you!

I think I found it - you don't have
<meta-data android:name="android.app.shortcuts"
         android:resource="@xml/shortcuts" />
</activity>

in AndroidManifest.xml, as decribed here.

I appreciate the effort, but please double check the information that you share. The link points to the different type of shortcuts. You can even see it on the screenshot.

Sorry for the rush. New find: other apps have:
<intent-filter>
         <action android:name="android.intent.action.CREATE_SHORTCUT" />
</intent-filter>

in AndroidManifest.xml

https://github.com/termux/termux-widget/blob/master/app/src/main/AndroidManifest.xml
https://github.com/shadowsocks/shadowsocks-android/blob/master/mobile/src/main/AndroidManifest.xml
https://github.com/federicoiosue/Omni-Notes/blob/develop/omniNotes/src/main/AndroidManifest.xml

That's for receiving events about shortcut creation, not for creating it.

Creating Termux shortcut from Apex Launcher:
05-24 08:33:28.562 I/ActivityManager(5446): START u0 {act=android.intent.action.CREATE_SHORTCUT cmp=com.termux.widget/.TermuxCreateShortcutActivity} from uid 10196 on display 0

from Llama:
05-24 08:39:19.009 I/ActivityManager(5446): START u0 {act=android.intent.action.CREATE_SHORTCUT cmp=com.termux.widget/.TermuxCreateShortcutActivity} from uid 10158 on display 0

I am not sure anymore what you are talking about.

To able to use shortcuts, other app creates them using intent action.

Traccar Client also uses intent action to create shortcuts. Can you please make sure that you know what you are talking about before making any further comments.

I'm 99% shure:
...o you can create a shortcut to a product from there, in addition to the "Add to home screen" menu option. However if you don't want to do this simply remove the android.intent.action.CREATE_SHORTCUT intent-filter from the activity. You can still add a shortcut to the homescreen using the INSTALL_SHORTCUT permission with your existing method.
From: https://stackoverflow.com/questions/32401211/can-i-prevent-a-shortcut-android-intent-action-create-shortcut-to-appear-in-th

Sorry, but you making less and less sense with every comment. How is it different what I just said? We are ALREADY USING INTENT ACTION in Traccar Client app.

Sorry, my English don't let me explain this right. Traccar uses INSTALL_SHORTCUT to able to install shortcuts from app itself. But you need add CREATE_SHORTCUT intent-filter to AndroidManifest.xml that other apps can create/use this shortcuts.

I don't want other apps to create shortcuts.

Well, this should be second comment, because automation apps do this exactly (just don't adding them to Desktop).

OK, I see now how it works. The app can't reuse launcher shortcuts. It needs to create own shortcuts. Is that what you are trying to say?

Exactly!

OK, I will investigate it when I have more time.

Thank you!

Following this, too. Being able to control Traccar from Tasker would be great! Currently you can not even launch the shortcuts.

I will implement this with release of new version of Android system.

Great!

Any ETA?

You should ask Google when they plan to release their new version. My guess is that it's going to be somewhere in September.

OK, I see you couple the release of an updated app to the release of a new Android version. I didn't get that. But: Why?!

Because shortcuts and notifications APIs are changing in Android O, so it doesn't make sense to implement a solution that would need to be changed in two months time again.

Obviously it is your own decision, but given the fact that most phones will still run Android versions < O for the next years, I consider it unfortunate to couple simple app improvements to major OS release updates. I think many Traccar users will still have a need for pre-O-compatible improvements after O is released.

My point is that I don't want to do it twice.

Understandable, but unfortunate.

Traccar Client version 5.0 has just been released. It fixes all the issues with shortcuts.


gz compressed files

added gz compressed files (from .txt files) for pako support

Why do we want to store compressed files in git? Seems like that git repo should just contain the .txt files and it's up to the user to compress them if they want.

@scottchiefbaker good question.
The reasoning for uploading the compressed files is to let people download them directly from GitHub.

Believe it or not, most of the world is still "bandwidth constrained" ... 😞
Ideally the zipping/compression would be automated to avoid people having to do it manually in pull requests when a word is added to the list ... 🤔

@scottchiefbaker good question.
The reasoning for uploading the compressed files is to let people download them directly from GitHub.

Believe it or not, most of the world is still "bandwidth constrained" ... 😞
Ideally the zipping/compression would be automated to avoid people having to do it manually in pull requests when a word is added to the list ... 🤔

Bandwidth constraints are still not much of an issue, the whole repository is about 6MB.

Note that even if it is a plain-text file, GitHub does not allow viewing such file (too big: 4MB)
clicking on the link to download it will by default attempt to view the raw file in the browser (which may crash as well)
So compressing the raw file is a valid option for GitHub (where this text file cannot be directly edited online in a browser without crashing it, GitHub already forbids it and treats it as a raw uneditable file).
Even if people don't like complex compression, given that the file should be sorted, it can evidently be compressed a lot with common prefixes. For example, the sequence of words (here shown in JSON format only for illustration):

['ab', 'abc', 'abdef', 'ac']

could be represented as:

['0ab', '0c', '1def', '4c']

where the initial integer (also storable as a single byte, rather than an ASCII digit here to allow more than 9) would indicate how many characters (possibly 0) to drop from the end of the previous entry before appending a new suffix indicated after this integer.


Is expected that older versions read different globals?

Hi, when I use a library that depends on v0.0.11 the global value that I set in my application has no effect. Only if the library also uses v0.1.0 (same as the binary) the globals are shared between the aplication and the library.
I tested this having 2 identical libs in a workspace with only this function. One with concolor v0.0.11 (or v0.0.12) and the other with v0.1.0.
pub fn has_color() -> bool {
    concolor::get(concolor::Stream::Stderr).color()
}

Then I call these functions from binary that depends on those libs and only the new version stays in sync. (I can upload a test repo but honestly it's just 10 lines of code)
Is this expected before 1.0? If so, it would be great to mention it in the readme to avoid confusion.

This is why the feature name for using the global was named api_unstable, it required keeping everything in lockstep with each other and so any version upgrade could be a breaking change.
With splitting out concolor_override, we have a fairly safe path forward for compatibility so we can keep one instance of this global that all crates talk so we can avoid this problem in the future.  This allowed dropping the _unstable suffix and why I felt like I could move the version numbers outside of 0.0.x


Add two more affected functions and accepted date

Description of changes:
Add two more affected functions (EntityNamespace::from_str() and EntityUid::from_str()) and accepted date (today).
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@andrewmwells-amazon can you also update the link for "Implementation PR" to be cedar-policy/cedar#133? Thanks

I tend to object to these changes. I tend to disagree. IIRC, the motivation of the RFC is based on the usage pattern where an entity id is referred by two components (typename + uid) instead of a unified struct (i.e., EntityUid). And this usage pattern kind of justifies the discrepancy from the Cedar grammar. I think the rule of thumb is to avoid such discrepancy as much as possible unless we have a compelling use case.

I think we should make the change @andrewmwells-amazon is currently proposing.  The RFC motivation speaks to the case where two strings are treated as different by JSON (eg in the Cedar schema) but the same by Cedar.  This trap occurs not just with entity types, but also in namespaces and full UIDs.  Consider two schemas, one declared with namespace "Foo " and the other with "Foo" -- Cedar will see these as the same namespace, which could cause customer confusion.
More generally, people don't expect whitespace and comments to be valid inside JSON strings, which is what the status quo has.  Adjusting all three functions should cover all of these cases where whitespace and comments are currently valid inside JSON strings.

Got it. I didn't expect namespaces to appear in the schemas other than being entity type names.


GrooveShark is gone, let's regroup and try this again...

Hi! This is "Nathan" from the broadcast.
It's a very sad day because GrooveShark was shut down today.
I was thinking of making a Facebook group and hopefully some of the MoS regulars will find us, and from there we could decide where the broadcasts will be moved to or what our next step is.
What are your thoughts?
PS. sorry about the abuse of Github issues -- this was the only way I knew how to get in touch with someone from the broadcast.

Never mind. It looks like there's a subreddit: /r/MasterOfSoundtrack.


[Feature Request] Account for multiple speed attributes

There's multiple movement attributes in D&D5e (fly, hover, climb, swim, etc):

It would be great to have a setting to set multiple speed attributes and take the highest one.

Hello. This can be achieved via Drag Ruler's API, either by the game system directly or by a separate module. Examples of game systems doing this are Pathfinder 1 (directly in the game system) and Pathfinder 2 (as a separate module).

Ah, I see, it will take some work learning to do this but that should suffice

If you need any help, let me know


Wrong divisor in image_helpers.cpp

On branch cl12_trunk, in file:

test_conformance/images/image_helpers.cpp: generate_random_image_data

There is an obviously wrong divisor:
    if( gTestRounding )
    {
        // Special case: fill with a ramp from 0 to the size of the type
        size_t typeSize = get_format_type_size( imageInfo->format );
        switch( typeSize )
        {
            case 1:
            {
                char *ptr = data;
                for( i = 0; i < allocSize; i++ )
                    ptr[i] = (cl_char) (i + gRoundingStartValue);
            }
                break;
            case 2:
            {
                cl_short *ptr = (cl_short*) data;
                for( i = 0; i < allocSize / 2; i++ )
                    ptr[i] = (cl_short) (i +  gRoundingStartValue);
            }
                break;
            case 4:
            {
                cl_int *ptr = (cl_int*) data;
                for( i = 0; i < allocSize / 2; i++ )
                    ptr[i] = (cl_int) (i +  gRoundingStartValue);
            }
                break;
        }
        return data;
    }

The divisor should be 4 in case 4.
Best regards!
Feb. 12. 2020.

Could you open a PR please?

cl12_trunk was merged into master where this code is correct. Please use the master branch to test 1.2 implementations.

cl12_trunk was merged into master where this code is correct. Please use the master branch to test 1.2 implementations.


Fix linux binaries

Newest Meson broke the binaries we install on Linux; fix the problem and add test infrastructure to try to prevent reoccurences.
Checklist

[x] Used a fork of the feedstock to propose changes
[x] Bumped the build number (the version is unchanged)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@mariusvniekerk The aarch64/ppc64le builds are dying with "invalid cross-device link" in the setup stage. Any idea what that's about, and/or how to work around?
INFO:conda_build.metadata:Attempting to finalize metadata for glib
Traceback (most recent call last):
  File "/opt/conda/lib/python3.7/shutil.py", line 563, in move
    os.rename(src, real_dst)
OSError: [Errno 18] Invalid cross-device link: '/tmp/4be0cda0-21e0-4e0f-9375-e282a6aeb501' -> '/home/conda/feedstock_root/build_artifacts/linux-ppc64le/repodata.json'


Unexpected output after running code with Jupyter Notebook Go kernel.

Steps to cause the bug to occur

Add Go kernel to Jupyter kernel
Open a test.ipynb in VSC
Start Jupyter server and choose Go kernel
Run cell

a :=2
import "fmt"
fmt.Println(a)

Actual behavior
In VSC

In Jupyter notebook

Expected behavior

Your Jupyter and/or Python environment
Please provide as much info as you readily know

Jupyter server running: Local
**Extension version: 2020.7.96456
**VS Code version:

Setting python.jediEnabled: true
Setting python.languageServer: Jedi
Anaconda version:

OS: Mac
Virtual environment: N/A

The output I get from Jupyter is the same as the output I get from VS Code.


Fix CanBeInitializedInline and GetParameterInitializer

In CanBeInitializedInline, type may be initialized inline (e.g. string), but defaultValue, though convertible to type, may not be used for inline initialization (e.g. extensible enum). So, if type is different than the type of defaultValue, we need to check if defaultValue can be assigned to its own type, then check for the provided type
GetParameterInitializer should add conversion extension method if required

Fixes build issue in https://github.com/Azure/azure-sdk-for-net/pull/30472


Support devices that send a MultiChannelCCCommandEncapsulation (0x0D) but with a V1 CCCommand (0x06)

I am switching from zwave to zwave2. Several devices which were recognized in zwave are not fully recognized in zwave. All devices and parameters are available on Object page, but some are missing on Device Tab of Instances page.
Elexa Consumer Products Inc. (Dome) On/Off Plug-In Switch
manufacturid: 543
productid: 135
productType: 3
2GIG Technologies CT101 Thermostat (Iris)
manufacturid: 152
productid: 12
productType: 25857

This should be fixed in the next adapter version

Thank you! Beer is on me...
Anatoly
On 9/4/2020 2:23 PM, AlCalzone wrote:

This should be fixed in the next adapter version
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/AlCalzone/node-zwave-js/issues/938#issuecomment-687309136,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEV7FRL4STNKXZWHGANE6HLSEEWDNANCNFSM4QY7LP2A.

Thank you, works fine now!
Anatoly
On 9/4/2020 2:23 PM, AlCalzone wrote:

This should be fixed in the next adapter version
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/AlCalzone/node-zwave-js/issues/938#issuecomment-687309136,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEV7FRL4STNKXZWHGANE6HLSEEWDNANCNFSM4QY7LP2A.

Thank you! Beer is on me... Anatoly

Much appreciated :)

Hello,
Sorry to bother you again. I have an issue with zWave device that you
fixed for me - Radio Thermostat Company of America (RTC) CT101. It seems
to be operational in general, but I have some issues:

If I change setpoint on the actual thermostat, I see changes in
corresponding Object value

If I change setpoint in Object value (via VIS gadget), I don't see
changes applied to the thermostat setpoint

The room temperature displayed on the actual thermostat does not get
updated into Object Value

Could it be related to latest fix that you implemented? Or, since your
version of zWave provides more parameters for devices than the old one,
I did not set one of the device configuration parameter?
Thank you,
Anatoly
On 9/4/2020 2:23 PM, AlCalzone wrote:

This should be fixed in the next adapter version
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/AlCalzone/node-zwave-js/issues/938#issuecomment-687309136,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEV7FRL4STNKXZWHGANE6HLSEEWDNANCNFSM4QY7LP2A.

Please open a new issue with that description and attach a log file so I don't have to guess.


Occupy whole screen on click if menu is positioned right?

Is it possible for the dropdown to occupy the whole screen (after clicking the menu) if the menu is positioned to the right?
Currently this is the behavior:
https://i.imgur.com/8wJKCcO.png
Can it be made to look like this?
https://i.imgur.com/fStvxON.png
Also, the word "Menu" is moving left with the dropdown when clicked (you can see in the first image the word "Menu" moves slightly to the left ). It would be nice if it sticks to its position.

Hi there,
I don't recommend doing it for better UI purposes, but if you wish to do so you can simply add this to your stylesheet.
.stellarnav.mobile.right > ul, .stellarnav.mobile.left > ul { max-width: 100%; }
Also, the screenshot is showing two menus in one page. This will cause conflicts between them. Try to just have one nav.


terraform_tfsec hook always runs on all files

Describe the bug
The terraform_tfsec hook always runs on all Terraform files, even though none of them were modified or staged.
I would expect the hook to only run if I explicitly use pre-commit run --all-files or if there were any Terraform files modified and staged.

How can we reproduce it?
What I did to produce the bug:
$ touch test.py
$ git add test.py
$ pre-commit run

My .pre-commit-config.yaml contains:
repos:
  - repo: https://github.com/antonbabenko/pre-commit-terraform
    rev: v1.83.2
    hooks:
      - id: terraform_tfsec

Environment information

OS: Ubuntu 22.04

uname -a and/or systeminfo | Select-String "^OS" output:

Linux Yggdrasil <IP_ADDRESS>-microsoft-standard-WSL2 #1 SMP Fri Jan 27 02:56:13 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Tools availability and versions:

pre-commit 3.4.0

.pre-commit-config.yaml:

file content
repos:
  - repo: https://github.com/antonbabenko/pre-commit-terraform
    rev: v1.83.2
    hooks:
      - id: terraform_tfsec

This issue has been resolved in version 1.83.3 :tada:


Method naming

In the class reference of the Response Object in the user guide, statusCode() and reason() are listed. However, it should be getStatusCode() and getReason(), as statusCode() and reason() are not methods in HTTP\Response.

I will merge this, but expect future contributions to be GPG-signed.


super-slicer: fix build with GCC 14

Continued from #361477
Things done

Built on platform(s)

[ ] x86_64-linux

[x] Fits CONTRIBUTING.md.

I'm getting a build error, when applying this on latest unstable:
± nix-build . -A super-slicer-latest
this derivation will be built:
  /nix/store/47j1v340k32jn3v46bjkzqi9k42xdzlr-super-slicer-<IP_ADDRESS>.drv
building '/nix/store/47j1v340k32jn3v46bjkzqi9k42xdzlr-super-slicer-<IP_ADDRESS>.drv'...
Running phase: unpackPhase
unpacking source archive /nix/store/vfqwfnc0m23mlndi80amcfagyk3dddrn-source
source root is source
Running phase: patchPhase
substituteStream() in derivation super-slicer-<IP_ADDRESS>: WARNING: '--replace' is deprecated, use --replace-{fail,warn,quiet}. (file 'src/PrusaSlicer.cpp')
substituteStream() in derivation super-slicer-<IP_ADDRESS>: WARNING: pattern list\(APPEND\ wxWidgets_LIBRARIES\ libexpat\) doesn't match anything in file 'src/CMakeLists.txt'
substituteStream() in derivation super-slicer-<IP_ADDRESS>: WARNING: pattern libexpat doesn't match anything in file 'src/libslic3r/CMakeLists.txt'
applying patch /nix/store/a1vdclpnypig8j0n419590qjk9vgqdki-superslicer-<IP_ADDRESS>-boost-1.79-port-v2.patch
patching file src/hints/HintsToPot.cpp
patching file src/libslic3r/AppConfig.cpp
patching file src/libslic3r/AppConfig.hpp
patching file src/libslic3r/LocalesUtils.cpp
patching file src/libslic3r/Preset.cpp
patching file src/slic3r/GUI/CreateMMUTiledCanvas.cpp
patching file src/slic3r/GUI/DesktopIntegrationDialog.cpp
patching file src/slic3r/GUI/GUI_App.cpp
patching file src/slic3r/GUI/HintNotification.cpp
patching file src/slic3r/GUI/Preferences.cpp
patching file src/slic3r/GUI/ScriptExecutor.cpp
applying patch /nix/store/xgd5yzxl0ln024327ipsz2kdjmdslcwf-meshboolean-const.patch
patching file src/libslic3r/MeshBoolean.cpp
Hunk #1 FAILED at 147.
1 out of 1 hunk FAILED -- saving rejects to file src/libslic3r/MeshBoolean.cpp.rej
error: builder for '/nix/store/47j1v340k32jn3v46bjkzqi9k42xdzlr-super-slicer-<IP_ADDRESS>.drv' failed with exit code 1;
       last 23 log lines:
       > Running phase: unpackPhase
       > unpacking source archive /nix/store/vfqwfnc0m23mlndi80amcfagyk3dddrn-source
       > source root is source
       > Running phase: patchPhase
       > substituteStream() in derivation super-slicer-<IP_ADDRESS>: WARNING: '--replace' is deprecated, use --replace-{fail,warn,quiet}. (file 'src/PrusaSlicer.cpp')
       > substituteStream() in derivation super-slicer-<IP_ADDRESS>: WARNING: pattern list\(APPEND\ wxWidgets_LIBRARIES\ libexpat\) doesn't match anything in file 'src/CMakeLists.txt'
       > substituteStream() in derivation super-slicer-<IP_ADDRESS>: WARNING: pattern libexpat doesn't match anything in file 'src/libslic3r/CMakeLists.txt'
       > applying patch /nix/store/a1vdclpnypig8j0n419590qjk9vgqdki-superslicer-<IP_ADDRESS>-boost-1.79-port-v2.patch
       > patching file src/hints/HintsToPot.cpp
       > patching file src/libslic3r/AppConfig.cpp
       > patching file src/libslic3r/AppConfig.hpp
       > patching file src/libslic3r/LocalesUtils.cpp
       > patching file src/libslic3r/Preset.cpp
       > patching file src/slic3r/GUI/CreateMMUTiledCanvas.cpp
       > patching file src/slic3r/GUI/DesktopIntegrationDialog.cpp
       > patching file src/slic3r/GUI/GUI_App.cpp
       > patching file src/slic3r/GUI/HintNotification.cpp
       > patching file src/slic3r/GUI/Preferences.cpp
       > patching file src/slic3r/GUI/ScriptExecutor.cpp
       > applying patch /nix/store/xgd5yzxl0ln024327ipsz2kdjmdslcwf-meshboolean-const.patch
       > patching file src/libslic3r/MeshBoolean.cpp
       > Hunk #1 FAILED at 147.
       > 1 out of 1 hunk FAILED -- saving rejects to file src/libslic3r/MeshBoolean.cpp.rej
       For full logs, run 'nix log /nix/store/47j1v340k32jn3v46bjkzqi9k42xdzlr-super-slicer-<IP_ADDRESS>.drv'.

I moved the custom patches to postPatch.

I've found that the postInstall is also incorrect for super-slicer packages.
It should be, otherwise the OCCTWrapper.so that is output to the bin directory will fail to load. This is done in the original prusa-slicer derivation but postInstall is set to null in super-slicer.
    postInstall = ''
      mkdir -p "$out/lib"
      mv -v $out/bin/*.so $out/lib/
    '';

I'd submit a PR for this but given the build is currently broken I'll hold off until this PR is merged.

Works. Thanks for the fix!


[Dev] Remove react-native-siri-shortcut

Changes
Remove react-native-siri-shortcut module
Requirements
run the setup script
Testing
Does it run on iOS and Android with no problems

[x] Manual

@wynnset This PR is removes dead code as well as a dependency that is not used and introducing strange behaviour with the android folders. The code in App.tsx was originally commented out by Vitor many months ago and as you pointed out there's no comment describing why!

@MarkDavies0 can you please fix the merge conflicts and then mark as ready for merge?


box-box collisions unsupported

Hi,
I noticed the box-box collider pair is still unsupported. I was wondering this would be available anytime soon or can be easily addressed. Thanks!

Hi @btaba, thanks for the quick response! Appreciate it! If I may ask, do you know when this is expected to be done?

Hi @limbryan, we don't have a good estimate at the moment but we're actively working on convex<>convex which would cover box<>box

We added an initial impl of box-box, we hope to expand on it and make it more performant in the future. Let us know if there are any bugs/issues!


isOutsideRange property ends up nullifying invalid dates entirely

react-dates version
<EMAIL_ADDRESS>Describe the bug
Using isOutsideRange prop will completely remove an invalid date when a date outside the range is manually typed in. This prevents us from handling invalid inputs with validation schemas like Yup and creating better error messaging experiences for our app.
Source code (including props configuration)
We recommend checking out this CodeSandbox to see the other libraries we use in conjunction with SDP.
https://codesandbox.io/s/single-date-picker-range-validation-reproducible-chrrlt?file=/src/Form.jsx:1707-2451
Steps to reproduce the behavior:
        <SingleDatePicker
            name={name}
            focused={isDatePickerOpen}
            onFocusChange={({ focused }) => setIsDatePickerOpen(focused)}
            date={value}
            onClose={() => trigger("date")}
            onDateChange={(date) => {
              onChange({ target: { name, value: date } });
            }}
            numberOfMonths={1}
            isOutsideRange={(day) =>
              isInclusivelyBeforeDay(
                moment(day).startOf("day"),
                moment().startOf("day").subtract(1, "days")
              ) ||
              isInclusivelyAfterDay(
                moment(day).startOf("day"),
                moment().startOf("day").add(31, "days")
              )
            }
          />

Screenshots/Gifs

https://github.com/react-dates/react-dates/assets/10050800/726aa48d-452d-4b00-b246-13926fad7748
Desktop (please complete the following information):

OS: MacOS 12.6
Browser Arc
Version 1.6.0

Is the issue reproducible in Storybook?
Yes, but it's not apparent what happens under the scenes. The text remains, but the value is not stored.
https://react-dates.github.io/react-dates/?path=/story/sdp-day-props--allows-next-two-weeks-only
Additional context
We're aware this isn't necessarily a bug, but the pattern here feels incorrect. The library should allow developers to decide how they want to handle invalid inputs. Blanket removing all invalid inputs leads to some confusing and vague behaviors.

What change would you suggest that wouldn't be semver-major?

What change would you suggest that wouldn't be semver-major?

@ljharb potentially adding an additional optionally accessible parameter to the onDateChange and onClose function parameters. It'd allow developers to grab that value and store it if they choose without breaking current behavior.
<SDP
  onDateChange={(date, rawValue) => /* we could do something with rawValue if we wanted to */}
  onClose={(date, rawValue) => ...}
/>

// but should work normally without accessing that param i.e.
<SDP
  onDateChange={(date) => ...}
  onClose={(date) => ...}
/>

onClose seems to already pass an object with a date property, so we could add a rawValue property to it. onDateChange would indeed need to take a second parameter.
Any chance #1941 would solve this, making this a duplicate of #1937?

@ljharb oh yes! #1941 would work really nicely! Thank you for surfacing that issue, sorry I couldn't find it before posting.
would love to see your onClose suggestion as well. Happy to close or keep this issue open depending on how you see fit.

Let's keep this open for the onClose change.


Add docker for platform independent testing

Added a docker file, start up script, and updated readme for contribution.

Pull Request Test Coverage Report for Build 560

0 of 0   changed or added relevant lines in 0 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.06%) to 64.323%

Files with Coverage Reduction
New Missed Lines
%

lib/i18n/js/dependencies.rb
2
50.0%

Totals

Change from base Build 559:
-0.06%

Covered Lines:
247

Relevant Lines:
384

💛  - Coveralls

Pull Request Test Coverage Report for Build 560

0 of 0   changed or added relevant lines in 0 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.06%) to 64.323%

Files with Coverage Reduction
New Missed Lines
%

lib/i18n/js/dependencies.rb
2
50.0%

Totals

Change from base Build 559:
-0.06%

Covered Lines:
247

Relevant Lines:
384

💛  - Coveralls

Pull Request Test Coverage Report for Build 560

0 of 0   changed or added relevant lines in 0 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.06%) to 64.323%

Files with Coverage Reduction
New Missed Lines
%

lib/i18n/js/dependencies.rb
2
50.0%

Totals

Change from base Build 559:
-0.06%

Covered Lines:
247

Relevant Lines:
384

💛  - Coveralls

Pull Request Test Coverage Report for Build 560

0 of 0   changed or added relevant lines in 0 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.06%) to 64.323%

Files with Coverage Reduction
New Missed Lines
%

lib/i18n/js/dependencies.rb
2
50.0%

Totals

Change from base Build 559:
-0.06%

Covered Lines:
247

Relevant Lines:
384

💛  - Coveralls

Pull Request Test Coverage Report for Build 560

0 of 0   changed or added relevant lines in 0 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.06%) to 64.323%

Files with Coverage Reduction
New Missed Lines
%

lib/i18n/js/dependencies.rb
2
50.0%

Totals

Change from base Build 559:
-0.06%

Covered Lines:
247

Relevant Lines:
384

💛  - Coveralls

Pull Request Test Coverage Report for Build 560

0 of 0   changed or added relevant lines in 0 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.06%) to 64.323%

Files with Coverage Reduction
New Missed Lines
%

lib/i18n/js/dependencies.rb
2
50.0%

Totals

Change from base Build 559:
-0.06%

Covered Lines:
247

Relevant Lines:
384

💛  - Coveralls

That's why we have Travis CI setup isn't it?
What cannot be archived without docker?


OCPBUGS-34107: Updating ose-cluster-image-registry-operator-container image to be consistent with ART for 4.17

This is a manual override of https://github.com/openshift/cluster-image-registry-operator/pull/1044.
Apparently, bumping Go to 1.22 caused a change in the vendored files.
This adds a commit after running go mod vendor to the original bot commit.

/jira refresh

/label qe-approved

Some jobs are failed, reruned

test failures seem unrelated
/restest

/lgtm

/retest

test failures are unrelated to the changes in this PR.
/hold cancel

/retest

Hypershift tests are still struggling - let's allow them some time to fix it before retesting.

/retest

/hold cancel

/retest

/retest

/retest

aws operator e2e seems extra flaky...
/retest

/retest

/retest


Fix solution image scaling

Fixes #110

I'll let you look at the comment on the for loop before merge, otherwise good to go


Add measuring nvlink traffic to diagnostics?

Learned that the main way to do this is via use of nsight, which is a whole external program. WOn't be adding


Edit Community docs pg

Answer to “How can I join” meetings question? on Commune with us docs page

Suggestion: funnel all requests through Introduction post - https://we.hypha.app/t/welcome-to-the-hypha-lounge/8

Action plan: edit Commune page to direct folks to this post plus advise "request access in your introduction post"

One question I have is who do we ping to get this access?  Who is actually responsible for giving the access to the Google meetings? @Erioldoesdesign do you know?

The choices on how/who to invite to maintainers calls:

Governance processes will further define how/who is invited and what that process includes
What tools we use for what reasons

Currently at the top of each maintainer's call agenda on we.hypha.app is the following:
"If you’d like access to the google meet room, send a message to the @maintainers group. If you’d like to be added to the calendar invite please DM @eriol ."
Will this phrasing work for now for the "How can I join" question on the Maintainer's call and the Adopter's call?

I think for now it solves some of the immediate problem as we develop the first iteration of governance :)
These kind of things will never be 'perfect' in that we'll never cover every potential new users needs to join and understand spaces but i feel like we have a good casual iteration process for now.

Individuals could reach out to the Hypha team via we.hypha.app or the product page https://www.hypha.app
Contact information is no longer included in documentation. Documentation will primarily focused on providing users with guidance on how to use the platform.


refactor(gateway, http, lavalink): Switch to tokio-websockets

This switches our websocket library from tokio-tungstenite to tokio-websockets.
Why?

tokio-tungstenite is notoriously slow with dependency updates (it took them one month from updating rustls to drafting a new release), which means we are held back on updating these shared dependencies
tokio-websockets pulls in fewer dependencies: a bare repository that only depends on model, http and gateway with only rustls-webpki-roots enabled sees this dependency drop when using this PR:

    Updating git repository `https://github.com/Gelbpunkt/twilight`
    Updating crates.io index
      Adding base64 v0.21.2
    Removing block-buffer v0.10.4
    Removing byteorder v1.4.3
    Removing cpufeatures v0.2.9
    Removing crypto-common v0.1.6
    Removing data-encoding v2.4.0
    Removing digest v0.10.7
      Adding fastrand v2.0.0
    Removing form_urlencoded v1.2.0
    Removing generic-array v0.14.7
    Removing getrandom v0.2.10
    Removing idna v0.4.0
    Removing ppv-lite86 v0.2.17
    Removing rand v0.8.5
    Removing rand_chacha v0.3.1
    Removing rand_core v0.6.4
    Removing sha1 v0.10.5
    Removing thiserror v1.0.43
    Removing thiserror-impl v1.0.43
    Removing tinyvec v1.6.0
    Removing tinyvec_macros v0.1.1
    Removing tokio-tungstenite v0.19.0
      Adding tokio-websockets v0.3.3
    Removing tungstenite v0.19.0
    Removing twilight-gateway v0.15.2 (https://github.com/twilight-rs/twilight?branch=next#8c48c3c7)
      Adding twilight-gateway v0.15.2 (https://github.com/Gelbpunkt/twilight?branch=tokio-websockets#b8234991)
    Removing twilight-gateway-queue v0.15.2 (https://github.com/twilight-rs/twilight?branch=next#8c48c3c7)
      Adding twilight-gateway-queue v0.15.2 (https://github.com/Gelbpunkt/twilight?branch=tokio-websockets#b8234991)
    Removing twilight-http v0.15.2 (https://github.com/twilight-rs/twilight?branch=next#8c48c3c7)
      Adding twilight-http v0.15.2 (https://github.com/Gelbpunkt/twilight?branch=tokio-websockets#b8234991)
    Removing twilight-http-ratelimiting v0.15.1 (https://github.com/twilight-rs/twilight?branch=next#8c48c3c7)
      Adding twilight-http-ratelimiting v0.15.1 (https://github.com/Gelbpunkt/twilight?branch=tokio-websockets#b8234991)
    Removing twilight-model v0.15.2 (https://github.com/twilight-rs/twilight?branch=next#8c48c3c7)
      Adding twilight-model v0.15.2 (https://github.com/Gelbpunkt/twilight?branch=tokio-websockets#b8234991)
    Removing twilight-validate v0.15.1 (https://github.com/twilight-rs/twilight?branch=next#8c48c3c7)
      Adding twilight-validate v0.15.1 (https://github.com/Gelbpunkt/twilight?branch=tokio-websockets#b8234991)
    Removing typenum v1.16.0
    Removing unicode-bidi v0.3.13
    Removing unicode-normalization v0.1.22
    Removing url v2.4.0
    Removing utf-8 v0.7.6
    Removing version_check v0.9.4
    Removing webpki v0.22.0

tokio-websockets is actively maintained (by me). I would not mind whatsoever moving it to the twilight organization to make it more accessible to fellow twilight maintainers
I have done excessive testing of tokio-websockets against the autobahn test suite that verifies RFC compliance of websocket libraries, tokio-websockets passes all cases it implements (see the results) and implements the entire required specification which is also used by Discord
Benchmark results reported by the autobahn testsuite when compared against tokio-tungstenite are within margin of error (and vary quite a bit, probably because the Rust clients are faster than the Python server)
tokio-websockets supports SIMD-accelerated masking and unmasking of websocket frames on x86 and can also use SIMD for UTF-8 validation, while tokio-tungstenite has to rely on auto-vectorization
The entire public API of twilight remains the same with this change (PR is against next because this is still a too big change to be deployed in a patch release)
Allows us to drop our custom TlsConnector logic, since tokio-websockets has this in-built

Why not?

tokio-tungstenite is probably more well-tested, despite tokio-websockets being used in some production applications for 1-2 years now
tokio-tungstenite has corporate backing in maintainership (although that argument doesn't hold up well if we look at the frequency of their commits)

Notes

Currently using a git dependency on tokio-websockets because I've added a few changes for easier integration with twilight that will require a new minor release
The entire twilight integration is completely untested I've verified that the gateway implementation runs shards properly for a long time (with several resumes), lavalink needs testing
I've ditched rand since it is a bit big for our uses and switched to fastrand because tokio-websockets supports it and uses it by default. I could revert that for now if desired.

TODO

Test test test test and did I mention testing?
Need to figure how to make cargo-hack skip the --no-default-features case and instead enable the no-tls feature for that

i like this change overall, but users might expect us to use de facto libraries, how much maintenance cost would it add to offer this under a feature flag?

i like this change overall, but users might expect us to use de facto libraries, how much maintenance cost would it add to offer this under a feature flag?

Impossible because we would have to make both websocket libraries opt-in to avoid pulling in both for those who do not want to use the other one. It wouldn't be worth the maintainance cost either and would probably require abstracting out a lot of things here in no-so-pretty-ways. In my view we should use whatever we consider superior, the concept of "de facto libraries" is flawed if the libraries are unmaintained or otherwise abandoned, slow or bloated. In my view, if we consider something to be superior, we should use it.

i like this change overall, but users might expect us to use de facto libraries, how much maintenance cost would it add to offer this under a feature flag?

Impossible because we would have to make both websocket libraries opt-in to avoid pulling in both for those who do not want to use the other one. It wouldn't be worth the maintainance cost either and would probably require abstracting out a lot of things here in not-so-pretty-ways. In my view we should use whatever we consider superior, the concept of "de facto libraries" is flawed if the libraries are unmaintained or otherwise abandoned, slow or bloated. In my view, if we consider something to be superior, we should use it.

i dont agree with the de facto libraries are better idea either i was just mentioning what most users would expect from twilight


[Linux] uWSGI: Fix permission denied on subprocess.getoutput

Using uWSGI on Linux, Python fails to call subprocess.getoutput method due to a permissions problem.
mkdir: cannot create directory '/.local': Permission denied
touch: cannot touch '/.local/share/applications/mimeapps.list': No such file or directory

Using the subprocess.check_output method, no directory creation request is made and the command returns the expected value
To be tested on other OS

@MatteoNet
Do you have an error log which lines was causing the issue? I tried checking out your changes but it fails on Ubuntu, snap-installed browsers.
mkdir: cannot create directory '/.local': Permission denied
touch: cannot touch '/.local/share/applications/mimeapps.list': No such file or directory

Looking at the code, I believe it is not related to getoutput() as this line is only running {browser} --version command and not mkdir.

Looks like this is related to chrome trying to write to /.local.

https://github.com/chrome-php/chrome/issues/106
https://github.com/chrome-php/chrome/issues/142


fix jsonPath -> JSONPath

Thanks for the PR, but the field name is jsonPath in v1, so the current documentation is correct.
/close


The difference between data in extension and debug mode

When displayed in debug mode, for an Entity that has a TransformComponent to display the position value on the screen, but not in the extension.

import {
    Color,
    DisplayMode,
    Engine,
    Entity,
    GraphicsComponent,
    Rectangle,
    TransformComponent,
    vec,
} from 'excalibur';

const game = new Engine({
    width: 800,
    height: 600,
    displayMode: DisplayMode.FitScreen,
});

const ent: Entity = new Entity({ name: 'Bubble' });
const transformComponent = new TransformComponent();
const graphicsComponent = new GraphicsComponent();
const rec2 = new Rectangle({
    width: 400,
    height: 20,
    color: Color.Cyan,
});
rec2.scale = vec(2, 2);
graphicsComponent.add(rec2);
transformComponent.pos = vec(150, 50);
ent.addComponent(graphicsComponent);
ent.addComponent(transformComponent);
ent.addTag('Bubble');

game.add(ent);
game.start();

@e1e5en-gd Definitely looks like a bug in the extension
I think this is assume that everything is an Actor type and has a .pos available. Entities would not have this https://github.com/excaliburjs/excalibur-extension/blob/main/src/background.js#L42


add an openssl mirror that points to where old releases will be archived

Fixes openssl breakage. There is a new version available and the 1.0.2k archive has been moved. There is probably a more tasteful way of doing this (the new location has 1.0.2 hardcoded in the path) but I didn't want to do it by adding a variable, and my cmake string parsing skills are weak.

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot


Setting status complete when transaction is successful

Description
Setting the status of the stand by as complete if we already know the transaction was successful.
Tested
Manually with the local emulator
How others should test
Does this need to be tested by QA in the next release cycle? If so please give a brief explanation of how to test these changes.
Related issues

Fixes #1573

Backwards compatibility
Compatible

This looks great, I'm just wondering now, does the comment show up whe nthe tx is comfirmed by this mechanism? I think we're not sending the comment to the standby tx thing, but I might be wrong.
Anways, amazing job! 👏

Yep, I have never added the comment to the standby tx. However, I think this was working like this in the previous version. Right?
I'm testing with the previous flow, and I can't see the comment anywhere. :/

Hey @MuckT, We will verify all the transaction status, while performing regression test plan.
Thanks...!!


Add email options to script

Several people have asked for an option to be able to email the report file.

A couple suggestions for the (now implemented) mail enhancement:

I like to do the following for my mail-enabled scripts:

...
[Parameter(Mandatory = $False)]
[String] $MailFrom,
[Parameter(Mandatory = $False)]
[String] $MailServer,
...
If ((Get-Module ActiveDirectory) -eq $Null) {
Import-Module ActiveDirectory
}
...
Fix some defaults that couldn't be done in Param block...
If ($MailFrom -eq "") {
$MailFrom = "administrator@" + (Get-ADDomain).DNSRoot
}
If ($MailServer -eq "") {
$MailServer = "mail."

Consider parameterizing the MailSubject as well...

SendEmail w/o a MailTo is non-sensical, as is setting MailTo w/o specifying SendEmail. -MailTo should be your sole routing trigger. No need to have a -SendEmail argument at all.

.\GetMailboxReport.ps1 -All -MailTo user@domain


Integrate TEEHR with NGIAB

Closing as completed, see: https://github.com/RTIInternational/ngiab-teehr


Fix and simplify a set cleaning logic

Hot-fix for #1041

@Zizitto v0.2.2 has been published  to NPM. Please check again and let me know.
Also, do you know what the actual problem was? how can this be reproduced? In order for me to write tests for this scenario, I need to know the actual problem.

There were wrong parameters passed to "srem" command.
The first parameter should be a key, but i`ve passed a list of members there, by mistake.

Checked 0.2.2, issue gone.

Many thanks for the fast resolving.

Many thanks for the fast resolving.

Many thanks for contributing!


Use drop-down menus instead of TextFields for changing the settings.

https://github.com/sopra-fs23-group-05/Client/pull/176

https://github.com/sopra-fs23-group-05/Client/pull/176/commits/46b1763f362921ce3a9982cb531e632776ce40b0


[wip] Fixes #2055 add MarkdownCodeFormatter to format markdown code

@TomasVotruba current update:

markdown parsed code inside

create files per code block with $this->smartFileSystem->dumpFile($file, $match) as php-code-{index}.php as many as the code block found.

apply $this->singleFileProcessor->processFileInfo($fileInfo); into it

Looking at the file created, it seems the CS not patch it.

Do you have idea how to make CS patch to new created file?

Here is the output for parsed markdown file, the SingleFileProcessor seems not patch cs the code:

Using shell_exec to run ecs seems working but not sure if it is a good solution?
            // try using shell_exec ?
            shell_exec(dirname(__DIR__, 3) . '/bin/ecs check ' . $file . ' --fix');

Using shell_exec to run ecs seems working but not sure if it is a good solution?

I think it would be better to use FileProcessor, but it might take many extra hours just to be ready for re-use.
Let's got with shell_exec() and see, if it works correctly.

@TomasVotruba it is functional now like the following:

I see. The output is now pretty unclear. Also failing on any exception will be wrapped around shell_exec() and hard to debug as it's different sub-process now.
Saying that, it would be better to have good quality solution over fast hacky one.
We'll need to use FileProcessor after all.
Maybe the code is running in dry-run mode.
Adding Configuration to the command and using this method to set true might help:
https://github.com/symplify/symplify/blob/4964d3cea202f240db9c2c0705c6187bb699f58a/packages/easy-coding-standard/packages/configuration/src/Configuration.php#L88-L94

I tried using Symplify\EasyCodingStandard\FixerRunner\Application\FixerFileProcessor, not working, how to apply the configuration to make option isFixer in the command ?

The Configurarion is a service, so you can require it in the constructor of the command.
Then call the resolveFromArray() in the start of execute() method

implemented with FixerFileProcessor now.

It is ready for review now 🎉

Updated with $this->easyCodingStandardStyle->success() to set message and return ShellCode::SUCCESS:

I'll do some changes locally in naming, to respect Symplify conventions, but otherwise it looks good to me.
Can I merge it?

yes :+1:

Thank you :+1:

There is one follow up feature that is needed for Rector.
Basically the same process, just instead of markdown files,
it should process the HERE/NOWDOCS in PHP files:
https://github.com/rectorphp/rector/blob/71682d2b52edd8d0f36fe822e077c7f05a8311f4/rules/php55/src/Rector/String_/StringClassNameToClassConstantRector.php#L58-L69

It can be a new command:
vendor/bin/ecs check-heredoc src

Instead of 1 file, it will go through all found files in /src


🪲[Bug]: Back to top option is very small in mobile screen

Back to top option is very small in size in small screens.

I would love to solve this issue. Please assign this issue to me under gssoc'24.
Also can you add gssoc label


Test for editable page title when there are random times of space entered in the front of the title like '       xxxxx'

There is a special edge case that the user may enter some random space before they enter the core title.
Like '          translation'
To implement random times of space, I firstly initialize a random number. Then I search in the Stack overflow how to use the regular expression to write the format.
Source can be found here :  https://stackoverflow.com/questions/33539797/how-to-create-string-with-multiple-spaces-in-javascript
component.setTitle( Array(num).fill('\xa0').join('') + 'new editable Page');

describe("DemoComponent-pagetitle-edittwice", () => {
  let component: DemoComponent;
  let fixture: ComponentFixture<DemoComponent>;
  let num:number = Math.ceil(Math.random()*10);

  beforeEach(async () => {
    await TestBed.configureTestingModule({
      imports: [MaterialModule],
      declarations: [DemoComponent],
      schemas: [CUSTOM_ELEMENTS_SCHEMA],
    }).compileComponents();

    fixture = TestBed.createComponent(DemoComponent);
    component = fixture.componentInstance;
    component.setTitle( Array(num).fill('\xa0').join('') + 'new editable Page');
    fixture.detectChanges();
  });

  it("test editable page title after random times of edit ", () => {
    const { debugElement } = fixture;
    const title1 = debugElement.query(By.css('#spanid')).nativeElement;
    expect(title1.textContent).toContain('\xa0'.repeat(num) + 'new editable Page');
 });
});


Changed content-type to only be used on POST requests

When using the eventbrite API you can specify a changed_since parameter. This is ignored by eventbrite on GET requests when changed_since is used, so you get ALL results back.
This is obviously an issue on the eventbrite side of the house BUT as it's not important to set the Content-Type header on GET requests (as there is no body), it seems easy enough to fix here.

You should fix your editor settings so that only intended changes are committed

Hi @millsy! Just an FYI that I'll review the changes either tonight or in the next couple of days. As @blairanderson said, mind updating the PR to have two spaces?

@millsy mind rebasing on the latest master? merged / pushed a few PRs

Hi guys. what @millsy is saying is absolutely true!
I was fighting with this issue for 2 days when I started to think that it could be a bug within the node-eventbrite node module.
Figured out after reading here that what @millsy is saying is actually true for ALL REQUESTS!
I was trying to perform a search based on location using the parameters:
location.latitude
location.longitude
location.within
and I was always getting an unfiltered response from eventbrite.
Please accept his pull request. This is a serious issue.
If you guys lost his PR because of merging the deal is really simple:
Here's what I could come up with by reading his post:
First lines of the eventBritAPI_v3.prototype.execute could be changed to this:
` if (!verb) {
verb = "GET";
}
var headers = {
"Authorization": 'Bearer ' + this.token,
"User-Agent": this.userAgent
};
if (verb === "POST") {
    headers["Content-type"] = this.contentType;
}`

@amostech the branch is messed up. it needs to be fixed.

Check out my pull request.
It has no conflict with the master branch.

I've just created it. Hope it helps.

I hear you Arthur, thanks for investigating this. I'll take a look later
today!
On Wednesday, March 9, 2016, Arthur Morales<EMAIL_ADDRESS>wrote:

I've just created it. Hope it helps.
—
Reply to this email directly or view it on GitHub
https://github.com/Datahero/node-eventbrite/pull/7#issuecomment-194705800
.

--
Islam Sharabash
217-377-9657

Closing, changes are now merged + published.


Auto corrected by following Format Ruby Code

Auto corrected by following Format Ruby Code
Click here to configure it on awesomecode.io

Coverage increased (+0.05%) to 97.086% when pulling 137af82c21a5720e33c5f17530f72de1809dfd47 on awesomecode-format-ruby-code-47988 into c1c881357d3a80de23f363a82e901e5db64926d4 on master.

Coverage increased (+0.05%) to 97.086% when pulling 137af82c21a5720e33c5f17530f72de1809dfd47 on awesomecode-format-ruby-code-47988 into c1c881357d3a80de23f363a82e901e5db64926d4 on master.


parseFromString pushes custom elements in the  to the

Hello, I noticed that parseFromString tends to push all elements in the  to the  as soon as it encounters either a custom element, or an element that is not intended for the head (such as
 or ).
Example:
import { DOMParser } from "jsr<EMAIL_ADDRESS>
const my_html = `

	<custom-element id="2"></custom-element>

`

const doc = new DOMParser().parseFromString(my_html, "text/html")
console.log(doc.documentElement!.outerHTML)

This produces the (prettified) html:

	<custom-element id="2"></custom-element>

The expected output should have been:

	<custom-element id="2"></custom-element>

From what I've tested, this seems to be an issue with the parseFromString method, and not the outerHTML accessor, because if I replace an element inside of the head (e.g. element.replaceWith(doc.createElement("custom-element"))), then the custom element is not pushed into the body instead.
Is this by design? Because it certainly makes it extremely inconvenient to make transformations to head elements.
Thanks in advance!

I've tried a few things in web browsers (chromium and firefox), and seems like both DOMParser.prototype.parseFromString and Document.parseHTMLUnsafe do not force non-head child elements into the body.
If you execute the following in your browser's console, you'll notice that the head's child elements do in fact have their positions preserved after being parsed:
console.log((new DOMParser().parseFromString(`

`, "text/html")).documentElement.outerHTML)

On the other hand, if you set the innerHTML or outerHTML of document.documentElement, then the browser pushes some of the head's child elements into the body, similar to how this library does it.
Since this library uses servo's html5ever under the hood, I can't say whether or not the inconsistency between firefox's behavior and this library's output stems from html5ever.

I've tried a few things in web browsers (chromium and firefox), and seems like DOMParser.prototype.parseFromString does in fact forcefully push custom elements in the head to the body.
In other words, the behavior of this library is consistent with browser implementations.
I imagine that changing the behavior would not only be a non-goal, but also extremely difficult, given that it relies on servo's html5ever crate.
So, please feel free to close this issue if that is the case.