kaggle api returns 401 - Unauthorized

I can't download kaggle data via kaggle api, either on local and on google colab.
I can download data on kaggle GUI, which means I successfully enrolled in the competition.
I followed the procedure on https://github.com/Kaggle/kaggle-api to use kaggle api.
Here are information on my environment.
ls /Users/.kaggle/
# ls /Users/.kaggle/
# kaggle.json

ls -l /Users/.kaggle/
# total 8
# -rw-r--r--@ 1 root  admin  64  6 26 18:59 kaggle.json

kaggle competitions list
# 401 - Unauthorized

kaggle competitions download -c global-wheat-detection
# 401 - Unauthorized

pip show kaggle
# Name: kaggle
# Version: 1.5.6
# Summary: Kaggle API
# Home-page: https://github.com/Kaggle/kaggle-api
# Author: Kaggle
# Author-email<EMAIL_ADDRESS># License: Apache 2.0
# Location: /Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages
# Requires: python-dateutil, requests, python-slugify, six, tqdm, certifi, urllib3
# Required-by:

I thought the api token was not made correctly, so I made them all expire and made a new token again, but it did not work.
I appreciate if anyone help me out.

I've also run into this issue!

I ran into the same problem, but after creating a new Kaggle Token, the problem was fixed!

Ran into this problem as well, even when creating a new Kaggle Token and/or expiring all tokens before I'm still getting 401 Unauthorized.

I overcame this issue by deleteing the kagge.json file and replacing it with a new one downloaded from kaggle. Its the file that goes exacty at root/.kaggle/kaggle.json

Thank you all. I resolved this issue with you all's process.

I overcome this problem by creating a new API token and then replaced that with the older one.

issue resolved for me when i took new api token and expired all previous ones and downloaded json file again from kaggle by deleting old json file. It works

I had uploaded the JSON file into colab already while working, so even after creating a new token since I forgot to clear all the outputs from the kernel it was still showing an error. If anyone's working in google colab they should do a factory reset before uploading a new JSON file.

Hi. I ran into the same issue while following this guideline in google colab:
https://www.kaggle.com/general/74235
I tried @Chizuchizu's tip, and it worked.

Factory reset runtime
Expire and redownload a new API.

Thanks everyone!

Same issue, but I also fixed it by creating a new API token!
For me, I think the issue was that I clicked "Expire" and "Create" too close to each other, so it may have created the new API token first then expired it. So wait until the token expiration completes before creating a new token.

You can check if the following in ~ / .bashrc are the same as kaggle.json
export KAGGLE_USERNAME=datadinosaur
export KAGGLE_KEY=xxxxxxxxxxxxxx

I still have this problem , please help me

If your are on a jupyter instance: For me it helped to restart the kernel after updating the API Key.

So why is this closed? The code is definitely broken. If Kaggle cannot generate tokens, or have problems with their request validation or whatever else the problem is, they need to know about it / fix it.
Why close this issue if nothing was fixed?

Facing this issue here as well.
Tried to expire the tokens and run it (saved the json in ~/.kaggle/kaggle.json & also tried to do in bashrc with the export command + source command)
Still no luck. Suprising.

What worked for me was creating a token without expiring the old one(s). Based on the toast notifications in the Kaggle web app, it looked like clicking "Expire API Token" followed by "Create New API Token" actually resulted in the new token getting created and then immediately being expired. When I clicked "Create" without first "Expire", the newly generated token worked as expected.

I ran into the same problem today.@bi1yeu tip worked for me.Thank you.

issue resolved for me when i took new api token and expired all previous ones and downloaded json file again from kaggle by deleting old json file. It works

Thanks  a lot man, it  worked!!

Okay, strangely enough, it started to work, my bad.
FYI, try the EXPORT Command, it will precendence over the kaggle.json file. This was how it started to work in mine. Thanks

how did u apply EXPORT, can you write th code for me

Same problem here.
I repeat expire all token and then create new token but always 401 unauthorized...

So, do check your file manually as well. Which is placed at ~/kaggle/kaggle.json. Quite often the export commands don't update it.

how did u apply EXPORT, can you write th code for me

It's a Linux command to create a variable and assign it a value

After renewing your API make sure you're code is the same as below.
! mkdir ~/.kaggle ! cp kaggle.json ~/.kaggle/kaggle.json ! chmod 600 ~/.kaggle/kaggle.json ! kaggle datasets list

I am facing the same issue (ApiException: (401)) while downloading the dataset from Kaggle
I gave the right credentials but still it is showing the same issue

Ich habe das gleiche Problem (ApiException: (401)) beim Herunterladen des Datensatzes von Kaggle . Ich habe die richtigen Anmeldeinformationen angegeben, aber es zeigt immer noch das gleiche Problem

Vorher war alles in Ordnung. Nur seit heute habe ich das gleiche Problem wie du.

All solutions described above don't work. The only solution is to manually download. Not sure why kaggle can't fix this issue:
401 - Unauthorized

I finally resolved this problem by running sudo kaggle ... (after KAGGLE_USERNAME is set). I think it is because I am not using the admin account and chmod 600 only gives permission to the admin.

I overcame this issue by deleteing the kagge.json file and replacing it with a new one downloaded from kaggle. Its the file that goes exacty at root/.kaggle/kaggle.json

yes it worked!

In my case the issue was how kaggle cli was installed.
Saw this error after running:
pip install kaggle
but fixed after running:
pip uninstall kaggle
pip install --user kaggle
(restart shell)
So the issue was actually which user/where the home directory was.

I overcame this issue by deleteing the kagge.json file and replacing it with a new one downloaded from kaggle. Its the file that goes exacty at root/.kaggle/kaggle.json

I fixed my error with your suggestion thank you for helping the community

hi everyone. i have my .kaggle directory with kaggle.json file in it. there is no syntax error with the key or anything else. i expired tokens and replace it. however problem persisted.
resolved 401 - Unauthorized issue with the following:
mkdir ~/.kaggle
cp command requires both a source file and a target location. In your command, you've only specified the source file (/Users/username/directory/.kaggle/kaggle.json). You also need to provide the destination where the file should be copied to.
cp /Users/yourusername/Downloads/kaggle.json ~/.kaggle/kaggle.json
kaggle datasets download -d <dataset_identifier>

I fix by reopen the terminal


Resurrection of Sitobolium Desv. (Dennstaedtiaceae) [PASSED]

Name of taxon
Sitobolium Desv.
Rank of taxon
Genus
Approximate number of species affected
five. Sitobolium appendiculatum (Wall. ex Hook.) L.A.Triana & Sundue, Sitobolium hirsutum (Sw.) L.A.Triana & Sundue, Sitobolium punctilobulum (Michx.) Desv., Sitobolium wilfordii (T.Moore) L.A.Triana & Sundue, Sitobolium zeylanicum (Sw.) L.A.Triana & Sundue.
Description of change
Resurrection of Sitobolium Desv. (Dennstaedtiaceae)
Reason for change
This genus of ferns was resurrected by Triana-Moreno et al. (2022b) after performing a phylogeny of the subfamily Dennstaedtioideae (Dennstaedtiaceae) based on four regions of the chloroplast (rbcL coding gene, rpl16 intron, rps4 coding region along with the rps4-trnS intergenic spacer, and the trnL-F intergenic spacer). In the article the authors carried out several taxonomic changes according to the phylogenetic relationships suggested by morphological and molecular evidence and several autapomorphic states recovered through ancestral character state reconstruction.
The authors proposed a classification that recognizes four morphologically diagnosable and geographically coherent Dennstaedtioideae clades as genera: Dennstaedtia that consists of the bulk of species traditionally recognized in that genus; Mucura, which includes D. globulifera and D. bipinnata; Sitobolium, which  includes a set of north-temperate species, and Microlepia that includes the species traditionally recognized in that genus. This treatment is made possible by an associated proposal to conserve Dennstaedtia with a new type (D. cicutaria; Triana-Moreno & al., 2022a). (While it’s beyond the scope of this PPG II proposal, conservation of Dennstaedtia with a new type was necessary in order to avoid the large number of name changes that would be associated with transferring Microlepia species to Dennstaedtia and the bulk of Dennstaedtia to Patania).
Sitobolium was in use by early authors until Moore (1859) subsumed it under his concept of Dennstaedtia (Tryon & Tryon, 1980). In Triana-Moreno et al. (2022b) Sitobolium constitutes a small clade of ca. five species sister to Microlepia. The species of the genus are distinguished by their relatively small leaves that have elongate catenate hairs, epipetiolar buds, enlarged vein endings, and marginal cup-shaped sori comprised of both abaxial and adaxial indusia. The spores are verrucate with prominent ridges, except in Sitobolium appendiculatum (ex Emodiopteris) and S. wilfordii (ex Coptidipteris) in which they are tuberculate, but otherwise lack diagnostic characters to distinguish them as a distinct genus and are therefore included in Sitobolium.
Reference(s) for publication of the name
Triana-Moreno, L.A., Schwartsburd, P.B., Yañez, A., Pena, N.T.L., Kuo, L.Y., Rothfels, C. & Sundue, M. 2022a. (2892) Proposal to conserve the name Dennstaedtia (Dennstaedtiaceae) with a conserved type. Taxon 71: 688–690. https://doi.org/10.1002/tax.12756
Triana‐Moreno, L. A., Yañez, A., Kuo, L. Y., Rothfels, C. J., Pena, N. T. L., Schwartsburd, P. B., & Sundue, M. (2022b). Phylogenetic revision of Dennstaedtioideae (Dennstaedtiaceae: Polypodiales) with description of Mucura, gen. nov. TAXON 72(1): 20–46. https://doi.org/10.1002/tax.12858
List the numbers of any related issues
#4
Code of Conduct

[X] I agree to follow the PPG Code of Conduct

I support this proposal.  I am already following it in the Flora of the Southeastern US Project:  https://fsus.ncbg.unc.edu/show-taxon.php?&parentid=66186&limit=1&offset=4&taxonid=67971

Dennstaedtia (sensu Kramer & Green 1990, PPG I 2016) is polyphyletic. The new scheme provided by Triana-Moreno & al. (I participated as co-author) makes Dennstaedtia s.str. monophyletic, rescues Sitobolium, re-defines Microlepia, and created a new genus, Mucura, to accomodate two Neotropical species. All genera can be morphologically recognizable, and this new classification is monophyletic. It also minimized new combinations, since we proposed some type conservations. I strongly agree with this proposal, and that of Mucura.

This proposal was voted on during PPG Ballot 1 (voting period July 2023). A total of 65 votes were cast. There were 63 'Yes' votes (96.9%) and 2 'No' votes (3.1%). The proposal passes.

Already implemented in data, closing.


People search API does not work on SharePoint Online anymore

Target SharePoint environment
SharePoint Online
What SharePoint development model, framework, SDK or API is this about?
SharePoint REST API
Developer environment
Windows
What browser(s) / client(s) have you tested

[ ] 💥 Internet Explorer
[ ] 💥 Microsoft Edge
[ ] 💥 Google Chrome
[ ] 💥 FireFox
[ ] 💥 Safari
[ ] mobile (iOS/iPadOS)
[ ] mobile (Android)
[ ] not applicable
[ ] other (enter in the "Additional environment details" area below)

Additional environment details
any browser
Describe the bug / error
We have developed several SPFx based web parts, which retrieve user information from SharePoint User Profile Services (UPS) using search API (we have mapped some managed search properties to UPS properties)
It used to work without problem for long time, however, now none of the search queries return any results. They do not return error messages either. Just structure with 0 result rows.
We use sourceId=B09A7990-05EA-4AF9-81EF-EDFAB16C4E31
Steps to reproduce
You can try simple REST API (just search for some employee in your organization):
https://___.sharepoint.com/_api/search/query?querytext='user'&sourceid='b09a7990-05ea-4af9-81ef-edfab16c4e31'

Expected behavior
We expect people search results to be returned. As they used to.

This is a very critical issue for us as well, and it affects every one of our clients.

We have the same issue on several customers environments. Due to this issue, many of our production solutions were stopped working. We need a quick solution.
Thanks.

This could be related to https://admin.microsoft.com/#/servicehealth/:/alerts/SP709902

Same issue here affecting internal environments and all of our clients

Thanks everyone for your input on the issue. Great to see the discussion and also sharing the latest status when it was fixed. This was an unfortunate regression which has been fixed.
Closing issue as issue has been resolved.


Returning a new instance of default value for default types

Ran into this bug when working on a project using dry-structs where the same instance of a default value is given to all instances of a class. It only applies when using defaults with a value String.default('foo').
The current workaround for this is to use the callable version String.default { 'foo' }.
If this is expected behavior, I'd be happy to submit a PR to update the docs to reflect the nuance.
Use case where I ran into the issue:
require 'dry-struct'

describe 'Example' do
  module Types
    include ::Dry::Types.module
  end

  class User < ::Dry::Struct
    constructor_type :schema
    attribute :friends, ::Types::Array.default([])
  end

  it 'makes new friends' do
    user = User.new
    expect(user.friends.length).to eq 0 # passes

    user_2 = User.new
    user_2.friends << {}
    expect(user_2.friends.length).to eq 1 # passes

    # Fails here
    expect(user.friends.length).to eq 0
  end
end

The above example fails because user and user_2 share the same reference to the default value []
Failures:

  1) Example makes new friends
     Failure/Error: expect(user.friends.length).to eq 0

       expected: 0
            got: 1

       (compared using ==)
     # ./spec/example_spec.rb:24:in `block (2 levels) in <top (required)>'

It seems like Dry::Struct just delegates to the Default type for the value so I figured this was the correct spot to account for this change. I also updated the README since rake spec is not a defined task.

hm.. good catch! Just checked my project - found a couple of similar places.
#dup inside of default is kind of bad, because it's unexpected and implicit.
On other hand, it's so easy to get into this bug.
If we consider Type as set of all possible values, every value is represented by its value itself (value object) and can be considered immutable.
With this said, we expect that Dry::Types['strict.string']['foo'] == Dry::Types['strict.string']['foo']
Method .[] returns value, one from the whole set of possible values for such type. And this value is immutable.
So, one possible solution is to freeze argument given to .default.
But can't modify frozen String exception isn't clear as well, and implicit as well - we need a better way to notify programmer about this nuance.
But @tchdp's usecase is still valid, so we need to do something with it. Interesting to hear other ideas.
P.S. One more subtle bug caused by mutability

If you want to mutate default value then it shouldn't be surprising that this side effect will affect all places where this value is used.  I don't it's a good idea to expect dry-types to dup defaults "just in case".

@solnic let's think about good way to notify programmer about such nuance.
At least, describe such case in the documentation.
It'd also may make sense to add .frozen scope to dry-type, which will be an alias to .constructor(&:freeze) - having such modifier would remind a programmer about mutating problems

@Kukunin it's not a good idea to have such an implicit behavior fwiw. This caveat definitely must be described in the docs. @solnic we could issue a warning if the value passed as a default is not frozen, I'm not sure about this decision but at least we could try and see whether it works fine or not

@flash-gordon I didn't mean to freeze types by default, but just provide a neat ability to do so.
attribute :friends, ::Types::Array.default([]).frozen

Currently it's possible by
attribute :friends, ::Types::Array.default([]).constructor(&:freeze)

Sorry but we're not going to do anything special about this. Thanks for PR and discussion. Closing this.

ps. we definitely want to document this though :)

btw if anyone will program in Python, don't be surprised! :)
$ python
Python 3.6.0 (default, Feb 14 2017, 01:02:14)
[GCC 4.2.1 Compatible Apple LLVM 8.0.0 (clang-8<IP_ADDRESS>)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> def foo(a=[]):
...     a.append(1)
...     return a
...
>>> foo()
[1]
>>> foo()
[1, 1]
>>>

Thanks for taking the time to look through the issue, y'all. 👍


next: Caller api for executors

This brings the executor API into alignment w/ the Caller API that's available for schedulers

superseded by #301


add items.location.type value to aggregations

Ref: https://github.com/wellcomecollection/platform/issues/4899
We'll add this, then move the frontend over, and remove locationType.

Will this update the swagger automatically or is this one of things documented manually?

Will this update the swagger automatically or is this one of things documented manually?

Swagger isn't generated automagically, but we have tests to make sure this PR won't pass, which I have updated

Thanks @alexwlchan - sorry to leave it lingering.

Thanks @alexwlchan - sorry to leave it lingering.


Upgrade to sbt 1.9.0.

sbt 1.9.0 contains the new sbt plugin publishing mechanism. It dual-publishes sbt plugins with Ivy-style paths (invalid in Maven, although it works out when released from sbt) and valid Maven paths.
See https://github.com/sbt/sbt/issues/3410 and https://github.com/sbt/sbt/pull/7096.

sbt 1.9.0 final is now released, so this is ready for review.


s4cmd: 2.0.1 -> 2.1.0

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/s4cmd/versions.
meta.description for s4cmd is: '"Super S3 command line tool"'.

Checks done (click to expand)

built on NixOS
/nix/store/bd4fqfhiicmpij9lj5hlslxj24z2hqaq-s4cmd-2.1.0/bin/s4cmd passed the binary check.
/nix/store/bd4fqfhiicmpij9lj5hlslxj24z2hqaq-s4cmd-2.1.0/bin/.s4cmd.py-wrapped passed the binary check.
/nix/store/bd4fqfhiicmpij9lj5hlslxj24z2hqaq-s4cmd-2.1.0/bin/s4cmd.py passed the binary check.
3 of 3 passed binary check by having a zero exit code.
3 of 3 passed binary check by having the new version present in output.
found 2.1.0 with grep in /nix/store/bd4fqfhiicmpij9lj5hlslxj24z2hqaq-s4cmd-2.1.0
directory tree listing: https://gist.github.com/d95f37efb84a1d6b072eb0e03cf614fa
du listing: https://gist.github.com/e693dc6bb8443e65b627b2fa6ab03dc8

Test this build with Cachix (click to expand)

One time setup in nixpkgs Git checkout:
cachix use r-ryantm
git remote add r-ryantm https://github.com/r-ryantm/nixpkgs.git

Test this build:
git fetch r-ryantm && git checkout f58db07ca9d9b9895450d56c4477daca8bcf0954 && nix-shell --pure -I nixpkgs=. -p s4cmd

cc @bhipple for testing.

Success on x86_64-darwin (full log)
Attempted: s4cmd
Partial log (click to expand)
  The script s4cmd is installed in '/nix/store/0951lgfys0ymm43c4irgarvx22bmkcqw-s4cmd-2.1.0/bin' which is not on PATH.
  Consider adding this directory to PATH or, if you prefer to suppress this warning, use --no-warn-script-location.
Successfully installed s4cmd-2.1.0
/private/tmp/nix-build-s4cmd-2.1.0.drv-0/s4cmd-2.1.0
post-installation fixup
/nix/store/5im29qx9rni3w8l3j8i2yr22sin55kxv-cctools-binutils-darwin/bin/strip is /nix/store/5im29qx9rni3w8l3j8i2yr22sin55kxv-cctools-binutils-darwin/bin/strip
stripping (with command /nix/store/5im29qx9rni3w8l3j8i2yr22sin55kxv-cctools-binutils-darwin/bin/strip and flags -S) in /nix/store/0951lgfys0ymm43c4irgarvx22bmkcqw-s4cmd-2.1.0/lib  /nix/store/0951lgfys0ymm43c4irgarvx22bmkcqw-s4cmd-2.1.0/bin
patching script interpreter paths in /nix/store/0951lgfys0ymm43c4irgarvx22bmkcqw-s4cmd-2.1.0
wrapping `/nix/store/0951lgfys0ymm43c4irgarvx22bmkcqw-s4cmd-2.1.0/bin/s4cmd.py'...
/nix/store/0951lgfys0ymm43c4irgarvx22bmkcqw-s4cmd-2.1.0

Success on x86_64-linux (full log)
Attempted: s4cmd
Partial log (click to expand)
Successfully installed s4cmd-2.1.0
/build/s4cmd-2.1.0
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/bd4fqfhiicmpij9lj5hlslxj24z2hqaq-s4cmd-2.1.0
/nix/store/vp40my263xk32f07788srrgl59rycsna-binutils-2.30/bin/strip is /nix/store/vp40my263xk32f07788srrgl59rycsna-binutils-2.30/bin/strip
stripping (with command /nix/store/vp40my263xk32f07788srrgl59rycsna-binutils-2.30/bin/strip and flags -S) in /nix/store/bd4fqfhiicmpij9lj5hlslxj24z2hqaq-s4cmd-2.1.0/lib  /nix/store/bd4fqfhiicmpij9lj5hlslxj24z2hqaq-s4cmd-2.1.0/bin
patching script interpreter paths in /nix/store/bd4fqfhiicmpij9lj5hlslxj24z2hqaq-s4cmd-2.1.0
checking for references to /build in /nix/store/bd4fqfhiicmpij9lj5hlslxj24z2hqaq-s4cmd-2.1.0...
wrapping `/nix/store/bd4fqfhiicmpij9lj5hlslxj24z2hqaq-s4cmd-2.1.0/bin/s4cmd.py'...
/nix/store/bd4fqfhiicmpij9lj5hlslxj24z2hqaq-s4cmd-2.1.0

LGTM :+1:

Success on aarch64-linux (full log)
Attempted: s4cmd
Partial log (click to expand)
Successfully installed s4cmd-2.1.0
/build/s4cmd-2.1.0
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/5n3x2y36znhfmc57hs1l12bsdw0084a9-s4cmd-2.1.0
/nix/store/8wl4dykwswy42wxj671b6k7vk2ydxg86-binutils-2.30/bin/strip is /nix/store/8wl4dykwswy42wxj671b6k7vk2ydxg86-binutils-2.30/bin/strip
stripping (with command /nix/store/8wl4dykwswy42wxj671b6k7vk2ydxg86-binutils-2.30/bin/strip and flags -S) in /nix/store/5n3x2y36znhfmc57hs1l12bsdw0084a9-s4cmd-2.1.0/lib  /nix/store/5n3x2y36znhfmc57hs1l12bsdw0084a9-s4cmd-2.1.0/bin
patching script interpreter paths in /nix/store/5n3x2y36znhfmc57hs1l12bsdw0084a9-s4cmd-2.1.0
checking for references to /build in /nix/store/5n3x2y36znhfmc57hs1l12bsdw0084a9-s4cmd-2.1.0...
wrapping `/nix/store/5n3x2y36znhfmc57hs1l12bsdw0084a9-s4cmd-2.1.0/bin/s4cmd.py'...
/nix/store/5n3x2y36znhfmc57hs1l12bsdw0084a9-s4cmd-2.1.0


Refactoring of AppsController routes

Summary: Moved routes structure in a different commit, so it will be easier to review separate controller method implementation
JIRA issues: MARATHON-7299

I have mixed feelings :) On the one hand, I see the value in being able to focus on reviewing and negotiating routes, on the other hand, it seems like this approach compromises the atomicity of our commits?
Just a thought. I don't have an extremely strong objection :) Interested to hear what others on the team think.


Include link to withdraw page in account balance page

https://github.com/yzernik/squeakroad/pull/413


Docs: Remove duplicated amazonec2-userdata flag

Proposed changes
Remove the duplication of flag amazonec2-userdata. It's already on line 71.

Unreleased project version (optional)

Related issues (optional)

Thank you for you comment! It turned out that the last 3 rows where already in the list, so I have just removed them with 8ae775ff84ccef070c73d9b68056bc80a6575e3d
I sorted the table Environment variables and default values as well for you in d1df5337ff5eb4bc2259274fec002e460525aa80
Let me know if it's ok for you :)


Use resources to find instances in AWS util

Using tags for finding instances in groups resulted in failures as tagging is not guaranteed at deployment time, but resources are guaranteed to be created. See: https://mesosphere.atlassian.net/browse/DCOS-11009

@cmaloney This is ready for review

@cmaloney This is ready for another pass
@orsenthil @amitaekbote PTAL

@cmaloney This is ready for another review

:ship:


Broadlink sensor and switch

Description:
Finishing the work started by @skyval
https://github.com/home-assistant/home-assistant/pulls?utf8=✓&q=broadlink
Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#1485
and https://github.com/home-assistant/home-assistant.github.io/pull/1457
Example entry for configuration.yaml (if applicable):*
switch:
  platform: broadlink
  host: IP_ADDRESS
  mac: 'MAC_ADDRESS'
  switches:
    reciever:
      command_on: 'switch_packet on'
      command_off: 'switch_packet off'

Configuration variables:

host (Required): The hostname/IP address to connect to.
mac (Required):  Device mac address.
switches (Required): The array that contains all switches.

identifier (Required): Name of the command switch as slug. Multiple entries are possible.

command_on (Optional): Base64 encoded packet from RM device to take for on.
command_off (Optional): Base64 encoded packet from RM device to take for off.
optimistic (Optional): Default true: Flag that defines if switch works in optimistic mode.
friendly_name (Optional): The name used to display the switch in the frontend.

Checklist:
If user exposed functionality or configuration variables are added/changed:

[x] Documentation added/updated in home-assistant.github.io

If the code communicates with devices, web services, or third-party tools:

[x] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[x] New dependencies have been added to the REQUIREMENTS variable (example).
[x] New dependencies are only imported inside functions that use them (example).
[x] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[x] New files were added to .coveragerc.

Hi @Danielhiversen ,
I've tested both components and both work perfectly. Good work!
I have one proposal: what do you think about define the component that represents the 'hub' itself where the user setups the mac and ip address, and add a dependency from the sensor and switch components to this hub? It can simplyfy the configuration for more complex sistems (e.g: more than one RM device, not on/off commands, etc.)

Thanks for testing it.
I do not understand how that will simplify the setup. Each switch and each sensor will have an unique ip and mac address. So if you have several sensors, you have to configure one platform and one sensor for each physical sensor.

I agree with @Danielhiversen that a hub doesn't seem necessary. Unless of course we can add discovery, but even that is out of scope for the initial PR.

May I suggest to add MAX_TEMP variable to detect incorrect temperature value. Sometimes python-broadlink returns no exception, but incorrect temperature value 249.0.
We can prevent update in case of incorrect value like in patch:
https://github.com/home-assistant/home-assistant/compare/dev...Paxy:patch-2?


Selecting new drive does not recalculate storage capacity.

Reported from Discord. See thread here: https://discord.com/channels/864285291518361610/973771960502870106/973933870091210852
Issue
If the users starts subspace desktop, then selects a different drive it does not recalculate the storage of the new drive, and continues to show the space of the default drive.
Screenshots

@ozgunozerk probably should include this in next release, users are having issues with it on gemini.

Will this be fixed? looks like it was noticed a month ago. Im having the same issues. pretty major problem for all GUI users.

@js2667
We will focus on this as the next major step (version 0.7.x).
Can't give an exact date about it, but it is definitely on our list.
Also, i'd rather approach to this issue with the word implement, then fix. Because this is not a bug to be fixed. It has not been implemented yet :)

@ozgunozerk i understand but how can I farm,  only on my local drive?

Thats true. It is only supporting the drive that the OS is installed on at the moment. It may or may not work for other scenarios, they are not supported.


Replace various config files with a single config

This is the re-factor for DB-296.

Get all config settings via import from dataactcore
Remove app init scripts that prompt for config settings
Interfaces now get db names from config

There will be a subsequent PR that includes the corresponding doc changes.

@jworcestBAH or @nmonga91 ready for review

No other concerns found. Merging into dev.


remove icons as part of fixing hyperlinks

I observed the hyperlinks for the following Exercises and Extra Curriculum is not working due to icons present in the starting of the headline. Hence, removing these icons should fix the issue.
Ref -
https://dev.mrdbourke.com/tensorflow-deep-learning/08_introduction_to_nlp_in_tensorflow/#exercises
https://dev.mrdbourke.com/tensorflow-deep-learning/08_introduction_to_nlp_in_tensorflow/#extra-curriculum

Thank you for this! I've noticed emojis don't play well with file paths and links...


Support variably bathymetry in mprains.SpatialTools.Tank3D

@bchambers28 @adimako  @tridelat here's a start on what we discussed on the proteus slack channel. In any case I think this provides a way forward with your work on the soliton @bchambers28 . It seem to me that for general basin geometries it's better to define the geometry directly with the PiecewiseLinearComplexDomain.
Example script:
from proteus import Domain
from proteus.mprans import SpatialTools as st
import numpy as np

domain = Domain.PiecewiseLinearComplexDomain()
tank = st.Tank3D(domain, dim=[4., 4., 1.],bathyFunc=lambda x,y : x/5.)
tank.setSponge(x_p=1.0,x_n=1.0)#,y_p=1.0,y_n=1.0)
tank.setAbsorptionZones(dragAlpha=10,x_n=True, x_p=True)#, y_n=True, y_p=True)
st.assembleDomain(domain)

Generate test mesh with:
tetgen -Kp mesh.poly ; pv mesh.1.vtk

@cekees Just realised that my comment above does not really make sense, as the user could want to have this slope in the y direction of your example even if it affects one of the relaxation zones.

@tridelat Is this worth merging once the issues are fixed?

@bchambers28 are you using this functionality?

I am not using that branch anymore.
Thank You,
Bradley Chambers
On Tue, Jun 18, 2019, 2:22 PM Chris Kees<EMAIL_ADDRESS>wrote:

@bchambers28 https://github.com/bchambers28 are you using this
functionality?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/erdc/proteus/pull/863?email_source=notifications&email_token=AJ72OLU7MEPMIZQTJPLBHQTP3EYXDA5CNFSM4GIDRYL2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODX7WCFI#issuecomment-503275797,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJ72OLTNQUUFSNBMQCW6PELP3EYXDANCNFSM4GIDRYLQ
.


/POST returns "Checksum mismatch, please read the file again"

When I'm using /POST, and provide the checksum I received from the /GET operation, I receive an 400 status with the message 'Checksum mismatch, please read the file again'.

fixed in #22


Issue while connecting Demo app with Partner Messaging

Hello Team,
As per Partner Messaging Documentation are testing out Interaction service inbound and outbound messages with Demo app but we are stuck while setting up please advise.

We have some doubts while configs the vars to the .env file -
END_USER_CLIENT_IDENTIFIER : what should be the value for it? We tried giving some arbitrary value though.

We have installed the Partner Messaging package(created as per the instructions) in client org and now we are communicating this client org to Demo app, so the rest of the below parameters we have setup as per client org details like SF_ORG_ID, INSTACE_URL,  consumer Key, SF_SCRT_INSTANCE but while starting the localhost server we are getting below error attaching our env file screenshot for your reference, please advise what could be the reason for this error.

Env file configuration:

Thanks ,
Simran

END_USER_CLIENT_IDENTIFIER can be any id by which you identify your user uniquely. forexample phonenumber/username or any other id which you have to identify user uniquely

also if you are facing any issue in your setup. you can open investigation with salesforce so someone from our team can help take a look at your org configurations if needed.

Hi @dmadhwani , we have check setup of PMS from our end its looks good, only thing we updated .env file and starting the demo app server, then we are getting error,

Also we have raised case with salesforce FYR: please let me know if its works and we can connect today to troubleshoot if possible.
https://help.salesforce.com/s/case-view?caseId=500Hx00000W37aQIAR
Thanks..

@james-wang-sfdc is our trust hero this sprint so he should be able to help you.

Hi @james-wang-sfdc , please let me know if we can connect today as per your availabilty to troubleshoot the issue. Thanks

Hi @dmadhwani , @james-wang-sfdc please let us know if we can connect to troubleshoot or let us know with who we can connect and get advise.
Thanks!!

Hi @dmadhwani , @james-wang-sfdc any update here?

hi @simran-concret best way to reachout tosalesforce team is via opening investigation and involving support engineers. So that salesforce engineers can get all needed data, org access. cc: @dineshrohra

@simran-concret
Please verify your SF_AUTH_ENDPOINT, it should be sth like this
SF_AUTH_ENDPOINT=https://.my.salesforce.com/services/oauth2/token
so I think in your case
SF_AUTH_ENDPOINT=https://concretio-eb-dev-ed.develop.my.salesforce.com/services/oauth2/token


Implement E2E tests

As a developer, I want to run end-to-end (E2E) tests so that I can implement changes with greater assurance that modifications to the code will not unexpectedly break existing functionality.
According to this official blog post, as of Angular v12, Protractor is being deprecated and replaced by Cypress, Nightwatch, and WebdriverIO.

+1 for Cypress


Installation not very clear

Hello!
In attempting to start using your libraries, there are no formal packages, making it not possible to either pip install sphinxtr from PyPI, nor using the direct source from GitHub, as there is no setup.py package either.
These would be helpful to get the package installed and usable quickly.
Here's a reference on Python packaging: http://python-packaging-user-guide.readthedocs.io/en/latest/distributing/

Making it a package doesn't really make sense in this case. The expected way to use the project is to fork it and write your own text.

I see. That's not entirely clear from the README, but I understand.

I agree the docs could be more clear. Opening back up to update the README

The main question I have is how to incorporate this into an existing Sphinx-based documentation set.  I would love to use some of the features here, but I just don't know how to do that.

Closing some of my older open issues.


Update - Rework variants into dark/interactive

Reworks the variants into dark and interactive versions.

[x] Move variants into the new dark and interactive setup
[x] Remove references in the code to old variants setup
[x] Add settings for default dark mode
[x] Add settings for default interactive mode

This has allowed the addition of the "Default Dark Mode" setting 🎉

I've removed some old blog posts about HyperUI updates in this PR as well.


Static code analysis (part 1)

Some issues of the below types have been addressed that were identified using the Visual Studio static code analysis. Only issues that are easy and safe to fix are included in this set.

initialised variables
removed unused variables
removed unreachable code
renaming to avoid ‘hidden’ variables
prevent overflow in loop where decrementing UINT32 and checking if > 0
avoid unintentional possible dataloss by assigning large variable to small variable (change type or add explicit cast)

@rogerfraser, merging that PR before Neil had time to make that change you wanted means that line has been removed. I will add it back in and make a PR


Startup.cs not fully compatible with .NET 6 secrets

I have an issue with the following statement: "Apps migrating to 6.0 don't need to use the new minimal hosting model."
It seems as though secrets.json will not get read if you are not using the new minimal hosting model, and decide to use Startup.cs. We upgraded an app from .NET Framework 4.7.2 and the upgrade assistant upgraded to .NET 6 using Startup.cs insted of the minimal hosting model. However, configuration won't read from secrets.json.
Based on this documentation here https://docs.microsoft.com/en-us/aspnet/core/security/app-secrets?view=aspnetcore-6.0&tabs=windows:

WebApplication.CreateBuilder initializes a new instance of the WebApplicationBuilder class with preconfigured defaults. The initialized WebApplicationBuilder (builder) provides default configuration and calls AddUserSecrets when the EnvironmentName is Development

I don't see any way to call AddUserSecrets from within Startup.cs or Program.cs when using .NET 6 with Startup.cs.
Switching to the .NET 5 docs here https://docs.microsoft.com/en-us/aspnet/core/security/app-secrets?view=aspnetcore-5.0&tabs=windows I see the following:

The user secrets configuration provider registers the appropriate configuration source with the .NET Configuration API.
The user secrets configuration source is automatically added in Development mode when the project calls CreateDefaultBuilder. CreateDefaultBuilder calls AddUserSecrets when the EnvironmentName is Development:

public static IHostBuilder CreateHostBuilder(string[] args) =>
    Host.CreateDefaultBuilder(args)
        .ConfigureWebHostDefaults(webBuilder =>
        {
            webBuilder.UseStartup<Startup>();
        });

This is the code added when using the upgrade assistant.
When replacing CreateHostBuilder(args).Build().Run(); in Program.cs Main method with code that explicitly adds secrets.json as per the .NET 5 docs, the solution won't run in .NET 6:
public class Program
{
    public static void Main(string[] args)
    {
        var host = new HostBuilder()
            .ConfigureAppConfiguration((hostContext, builder) =>
            {
                // Add other providers for JSON, etc.

                if (hostContext.HostingEnvironment.IsDevelopment())
                {
                    builder.AddUserSecrets<Program>();
                }
            })
            .Build();

        host.Run();
    }
}

I've read through the migration documentation and I can't seem to find anything that addresses this issue, so I guess in the meantime I will just migrate over to using Program.cs. If these findings are correct, it would be helpful to add an annotation to the documentation that clarifies this issue. However, I assume there is a way to do this that I just can't figure out.

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

ID: 5bec61f9-7298-170d-5e12-abb27cde584e
Version Independent ID: 27a43e3f-149d-9058-f937-0eda1d6dd4f2
Content: Migrate from ASP.NET Core 5.0 to 6.0
Content Source: aspnetcore/migration/50-to-60.md
Product: aspnet-core
Technology: aspnetcore-migration
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

Access to secret manger is just part of configuration, can you get other configuration providers to work?

Thank you for contacting us. Due to a lack of activity on this discussion issue we're closing it in an effort to keep our backlog manageable. If you believe there is a concern which hasn't been addressed, please file a new issue.


Stream transfer callback is not called

In atmosphere basic, after a stream transfer initiation, the byte transfer call get the number of byte transferred but the stream completion callback is not called.

There is no error in the app logs. After the "sending stream receive" log, the app just stays idle for a long time.

@sarika01 how many bytes are you receiving ? in the log I see total file size is 2604784..Are you getting these many bytes at the receiver ?

I didn't track it. But, in the simulator I am seeing this temp file which is incomplete transfer of 46.9Mb

There is one issue of file size being transferred i.e. test_transfer of 19 bytes was successful (This is on current dev_env branch changes). Then there is other random issue (on master / published package) where one image is successfully transferred and fails for another in similar scenario (i.e. file transferred in bytes is visible but completion callback is not called).

fixed and pushed to dev_env branch

@murali-shris Issue is resolved with the latest code on dev_env branch.

bug found by Sarika in transferring multiple files is fixed in dev_env..Closing this issue.


update to swift 2

Fixes #85 by using unsafeBitcast

Thank you for doing this. I just learned there might be a way to get this to work as it was originally implemented using the as! for type casting. This would require a change to the main library to get the custom CF types registered with the swift runtime, so when I get to review this PR I will see about making that change to make it work without the unsafeBitcast() you had to add to get this to work.

Awesome! Thanks a lot for this project.
I saw on the readme that there are plans for a cocoa version, I have the option of starting a project using this library now or wait for a few more months so I'm wondering if the cocoa version is near-future or long future?

haha, the cocoa version is probably "never" as I don't see myself having a couple of free months to do work on exclusively this. There has been a cocoa implementation of this done by a third party to wrap the CF interfaces but none of that has been contributed upstream to the project yet (and I don't necessarily expect it to be). Sorry. The readme is drastically out of date and I should probably open an issue to eventually getting around to updating it to reflect the current project state.

Ok no problem I understand :)


Added backend url args for frontend container

This is no longer needed as @omehes addressed it in #510.


video demonstration

can you please upload a video on YouTube showing how to download it on your android phone
i'll like, subscribe, share etc...

Sorry, I don't want to make this too easy otherwise I'll be stuck providing tech support for the next century. If you can't follow the setup instructions this build isn't appropriate for you.
I'll keep this open for the time being because I intend to make a promo video but it's not going to be an instructional setup video.

im not a coding person so do you need a computer to do this??

 There is a very specific reason why this is all FOSS.
And anyways - I'd have to keep a mac server running just for you and that wouldn't be cheap. Maybe try asking around in your friend group? Really can't help you.


bartlett roof breachable hatch missing

on the 2nd floor, there should be one ceilling hatch, from the roof (there should be only one)
thank you guys for this amazing project!

Thanks for catching that!  Will be fixed soon.


Svelte plugin: incompatibility with svelte-kit starting from 1.0.0-next.574

Describe the bug
Context
There have been 2 recent releases of svelte-kit that causes histoire to fail:

1.0.0-next.574, in which the internal vite-plugin-svelte-kit was split into vite-plugin-sveltekit-build and vite-plugin-sveltekit-middleware in PR #7990.

1.0.0-next.576, in which the sveltekit vite plugin became async (PR #7994).

Resolution
For (1), please see this open PR that updates viteIgnorePlugins.
For (2), I'm not sure there is a way to get around automatically from @histoire/plugin-svelte side; I'm happy to help out further if someone can give me some direction. For now, here is a working workaround for me:
// vite.config.ts/js

import { sveltekit } from '@sveltejs/kit/vite';
+ import { defineConfig } from 'vite';

/** @type {import('vite').UserConfig} */
+ const config = defineConfig(async () => ({
+       // await for for the new async `sveltekit` here
+	plugins: [await sveltekit()]
+ });

export default config;

Maybe if nothing can be done, then this should be added to the documentation somewhere?
Reproduction
Please run npm run story:dev from this StackBlitz. Notice:

verify that the startup site becomes the svelte-kit app instead of histore,
if svelte-kit is reverted to 1.0.0-next.573, everything works as expected.

System Info
❯ npx envinfo --system --npmPackages '{histoire,@histoire/*,vite,@vitejs/*}' --binaries --browsers
success Install finished in 1.829s

  System:
    OS: Linux 5.0 undefined
    CPU: (4) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 16.14.2 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 7.17.0 - /usr/local/bin/npm
  npmPackages:
    @histoire/controls: 0.11.9 => 0.11.9
    @histoire/plugin-svelte: 0.11.9 => 0.11.9
    histoire: 0.11.7 => 0.11.7
    vite: ^3.2.4 => 3.2.5

(Ran from the same stackblitz above)

Used Package Manager
npm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion.
[X] The provided reproduction is a minimal reproducible example of the bug.

have you seen these fixes @bivainis ?
https://github.com/histoire-dev/histoire/pull/393#issuecomment-1351954932


Add CHANGELOG.md to hex package

Hello! 👋
This PR adds the changelog to explorer's hex package, so we can more easily understand what has changed in hex diff: https://diff.hex.pm/diff/explorer/0.7.0..0.7.1
Thanks!

:green_heart: :blue_heart: :purple_heart: :yellow_heart: :heart:


Put options for ldapquery into opts argument

Pull Request (PR) description

Move connection options for ldapquery into a hash of options to avoid having to specify a bunch of options when all that is needed is to specify something like unique LDAP server.
Example usage we have been using in production:
if $facts['puppet_environment'] in ['production','next'] {
    $ldapquery_opts = {'server' => $ldapservers['production'][0]}
  } else {
    $ldapquery_opts = {'server' => $ldapservers['test'][0]}
  }

$ldap_projects = ldapquery('(&(objectClass=oscGroup)(!(ou=ENTITLEMENT))(!(ou=SOFTWARE)))', ['cn','o','ou','status','properties'], $ldapquery_opts)

We have a single set of Puppet masters for many environments and those environments have different LDAP servers that are just test/production versions of our LDAP all using the same Puppet masters.  Rather than add a new ldapserver argument to ldapquery and having to then specify sub and base which would be extremely verbose, using an options hash allows for specifying individual overrides and then the rest come from defaults specified on master.
This would be a breaking change to this module.

@bastelfreak Any chance to get this tagged and released to forge?


Update localstack images in tests

atlassian/pipelines-awscli is deprecated and it recommends to use
amazon/aws-cli. Also, testing against localstack/localstack:1.0.4.

Fails on CI:
https://github.com/testcontainers/testcontainers-java/runs/8082354387?check_suite_focus=true#step:7:156

locally the test pass. However in ci
    java.lang.AssertionError: [Created queue has external hostname URL]
    Expecting actual:
      "http://<IP_ADDRESS>:49165/000000000000/baz"
    to contain:
      "http://localhost:49165"
        at org.testcontainers.containers.localstack.LocalstackContainerTest$WithoutNetwork.sqsTestOverBridgeNetwork(LocalstackContainerTest.java:156)

I tested with different versions here and it seems that it's failing with versions we are not testing. In the repo attached it fails for 0.14.5 and 1.0.4
See logs here

The issue starts using 0.14.3. Just reach out localstack in slack in order to get more info about this due to it only fails in GHA. didn't find anything related by reading the release notes

I think this might be related to the config of the Docker daemon on GHA and it might even be an issue regarding the assumptions of our test. However, obviously there is also some kind of change in the image itself, that triggers this behavior.


Add compatibility tests for MaskedArray

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (5ec1bd4) 100.00% compared to head (69aba2e) 100.00%.

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #529   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           24        24
  Lines         1874      1874
  Branches       268       268
=========================================
  Hits          1874      1874

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


Adding binary reader class

Adding a generic binary reader.

In general this looks sensible. Do we have any way of testing this?

Yes, there are 3 data files stored in the "data" repo I used for testing purposes: SmoothM.lfs, TrueM.lfs, data.lfs.
Those files were pushed via git-lfs. Follow the instructions in the updated README of the data repo (check the pull request).
I can add a travis config file and a test for this.

A small travis test would be great, just load and ensure the final data has the right shape.

Test is included, works locally. Travis needs a bit more sorting out due to the git-lfs --> git-fat issue as described in opesci/data.
As agreed with @ggorman earlier, this can go into master now. As soon as travis/git-lfs/git-fat is sorted out, the binreader will be tested.


Crash on Boot

When the exe is executed it causes the game launcher to open. However, when the game is launched it crashes, thank you for your time.

I need a propper error output, also what exe are you talking about?
Can you open source.py with Idle and build it there?
How to:
Windows Search > Type in Idle > open idle
Inside Idle > Click on File (top left side) > Open > select source.py from your install location > Now either go to Run and press Run Module or just press F5 > In the new window it should show the error that causes it to crash.
Respond here with the error!

Traceback (most recent call last):
File "F:\Downloads\EFT_Flea_Market_Bot-master\source.py", line 449, in
PHPSESSID = token.getToken()
File "F:\Downloads\EFT_Flea_Market_Bot-master\getToken.py", line 45, in getToken
subprocess.Popen(command_tarkov, stdout=DEVNULL, stderr=DEVNULL)
UnboundLocalError: local variable 'command_tarkov' referenced before assignment

Delete the old folder and download the new version I just published!

Traceback (most recent call last):
File "F:\Downloads\EFT_Flea_Market_Bot-master\source.py", line 449, in
PHPSESSID = token.getToken()
File "F:\Downloads\EFT_Flea_Market_Bot-master\getToken.py", line 45, in getToken
subprocess.Popen(command_tarkov, stdout=DEVNULL, stderr=DEVNULL)
UnboundLocalError: local variable 'command_tarkov' referenced before assignment

Does it work now ?

Checking now

It seems to be working now appreciate the help 😄


Will this support the /mov function that was deprecated?

Hi @Mark7even, thanks for reaching out!
Could you please elaborate on what the /mov function does? I couldn't find it in the documentation.

Hi @Mark7even, thanks for providing the context!
I see that this feature was discontinued due to data corruption concerns. If two users both move data into a container simultaneously, but some of the blobs share the same name, then one of the users will lose the original data due to it being deleted after the copy operation is complete.
Is there a particular reason why you would like to have this feature? It is currently not on our radar.

Well since blob storage is endless, the goal would be to make weekly transfers (moves) from On-premise to low-cost blob storage. I guess a copy and subsequent delete could work, but I am unsure how to do that.
For instance a scenario is data being written to a 5TB share which fills up weekly, once a week AzCopy runs and moves this data solely to blob freeing up the 5TB on-premise share.

Hi @Mark7even, thanks for providing more context!
To be clear, is more data coming in as AzCopy is running? Is that why it's hard for you to delete the files that were transferred?
@seguler what's your opinion?

@zezha-msft Not necessarily more data coming in as AzCopy is running, but the point would be to have AzCopy do a move, or a copy-delete so that only the files that were successfully transferred would be deleted. As opposed to copying the directory to blob, deleting it from on-premise manually, and then realizing the transfer failed on a couple items and they are now deleted from on-premise.

Hello @Mark7even - thanks for the feedback. For now let's keep this request open and hear what others have to say. We as the Storage team are worried about wrongfully deletion of source data, and possible data loss issues...
For now you can accomplish this yourself using an additional 'del' command for each file that is uploaded successfully.
Once AzCopy upload completes, you can get a list of succeeded file transfers using azcopy jobs show command. Here is how you can view each file that succeeded:
.\azcopy jobs show 8f925120-9bb6-b540-707e-4be86899b4ff --with-status=Success
You can for instance parse out the source files, and prepend 'DEL' and delete files one by one.. E.g.
 .\azcopy jobs show 8f925120-9bb6-b540-707e-4be86899b4ff --with-status=Success | ForEach-Object {     Write-Host "DEL " $_.Split(" ")[2]  }
If you think this is a good enough workaround, we can place this in the documentation so others can make use of it as well.

We have the exact same scenario and can't upgrade our azcopy version and have to remain on the old version that has the /mov.

Thanks @srakins for adding to this thread.
We will discuss it within the AzCopy team, but for now the best option remains the one suggested by @seguler above.

We have the exact same scenario and can't upgrade our azcopy version and have to remain on the old version that has the /mov.

Request you to vote for this feature
https://feedback.azure.com/forums/217298-storage/suggestions/37164085-azcopy-with-move-feature-from-on-premise-to-azure

The MOVE functionality is very basic and AzCopy really need to have this option.
In our case, we need to continuously transfer files from one Azure server to an on-prem server.
Except once during midnight, we cannot purge the source files, so a MOVE option would be optimal.
Have voted to request this feature back.

@rishabpoh

hey John, Just wanted to know is this added in roasmap? As feature request vote is above 190+ in Azcopy section of user voice.

It's not currently.  We'll discuss it.


Add containerd integration

Summary of changes:
Add containerd integration
Note to reviewers: the first 4 commits belong to PR #4128

test-me-please

test-me-please

test-me-please

test-me-please

+1 Nothing terribly big, but I'm not sure about the intention with the CLI option. It's like we want to support multiple runtimes, but we only store one internally. It might be better to avoid that until we're sure we'll add more (it's non-breaking to make the CLI option take multiple from taking only one)

@raybejjani I've noticed that your comments were most related with the one vs multiple clients. The flag was always intended to support multiple runtimes at the same time, and it will be. Since I don't want to break backwards compatibility I'll keep it as such, if the user uses "auto" it will automatically detect which container runtime is running.
I'll add a new PR later on to have multiple container runtimes running and every time the daemon calls pkg/workloads.Client(). there will be a call for all the runtimes connected. Does that makes sense?


Example of dispatch not working with useElmish but works using useState

@Zaid-Ajaj I have created a branch zaid showing the failing case.

@Zaid-Ajaj : that is totally working!! Thank you so much.


Suppress logging output in tests

Part of #1032
Also some gofmt noise unfortunately

I'm not sure how valuable this change is, as it'll make debugging any failure in CI difficult

Yeah, I think it might be better to go through the log messages and move some of them down a log-level, i.e. from Debug to Trace or whatever, rather than silencing them entirely.

There's no need to emit logs for tests that have passed, but it's useful for debugging failures. This approach allows tests to be re-run with the env variable set but I admit that's rather a brute force approach. I'll look at whether I can buffer logs via ConfigureTestLogging and emit on failure.
Downgrading log levels isn't very helpful. Many of the tests pass but emit noisy logs at ERROR level or similar.

Oh, I think it's only the ipfs logging that is not being diverted in ConfigureTestLogging

My take is only that any transport stuff is just brutal. I don't want to turn it off or hide! Even if we just shunt it to a file or endpoint in CI or devstack that's be valuable

Yeah, let's investigate how to make only failed tests show verbose logs. (Not showing logs for failed tests would be bad, because they're flaky, it's hard to re-run them and get the same behavior, also it's hard to set env vars in CI).
If passing tests are emitting noisy error logging, let's move the noise down to Trace level?

The current behaviour of the tests is to only output the failed test(s) - apart from a bunch of noise from system/environment.go and system/tracer.go that is outputted before we've had a chance to redirect the logging output.
A failing test does have the tendency to be very verbose, especially as some tests don't correctly use parameterised tests and so includes the output from other tests.

I mean let's start by just having people run devstack locally and seeing how brutal it is. Two birds with one stone?
CI tests are already useless now. Every failure spins until timeout which causes a totally lack of debugging information due to it running off the end of the logs - https://app.circleci.com/pipelines/github/filecoin-project/bacalhau/1753/workflows/a8cec7c3-0da7-4201-97c6-8734e651f0cb/jobs/10833/parallel-runs/0/steps/0-109

Here's an alternate implementation that configures the iipfs logging package to use zerolog. Since ConfigureTestLogging redirects logging to Go's test logger this has the effect of suppressing logs for tests that pass (unless verbose testing is requested).
Before this change, a failing test looked like:
15:27 $ go test -run TestComputeNodeResourceLimitsSuite
2022-11-07T15:28:22.692Z	ERROR	flatfs	go-ds-flatfs@v0.5.1/flatfs.go:997	could not store final value of disk usage to file, future estimates may be inaccurate
2022-11-07T15:28:23.001Z	ERROR	flatfs	go-ds-flatfs@v0.5.1/flatfs.go:997	could not store final value of disk usage to file, future estimates may be inaccurate
2022-11-07T15:28:23.284Z	ERROR	flatfs	go-ds-flatfs@v0.5.1/flatfs.go:997	could not store final value of disk usage to file, future estimates may be inaccurate
2022-11-07T15:28:23.990Z	ERROR	flatfs	go-ds-flatfs@v0.5.1/flatfs.go:997	could not store final value of disk usage to file, future estimates may be inaccurate
2022-11-07T15:28:24.530Z	ERROR	flatfs	go-ds-flatfs@v0.5.1/flatfs.go:997	could not store final value of disk usage to file, future estimates may be inaccurate
2022-11-07T15:28:24.739Z	ERROR	flatfs	go-ds-flatfs@v0.5.1/flatfs.go:997	could not store final value of disk usage to file, future estimates may be inaccurate
--- FAIL: TestComputeNodeResourceLimitsSuite (12.27s)
    --- FAIL: TestComputeNodeResourceLimitsSuite/TestJobResourceLimits (0.27s)
        resourcelimits_test.go:83:
            	Error Trace:	/home/iand/ws/cod/bacalhau/pkg/test/computenode/resourcelimits_test.go:83
            	            				/home/iand/ws/cod/bacalhau/pkg/test/computenode/resourcelimits_test.go:87
            	Error:      	Not equal:
            	            	expected: 1
            	            	actual  : 2
            	Test:       	TestComputeNodeResourceLimitsSuite/TestJobResourceLimits
FAIL
exit status 1
FAIL	github.com/filecoin-project/bacalhau/pkg/test/computenode	12.288s

After change:
15:28 $ go test -run TestComputeNodeResourceLimitsSuite
--- FAIL: TestComputeNodeResourceLimitsSuite (12.52s)
    --- FAIL: TestComputeNodeResourceLimitsSuite/TestJobResourceLimits (0.27s)
        logger.go:174: 15:28:47.472 | ??? go-ds-flatfs@v0.5.1/flatfs.go:997 > ERROR flatfs could not store final value of disk usage to file, future estimates may be inaccurate
        resourcelimits_test.go:83:
            	Error Trace:	/home/iand/ws/cod/bacalhau/pkg/test/computenode/resourcelimits_test.go:83
            	            				/home/iand/ws/cod/bacalhau/pkg/test/computenode/resourcelimits_test.go:87
            	Error:      	Not equal:
            	            	expected: 1
            	            	actual  : 2
            	Test:       	TestComputeNodeResourceLimitsSuite/TestJobResourceLimits
FAIL
exit status 1
FAIL	github.com/filecoin-project/bacalhau/pkg/test/computenode	12.534s

This looks like a good change now, thanks! Please merge

Since this was an external PR, looks like our tests didn't actually run. We have #1040 to fix that, just going to merge for now and we'll see how the test suite feels about it momentarily!

Thanks @iand - if you'd like merge permissions, please ping me on Slack :)


External redis crash fix

When specifying the redis_ip for the DockerContainerManager constructor, then connecting to Clipper an exception will be thrown similiar to the following.
    clipper_conn.start_clipper()
  File "/app/anaconda3/envs/ml-serve/lib/python3.6/site-packages/clipper_admin-develop-py3.6.egg/clipper_admin/clipper_admin.py", line 126, in start_clipper
    num_frontend_replicas)
  File "/app/anaconda3/envs/ml-serve/lib/python3.6/site-packages/clipper_admin-develop-py3.6.egg/clipper_admin/docker/docker_container_manager.py", line 246, in start_clipper
    self.connect()
  File "/app/anaconda3/envs/ml-serve/lib/python3.6/site-packages/clipper_admin-develop-py3.6.egg/clipper_admin/docker/docker_container_manager.py", line 265, in connect
    self.redis_port = all_labels[CLIPPER_DOCKER_PORT_LABELS['redis']]
KeyError: 'ai.clipper.redis.port'

The fix for this is to skip port look up and use the value of self.redis_port by replacing line 261 of clipper/clipper_admin/clipper_admin/docker/docker_container_manager.py with the following:
        if not self.external_redis:
            self.redis_port = all_labels[CLIPPER_DOCKER_PORT_LABELS['redis']]

@simon-mo Is it fixed in the current develop?

@rkooo567 I had this issue today while working with a fresh install from develop. I fixed it by simply performing a key check before the assignment. This is what I got at line 312 of DockerContainerManager:
if CLIPPER_DOCKER_PORT_LABELS['redis'] in all_labels:
    self.redis_port = all_labels[CLIPPER_DOCKER_PORT_LABELS['redis']]

By doing this the redis_port is not reassigned when an external value is passed, while still behaving normally in case it isn't.

@DNCoelho Good point. I think it's missed check. Would you please create a new PR?

@withsmilo  Done :+1:


Improve documentation

This PR improves documentation by

adding code fence (with language where relevant)
fixing spelling and/or grammar
changing wording or phrasing so it sounds more fluent
adding GitHub style alert box for better visual, like this

I have read the CLA Document and I hereby sign the CLA

recheckcla


Convert html to delta

Hello to all.
I would like to know if there is a simple way to do the reverse conversion, i.e. from Html to Delta.
Thank you very much

Sorry. I didn't see that there is already a closed issue asking the same question last month here https://github.com/VisualSystemsCorp/vsc_quill_delta_to_html/issues/4
I close the issue.


add part_of relation in CL:0000066 and in CL:0000586

Hi,

We would like to have the following relationships:

CL:0000066  epithelial cell
part_of UBERON:0000483 epithelium

CL:0000586  germ cell
part_of UBERON:0000990 reproductive system

Do you agree?
Thank you in advance,

Anne

Anne Niknejad
Bgee curator
http://bgee.unil.ch

Dept Ecology & Evolution
Biophore, UNIL-Sorge
UNIL-CH-1015 Lausanne
Switzerland

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 16 Jun 2014 at 11:09

WARNING: This issue has been automatically closed because it has not been updated in more than 3 years. Please re-open it if you still need this to be addressed – we are now getting some resources to deal with such issues.


(200) Add MAINTAINERS

@jpinsonault I didn't know who else to put on this.  Any ideas?  We can always add other people later.

I can't think of anyone else =/


PutObjectRequest is missing Timeout & ReadWriteTimeout in .net core 3.1 version of AWSSDK.S3 <IP_ADDRESS>

The Question
In the AWSSDK.S3 for .net 4.5 the Timeout & ReadWriteTimeout properties are present on PutObjectRequest. Those same properties are missing in the sdk for .net core 3.1.

Does anyone know if this is intentional or is this bug?
Environment

SDK Version: AWSSDK.S3 <IP_ADDRESS>
Package Version: AWSSDK.S3 <IP_ADDRESS>
OS Info: Windows 10
Build Environment: Visual Studio 2019
Targeted .NET Platform:  .net core 3.1

This is a :question: general question

Hi @eangelov,
Good morning.
You are correct, BCL version of some of the request objects, e.g. PutObjectRequest, provide the Timeout & ReadWriteTimeout properties which are missing in corresponding NETSTANDARD version.
For setting the Timeout & ReadWriteTimeout values, you could use AmazonS3Config object that could be configured for AmazonS3Client. The Timeouts section in https://docs.aws.amazon.com/sdk-for-net/v3/developer-guide/retries-timeouts.html provides an example. However, please note that the ReadWriteTimeout is obsolete for versions of the AWS SDK for .NET that target .NET Core. The reason is that the version of the AWS SDK for .NET that targets the portable class library (PCL) uses the HttpClient class instead of the HttpWebRequest class, and supports the Timeout property only.
The probably reason on why these properties were not removed from BCL version is to maintain backwards compatibility.
Hope this helps.
Thanks,
Ashish

Hi @eangelov,
Good morning.
You are correct, BCL version of some of the request objects, e.g. PutObjectRequest, provide the Timeout & ReadWriteTimeout properties which are missing in corresponding NETSTANDARD version.
For setting the Timeout & ReadWriteTimeout values, you could use AmazonS3Config object that could be configured for AmazonS3Client. The Timeouts section in https://docs.aws.amazon.com/sdk-for-net/v3/developer-guide/retries-timeouts.html provides an example. However, please note that the ReadWriteTimeout is obsolete for versions of the AWS SDK for .NET that target .NET Core. The reason is that the version of the AWS SDK for .NET that targets the portable class library (PCL) uses the HttpClient class instead of the HttpWebRequest class, and supports the Timeout property only.
The probably reason on why these properties were not removed from BCL version is to maintain backwards compatibility.
Hope this helps.
Thanks, Ashish

Thanks for the info.


Running fsck on extra partitions when no SD card is present

When no SD card is present for the BBB and MBM2, the partition numbers change. This PR updates the fsck calls at startup to add the additional partitions.
(Note: If there is an SD card present, so those partitions don't exist, the particular fsck commands will fail, but it won't affect the rest of the system in any way)

 Expand fsck for no-sd card case


CSS Change - reducing font-family declarations

made slight changes to the css so that I was able to reduce the amout of font-family declarations in the file

Compared main branch with css-tweaks and all looks ok.


Auth: store TokenParams for subsequent authorisations

Auth#authorise (RSA10g) Stores the AuthOptions and TokenParams arguments as defaults for subsequent authorisations

ARTAuth does not store the AuthOptions/TokenParams for subsequent authorisations.

@mattheworiordan About storing the TokenParams, should I store the timestamp field? As far as I know the timestamp should always have the time of the current request, right?

@ricardopereira that is a very good point, the timestamp field should not be stored.  I believe every other client library blindly stores the complete hash.  I will need to add an issue to all client libraries to exclude the timestamp and the nonce

Sorry, nonce is a TokenRequest field, ignore me.  However, @force@ attribute of AuthOptions should also not be stored as this would then mean every auth check would force a new authentication

@mattheworiordan Yes, I was questioning me as well about AuthOptions.force. So, I will implement it without storing timestamp and force. :+1:

See https://github.com/ably/docs/commit/f768f0db76020d945cf34974ef7d14d36113f0cd


Vectorx keeps changing locale from en-GP to en-US

Vectorx keeps changing locale from en-GP to en-US via wire-pod\chipper\jdocs.
Is there any way to prevent this? Many thanks

That’s tough. www.keriganc.com/vector-wirepod-setup doesn’t provide any type except time zone, and jdocs are robot settings. However, Wire-Pod has the ability to write jdocs. Go to wirepod console, server settings, then set language, and set your desired language.

Have the same error with DE language.

For German, try changing locale with WirePod (bot settings page) or through
VectorX initial setup.
en-GB or en-US shouldn't do any difference, as far as I know the only
natively supported locale for production bots is en-US, and you can have
fr-FR, de-DE and jp-JP on OSKR bots. VectorX provides support for italian,
spanish, french, german and (US) english, but only for its extra commands.
What changes (or what do you expect to change) when you set Vector to use
en-GB?
On Sun, Nov 19, 2023 at 12:14 PM Schattenruf @.***>
wrote:

Have the same error with DE language.
—
Reply to this email directly, view it on GitHub
https://github.com/fforchino/vectorx/issues/28#issuecomment-1817823169,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA4AIJBMSU7PMZTS2XRTNELYFHSZXAVCNFSM6AAAAAA7HBOHPGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJXHAZDGMJWHE
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

I can change to GB in Wirepod server settings, but any time a custom intent is called when using VectorX, it seems to reset it to en-US.
I assumed setting en-GB (or en_US, en_AU) would affect how commands are understood based on accent etc.
Many thanks


Refactor: Marshal

I reorganized the very large visitModelNode function (the internal logic that builds a Node struct by recursively descending into a jsonapi-annotated struct model) into a couple of abstractions:

modelFieldCursor encapsulates reflection data about each field in a model struct.
modelVisitor uses cursor method Next() to move the cursor to each field. It retains config about sideloading relations as included Nodes and provides the top level Visit() interface. Most of the field-specific code was relocated as methods of the visitor, each receives the cursor as an argument.

I don't think this is ready because I just benchmarked it and it appears to be slower than the main branch. I'll keep working on it.


Warn on case mismatch while opening a file on macOS

Fixes #23441

In my opinion this should happen on Linux too, so that projects can be cross-compatible. Godot should not allow names that only differ by case, and require names to have the same casing everywhere.

It is true that it could be possible to have the same problem on Linux (for example for a project stored on a USB key with a FAT32 filesystem).

So, should I remove the macos check so that the warning can be issued on any unix system ?

I would appreciate feedback from the Godot devs about this one.

Closing as superseded by #24860 which looks like a better option. Still, thanks for the contribution which help get closer to a good solution!


Analyze current test Flakes

We have some flakes, potentially related to UDP dependent tests (i.e. DNS specific testS)
@qabpea has some suspicions about these being related to conntrack
cc @hanamantagoudvk  was suggesting that maybe our tests lately have become more flakey

/assign @hanamantagoudvk


Capturing docker build logs in memory

Hello,
I would like to use the package but am needing to capture the stdout and stderr build logs in my context instead of outputting it to the console, is that a possibility?

Hi, is this feature being implemented now?


Can messages be good?

Having a quick look through the history of this project, it looks like messages were once a way to raise warnings or errors. The deprecation of warn though makes me think that messages could be one way to have an 'audit trail' of what has occurred to a file.
Would it be possible to add a type or level to a message so that libraries downstream, such as vfile-reporter can be a little smarter than just fatal or warning?
Or is that not the intentions of messages?

VFile only dictates fatal: true as meaning a file is no longer processable. As the fatal property is an optional boolean, it has three states: nully (null/undefined), false, or true.
No plugin/linter actually creates “positive” messages yet, so there hasn’t been any need to deal with that, but some related projects do support it.
I welcome any PR to projects to support this, or docs to include this!
Does that answer your question?

Oh I meant to close this, but feel free to comment if you don‘t agree!


'go build' takes too long and creates huge executable

What version of Go are you using (go version)?
go version go1.10.1 windows/amd64
Does this issue reproduce with the latest release?
Yes.
What operating system and processor architecture are you using (go env)?
set GOARCH=amd64
set GOBIN=
set GOEXE=.exe
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOOS=windows
set GORACE=
set GOROOT=C:\Go
set GOTMPDIR=
set GOTOOLDIR=C:\Go\pkg\tool\windows_amd64
set GCCGO=gccgo
set CC=gcc
set CXX=g++
set CGO_ENABLED=1
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -mthreads -fmessage-length=0 -fdebug-prefix-map=...
What did you do and what happened?
I'm learning Go and I decided to make a few little programs to get comfortable with the language. Usually the executables are ~1MB. But when I tried to compile the following program, the compilation took a long time and the executable was ~800MB.
https://play.golang.org/p/EK8zDu5vVQN
What did you expect to see?
I expected the executable to be ~1MB, because I tried a similar program, but without the explicit initialization of the first element of the array to 1, and it worked fine. Like the other times, the executable was ~1MB.
https://play.golang.org/p/LM9TBaQcRIo

Thanks for the report.
This is a duplicate of issue #17378 (cmd/compile: large arrays cause large binaries and toolchain errors); so I'm closing this thread in favour of the old one.


remnote: remove max-niederman as maintainer

Description of changes
Remove max-neiderman as maintainer.
Hasn't been active for over 2 years:
https://github.com/NixOS/nixpkgs/commits/nixos-unstable/pkgs/applications/misc/remnote/default.nix

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

I will include theem at https://github.com/NixOS/nixpkgs/issues/290642

P.S.: is theem merely not maintaining this package, or it is something more general?

He init'ed the package over 2 years ago. I have been sole maintainer since. Its mainly that he gets auto-added as a reviewer every time I make a PR which is really annoying.

I'm all good with this.

Much appreciated!

Can this be merged please? I have some package updates I'd like to push. Many thanks!


(fix) prevent 500 server error on a just removed folder when listing files

What is the problem that this fixes or functionality that this introduces? Does it fix any open issues?
If a folder in the workspace is being removed (in the actual filesystem, outside of OpenHands) and then in the UI the "Refresh" icon on the file explorer is clicked, an error "500 internal server error" will appear in the UI. This PR prevents this.

Give a summary of what the PR does, explaining any non-trivial design decisions
Instead of returning a 400 error from the runtime client back in case a folder no longer exists, this should just return an empty list and not error about it, which is confusing in the UI.

Other references

I'm a little bit confused by this. Is it only the case that this error would be thrown when a user just removed a folder? It seems like it also might be thrown if we call list_files on a file/directory that never existed in the first place.

Just for illustration, my workspace has these entries:

So if I'd go outside of OH and removed the folder "temp2" myself and then clicked the "Refresh" button, the UI would retrieve the error as the list_files would still think it existed and try to get the content for it, still.
And that error message is now removed.

This LGTM! Although i wonder if the file structure will also be updated on the FE side, so it will not call list file on the same folder next time?

Yes, the file explorer is updated correctly.


download data, don't download data that is already downloaded (from prior exports)

Scenario:

I download all 50 images and labels in my labelset
I label 50 more images
I download the labelset again with all 100 images. But only download the new 50 and add to the existing 50.

Possible incompatibility with feature use_name of Exporter class.
If use_name is True, then a collision check is performed until downloaded image has an unique filename.
Will implement only when use_name is False for now.

This is a good compromise.


WIP {KubernetesConfiguration} Add extension CLI

This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your PR is merged into master branch, a new PR will be created to update src/index.json automatically.
The precondition is to put your code inside this repo and upgrade the version in the PR but do not modify src/index.json.

add to S169

Is this PR ready to merge?

We are taking a couple of bug fixes that I'd want to be merged along with this.  Once I am done with those fixes, I will ping you.


Enforce Xaml indentation in EditorConfig

Description
Similar to what is currently there for C# source files, it would make Visual Studio automatically use tabs instead of the default spaces
Concerned code
All Xaml files
Gains
A more seamless contribution experience by having code automatically comply with style guidelines
Requirements
No response
Comments
No response

Do you want to do this?

Sure, I'll do it
On Fri, Feb 17, 2023, 8:15 PM Yair @.***> wrote:

Do you want to do this?
—
Reply to this email directly, view it on GitHub
https://github.com/files-community/Files/issues/11337#issuecomment-1434746466,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOJEU7X44QPVG3UZJM3WRQDWX6FIXANCNFSM6AAAAAAU7G5SHY
.
You are receiving this because you authored the thread.Message ID:
@.***>


Removed livereload.js file loading from localhost

Looks like a leftover file, shouldn't be loading anything from localhost anyway on live site.

We are probably missing a conditional in the site generator so that this is included in both dev and prod. it should ofc only be used in dev mode..
Thanks for reporting!


[Extensibility Enhancement] Retrieve Vendor details in Approval Entry's GetCustVendorDetails procedure

Hi Microsoft AL Development Team,
I would like to suggest a simple enhancement to GetCustVendorDetails procedure in table 454 "Approval Entry".
Currently, the procedure doesn't handle Vendor scenario while the parameters suggest that the Customer/Vendor No. or Name are retrieved. Here is the change:

Kind regards,
Tuan Nguyen

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 51686.


Incapsula

Hi,
Could you do the same for Incapsula?

I have no plans to add support for Incapsula or other cloud WAFs/reverse proxies at this time. It probably shouldn't be too hard to write your own version, using PyExecJS.


Kotel consumer not setting trace id correctly.

I'm using the kotel tracing plugin, and viewing in jaeger.
The consumer isn't setting the trace ID of the created span to be the trace ID created by the publisher. This means the trace is being shown as 2 separate traces in jaeger, with no way of linking the 2.
I'm passing the instrument context to the publisher as per the example.

Tagging @brunsgaard

Hi, thanks for the ping. Unfortunately do not have enough time on my hands right now to investigate this. @JamesArthurHolland, I think it would be helpful if you could provide an running example snippet of what you are experiencing. You are taking the context from record.Context in your consumer and using that context in your further execution flow?

@brunsgaard  Hi, I followed the execution in Goland debugger.
On the publisher side, the kgo.Record is getting the context set correctly.
On the consumer side, the context is not being retrieved from the record.
There are some header values set, such as "traceparent" which is correct. But the kotel plugin doesn't use this and tries to read it from the record's context.
versions used:
	github.com/twmb/franz-go v1.15.2
	github.com/twmb/franz-go/plugin/kotel v1.4.0
	go.opentelemetry.io/otel v1.18.0
	go.opentelemetry.io/otel/trace v1.18.0


GUACAMOLE-903 Improved Chinese internationalization support

@XYUU: Thank you for the contribution to improving the support for non-English languages!
Before we go further with this, you need to do a couple of things:

Open a JIRA issue for these changes.  All changes to the code must have an associated JIRA issue.
Once the JIRA issue is open, tag both the pull request and the git commit messages with the JIRA issue.  Please have a look at other pull requests to see how this is done.
Make the commit message(s) a little more descriptive of the changes being done.  The commit message should tell us something meaningful about the changes - more details than just the title of the pull request, but not so detailed as to describe the actual code changes.

Okay, I did.

Okay, I did.

@XYUU: Almost :-).  The commit messages need to be edited and tagged with this same "GUACAMOLE-903:" JIRA issue.


Unable to get Nimbus to pair

Been attempting all that i know, it wont connect when attempted from the SETTINGS windows app..it  requests a code, which i do not know..
And when i try to pair through the control panel "add device" , it seems to connect for 10seconds and then disconnects and the device disappears..
Anything i can do or am doing wrong maybe..?
Using a Dongle btw

Which controller are you using? Nimbus+ or the old nimbus?

Old Nimbus (the one with only the MENU button in the middle)

What dongle are you using? Have the same controller, and that works fine with a Belkin USB-adapter (BCM920702 Bluetooth 4.0)
Maybe you need to update its drivers?

An old MSI Bluetooth Dongle.. but i purchased a TP-link UB400 with bluetooth 4.0 two days ago and still nothing.. :/

I had to add the Nimbus by choosing the add mouse, keyboard etc option. The documentation says to choose 'other', but I couldn't get the controller to show up at all when I did that. Did you try that option?

...oh, and how about the Nimbus' firmware? Have you checked that it's up to date using the iOS app?
Just trying to come up with things to check :)

Ok so i have managed to get it connected via "Add a Device" in Devices and Printers. And then seemed to work instantly through the Bluetooth settings too after that, so thats nice. Next issue is.. button mapping isnt exactly optimal i guess? (Software has been setup and ran according to instructions and xbox 360 was initialized)  Like, it'll be a bit.. weird..  buttons are going random abit and (using this game as a prime example since i really wanted to use it for it) Forza Horizon 4 didnt even acknowledge the button presses..  When i press a button in the menu, the layout does shift to show a A button rather than "Enter" to go into the main menu, but it literally lasts half a second..

Weird. Just tried mine again for about half an hour with FarCry 3, and it works without a hitch.
I have my USB adapter connected directly to a USB 3 port on the PC - not to a hub. Hubs may in some cases be a source of error.
Another thing I just remembered. Windows has something called USB Power Management, which is used to conserve power on laptops. This -might- explain why this suddenly stops listening to inputs from your device. I use SPAD.Next's software to control some Logitech panels I have for flight simming, and they recommend switching USB Power Management off - so it's off on my rig.
Try disabling that and see what happens. Description:
https://www.windowscentral.com/how-prevent-windows-10-turning-usb-devices

The setting was already disabled and the adapter is in a USB 3 port.
Ok, so I tried a few other games... it seems to be very dependent on the how the game handles input i guess?
Forza Horizon 4 didnt work one bit. Split Second worked but there was delay in the inputs. Asphalt 8 worked flawlessly.
Not sure what to think of it..
Oh and i tried going to Controller Settings on the controller in Printers & Devices to test out inputs, it doesnt even open.. I click the button and it just closes the window.. so yeah, not sure what to do to fix it up with what i would like to run it with..

The same thing happened to me. I am using the new nimbus+, maybe because of that for me it's not working. But it should work for you. Did you check the mapping editor if everything are included?

Mapping Editor seems all good.. (Opened the config file and from what i saw, there seemed to be all the buttons in there)

I am sorry, I am unable to help. But there are thousands of apps in the app store that support controllers.

No worries mate, thanks a lot for trying to help still, greatly appreciated ^-^


IPFS Pinning Service integrated into P2WDB

In previous versions, the p2wdb-pinning-service was an external application that ran in parallel to the P2WDB. It would be triggered by a webhook and would pin any content with an app ID of p2wdb-pin-001 by sending a pinning command to the external Kubo (go-ipfs) IPFS node.
With v5 of P2WDB integrating a Helia IPFS node into the app, there is no external IPFS node. It is now more appropriate to integrate the pinning feature right into P2WDB. That's what this release does.
Pinning is turned off by default. To enable the pinning feature, set an ENABLE_PINNING environment variable to any value. When new DB entries with an app ID of ipfs-pin-001 are validated, the content the entry points to will also be downloaded and pinned by the Helia IPFS node integrated into the P2WDB.

:tada: This PR is included in version 5.1.0 :tada:
Your semantic-release bot :package::rocket:


DateTime not running in the controller

I want to work with the built-in php DateTime. I receive an error
PHP Fatal Error – yii\base\ErrorException
Class 'frontend\controllers\DateTime' not found
Code
$datetime1 = new DateTime('2009-10-11');

The most interesting works so
$datetime1 = date_create('2009-10-11');

why php built-in function does not work?

@cebe I aplogize to reopen 3 years later this issue but it (at least for me) does not work.
With or without backslash I am receiving the same error.
I am using Yii2 with advanced app.

Can you show us the code, where it's not working?

Searching on Laravel samples and forums I found I have to declare the use of DateTime on class header or declare as new DateTime\DateTime .
My code is just like
$datetime1 = new \DateTime('2009-10-11');
But a I said, thanks to some Laravel examples I could sort this.

I did use DateTime;
And finally I could use the DateTime add is commonly used.
As @cebe said before, when your are in namespace,  You must put full namespace with object name, but as this object comes directly from PHP core, maybe you can use simply with \DateTime in a common project, but in Laravel or Yii2 I am seeing you need to declare first on top.


XSS vulnerability in RichTextBox

Version information

Laravel: v5.8.35
Voyager: v1.2.7
PHP: 7.1
Database: MySQL

Description
You can put JavaScript into rich text box which then is executed in admin and frontend as well.
Steps To Reproduce
Steps to reproduce the behavior:

Create a BREAD with RichTextBox
Disable JavaScript and remove TinyMCE
Write some JS into previously hidden textarea
Save

I know, best practise is to sanitize data on output. There is tool http://htmlpurifier.org/ which does a great job. But is quite slow as does tons of checking and clearing. So maybe it would be nice to do this check before saving.

Besides HTMLPurify adding CORS would help, but it's not that easy to "retrofit".


you can get more arrays, as a treat

wait i forgot the commas

Hope you don't mind that I fixed it up :3 (after breaking it a little more!) — thank you for the additions!


Question about the priority order for handling interrupts from multiple supervisor domains

The default interrupt handling priority described in Section 6.4. And with the Note below, RDSM will clear the bit corresponding to that interrupt controller selected by msdcfg.SDICN in msdeie prior to resuming execution of the supervisor domain.
Here I have a question:
When both a "non-active supervisor domain interrupt (LSDEIP)" and an "active supervisor domain interrupt (VSEI)" occur simultaneously, why is the default to prioritize handling interrupts from other domains rather than prioritizing TVM interrupts within the current active domain?
If currently in the confidential supervisor domain, TSM needs to perform a TEERET to the VMM, leaving the scheduling decision to the VMM.
When interrupts occur in multiple supervisor domains simultaneously, if each domain prioritizes handling interrupts from other domains, could this lead to a "domain scheduling storm" where no interrupt is actually processed to completion?
Looking forward to your answer, thank you!

hi @xlxxxxxl - LSDEI is higher priority following the rule that interrupts for higher privilege level have higher priority - that said, there was a bug in that part of the spec - see PR #115   - the priority order should have been: high-priority RAS event, MEI, MSI, MTI,  LSDEI, SEI, SSI, STI, SGEI, VSEI, VSSI, VSTI, LCOFI, low-priority RAS event.
Regarding your other question - no such storm/starvation is possible since the RDSM has higher priority and can choose any scheduling policy. The confidential domain scenario you mentioned is one policy model where the VMM controls the scheduling, but other models are also possible.

Hi @rsahita, thank you for your answer. Also please allow me to ask one more question.
The newly introduced mip.LSDEI and sip.LSDEI in smmtt spec do allow a flexible choice of handling interrupts from inactive SDs in either M-mode or S-mode. This capability comes from instantiating multiple physical IMSICs for each SD in each hart, thereby providing independent S and VS interrupt files resources for each SD.
But why are these function points not reflected in the CoVE specification? The definition of COVI's ABI in CoVE does not seem to mention the use of mip.LSDEI, sip.LSDEI, and the independent VS interrupt files that each SD has because of multiple IMSICs, as well as the related process processing.
The description I've seen in CoVE is that it looks like all SDs are using one set of VS interrupt files. VMM manages and distributes them between SDs. The guest interrupt files are converted between the non-confidential SD and the confidential SD (using MPT page table isolation) through the tvm_vhart_imsic_bind and tvm_vhart_imsic_unbind interfaces, and also migrates the interrupt status between the MRIF and the guest interrupt file. It does not reflect the use of the VS interrupt file resources in different IMSIC that are independently provided for each domain.
I'm confused as to how the functionality of mip.LSDEI and sip.LSDEI, as well as the VS interrupt file resources in multiple physical IMSICs, will ultimately be applied to resolve interrupt handling for active and inactive SDs.
Please help solve my confusion, thank you!

When considering the support for setting different numbers of VS interrupt files for different Supervisor Domians, I was confused by the definition and implementation of some parameters (e.g. GEILEN, VGEIN, hgeie, and hgeip)
The GEILEN parameter is described in the specification as follows
For any one physical hart, the maximum number of virtual harts that may directly receive guest external interrupts is limited by GEILEN.
This parameter appears to describe the total number of VS interrupt files for a physical hart(regardless of how many S-domains are running on that physical hart);
In the SMMTT specification, VGEIN is described as follows
The hstatus. VGEIN selects a guest interrupt file in the selected IMSIC and vsiselect and vstopei CSRs operate on the registers of the corresponding guest interrupt file in the selected IMSIC.
VGEIN selects a VS interrupt file in an IMSIC on a physical hart. But for the first VS interrupt file of a certain domain, it may actually be the nth VS interrupt file on this physical hart. Should the VGEIN be assigned to the actual VS interrupt file number instead of the VS interrupt file number from a certain domain perspective?
My question is, should the parameters related to VS interrupt files (e.g. GEILEN, VGEIN, HGEIE, and hgeip) be assigned from the perspective of the domain or from the perspective of the physical hart under the smmtt specification?
Many Thanks！

@jimingchen111 hi, so VGEIN etc. is assigned from the perspective of the selected IMSIC (which is assigned to an SD and is in turn selected based on the interrupt controller identified by the SDICN).

PR #115 merged.


Ability to add Orderlist

Ability for user to add OL tag dynamically on creative board.

This issue has been resolved via this commit.


Move detailed descriptions out of JSON schema

It's a good idea to put the full description of the spec into the JSON schema yaml file, but I think it has some limitations. It makes it more difficult to cross reference sections, and the formatting we can do is pretty limited. Also, (and the clincher for me) it results in pretty much unreadable error messages coming out of jsonschema.validate(), which writes out the full schema text and you therefore get pages of text you need to scroll through.
So, I suggest we structure the schema description as an RST file, and put in terse descriptions with URL section links to the full documentation in the schema text. It should be easy enough to make stable URLs for these, now?

Yeah, that sounds like a good plan.

Yeah, that sounds like a good plan.

I'm going to make a pass at this now @grahamgower, in case you were planning on doing stuff in here.

Thanks Jerome, I've been putting this off. :)

Closed in #80