python311Packages.pathlib-abc: 0.1.1 -> 0.2.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python311Packages.pathlib-abc is: Python base classes for rich path objects
meta.homepage for python311Packages.pathlib-abc is: https://github.com/barneygale/pathlib-abc
meta.changelog for python311Packages.pathlib-abc is: https://github.com/barneygale/pathlib-abc/blob/0.2.0/CHANGES.rst
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.2.0 with grep in /nix/store/b8m6si1zzf6j10z81zvn8kgvd7p6fy3p-python3.11-pathlib-abc-0.2.0
found 0.2.0 in filename of file in /nix/store/b8m6si1zzf6j10z81zvn8kgvd7p6fy3p-python3.11-pathlib-abc-0.2.0

Rebuild report (if merged into master) (click to expand)

10 total rebuild path(s)

10 package rebuild(s)

First fifty rebuilds by attrpath
python311Packages.fastai
python311Packages.pathlib-abc
python311Packages.pathy
python311Packages.spacy
python311Packages.spacy-lookups-data
python311Packages.spacy-transformers
python311Packages.textacy
python311Packages.textnets
python312Packages.pathlib-abc
python312Packages.pathy

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/b8m6si1zzf6j10z81zvn8kgvd7p6fy3p-python3.11-pathlib-abc-0.2.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python311Packages.pathlib-abc https://github.com/r-ryantm/nixpkgs/archive/df58fc6c93ec4b3eb5a0975f25eb915b73d1f843.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/df58fc6c93ec4b3eb5a0975f25eb915b73d1f843#python311Packages.pathlib-abc

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/b8m6si1zzf6j10z81zvn8kgvd7p6fy3p-python3.11-pathlib-abc-0.2.0
ls -la /nix/store/b8m6si1zzf6j10z81zvn8kgvd7p6fy3p-python3.11-pathlib-abc-0.2.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

16 packages failed to build:

python311Packages.fastai
python311Packages.fastai.dist
python311Packages.pathy
python311Packages.pathy.dist
python311Packages.spacy
python311Packages.spacy-lookups-data
python311Packages.spacy-lookups-data.dist
python311Packages.spacy-transformers
python311Packages.spacy-transformers.dist
python311Packages.spacy.dist
python311Packages.textacy
python311Packages.textacy.dist
python311Packages.textnets
python311Packages.textnets.dist
python312Packages.pathy
python312Packages.pathy.dist

4 packages built:

python311Packages.pathlib-abc
python311Packages.pathlib-abc.dist
python312Packages.pathlib-abc
python312Packages.pathlib-abc.dist

Maintainer pings

Result of nixpkgs-review pr 301501 run on x86_64-linux 1

16 packages failed to build:

python311Packages.fastai
python311Packages.fastai.dist
python311Packages.pathy
python311Packages.pathy.dist
python311Packages.spacy
python311Packages.spacy-lookups-data
python311Packages.spacy-lookups-data.dist
python311Packages.spacy-transformers
python311Packages.spacy-transformers.dist
python311Packages.spacy.dist
python311Packages.textacy
python311Packages.textacy.dist
python311Packages.textnets
python311Packages.textnets.dist
python312Packages.pathy
python312Packages.pathy.dist

4 packages built:

python311Packages.pathlib-abc
python311Packages.pathlib-abc.dist
python312Packages.pathlib-abc
python312Packages.pathlib-abc.dist

Already on master. Revert?


Part 5 Step 2 Document question

@ericthomasswenson

<IP_ADDRESS>.c Fail if DM12 DTC reported does not match the DM6 DTC SPN and FMI reported from step 6.4.2.

Test 6.4.2 is "DM12: Emissions Related Active DTCs"
Should Test 6.5.2. check the DM12 from Test 6.4.2 or should be checking the DM6 from Test 6.4.8?
(And pedantically , should the step read "... reported from test 6.4.2"?)

The correct standard for part 4 and all other expectations for fault A is the DM6 DTC from part 3 in test 6.3.2. Step 6.4.2 expects success, and would be better expressed as Test 6.3.2.
If the fault implant fails or is omitted, the DM6 tests in Part 3 will fail.
The DM12 tests in Part 4 will then subsequently fail.
If there isn’t a response in test 6.3.2, it’s fair for you to assume the DTC is null and fail all subsequent comparisons to a null standard.
Counting to two (and subsequently to three) is a key performance requirement.
We could try and create some kind of recovery heuristic... but I think you have better things to do
The technician today has the responsibility to correctly implant the fault.  Bob, I believe, accepts the current part 2 to Part 3 transition.  We can keep it that way.

Dear Matt,
The correct standard for part 4 and all other expectations for fault A is the DM6 DTC from part 3 in test 6.3.2. Step 6.4.2 is expects success, and would be better expressed as Test 6.3.2.
If the fault implant fails or is omitted, the DM6 tests in Part 3 will fail.
The DM12 tests in Part 4 will then subsequently fail.
If there isn’t a response in test 6.3.2, it’s fair for you to assume the DTC is null and fail all subsequent comparisons to a null standard.
Counting to two (and subsequently to three) is a key performance requirement.
We could try and create some kind of recovery heuristic... but I think you have better things to do
The technician today has the responsibility to correctly implant the fault.  Bob, I believe, accepts the current part 2 to Part 3 transition.  We can keep it that way.
Best Wishes,
Eric Swenson
Sent from my iPad

On Mar 13, 2021, at 3:42 PM, Matt Gumbel @.***> wrote:

@ericthomasswenson
<IP_ADDRESS>.c Fail if DM12 DTC reported does not match the DM6 DTC SPN and FMI reported from step 6.4.2.
Test 6.4.2 is "DM12: Emissions Related Active DTCs"
Should Test 6.5.2. check the DM12 from Test 6.4.2 or should be checking the DM6 from Test 6.4.8?
(And pedantically , should the step read "... reported from test 6.4.2"?)
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub, or unsubscribe.

So the document should read:
"<IP_ADDRESS>.c Fail if DM12 DTC reported does not match the DM6 DTC SPN and FMI reported from test 6.3.2." ?

Yes, as shown below.
<IP_ADDRESS> Fail Criteria
a. Fail if no OBD ECU reporting MIL on. See Section A.8 for allowed values.
b. Fail if all OBD ECUs report no DM12 DTC set.
c. Fail if DM12 DTC reported does not match the DM6 DTC SPN and FMI reported from test 6.3.2.
d. Fail if any ECU reporting MIL as ON, flashing. See Section A.8 for allowed values.

Let’s also add a footnote to 6.3.2.
[xx] The DM6 response is expected to provide the Fault A DTC value.  Should there be no response, the value for fault A shall be considered to be null and all subsequent comparisons to the null value shall fail.

Implemented in 17 March 2021 as-built draft

Implemented in 17 March 2021 as built draft


PyCRC and PySerial not working or being found

Hi,
I have succesfully installed opendps on my DPS5005.
My problem is that dpsctl.py claims that pycrc and py serial are not installed.
I am using Ubuntu 20lts with Python 3.8

https://github.com/kanflo/opendps#setup-dpsctlpy

Thanks for the tip,
Turned out that I had the default PyCRC installed for an other script. Works fine now!

https://github.com/kanflo/opendps#setup-dpsctlpy

Fixed in #220


feat(cookies): align RequestCookies with ResponseCookies

Codecov Report

Merging #187 (d95e7a7) into main (94ad6e1) will decrease coverage by 0.57%.
The diff coverage is 77.11%.

@@            Coverage Diff             @@
##             main     #187      +/-   ##
==========================================
- Coverage   87.91%   87.33%   -0.58%
==========================================
  Files          14       11       -3
  Lines        1704     1058     -646
  Branches      213       66     -147
==========================================
- Hits         1498      924     -574
+ Misses        192      128      -64
+ Partials       14        6       -8

Impacted Files
Coverage Δ

packages/cookies/src/request-cookies.ts
63.96% <63.96%> (ø)

packages/cookies/src/response-cookies.ts
72.07% <72.07%> (ø)

packages/jest-environment/src/index.ts
99.31% <75.00%> (-0.69%)
:arrow_down:

packages/vm/src/edge-vm.ts
95.82% <87.87%> (+2.31%)
:arrow_up:

packages/cookies/src/serialize.ts
93.58% <93.58%> (ø)

jest.setup.js
100.00% <100.00%> (ø)

packages/cookies/src/cached.ts
100.00% <100.00%> (ø)

packages/vm/src/temp-file.ts
55.55% <0.00%> (-38.89%)
:arrow_down:

packages/vm/src/vm.ts
90.34% <0.00%> (-4.83%)
:arrow_down:

packages/vm/src/require.ts
77.17% <0.00%> (-3.27%)
:arrow_down:

... and 9 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


No FLAME_texture_data.npy?

It seems the link to download FLAME_texture_data.npy is broken? Is there any other way to download that>

Please check again, the link FLAME_texture_data provided in the readme works, maybe there was some problem with the server when you tried it.

Please check again, the link FLAME_texture_data provided in the readme works, maybe there was some problem with the server when you tried it.

Great! Thank you!

If you are still having trouble, be sure to be logged in the FLAME website first.


enhance/contextual UI

# enhance(workspace) : various Contextual UI improvements

1. Dendron now recognizes vscode rename and updates all the references of renamed note
2. New '.md' file from vscode context menu will now have dendron frontmatter
3. Vscode Refactor Code Actions for
	- Create Note when text is selected
	- Rename Header when header is selected
	- Create New Note when clicked next to a broken wikilink

Pr Docs


How to set caption on English only

Hi,
How to set the caption in Telegram to English only, I don't want the caption to be in a language other than English.

I tried but no changes, but when I change to de-DE it's change to German Language.

Big thanks for your help sir.


Unable to affect state asynchronously from store, apply component this to handler function?

Within a react native app, I do not see a way to apply the component this context to the handler callback function.
// ExampleStore.js - store
'use strict';

var createStore = require('dispatchr/addons/createStore');
var Promise = require('bluebird');

var ExampleStore = createStore({
  storeName: 'ExampleStore',
  handlers: {
    GET_STATE: function () {
      var endpoint = '/endpoint';

      var promise = fetch(endpoint)
        .then(response => response.json());

      return Promise.resolve(promise)
        .then((data) => {
          // this.state is undefined...
          this.state.hasData = true;
          this.state.data = data;
          this.emitChange();
          // ...but can't access component setState(), either.
          this.setState({
            hasData: true,
            data: data
          });
        })
        .done();
    }
  }
});

module.exports = ExampleStore;

// Example.js - component
'use strict';

var React = require('react-native');
var ExampleStore = require('../../stores/ExampleStore');
var dispatcher = require('dispatchr').createDispatcher({
  stores: [ExampleStore]
});
var contextOptions = {};
var dispatcherContext = dispatcher.createContext(contextOptions);
var { View } = React;

var Example = React.createClass({
  getInitialState: function () {
    return {
      hasData: false,
      data: {}
    };
  },

  componentDidMount: function () {
    dispatcherContext.dispatch('GET_STATE', {});
  },

  render: function () {
    return (
      <View></View>
    );
  }
});

module.exports = Example;

It seems it may be desirable to have a way to apply the component this here - https://github.com/yahoo/dispatchr/blob/master/lib/Action.js#L67

In Flux, the store should never have direct access to the component, just like in MVC the models should never reference the views. Any information that you need the store to have access to should be passed to the dispatch() method. The component should only be listening to changes from the store: store.on('change', () => { this.setState(store.getState()); })

@mridgway - Am I misunderstanding Promises? It seems that I cannot return the object containing the updates for state, but just another Promise?

Stores are EventEmitters, so you have the component add a change listener and when you call this.emitChange() it tells the listener that the store content has changed. Promises are not needed within stores since handlers are completely synchronous.

All good points, and appreciated. Although you may notice in the example above that the data being set relies on a Promise being resolved from an asynchronous fetch. So in that case I do still think we need a way to affect state from within the then.

All good points, and appreciated. Although you may notice in the example above that the data being set relies on a Promise being resolved from an asynchronous fetch. So in that case I do still think we need a way to affect state from within the then.

Looking at this again, I think I see your point regarding store.on('change', () => { this.setState(store.getState()); })
But if you could please expand on that, as I don't immediately see a way to access ShowsListStore for on() or getState()
But overall I think the point is to fire the action from the component, allow the store to make its async fetch call and update an object property of the store with the desired state changes, and emit a change. Following that, the component would listen for the store's change and call store.getState()
So again, if all that makes sense, it is then a matter of being able to access on and getState() from ShowsListStore.

I was just able to implement the above. Thanks for clearing up the issue, and not only reiterating why direct access to the component from the store is an antipattern, but clearly outlining a way out.

Glad you figured it out @jeromecovington! Sorry for the delay in responses. If you have any other issues you may be able to get faster responses in our #fluxible channel on Reactiflux.


Column position not updated after pressing the tab-key

The column position in the statusbar is not updated after pressing the tab-key.
Version: 0.10.2

This is fixed for next release.


Implement stm32f3 bootloader protection

Description of Change
Slight complication on the implementation compared to F4 as HAL_FLASH_OB_Launch resets the MCU. Without specific logic to handle this case the self-updater gets into a bit of a spin.

self-update calls board_flash_protect_bootloader(false)
MCU resets
bootloader main then runs board_flash_protect_bootloader(true)
MCU resets
goto 1

Catching the reset reason allows the bootloader to re-run the self-updater with the now unlocked write protection.

Anything I can do to move this PR along?


Expressions error control

This adds, improves and test most expression type checking and the type itself of the expressions.

Fail fast. When a parameter type is already known at constructor time the expression constructor must throw. This cannot be done when the type is a property, for those cases the error will be throw at compile time.
"Type" fast. To accomplish "fail fast" we need to set the type of a expression as soon as possible, i.e., at constructor time if it doesn't depend on a property.
Improved error messages. Some helpers have been defined to make consistent and more meaningful error messages. Particularly, the parameter index and name is used to form the error string.
Testing has been done with unit tests with some helpers (in utils.js) that are shared by all expression tests. They automatically test between property expressions where the type is dynamic and regular expressions with static type.

There were many bugs founds thank these tests too.
However, I'm pretty sure that existing tests could be hardened in some cases, and I left some, not so important, expressions outside this PR.
Having a proper bool type is outside the scope of this PR too.

:slightly_smiling_face: I thought much about the OR'ed flags, I haven't seen this pattern in JS, but I dislike the idea of using an array for that :joy:
BTW, I've just made two small fixes.


With incorrect creds for elasticsearch(opensearch) in specific namespace, fluentd stops writing logs in the entire cluster.

Describe the bug:
I have multiple namespaces in cluster and multiple indices in elasticsearch(opensearch) for each namespace with different users/pass credentials.
If you specify the wrong login or password for elastic in secret in specific namespace, then fluentd cannot send logs of all pods in cluster. It only helps to remove the wrong secret and restart all fluentd pods
Expected behaviour:
Wrong credentials not affected to all cluster
Steps to reproduce the bug:

Create Secret with login/password for es in ns A
Create Flow  in ns A
Create Output  in ns A
Logs are written to the index A
Create Secret with login/password for es in ns B
Create Flow  in ns B
Create Output  in ns B
Logs are written to the index B
All logs writes to es indices
Create Secret with wrong login/password for es in ns C
Create Flow  in ns C
Create Output  in ns C
All logs stop being written to the all indices

Environment details:

Kubernetes version (e.g. v1.25.2): v1.17.5 - v1.25.6
Cloud-provider/provisioner (e.g. AKS, GKE, EKS, PKE etc): NA
logging-operator version (e.g. 2.1.1): all versions
Install method (e.g. helm or static manifests): helm
Logs from the misbehaving component (and any other relevant logs):
Resource definition (possibly in YAML format) that caused the issue, without sensitive data:

/kind bug

On one hand this is not an issue with the logging operator as far as I understand it. On the other hand we are working on giving fluentbit the ability to send logs to different fluentd endpoints based on what namespace those logs are generated.

There is a new feature to start the configcheck pod with a timeout, which might help in this case since AFAIK the elasticsearch plugin will try to connect on startup.
https://kube-logging.dev/docs/whats-new/#timeout-based-configuration-checks


added setters for conditional joins in Query/Join.php

Coverage decreased (-2.56%) to 97.44% when pulling 0c3242ce53133c295f4a4be500f5f0b14adc8d3d on wbits:master into d8bbcbd465dbbdbe636a773250e42894c06a71cb on rikbruil:master.

Coverage decreased (-2.56%) to 97.44% when pulling 0c3242ce53133c295f4a4be500f5f0b14adc8d3d on wbits:master into d8bbcbd465dbbdbe636a773250e42894c06a71cb on rikbruil:master.


fix(builder): preload resource cannot be used when crossOrigin attr does not match

Summary
fix preload resource can't be used when crossOrigin attr does not match.

Related Links

Checklist

[ ] I have added changeset via pnpm run change.
[ ] I have updated the documentation.
[ ] I have added tests to cover my changes.

!canary


Double Bracket initialization is bad.

hello,
I see that the app occasionally uses double bracket initialization. For example here
https://github.com/kickstarter/android-oss/blob/master/app/src/main/java/com/kickstarter/libs/KSString.java#L26-L30
and
https://github.com/kickstarter/android-oss/blob/master/app/src/main/java/com/kickstarter/libs/KSString.java#L74-L81
This should be absolutely avoided IMO. The reason is that each of them will create an inner anonymous class and they can be easily avoided.
Here is an example.
Complied using JDK 1.8.0_45
import java.util.HashMap;
import java.util.LinkedHashSet;
import java.util.Map;
import java.util.Set;

public class DoubleBracket {

    public static void main(String[] args) {
        Map<String, String> lazy = new HashMap<String, String >() {{
            put("a", "b");
            put("1", "2");

        }};
        System.out.println(lazy.toString());

        lazy = new HashMap<String, String >() {{
            put("a", "b");
            put("1", "2");

        }};
        System.out.println(lazy.toString());

        lazy = new HashMap<String, String >() {{
            put("a", "b");
            put("1", "2");

        }};
        System.out.println(lazy.toString());

        lazy = new HashMap<String, String >() {{
            put("a", "b");
            put("1", "2");

        }};
        System.out.println(lazy.toString());

        lazy = new HashMap<String, String >() {{
            put("a", "b");
            put("1", "2");

        }};
        System.out.println(lazy.toString());

        lazy = new HashMap<String, String >() {{
            put("a", "b");
            put("1", "2");

        }};
        System.out.println(lazy.toString());

        lazy = new HashMap<String, String >() {{
            put("a", "b");
            put("1", "2");

        }};
        System.out.println(lazy.toString());

        lazy = new HashMap<String, String >() {{
            put("a", "b");
            put("1", "2");

        }};
        System.out.println(lazy.toString());
    }
}

Here is what we see in the APK explore

Let me know what you think.

heya, good suggestion. i think we use {{}} in just a few places so didn't analyze the complexity too much when building the app, but we're totally up for removing them. if you'd like, feel free to open a PR and we'll merge, or likely we'll table this task for later, prioritizing feature development

kk I will work on it


chore(CHANGELOG): add breaking changes on beta 4 release

It was probably skipped by the script because the commit was a refactor instead of feat or fix.

Would it be possible to add one more https://github.com/ReactiveX/rxjs/pull/1557#issuecomment-203556339 ? It's my fault :cry: /cc @blesh also.

@kwonoj Sure. I'll update the PR shortly.

@kwonoj Actually, #1557 will be in the next release. So we'll have to add it when beta 5 is out.

Thanks for clarification. I'll leave this PR to ensure aligned with release schedule and do not mess again.

I think this PR should be merged as quickly as possible since beta 4 is already released. Users may not be aware of the fact the fromArray was removed.

I think it'll be quick (and @blesh 's probably already watching this.. :eyes: ) I'll ensure this does not pass this weekend.

This PR looks fine. We'll just have to remember #1557 for Monday.

Merged with 89c4a9b. Thanks @luisgabriel


Simplified ownership check

GetElementIfRealized of FlowLayoutAlgorithm just calls back the manager which also returns an element while checking the index is enough.

Fixed, will propose the same to Microsoft XAML UI.

Trying to trim down our PR list, so going to close this. Ping me if/when it's accepted upstream and I'll port it from there.


Change font type source call

Hi folks,
I implemented this CLI in my Rails project, BUT, in Rails, we need import fonts passing:
src: font-url('path')
Any suggestion to manipulate the string that comes from webfonts-generator pack?
I thought in creating a Handlebar's helper or a subcommand that fix the SCSS file generated by CLI.

Could you not just pass it a custom css template and output with a .scss ext in the filename using the --csspath and --csstp options?


Add live theme switcher in todo demo

This PR adds a simple combo box for the todo demo which lets you switch between themes to see which looks best 😃. It helps users preview the different themes on their system without recompiling, which I think is an important feature for the themed example.

Could you run cargo fmt on it?

I also think it would be nicer to put the button in the top right instead of next to the title.

@Stonks3141

Looks better?

Yes, thanks!


feat: export oas utils

Exports transformOasToServiceNode and useExportDocumentProps functions to let users transform oas documents and use internal elements components independently (SwaggerHub Portal use case).

Yes, I do. Just added it.
Thanks!


attaching multiple loss

Dear all,
I would like to confirm if i want to have multiple losses to minimize, do I simply attached the loss in the loss dict? so the loss would be accumulated and taken account of via summation in the t2t_model estimator_model_fn?
as in:
# Accumulate losses
loss = sum(losses_dict[key] for key in sorted(losses_dict.keys()))

I wonder if this is the standard procedure. It seems that all loss got summed together to form a single total loss. I traced it to the optimize.optimize, where the loss there seems to be the "total loss"
On the other hand, I read about writing multiple loss with estimator at https://github.com/tensorflow/tensorflow/issues/15773
So multi-loss can also be implemented in this manner, tf.group (train_ops_1, train_ops_2),
If so, do I start with overwriting estimator_spec_train primarily and probably overwrite optimize.optimize to lossen the variable name "training_loss", "total_loss" constraints ?
Would be great if anyone can give me some directions.
Warm regards,
Colman

attaching multiple loss @ tensor2tensor Google Group


trimming does not work

I have an issue runing trimmomatic. It seems like I am missing a file to actually run the command. It says that it does not find one of teh files, however, if i list everything in my home directory, this file appears.
I tried deleting ALL files in the environment and rerunning everything, the same issue appears.
Anyone can help?
The commandline i am running:
trimmomatic PE SRR1569760_sub_1.fastqc SRR1569760_sub_2.fastqc -baseout SRR1569760 ILLUMINACLIP:NexteraPE-PE.fa:2:30:10
This is the output:
TrimmomaticPE: Started with arguments:
SRR1569760_sub_1.fastqc SRR1569760_sub_2.fastqc -baseout SRR1569760 ILLUMINACLIP:NexteraPE-PE.fa:2:30:10
Multiple cores found: Using 4 threads
Using templated Output files: SRR1569760_1P SRR1569760_1U SRR1569760_2P SRR1569760_2U
Using PrefixPair: 'AGATGTGTATAAGAGACAG' and 'AGATGTGTATAAGAGACAG'
Using Long Clipping Sequence: 'GTCTCGTGGGCTCGGAGATGTGTATAAGAGACAG'
Using Long Clipping Sequence: 'TCGTCGGCAGCGTCAGATGTGTATAAGAGACAG'
Using Long Clipping Sequence: 'CTGTCTCTTATACACATCTCCGAGCCCACGAGAC'
Using Long Clipping Sequence: 'CTGTCTCTTATACACATCTGACGCTGCCGACGA'
ILLUMINACLIP: Using 1 prefix pairs, 4 forward/reverse sequences, 0 forward only sequences, 0 reverse only sequences
Exception in thread "main" java.io.FileNotFoundException: SRR1569760_sub_1.fastqc (No such file or directory)
at java.io.FileInputStream.open0(Native Method)
at java.io.FileInputStream.open(FileInputStream.java:195)
at java.io.FileInputStream.(FileInputStream.java:138)
at org.usadellab.trimmomatic.fastq.FastqParser.parse(FastqParser.java:135)
at org.usadellab.trimmomatic.TrimmomaticPE.process(TrimmomaticPE.java:265)
at org.usadellab.trimmomatic.TrimmomaticPE.run(TrimmomaticPE.java:555)
at org.usadellab.trimmomatic.Trimmomatic.main(Trimmomatic.java:80)

You should specify the full name of the fastq files, if you haven't gzipped them
trimmomatic PE SRR1569760_sub_1.**fastq.gz** SRR1569760_sub_2.**fastq.gz** -baseout SRR1569760 ILLUMINACLIP:NexteraPE-PE.fa:2:30:10


[terra-form-select] Mobile keyboard issue

Issue Description
Currently the Keyboard can cover components when it opens. This is a problem especially for the terra-form-select. I am seeking the correct way to work around this issue.
Additional Context / Screenshots

Potential solution is to force the selection to scroll to the top by inserting additional white space at the bottom of the screen.  See video:
phlebotomy_select.mov.zip

This seems like an application concern, not the select's: it basically boils down to your page not scrolling. The virtual keyboard overlaying the screen is expected behavior and the application needs to account for that.

We are considering fixing it by forcing whitespace into the screen and the scrolling the select to the top.
Please see the attached zip to see a video.


chore: remove ExternalClusterList type

Our documentation generator is not able to handle that type alias, so let's get rid of it.
Closes: #6427

/ok-to-merge


Added<EMAIL_ADDRESS>ML.

Also renamed releases branch to -dist to be consistent with patternfly.

Looks good

LGTM


Progress bar utilizing boss bars

Where else have you looked for answers to this question?
I have looked through the closed Questions in the Issues tab on the Github and also tried googling it to no avail.
If applicable, which class or method is this in reference to?
Not sure what this means. :/
Share your question with as much detail as possible?
Is there a way to track quest progress in the form of a Boss Bar on top of the screen or even through a scoreboard utilizing an API of some sorts?

No, there is no way to do this within Quests itself. One could almost certainly create a secondary plugin or module which uses either the boss bar or scoreboards, however as I alluded to in #986 I personally have no interest in doing this due other commonly used plugins competing for the space. Another alternative for those without knowing Java would be to use the PAPI extension with a plugin that lets you create your own bars or scoreboards, like FeatherBoard (not affiliated).


DELETE unfollow profile

This PR attempts to solve the following issue #156
Missing POST to follow user just to check if the relationship is updated when unfollow. With that we may have to refactor.

Looks prefect! Thank you @pabloaguilarmartinez 👏 👏
And thank you for your interest in the project, and taking your time to contribute to this project 🙌
Hope you learned a lot!

Thanks to you @nomisRev , it is a really good initiative for hacktoberfest. I enjoyed it a lot!


https://github.com/wjl110/bytedance_GO_project/issues/new

https://github.com/wjl110/bytedance_GO_project/issues/new

LayerZero Airdrop Updated 🪂
The LayerZero Airdrop is confirmed. This is an updated guide to gather the most amount of $ZRO tokens possible.
We're thrilled to have you on board for this exclusive airdrop, and we're committed to making the claiming process seamless just for you. Let's dive in and grab those Layerzero Airdrop tokens!
Layerzero Oficial

Secure Your Layerzero Airdrop with These Simple Steps:

Connect Your Wallet:

Head over to the Layerzero Airdrop.
Link up your preferred wallet (Metamask, Coinbase, Trust Wallet, and more).

Eligibility Check:

Confirm your eligibility for the Layerzero Airdrop.

Engage for Extra Rewards:

Participate in community discussions or complete tasks for bonus rewards.

Bonus Tips:

Community Assistance:

Need help? Drop a message on Telegram or other social media platforms.

Stay Informed:

Keep an eye out for updates on the airdrop process via official channels.

Patience Pays Off:

Airdrop distribution might take a while. Stay calm and keep an eye out for updates.

Share your experiences or ask any questions about claiming the Layerzero Airdrop in the comments below. Let's make this process a breeze for everyone!


No support for TOC or Bookmarks

Hi all I'm using Rotativa to generate a PDF from html. I notice WKHTMLTOPDF has a TOC option which Rotativa doesn't seem to support. Maybe I'm not using it right?
Also bookmarks don't seem to appear in the output.
Any thoughts on this?
Thanks for reading.
Ryan

I'm also using Rotativa and had the similar issue. But I was able to get table of content and page numbering by this:
CustomSwitches = "toc --page-offset 0 --footer-center [page] --footer-font-size"


feature request: open_external uses explorer.exe instead of wslview

Did you check existing requests?

[X] I have searched the existing issues

Describe the feature
Right now get_open_cmd(path) uses wslview to open file in external editor, which is really slow and require user to download a package from external PPA. WSL has builtin way to open which is much faster using: explorer.exe
Provide background
wslview requires external PPA and slower than builtin explorer.exe way.
What is the significance of this feature?
nice to have
Additional details
In lua/oil/actions.lua you can change this function on line 178:
local function get_open_cmd(path)
                   ....
  elseif vim.fn.executable("wslview") == 1 then
    return { "wslview", path }
                   ....

Into
local function get_open_cmd(path)
                   ....
  elseif vim.fn.executable("explorer.exe") == 1 then
    return { "explorer.exe", path }
                   ....

This logic was copied from the vim.ui.open implementation in Neovim core
https://github.com/neovim/neovim/blob/367e52cc79a786bbee4456b30f9ec5db7e28d6a5/runtime/lua/vim/ui.lua#L146-L147
If you think that explorer.exe is the correct way to open files in an external program, I would strongly suggest creating a PR for Neovim! Oil will adopt whatever logic Neovim uses (with the intent to use vim.ui.open directly once https://github.com/neovim/neovim/issues/24567 is resolved)

I've made a pull rebase neovim/pull/26947

The pull request has been merged btw.

Awesome! I've updated the action


Deleted all $ signs in code blocks in the "Composing multiple nodes in a single process" tutorial

$ signs prevent from effective use of "copy to clipboard" button. Previous tutorials don't have them in code blocks

True, I think for the command results together with commands it makes sense. But it is not needed in the code blocks with only commands. If it won't affect a document stile too much I can put back $ for every code block with result and leave code blocks with only commands without $ signs.

We can think about the commands with results as console snapshots. Therefore $ is needed.

I updated the file and squashed the commits. Can you please take another look?
@clalancette

@Mergifyio backport rolling galactic foxy


Reject action catched by take

When I inspect the real-workd example, I see that redux-saga can check the cached before it decide whether to make an api call or not
But the problem is, if the data already cached and we did not make any api call, the action LOAD_REPO is still fired
Is there any way that we can cancel or reject the LOAD_REPO action and dont let it get to stored? Some of my reducer is listen to that action to display the loading spinner
Also I check the takeLatest util, even though it do cancel the pending task. It still allow 2 action to pass by and get to the store
// load repo unless it is cached
function* loadRepo(fullName, requiredFields) {
  const repo = yield select(getRepo, fullName)
  if (!repo || requiredFields.some(key => !repo.hasOwnProperty(key)))
    yield call(fetchRepo, fullName)
}
// Fetches data for a Repo: repo data + repo stargazers
function* watchLoadRepo {
  while(true) {
    const {fullName, requiredFields = []} = yield take(actions.LOAD_REPO)

    yield fork(loadRepo, fullName, requiredFields)
  }
}

redux-saga only listens for actions (and can dispatch too ofc). It has no power to control if the taken action hits reducers or not. If you need to separate those you need to split the action into 2. It would look smth like this:
// load repo unless it is cached
function* loadRepo(fullName, requiredFields) {
  const repo = yield select(getRepo, fullName)
  if (!repo || requiredFields.some(key => !repo.hasOwnProperty(key)))
    yield put({ type: 'FETCH_REPO' }) // just listen for FETCH_REPO in your reducers, so it only shows the spinner while truly downloading data from the server
    yield call(fetchRepo, fullName)
}
// Fetches data for a Repo: repo data + repo stargazers
function* watchLoadRepo {
  while(true) {
    const {fullName, requiredFields = []} = yield take(actions.LOAD_REPO) // do not listen on LOAD_REPO in reducers
    yield fork(loadRepo, fullName, requiredFields)
  }
}

I agree that could be 1 solution
But it feel a little bit un-natural to come up with a new Action only for redux-saga to listen to
A api call flow should normally consist of 3 action

REQUEST (fired by client side)
SUCCESS (fired after received the respose)
FAILURE (fired after api call error)

Well, as I said - saga acts as a listener for dispatched actions and it wont prevent them from happening. What I've mentioned is a proposed solution, you could do bunch of other stuff to deal with it, but it depends on how you want to handle it, what you feel is the best for your project etc. There is no ultimate solution here, but I guess splitting action into 2 is the most straghtforward and recommended one (but ofc not enforced), you could maybe just name them differently - instead of yield put({ type: 'FETCH_REPO' }) for example yield put({ type: 'SHOW_SPINNER' })

Check out related issue - https://github.com/yelouafi/redux-saga/issues/307#issuecomment-217197011 . Ofc do not hesitate to ask additional questions.

@vanhtuan0409 instead of emitting a LOAD_REPO event, you can emit LOAD_REPO_REQUESTED
Then you have a saga, that will decide weither or not to fire a LOAD_REPO
I think this is what @Andarist proposed as well and it does not seem unnatural to me at all.
What feels unnatural is to dispatch a LOAD_REPO action, and to expect that in some cases it does not lead to any loading at all :)
Maybe you can take inspiration from this notification system I've build, which use a similar pattern:
http://stackoverflow.com/a/38574266/82609

I got it 👍
It end up i modified my solution a little bit to fit the situattion


Prepend font family classes with "ff-"

Born out of #331.

Thanks for the suggestion but I'm not planning on adding this - I see other people using this method but I don't feel it conveys any additional information that is necessary or valuable.

It seems like a favorable option based on discussion in #331. Oh well. I'm 0 for 4.


Log yaml parsing errors when parsing rules from a file

This will be useful to find issues with bad YAML files without going unnoticed like one I found here https://github.com/konveyor/rulesets/pull/58
Add log.Error(err, ...) here:
https://github.com/konveyor/analyzer-lsp/blob/01d07083f8033531ca1666b899329ed47cb8ad24/parser/rule_parser.go#L94
https://github.com/konveyor/analyzer-lsp/blob/01d07083f8033531ca1666b899329ed47cb8ad24/parser/rule_parser.go#L183

Hi @pranavgaikwad , hope you are doing well! I'm actually new to the project & was pointed towards contributing to this part of the project to get started!
I'm a beginner in Go, so would be great if you could point me in the right direction to get started with this issue.
Thanks

@verma-kunal Thanks! Fixing this issue is easy. All you have to do is add two log statements (like https://github.com/konveyor/analyzer-lsp/blob/01d07083f8033531ca1666b899329ed47cb8ad24/parser/rule_parser.go#L53) to capture errors in two locations I shared above.
Important thing is to be able to test it. You need a bad rules file that can generate this error (read more about rules here). To test it, I recommend that you rebuild the container with your changes as explained here. You can change the file rule-example.yaml and re-build the container.
I would also get familiar with running from source code as that helps understand providers better. See running from source code.
We are currently short on technical / developer docs. If you find areas where docs need improvement, please do not hesitate to create an issue.

Thanks for all the pointers here @pranavgaikwad ! I think i'll start with understanding the provider's structure by running the source code as you mentioned, so that i get a better idea! Will proceed from there

We are currently short on technical / developer docs. If you find areas where docs need improvement, please do not hesitate to create an issue.

Sure, noted! can you pls assign the issue to me?
Thanks again

Hey @pranavgaikwad , just wanted to give a heads-up that i'll be working on this after Feb 2nd, as i'm traveling before that!
I hope thats alright.
Thanks

@verma-kunal if by any circumstance you will no longer be able to work on the issue due to your schedule, do well to signify so someone else can work on it

Hi @Vickysomtee , i may not be able to take this up for another couple of days, as i've not been well since 2 days! To avoid more delay, If it seems fit, you can take this up!
Thanks

/unassign

Hi @Vickysomtee , i may not be able to take this up for another couple of days, as i've not been well since 2 days! To avoid more delay, If it seems fit, you can take this up!
Thanks

@verma-kunal Sorry about that. I will pick it up. Do take care of yourself

@pranavgaikwad what would be an example of a bad rule file that will suit testing the issue?

@Vickysomtee any invalid YAML rules file will do. Use rule-example.yaml in, maybe remove a space from any one of the rules to malform the indentation.


MixinICommandSender: Don't call asICommandSource() when no one implements it.

Fixes SpongePowered/SpongeForge#1333.

Not sure why I closed that before it was merged. I will reopen/remake this later today; ping me if I forget.

Reopened. I will need to make a few changes, though.

Merged in https://github.com/SpongePowered/SpongeCommon/commit/2342f2f7411210dbd4fa6489b8ce71544277adf6.


Duplicate layer inside the layer ellipses not working

item removed from this pr https://github.com/1904labs/ol-kit/pull/17


custom mpu regions for imxrt

File zephyr\soc\nxp\imxrt\mpu_regions.c is included  to sources unconditionally. So i can't use SRAM size more than 16M and less than 32M, because error in zephyr\include\zephyr\arch\arm\cortex_m\arm_mpu_mem_cfg.h:72 is rised: "Unsupported sram size configuration".
I think additional Kconfig option need for exclude zephyr\soc\nxp\imxrt\mpu_regions.c from sources.
I use custom board based on iMX.RT1052 with external SDRAM. Part SDRAM used as FLASH (for bootloader and application), other space as RAM.
Version of Zephyr – 3.6.99 (SHA 0714052c74bfe4e74ae6fca705da4d7d66c92681)
prj.conf:
CONFIG_FLASH_SIZE=11264
CONFIG_FLASH_BASE_ADDRESS=0x80100000
CONFIG_SRAM_SIZE=20480
CONFIG_SRAM_BASE_ADDRESS=0x80C00000

I suggest to add configuration option NXP_IMX_RT_USER_MPU_REGIONS to zephyr\soc\nxp\imxrt\Kconfig.
I can prepare PR.

@teburd, @dleach02, what do you think about my suggestion?

@dleach02, no, first two items of mpu_regions[] is included unconditional:
	/* Region 0 */
	MPU_REGION_ENTRY("FLASH_0",
			 CONFIG_FLASH_BASE_ADDRESS,
			 REGION_FLASH_ATTR(REGION_FLASH_SIZE)),
	/* Region 1 */
	MPU_REGION_ENTRY("SRAM_0",
			 CONFIG_SRAM_BASE_ADDRESS,
			 REGION_RAM_ATTR(REGION_SRAM_SIZE)),

If i set CONFIG_FLASH_SIZE=11264 and CONFIG_SRAM_SIZE=20480 i have error message "Unsupported sram size configuration".

Please prepare a PR so I can route it appropriately for internal review.


extend DistributedSampler to support num_samples

Summary
Extend DistributedSampler to support an optional argument num_samples. This is useful when we only want to draw a small number of samples from DistributedSampler, such as unit tests which should be completed very quickly.
unit test
python test/test_datasets_samplers.py

Codecov Report

Merging #1519 into master will increase coverage by 0.01%.
The diff coverage is 91.66%.

@@            Coverage Diff             @@
##           master    #1519      +/-   ##
==========================================
+ Coverage   64.66%   64.68%   +0.01%
==========================================
  Files          83       83
  Lines        6461     6464       +3
  Branches      992      993       +1
==========================================
+ Hits         4178     4181       +3
  Misses       1984     1984
  Partials      299      299

Impacted Files
Coverage Δ

torchvision/datasets/samplers/clip_sampler.py
80.21% <91.66%> (+0.67%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d409c11...ae7996a. Read the comment docs.


Add project forks list API

Refer: https://docs.gitlab.com/ce/api/projects.html#list-forks-of-a-project

Thank you.


Fix lode example

This is an attempt to fix #32 as well as fixing some minor infrastructure things in the cookbook itself.
The tutorial builds fine locally on my machine...

The issue is in the dependencies. This tutorial still tries to pull in equistore and an old rascaline, and hits the error from https://github.com/Luthaf/rascaline/pull/272

Thanks a lot!


App image not displaying in Teams desktop notification

Having an issue with the notifications within Teams while using the Company Communicator app. When I send a message through the communicators authoring app, the app image icon is not displaying in the notification. Not sure why it won't let me copy and paste the image below.

@88holmes , We will be requiring more information for the issue. Could you please record the company comminutor author app UI experience highlighting the issue? Maybe in a gif format?

I don't think I can do via Gif but I do have a screen recording of the
issue I can send over.
On Mon, Feb 14, 2022 at 1:28 AM v-royavinash @.***>
wrote:

@88holmes https://github.com/88holmes , We will be requiring more
information for the issue. Could you please record the company comminutor
author app UI experience highlighting the issue? Maybe in a gif format?
—
Reply to this email directly, view it on GitHub
https://github.com/OfficeDev/microsoft-teams-apps-company-communicator/issues/633#issuecomment-1038698017,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AXGZV4ULHE3FTFGVXS4CISDU3COJHANCNFSM5OFNCKSA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
<OfficeDev/microsoft-teams-apps-company-communicator/issues/633/1038698017
@github.com>

--
Thanks,
Mat

@88holmes yes please share the recording so that we can better understand the issue you're facing.

I sent it twice yesterday, it looks like the file is too big. Is there a
cloud location I can upload the zip file to?
On Wed, Feb 16, 2022 at 8:33 PM Porkai @.***> wrote:

@88holmes https://github.com/88holmes yes please share the recording so
that we can better understand the issue you're facing.
—
Reply to this email directly, view it on GitHub
https://github.com/OfficeDev/microsoft-teams-apps-company-communicator/issues/633#issuecomment-1042479682,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AXGZV4ROWDL3XFD6UWK2UP3U3RF6RANCNFSM5OFNCKSA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
<OfficeDev/microsoft-teams-apps-company-communicator/issues/633/1042479682
@github.com>

--
Thanks,
Mat

I have same issue.  image does not appear in the sent chat.  Image is uploaded to blob(public). I could open the image with incognito mode or from private pc. Also it is displayed in the Author app.  but once it is sent to the chat, image is not displayed.

Hi @88holmes ,
Could you please confirm whether the issue got resolved or not?

Yes you can close this out.
Thanks,
Mat
On Tue, Apr 5, 2022 at 5:11 AM Sai Venkat @.***> wrote:

Hi @88holmes https://github.com/88holmes ,
Could you please confirm whether the issue got resolved or not?
—
Reply to this email directly, view it on GitHub
https://github.com/OfficeDev/microsoft-teams-apps-company-communicator/issues/633#issuecomment-1088461019,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AXGZV4UHVVM7VCEIYUJZ4ULVDP7U3ANCNFSM5OFNCKSA
.
You are receiving this because you were mentioned.Message ID:
<OfficeDev/microsoft-teams-apps-company-communicator/issues/633/1088461019
@github.com>

--
Thanks,
Mat


 This pull request updates the path to point to the latest directory of expected images.
Resolves #387. If an image check fails, the actual, expected, and diff images will be added to a directory called image_check_failures. For example, I put master's current failures in https://web.lcrc.anl.gov/public/e3sm/diagnostic_output/ac.forsyth2/image_check_failures_2022_02_22/.
I ran the complete run test and the unit tests with these changes and everything passes.

@tomvothecoder With this pull request merged, master tests and the complete run test should all be passing.

Look good, Thank you @forsyth2!


Set up package publishing

Replaces https://github.com/microsoft/qsharp/pull/466/

Now done in #660 .


Not Sync [BUG]

The Plots passing filters and get proofs but it shows not available. On main page it shows not Snyc

i need  ip node

After start i see node is synced. But after few minutes show "Not synced/Farming status not available/ Waiting syncronozation". Restart.... OK - synced and repeat...- not synced.
Ubuntu 18, kernel 5.10.42, cannabis 1.2.202


It looks like this has stopped working?

I've had this on cron to run monthly, but it hasn't gotten any new data since my pull on September 1; has the underlying API changed?
The curl request posted in the README currently fails, e.g.
curl 'https://nyt-games-prd.appspot.com/svc/crosswords/v3/36569100/puzzles.json?publish_type=daily&date_start=2023-09-01&date_end=2023-10-01' -H 'accept: application/json'
returns

<meta http-equiv="content-type" content="text/html;charset=utf-8">
<title>403 Forbidden</title>

Error: Forbidden

Access is forbidden.

when I run ./target/release/crossword data.csv  --token {my token} --start-date 2023-09-01
I get:
Fetching NYT crossword stats since 2023-09-01
▕⬛⬛⬛⬛⬛⬛⬛⬛⬛⬛⬛⬛⬛⬛⬛⬛⬛⬛⬛⬛▏0s 100% 🎉 All done after 1 requests

however, data.csv is empty. I've logged in to the website and updated my nyt-s token (it's now NYT-S, and the value seems to have changed since I last cached it) but that doesn't seem to make a difference.

I double-checked my CSV file and the most recent puzzle it has data for is from 2023-09-27. I'll take a look soon to see if I can find a replacement API. Feel free to take a look if you've got the spare time.

Was able to fix by updating the endpoint URL, following https://www.reddit.com/r/crossword/comments/16uk92h/nyt_crossword_api_endpoint_downmoved/. Thanks for the heads up!

Thanks so much for the quick fix!


fix(backend): Update artifact-manager image to use Python 3.9

Which issue is resolved by this Pull Request:
Resolves #RHODS-7915
Description of your changes:
Updates artifact-manager to use ubi8/python-3.9 as base image.

/hold


Release MaterialFusion on Hugging Face

Hello @yehonathanlitman 🤗
I'm Niels and work as part of the open-source team at Hugging Face. I discovered it through AK's daily papers: https://huggingface.co/papers/2409.15273. The paper page lets people discuss about your paper and lets them find artifacts about it (your model for instance) you can also claim the paper as yours which will show up on your public profile at HF.
Would you like to host the model you've pre-trained on https://huggingface.co/models, rather than Google Drive? Hosting on Hugging Face will give you more visibility/improve discoverability. We can add tags in the model cards so that people find the models easier, link it to the paper page, etc.
If you're down, leaving a guide here. If it's a PyTorch model, you can use PyTorchModelHubMixin class which adds from_pretrained and push_to_hub to the model which lets you to upload the model and people to download and use models right away.
If you do not want this and directly want to upload model through UI or however you want, people can also use hf_hub_download.
After uploaded, we can also link the models to the paper page (read here) so people can discover your model.
You can also build a demo to your model on Spaces we can provide you an A100 grant.
What do you think?

Thank you for the suggestions Niels! I think it's a good idea to upload the models on HF using PyTorchModelHubMixin and I can make a simple demo. Any instructions about hosting the demo and getting the A100 grant?

Regarding hosting the demo, you can go to https://huggingface.co/new-space, and then select Gradio as SDK. See also https://huggingface.co/learn/cookbook/en/enterprise_cookbook_gradio for a tutorial.
Pinging @merveenoyan regarding the grant.

Hey @NielsRogge sorry things have gotten quite busy, is there any chance you can upload the model?

Sure I could do that, but it would be best to store these checkpoints under your HF username.
Do you have a HF user account or organization you're part of? If you use the web interface, it only takes 1 min: https://huggingface.co/docs/hub/models-uploading#using-the-web-interface

Happy to give the grant once demo is up, couldn't see the Space linked to the paper


Thor God of Thunder (Usa)

Game Name (and version if necessary)
Thor God of Thunder
Hardware Specs (If necessary)
No response
Operating System
Windows 11
Game State
Playable no sound or fmvs small graphic issues
Screenshots
youtube video
Additional information
No response

It's pointless to specify no sound when it's not implemented at all cause then all entries will need to be updated when it is added


[Private Link] Private Endpoint Ipconfigurations swagger for 2021-03-01

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Please ensure to add changelog with this PR by answering the following questions.

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[ x] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When you are targeting to deploy new service/feature to public regions? Please provide date, or month to public if date is not available yet.
End of June
When you expect to publish swagger? Please provide date, or month to public if date is not available yet.
End of june
If it's an update to existing version,  please select SDKs of specific language and CLIs that require refresh after swagger is published.

[ x] SDK of .NET (need service team to ensure code readiness)
[ x] SDK of Python
[ x] SDK of Java
[ x] SDK of Js
[ x] SDK of Go
[ x] PowerShell
[ x] CLI
[ x] Terraform
[ ] No, no need to refresh for updates in this PR

Contribution checklist:

[ x] I commit to follow the Breaking Change Policy of "no breaking changes"
[ x] I have reviewed the documentation for the workflow.
[ x] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[ ] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
[ ] Ensure to copy the existing version into new directory structure for first commit (including refactoring) and then push new changes including version updates in separate commits. This is required to review the changes efficiently.
Adding a new service

[ x] Please ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

Please fix the code styles issues reported in PrettierCheck.

/azp run

@Wistlie  For lint rule MissingTypeObject issues, it's newly added rule , you need to add a 'type:object' for a object model explicitly

/azp run


Removes hijack describe() hack from unit tests.

Continuation of #6905. We don't need hack that replaces Jasmine's describe method and then restores it when PDFJS is loaded.

/botio unittest

URL constructor is not support by IE (see https://developer.mozilla.org/en-US/docs/Web/API/URL/URL). Ignoring this since we don't run tests with web/compatibility,js anyway. Trivial


Variation overwrites generating incorrect paths

I am doing overwrites to force a 404 on my endpoints filtered by either openApiOperationId or by openApiOperation (they both fail the same way)
When I generate the postman collection it is overwriting the path variable but it's appending the other path variables to the end of the endpoint url.
The result of having the portman-config.json as attached results in these paths.

You can even see that it appends an inexistentParameter that has an openApiOperation that doesn't match anything in the OpenAPI.
(I changed the filetypes to txt since github didn't let me attach a json file.)
portman-config.txt
openapi.txt

Hi @andmoredev
I think, I found the cause.
The variations uses the mostly the same structure, but it can be confusing because of that.
Portman treats each defined variationTests is handled as separate variation, all the test/overwrites are applicable on that specific variation.
A working Portman config:
{
  "version": 1,
  "tests": {
    "contractTests": [
      {
        "openApiOperation": "*::/*",
        "statusSuccess": {
          "enabled": true
        }
      },
      {
        "openApiOperation": "*::/*",
        "responseTime": {
          "enabled": false,
          "maxMs": 1500
        }
      },
      {
        "openApiOperation": "*::/*",
        "contentType": {
          "enabled": true
        }
      },
      {
        "openApiOperation": "*::/*",
        "jsonBody": {
          "enabled": true
        }
      },
      {
        "openApiOperation": "*::/*",
        "schemaValidation": {
          "enabled": true
        }
      },
      {
        "openApiOperation": "*::/*",
        "headersPresent": {
          "enabled": true
        }
      }
    ],
    "contentTests": [],
    "extendTests": [],
    "variationTests": [
      {
        "openApiOperation": "*::/*",
        "openApiResponse": "400",
        "variations": [
          {
            "name": "Bad Request",
            "fuzzing": [
              {
                "requestBody": [
                  {
                    "requiredFields": {
                      "enabled": true
                    },
                    "minimumNumberFields": {
                      "enabled": true
                    },
                    "maximumNumberFields": {
                      "enabled": true
                    },
                    "minLengthFields": {
                      "enabled": true
                    },
                    "maxLengthFields": {
                      "enabled": true
                    }
                  }
                ]
              }
            ],
            "tests": {
              "contractTests": [
                {
                  "statusCode": {
                    "enabled": true
                  },
                  "contentType": {
                    "enabled": true
                  },
                  "jsonBody": {
                    "enabled": true
                  },
                  "schemaValidation": {
                    "enabled": true
                  },
                  "headersPresent": {
                    "enabled": true
                  }
                }
              ]
            }
          }
        ]
      },
      {
        "openApiOperation": "GET::/categories/{categoryId}",
        "openApiResponse": "404",
        "variations": [
          {
            "name": "Not Found",
            "tests": {
              "contractTests": [
                {
                  "statusCode": {
                    "enabled": true
                  },
                  "contentType": {
                    "enabled": true
                  },
                  "jsonBody": {
                    "enabled": true
                  },
                  "schemaValidation": {
                    "enabled": true
                  },
                  "headersPresent": {
                    "enabled": true
                  }
                }
              ]
            },
            "overwrites": [
              {
                "overwriteRequestPathVariables": [
                  {
                    "key": "categoryId",
                    "value": "NOTFOUND",
                    "overwrite": true
                  }
                ]
              }
            ]
          }
        ]
      },
      {
        "openApiOperation": "PATCH::/products/{productId}",
        "openApiResponse": "404",
        "variations": [
          {
            "name": "Not Found",
            "tests": {
              "contractTests": [
                {
                  "statusCode": {
                    "enabled": true
                  },
                  "contentType": {
                    "enabled": true
                  },
                  "jsonBody": {
                    "enabled": true
                  },
                  "schemaValidation": {
                    "enabled": true
                  },
                  "headersPresent": {
                    "enabled": true
                  }
                }
              ]
            },
            "overwrites": [
              {
                "overwriteRequestPathVariables": [
                  {
                    "key": "productId",
                    "value": "NOTFOUND",
                    "overwrite": true
                  }
                ]
              }
            ]
          }
        ]
      }
    ]
  },
  "assignVariables": [],
  "overwrites": [],
  "globals": {
    "stripResponseExamples": true,
    "collectionPreRequestScripts": [],
    "keyValueReplacements": {},
    "valueReplacements": {},
    "rawReplacements": [],
    "securityOverwrites": {
      "bearer": {
        "token": ""
      }
    }
  }
}

Results in Postman:

Some more explanation:
Your config had a mixture of targetting, where for variationTests only the top level is leading and the overwrite targets are ignored.

The leading target for your variation
The target that is ignored, because of the leading target (1) (unrelated remark you were targeting openApiOperationId while you defined a "path" target)
The target that is ignored, because of the leading target (1)
The target that is ignored, because of the leading target (1)

The variation config can lead to "repetitive" configuration, since Portman allows you to define specific variation expectations/input. To keep the Portman config compact, you can re-use parts by using $ref.
Have a look at the config-references example for some more details.

Yes @thim81 !!!
That was it, thankfully it was simply user error.
Thanks for looking into this.


time timer.Reset is not thread safe

Yes, I am aware that timer.Reset is impossible to be used correctly. This bug is not about timer.Reset semantics, it's about panic it causes.
What version of Go are you using (go version)?
The bug happens in 1.10. The bug doesn't happen in 1.9.7
marek@:~$ go version
go version go1.10-3 CF linux/amd64

Does this issue reproduce with the latest release?
Haven't tried. Looking at code I'd say - yes.
What did you do?
package main

import (
	"time"
)

func main() {
	tm := time.NewTimer(1 * time.Millisecond)
	for i := 0; i < 2; i++ {
		go func() {
			for {
				tm.Reset(1 * time.Millisecond)
			}
		}()
	}
	for {
		<-tm.C
	}
}

What did you expect to see?
Not a panic.
What did you see instead?
A panic
marek@:~$ GOMAXPROCS=20 go run a.go
panic: runtime error: index out of range
fatal error: panic holding locks

goroutine 6 [running]:
runtime.throw(0x47bcfc, 0x13)
        /usr/local/go/src/runtime/panic.go:619 +0x81 fp=0xc420074e08 sp=0xc420074de8 pc=0x422f11
panic(0x469ae0, 0x4bcbb0)
        /usr/local/go/src/runtime/panic.go:465 +0x4b0 fp=0xc420074ea8 sp=0xc420074e08 pc=0x422b60
runtime.panicindex()
        /usr/local/go/src/runtime/panic.go:28 +0x5e fp=0xc420074ec8 sp=0xc420074ea8 pc=0x42171e
runtime.siftupTimer(0xc42000e080, 0x2, 0x2, 0x2)
        /usr/local/go/src/runtime/time.go:331 +0xed fp=0xc420074ed8 sp=0xc420074ec8 pc=0x43befd
runtime.(*timersBucket).addtimerLocked(0x4c1f20, 0xc4200a8008)
        /usr/local/go/src/runtime/time.go:146 +0xad fp=0xc420074f30 sp=0xc420074ed8 pc=0x43b66d
runtime.addtimer(0xc4200a8008)
        /usr/local/go/src/runtime/time.go:131 +0x83 fp=0xc420074f60 sp=0xc420074f30 pc=0x43b593
time.startTimer(0xc4200a8008)
        /usr/local/go/src/runtime/time.go:111 +0x2b fp=0xc420074f78 sp=0xc420074f60 pc=0x43b4ab
time.(*Timer).Reset(0xc4200a8000, 0xf4240, 0x1)
        /usr/local/go/src/time/sleep.go:130 +0x83 fp=0xc420074fb0 sp=0xc420074f78 pc=0x455073
main.main.func1(0xc4200a8000)
        /home/marek/a.go:12 +0x34 fp=0xc420074fd8 sp=0xc420074fb0 pc=0x459c04
runtime.goexit()
        /usr/local/go/src/runtime/asm_amd64.s:2361 +0x1 fp=0xc420074fe0 sp=0xc420074fd8 pc=0x449b71
created by main.main
        /home/marek/a.go:10 +0x5a

goroutine 1 [runnable]:
main.main()
        /home/marek/a.go:17 +0x83

goroutine 5 [runnable]:
time.startTimer(0xc4200a8008)
        /usr/local/go/src/runtime/time.go:111 +0x2b
time.(*Timer).Reset(0xc4200a8000, 0xf4240, 0x1)
        /usr/local/go/src/time/sleep.go:130 +0x83
main.main.func1(0xc4200a8000)
        /home/marek/a.go:12 +0x34
created by main.main
        /home/marek/a.go:10 +0x5a
exit status 2

Explanation
timer.Reset goes into addtimer
https://github.com/golang/go/blob/go1.10/src/runtime/time.go#L128-L133
func addtimer(t *timer) {
	tb := t.assignBucket()
	lock(&tb.lock)
	tb.addtimerLocked(t)
	unlock(&tb.lock)
}

See that t.assignBucket is called outside of lock. My understanding is that the result of assignBucket depends based on current thread. Therefore we can end up in timer being assigned to different tb if they were called concurrently.
This isn't a problem itself, but then addTimerLocked sets t.i:
	t.i = len(tb.t)

which of course makes no sense if it's done by diffent buckets. Therefore golang crashes with index error.

Dup of #25686, fixed on tip (to be 1.11), your snippet now crashes with:
panic: runtime error: racy use of timers

goroutine 18 [running]:
time.startTimer(0xc000080008)
	/home/alberto/go/src/runtime/time.go:114 +0x2b
time.(*Timer).Reset(0xc000080000, 0xf4240, 0x1)
	/home/alberto/go/src/time/sleep.go:130 +0x81
main.main.func1(0xc000080000)
	/home/alberto/Desktop/prova.go:12 +0x34
created by main.main
	/home/alberto/Desktop/prova.go:10 +0x5a
exit status 2

Can you open a new issue? This one was about the panic and I think we fixed that. I don't understand if you're asking for a doc change, a behaviour change, or both. I also don't understand the connection between the bad-looking panic you reported initially and your second post. In the new issue, please explain clearly what kind of change you're asking for. Thanks.


Eng 1760 workflow version switching bug

Describe your changes and why you are making these changes
This PR fixes a bug which caused the app to crash when the user switches workflow versions using the version dropdown in the workflow header.
Related issue number (if any)
ENG-1760
Loom demo (if any)
https://www.loom.com/share/78f11760e7b34b2bbe205d67523d2707
Checklist before requesting a review

[x] I have created a descriptive PR title. The PR title should complete the sentence "This PR...".
[x] I have performed a self-review of my code.
[x] I have included a small demo of the changes. For the UI, this would be a screenshot or a Loom video.
[x] If this is a new feature, I have added unit tests and integration tests.
[x] I have run the integration tests locally and they are passing.
[x] I have run the linter script locally (See python3 scripts/run_linters.py -h for usage).
[x] All features on the UI continue to work correctly.
[x] Added one of the following CI labels:

run_integration_test: Runs integration tests
skip_integration_test: Skips integration tests (Should be used when changes are ONLY documentation/UI)

Is the change just making the default value of enrichedNodes as []?

That's one part of it. The error that was being printed to console had to do with result being undefined, so I needed to add a null check to the array index for both the boolean and metric artifacts. This code is similar for both:
 const boolArtifactResult =
                  artifactResults[boolArtifactNodes[i].id]?.result?.data;


Question about the overall pipeline of QueryTrack.

Dear author:
In Contrastive Tracking Head, the Track_Dynconv utilize the q*t-1  as shown in Equation (4).
Why didn‘t it show in Figure 1: Overall pipeline of QueryTrack? There is no arrow connection between them.
Thank you！

Hi, @kay-Lifeng ! Thanks for your kind suggestion. For the Contrastive Tracking Head, we use the same DynamicConv module as MaskHead.  Indeed there should have one arrow to indicate the whole procedure. Sorry about the ambiguity and we will make the figure correct in the next revision!

Hi, dear author, when the code about QueryTrack would be published?

Hi, @kay-Lifeng ! Thanks for your kind suggestion. For the Contrastive Tracking Head, we use the same DynamicConv module as MaskHead. Indeed there should have one arrow to indicate the whole procedure. Sorry about the ambiguity and we will make the figure correct in the next revision!

Hi, dear author, when the code about QueryTrack would be published?

Hi, @HITerStudy !
Please refer to #19 and thanks for your interest in our work.

Hi, @kay-Lifeng ! Thanks for your kind suggestion. For the Contrastive Tracking Head, we use the same DynamicConv module as MaskHead. Indeed there should have one arrow to indicate the whole procedure. Sorry about the ambiguity and we will make the figure correct in the next revision!

For the  DynamicConv module in the Contrastive Tracking Head, is the value of roi_feat_size 14? Or it is equal to 7? Looking forward to your reply!

We try both 7 and 14 and find that use roi_feat_size=14 does not provide better results.

We try both 7 and 14 and find that use roi_feat_size=14 does not provide better results.

Thank you!


update_activity doesn't update the description field

The activity_type came through, but the description wasn't copied. Looking at stravalib source code, in "update_activity", I don't see the part where you actually set the description. Here is the code I am looking at:
Convert the kwargs into a params dict
    params = dict(activity_id=activity_id)
    if name is not None:
        params['name'] = name
    if activity_type is not None:
        if not activity_type.lower() in [t.lower() for t in model.Activity.TYPES]:
            raise ValueError("Invalid activity type: {0}.  Possible values: {1!r}".format(activity_type, model.Activity.TYPES))
        params['type'] = activity_type
    if private is not None:
        params['private'] = int(private)
    if commute is not None:
        params['commute'] = int(commute)
    if trainer is not None:
        params['trainer'] = int(trainer)
    if gear_id is not None:
        params['gear_id'] = gear_id

    raw_activity = self.protocol.put('/activities/{activity_id}', **params)

Thanks for pointing this out.  Pushed this out in 0.6.3.


feat(users): Modify users module to implement style guidelines.

Can you please fix the tests.

@ilanbiala @codydaig one of you to review it? a big client-side PR

Someone is looking to this PR?

Yes. Rebase, and I'll start reviewing & testing.

@mleanos check now (:

@itelo I pulled this down & tested. Didn't notice any issues, other than the missing () in a few places, where I commented. Once I fixed those locally, everything seemed to function as expected.
Overall, this looks really good. Awesome job! Can someone else do a review here? Quite a bit of code, so I could have missed something.

@mleanos i re-checked everything and discover bugs, i already fixed them...

@meanjs/contributors More eyes on this?
I haven't tested since the issues were taken care of, but I plan to in the next couple of days.

LGTM.

I just pulled this down again, and tested. Everything seems good to me. Didn't notice any issues.
I think this is ready. I'll try to merge soon, pending one or two more LGTM's.

Yep, you can merge.

@itelo This is a huge huge help. Thanks! It's nice to have the style-guide here now :)


[Watson][ID]PRIVILEGED_INSTRUCTION_c0000096_MrmCoreR.dll! Microsoft :: Resources :: WindowsDisplayLanguageProvider :: CreateInstance

Generated issue from Watson
Watson Link:  https://watsonportal.microsoft.com/Failure?FailureSearchText=9ba7706a-9bd4-18c2-45c3-cda83b54c496
ADO Link: https://microsoft.visualstudio.com/DefaultCollection/OS/_workitems#id=29149953&triage=true&fullScreen=true&_a=edit
Process: powerlauncher.exe,
Module: mrmcorer.dll v10.0.19041.388

Moving out based on hit count:

1
0.18 %

No hits in the past 30 days


Startx displayManager doesn't pass xserverArgs to X

Describe the bug
A clear and concise description of what the bug is.
When you use the startx display manager and try to use xserver options like autoRepeatDelay, they do not get passed on to the X executable (displayManagers are expected to do that).
To Reproduce
Steps to reproduce the behavior:

Set an xserver option like autoRepeatDelay
Use the startx displayManager
Notice there's no effect

Expected behavior
A clear and concise description of what you expected to happen.
It should apply the settings to the X server
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
If you had the same issue I did and want a quick fix, put your desired args in ~/.xserverrc.
Xinit has a way for specifying the flags system-wide via the xserverrc which is located in /etc/X11/xinit/xserverrc on a normal Freedesktop system.
We are not on such a system though, by looking at the strace of startx I found out that it tries to read the config from ${pkgs.xorg.xinit}/etc/X11/xinit/xserverrc which doesn't exist.
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
 - system: `"x86_64-linux"`
 - host os: `Linux 4.19.102, NixOS, 19.09.2070.b9cb3b2fb2f (Loris)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.3.2`
 - channels(root): `"nixos-19.09.2070.b9cb3b2fb2f"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute:
# a list of nixos modules affected by the problem
module:
  - services.xserver.dislpayManager.startx

pinging creator of displayManager.startx: @xeji

I'm using displayManager.startx = enable and I use options to startx. BUT, I don't expect them to be embedded in the file $(which startx). Which makes sense IMO, because that's the whole point of using this "display manager" - you handle it your self. #80272 strives to fix your issue here but personally I see no need for a change.

I don't expect them to be embedded in the file $(which startx)

They wouldn't be, the issue here is that Nixpkgs's xinit doesn't provide a system xserverrc which the system could use to set the system-wide xserver args.
/etc/X11/xinit/xserverrc exists on any normal distro but for us it's /nix/store/$hash-xinit-$ver/etc/X11/xinit/xserverrc which isn't particularly mutable and doesn't even exist by default.
This has nothing to do with the startx script.

that's the whole point of using this "display manager" - you handle it your self

If $HOME/.xserverrc exists, it preceeds any system-wide config (just like $HOME/.xinitrc); if you have a custom xserverrc to handle xserver args, nothing changes for you.

Now that you mention it though, modifying the startx script slightly is much cleaner than what I did.
Not the server args though, just the sysserverrc variable.

I'm experiencing a potentially related issue @xeji @Atemu?
When using the default display manager, gpg does launch a X pinentry dialog. If I use startx it does use a curses pinentry, and it shouldn't.
I have narrowed it down to startx, but I haven't found which environment variable is responsible for this.

When using the default display manager, gpg does launch a X pinentry dialog. If I use startx it does use a curses pinentry, and it shouldn't.

Depending on your configuration changes that might be due to this logic of the NixOS module (which is a bit flawed as it's only an approximation).

@primeos Thanks. I don't use a desktop manager. I simply have xserver.enable = true and xserver.windowManager.stumpwm.enable = true.
With those 2 options, everything is fine and I get the expected X pinentry. I guess the GTK3 flavor.
When I also set xserver.displayManager.startx.enable = true in addition to those 2 options, I no longer get an X pinentry.
Do you think the logic of gnupg you pointed to is behind this issue? I would naively think xserverCfg = config.services.xserver should not change by enabling startx.

@primeos I have checked both NixOS configurations, with xserver.displayManager.startx.enable = true and false.
Both instantiate the same gpg-agent calling the same pinentry i.e, the corresponding gnupg and pinentry programs have identical hashes in the Nix store.
Unless I'm missing something obvious, it looks like a problem related to startx and the way it configures X at runtime.

Sorry for the multiple posts, I actually found the bug. It's an upstream issue in startx. They unset DBUS_SESSION_BUS_ADDRESS within startx and this is problematic.
Arch Linux patches startx to remove this line and pinentry runs fine instantiating the X dialog and not falling back to ncurses.

Well done @solna86. I was always curios why did I have to set it in my .xinitrc while back on Arch I didn't need to. :clap: Thanks a lot!

@doronbehar Thanks. That's one issue, but there are multiple issues within the startx script provided by upstream leading to the issue we are experiencing. I've detailed them in a new open issue:
https://github.com/NixOS/nixpkgs/issues/80198#issuecomment-665927307


WIP m4: propagate native dependency

Motivation for this change
m4 was propagated as non-native dependency. This caused native builds to build fine, but cross to fail because of a missing m4.
Should we propagate m4 to begin with? If so, which one, or both?
Replaces https://github.com/NixOS/nixpkgs/pull/108044.
Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Note this now fails because of missing m4.
I recall the discussion once that packages that propagate and are used natively, would have their propagated dependencies be added as native.

Main issue resolved with bf46afde6b22942ea605983f66ee23038986ba07

I recall the discussion once that packages that propagate and are used natively, would have their propagated dependencies be added as native.

That is true.


JS Can not auto import function

VSCode Version: 1.40.1
OS Version: Mac OS 10.15.1

Steps to Reproduce:

When I wrote some function which export from other files
The function can be sensed, but cannot sense the file path which in.
Log Error:

[2019-11-18 20:06:33.780] [exthost] [error] [vscode.typescript-language-features] provider FAILED
[2019-11-18 20:06:33.780] [exthost] [error] Error: <semantic> TypeScript Server Error (3.6.3)
Debug Failure.
Error: Debug Failure.
    at Object.assertDefined (tsserver.js:2101:24)
    at getDefaultExportInfoWorker (tsserver.js:118907:80)
    at getDefaultLikeExportInfo (tsserver.js:118867:24)
    at tsserver.js:118661:35
    at forEachExternalModule (tsserver.js:119036:21)
    at getAllReExportingModules (tsserver.js:118656:13)
    at Object.getImportCompletionAction (tsserver.js:118642:31)
    at getCompletionEntryCodeActionsAndSourceDisplay (tsserver.js:102585:33)
    at Object.getCompletionEntryDetails (tsserver.js:102549:30)
    at Object.getCompletionEntryDetails (tsserver.js:125564:35)
    at tsserver.js:134771:57
    at Object.mapDefined (tsserver.js:680:30)
    at IOSession.Session.getCompletionEntryDetails (tsserver.js:134769:33)
    at Session.handlers.ts.createMapFromTemplate._a.<computed> (tsserver.js:133732:61)
    at tsserver.js:135256:88
    at IOSession.Session.executeWithRequestId (tsserver.js:135247:28)
    at IOSession.Session.executeCommand (tsserver.js:135256:33)
    at IOSession.Session.onMessage (tsserver.js:135279:35)
    at Interface.<anonymous> (tsserver.js:136594:27)
    at Interface.emit (events.js:200:13)
    at Interface._onLine (readline.js:314:10)
    at Interface._normalWrite (readline.js:459:12)
    at Socket.ondata (readline.js:170:10)
    at Socket.emit (events.js:200:13)
    at addChunk (_stream_readable.js:294:12)
    at readableAddChunk (_stream_readable.js:275:11)
    at Socket.Readable.push (_stream_readable.js:210:10)
    at Pipe.onStreamRead (internal/stream_base_commons.js:166:17)
	at Function.create (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/typescript-language-features/dist/extension.js:53:63732)
	at h.dispatchResponse (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/typescript-language-features/dist/extension.js:53:56670)
	at h.dispatchMessage (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/typescript-language-features/dist/extension.js:53:55568)
	at /Applications/Visual Studio Code.app/Contents/Resources/app/extensions/typescript-language-features/dist/extension.js:53:55044
	at l.fire (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:47:207)
	at t.Reader.onLengthData (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/typescript-language-features/dist/extension.js:53:61946)
	at Socket.<anonymous> (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/typescript-language-features/dist/extension.js:53:61594)
	at Socket.emit (events.js:200:13)
	at addChunk (_stream_readable.js:294:12)
	at readableAddChunk (_stream_readable.js:275:11)
	at Socket.Readable.push (_stream_readable.js:210:10)
	at Pipe.onStreamRead (internal/stream_base_commons.js:166:17)

Does this issue occur when all extensions are disabled?: Yes

I've tried all of these methods.

Does this reproduce in the latest VS Code insiders build with all extensions disabled?

@mjbvz Yes, I use the version 1.40.1 of VS Code which had disabled all extensions.
Last night, I config exclude in jsconfig.json, I found  that after a folder excluded, problem is ok.
If TS Server can ignore the error and not crashed, or tell me which file occurred.

@mjbvz I have found the file which occurred this problem. Because it import a property from a file which didn't have the property. Could we ignore this problem. Because of the folder is a common folder which can be imported by two projects.

Can you please share some example code that demonstrates the issue?

@mjbvz Thank you for your patience.
For example:
test.js
export  {
  API
} from './Local';

a.js
import { ABC } from './test.js';
export default ABC.funcTest;

In fact, we knew that test.js doesn't have "ABC". In this case, the problem showed up.

I can't reproduce any errors using the current VS code insiders build (1.41)
Can you please test your example again on the insiders build to confirm you still see the problem.


Fix mypy errors attributed to pytorch_lightning.trainer.connectors.data_connector.py

What does this PR do?

Fix mypy errors attributed to pytorch_lightning.trainer.connectors.data_connector.py for issue #13445
Does your PR introduce any breaking changes? If yes, please list them.

Before submitting

[x] Was this discussed/approved via a GitHub issue? (not for typos and docs)
[x] Did you read the contributor guideline, Pull Request section?
[x] Did you make sure your PR does only one thing, instead of bundling different changes together?
[x] Did you make sure to update the documentation with your changes? (if necessary)
[x] Did you write any new necessary tests? (not for typos and docs)
[x] Did you verify new and existing tests pass locally with your changes?
[x] Did you list all the breaking changes introduced by this pull request?
[x] Did you update the CHANGELOG? (not for typos, docs, test updates, or minor internal changes/refactors)

PR review
Anyone in the community is welcome to review the PR.
Before you start reviewing, make sure you have read the review guidelines. In short, see the following bullet-list:

[x] Is this pull request ready for review? (if not, please submit in draft mode)
[x] Check that all items from Before submitting are resolved
[x] Make sure the title is self-explanatory and the description concisely explains the PR
[x] Add labels and milestones (and optionally projects) to the PR so it can be classified

messed up somewhere :p
will check tomorrow!

apologies, I'm no longer able to keep this PR up to date.

@JustinGoheen, we're sorry to hear that. @rohitgr7, are you gonna push it over the finish line or should I? I noticed you started pushing some commits :zap:

@otaj it's done. Any things else needs to be done here? The CI is blocking the merge for now

@rohitgr7, awesome, thank you! :tada:. I guess we just have to wait on codeowners and CI


[feat][add link to the logo]

Would you like to have a new feature? Please describe.
add a hyperlink to the logo, to send the user to the home page;
How would this feature be beneficial for the project

Yes, it will improve the SEO of the website.

A user often clicked on a site logo to get to your site, so it is consistent and makes perfect sense for any click on the same logo to take you back to that same entry point.

Additional context
No response

can i work on it?

I'm working on it.

Good to hear


HVAC Component Set Point Display and Manipulation Issues

Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (hass --version):
0.20.2
Python release (python3 --version):
3.4.2
Component/platform:
hvac/zwave
Description of problem:
While using a Trane XR524 ZWave thermostat the HVAC component in the UI has a single target temperature slider, which seems locked to "30".
Each mode generates a separate "Thermostat" device which is expected, however the "Target Temperature" in each instance only manipulates the target_temp_low value which is used for heating and there is no UI element to manipulate the target_temp_high set point which is used for cooling.
Expected:
The HVAC component should have two sliders, one that adjusts target_temp_low and another that adjusts target_temp_high.
Each of the thermostat components should manipulate the set point that corresponds to their mode.  For example the "Cooling" set points should manipulate the target_temp_high value and the "Heating" set points should manipulate the target_temp_low value.
Additional info:
Device State Information
{
  "current_operation": "Cool",
  "current_temperature": 76,
  "fan": "on",
  "friendly_name": "Trane Model TZEMT524AA21MA Cooling 1",
  "max_temp": 95,
  "min_temp": 45,
  "node_id": 4,
  "target_temp_high": 68,
  "target_temp_low": 68,
  "temperature": 68,
  "unit_of_measurement": "°F"
}

zwcfg_0x.xml Content of Interest
<CommandClass id="67" name="COMMAND_CLASS_THERMOSTAT_SETPOINT" version="1" request_flags="4" innif="true" base="0">
                                <Instance index="1" />
                                <Value type="decimal" genre="user" instance="1" index="1" label="Heating 1" units="F" read_only="false" write_only="false" verif
y_changes="false" poll_intensity="0" min="0" max="0" value="67" />
                                <Value type="decimal" genre="user" instance="1" index="2" label="Cooling 1" units="F" read_only="false" write_only="false" verif
y_changes="false" poll_intensity="0" min="0" max="0" value="75" />
                                <Value type="decimal" genre="user" instance="1" index="11" label="Heating Econ" units="F" read_only="false" write_only="false" v
erify_changes="false" poll_intensity="0" min="0" max="0" value="68" />
                                <Value type="decimal" genre="user" instance="1" index="12" label="Cooling Econ" units="F" read_only="false" write_only="false" v
erify_changes="false" poll_intensity="0" min="0" max="0" value="79" />
                        </CommandClass>

Screenshots:

If more information is necessary, please let me know!

Not really sure what is going on here. The unit of measurement is correct, but the slider looks like it is stuck in degrees Celcius.

Maybe I think I found the issue. We use a convert function to display temperatures, but it looks like that does not work with the slider temp. Will try to change that.

I will manually "patch" my existing installation with your changes and report back on what I find!

I've fixed the thermostat issue: https://github.com/srirams/home-assistant/commit/096f57f7e801fd73a1550ae702fbc4c702149dd9
I don't know how to select just this commit for a pull request, unfortunately.
@turbokongen : I'm having an issue with the fan mode displaying a graph instead of a bar...

Also is there any intention to track the operation state (idle or running)? I know the component does that, but it is not exposed in the front end. It would be useful to see how long the HVAC runs (per day, etc), also useful to know when to change the air filter (after 300 hrs, etc).
The nest component adds a binary sensor for this, which we could also do, but it might be better integrated here.

I have also that problem with it showing graph instead of operation mode.
Not sure what is going on there. I have tried deleting the database, but
still shows graph. For the thermostat fix, I think you can do a cherry pick
with git command (Google it)  and get a new branch for your pull request.
Have you tried the fix I have made for the hvac regarding temp stuck at 30?
4. jun. 2016 19:57 skrev "srirams"<EMAIL_ADDRESS>
I've fixed the thermostat issue: srirams@096f57f
https://github.com/srirams/home-assistant/commit/096f57f7e801fd73a1550ae702fbc4c702149dd9
I don't know how to select just this commit for a pull request,
unfortunately.
@turbokongen https://github.com/turbokongen : I'm having an issue with
the fan mode displaying a graph instead of a bar...
[image: trane]
https://cloud.githubusercontent.com/assets/638940/15801206/18cc26bc-2a53-11e6-9e4b-b550ae2117bc.png
Also is there any intention to track the operation state (idle or
running)? I know the component does that, but it is not exposed in the
front end. It would be useful to see how long the HVAC runs (per day, etc),
also useful to know when to change the air filter (after 300 hrs, etc).
The nest component adds a binary sensor for this, which we could also do,
but it might be better integrated here.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/home-assistant/issues/2189#issuecomment-223769179,
or mute the thread
https://github.com/notifications/unsubscribe/AP2koOpTxmG7QA8es44nmS0GYybkLFpYks5qIbw1gaJpZM4IrMQo
.

thanks, I've made a pull request. Your fix for the temperature slider works over here!


Upgrade appengine-maven-plugin to 0.1.2

As noted in GoogleCloudPlatform/jetty-runtime/pull/17 a new version of the appengine-maven-plugin version has been released.
We should start to use it.

Obsolete.


cannot enable plugin , do not have a conda environment

Hi
Is conda environment necessary for enabling the godot plugin ? I am unable to enable the plugin in godot. I installed SOFA on system and I pass sofapython3 root and python3 path every time to run a scene description script in runSofa. I tried to install it in a conda environment, but my system keeps crashing and I didnt pursue the option further as sofa was comfortably running in system without conda. Kindly let me know if there is a fix for this

Hi @saketh2002 ,
you technically do not need conda, but I highly recommend it, because you need sofa_env for sofa_godot to work.
What type of system are you on? Ubuntu 22.04?
Cheers,
Paul

I am currently running sofa_env scipts in Ubuntu 20.08 system. I use ./runSofa for running the scene description files. I can also run the RL training files on my system without any issues. I want to create a custom environment using godot, as I found it comparatively easier compared to writing the code from scratch. But somehow the plugin is not being loaded in godot. Is the python version a problem ? I am currently running my system in python 3.8

Hi @saketh2002 ,
that sounds like similar problem to https://github.com/ScheiklP/sofa_godot/issues/2
Could you read through that issue and let me know, whether that also works for you?
Cheers,
Paul

Hi @ScheiklP ,
Like I mentioned before, my conda keeps crashing when activated, hence I had to resort to using system for running sofa_env and sofa_zoo files (which are working properly, when I export environment variables to the terminal - sofa root, python path, sofa python3 root). It would be great if you could provide me with an alternative to conda

Hi @saketh2002 ,
did you also make sure that the commits between sofa_godot and sofa_env match?
That was ultimately the problem in https://github.com/ScheiklP/sofa_godot/issues/2
Cheers,
Paul

I am actually not sure.
Maybe @chhas could help us with that?

@ScheiklP, looks like upon release we changed the naming and must have forgotten to adapt the file paths 😅
@saketh2002 I think renaming the plugin folder from sofa_godot to sofa_godot_plugin (see screenshot below) should suffice for the plugin to be loaded.
However, to use this plugin without a conda environment adaptation of sofa_python/sofa_python_root.gd is required.

@chhas Thanks for the help. Just a small thing though. I am not able to visualize the nodes, even though when the generated code using terminal, I can see them in sofa perfectly. I sense my my conda bin might be the culprit. What should I put in the path of conda bin as I do not have the conda environment ?

@saketh2002, glad to hear that sofa_godot is working for you now.
You're right, Godot does not support importing *.stl files.
You can use an external tool like MeshLab for file conversion.
I also found an STL Importer in the asset library, but I never tested it and don't know if it will work with sofa_godot.

@chhas  Yeah I am using meshlab. I did try stl plugins but it's just too much effort. Hence I am continuing the work in obj files. Thanks for all the help!

Thanks @chhas :)