Fix service account typo for TSI ALTS

Fix service account macro typo for TSI ALTS.
Did a search in the repo and did not find any hardcoded strings "service_accout", so it's probably safe to merge this.

Thank you for your pull request. Before we can look at your contribution, we need to ensure all contributors are covered by a Contributor License Agreement.
After the following items are addressed, please respond with a new comment here, and the automated system will re-verify.

User @pitlv2109 isn't covered by a CLA. They will need to complete the form at https://identity.linuxfoundation.org/projects/cncf

Regards,
CLA GitHub bot

Thank you for your pull request. Before we can look at your contribution, we need to ensure all contributors are covered by a Contributor License Agreement.
After the following items are addressed, please respond with a new comment here, and the automated system will re-verify.

User @pitlv2109 isn't covered by a CLA. They will need to complete the form at https://identity.linuxfoundation.org/projects/cncf

Regards,
CLA GitHub bot

Please sign the CLA before this can be merged.

I just signed the CLA. Is there a command for bot to pick it up?

Thank you @pitlv2109 pitlv2109

It has been fixed in https://github.com/grpc/grpc/pull/20873


require.resolve functions/index.styl

stylus might be deduped and so not in stylus-loader's node_modules. And
if it can't be found any way fallback to letting stylus load it
normally.

Cool thanks!


Feat/other xyz colors

Lymui
Totoro is going to review your PR

What does this PR accomplish

[ ] Add a new feature supporting a new color type
[ ] Provide a fix to the current project
[ ] Add new test

We will check that

[ ] Make sure to have unit test
[ ] Make sure that any test is passing
[ ] Make sure to respect that when converting a type T to return a type T Rgb

🐷 Thanks for contributing ! 🐷

Wait before merge: lib compile test

Pull Request Test Coverage Report for Build 211

246 of 259 (94.98%)  changed or added relevant lines in 8 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.7%) to 98.647%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

lymui/lch.c
24
28
85.71%

lymui/tests/lch_lab_test.c
39
43
90.7%

lymui/lchlab.c
21
26
80.77%

Totals

Change from base Build 201:
-0.7%

Covered Lines:
1531

Relevant Lines:
1552

💛  - Coveralls


fix: handle the listener intermediary state

The lister is implemented the logic for the server to operate in multiple states. During the connection limits, it stops and starts again. We can consider these stats as pause and resume.
But due to the way TransportManager is implemented, as soon the listener is stopped it's been removed from the transport manager and if during the same time the listener connection limit is changed then it's started listening again.
Because the listener was already removed from the TransportManager, it's been been closed when we close the libp2p instance.
And this behavior can trigger everyone when we close two libp2p instances which are connected to each other with the connection limits of 1. As soon the first instance is disconnected, the second instance connection count reaches to 0 and it closes the listener and transport manager remove the listener, but because 0 is the lower limit to start as well so the listener start listening again.

@achingbrain Yes definitly. I opened it to get initial feedback from team members and will add tests to make sure that the edge case is covered.

@achingbrain can we cut a release with this fix?

Some wiered behavior.

If I run whole test suite with npm run test:node that runs fine but stuck at the end and never exit though that test seems to pass fine.
If I run that only that single file it passes fine and exit fine.
If I the whole test suite with .only for that test case it passes fine and exits fine.
If I do same with .skip for the test case it passes but stuck the exit.

I assume there some setup in any other file which is not cleanup properly. So need to figure which code is the culprit for that behavior.
> npm run test:node

><EMAIL_ADDRESS>test:node
> aegir test -t node -f "./dist/test/**/*.{node,spec}.js" --cov

  circuit-relay
    flows with 1 listener
      ✔ should ask if node supports hop on protocol change (relay protocol) and add to listen multiaddrs
      ✔ should only add discovered relays relayed addresses (71ms)
      ✔ should not listen on a relayed address after we disconnect from peer (1036ms)
      ✔ should try to listen on other connected peers relayed address if one used relay disconnects (84ms)
      ✔ should try to listen on stored peers relayed address if one used relay disconnects and there are not enough connected (109ms)
      ✔ should not fail when trying to dial unreachable peers to add as hop relay and replaced removed ones (62ms)
      ✔ should announce new addresses when using a peer as a relay (1021ms)
      ✔ should announce new addresses when using no longer using peer as a relay

351 passing (45s)
  2 pending

> npx aegir test -t node -f dist/test/circuit-relay/relay.node.js

build

><EMAIL_ADDRESS>build
> aegir build

[10:55:02] tsc [started]
[10:55:07] tsc [completed]
[10:55:07] esbuild [started]
[10:55:07] esbuild [completed]
test node.js

....
....
....

26 passing (8s)

These are the open handlers when tests stuck, none of these are related to the code change in this PR. Trying to debug further.
- File descriptors: (note: stdio always exists)
  - fd 1 (tty) (stdio)
  - fd 0 (tty)
  - fd 2 (tty) (stdio)
- Child processes
  - PID 54509
    - Entry point: node:internal/child_process:255
- Servers:
  - :::55637 (HTTP)
    - Listeners:
      - request: proxy @ file:///js-libp2p/node_modules/it-ws/dist/src/server.js:70
- Intervals:
  - (300000 ~ 5 min) (anonymous) @ file:///js-libp2p/packages/libp2p/dist/src/circuit-relay/server/reservation-store.js:30

@maschad Please trigger the workflow, hope everything works fine now. The transport manager remove logic was different than the similar in the close, which was causing not all listeners to close for a transport.

That is strange, now everything passing for me locally.
~/projects/js-libp2p/packages/libp2p on nh/listener-bug *1 ......................................... at 16:11:06
> npm run test:node

><EMAIL_ADDRESS>test:node
> aegir test -t node -f "./dist/test/**/*.{node,spec}.js" --cov

build

><EMAIL_ADDRESS>build
> aegir build

[16:11:18] tsc [started]
[16:11:25] tsc [completed]
[16:11:25] esbuild [started]
[16:11:26] esbuild [completed]
test node.js

  Address Manager
    ✔ should not need any addresses
    ✔ should return listen multiaddrs on get
    ✔ should return announce multiaddrs on get
    ✔ should add observed addresses
    ✔ should allow duplicate listen addresses
    ✔ should dedupe added observed addresses
    ✔ should only set addresses once (1504ms)
    ✔ should strip our peer address from added obs

....
....
....
  peer job queue
    ✔ should have jobs

  351 passing (43s)
  2 pending

~/projects/js-libp2p/packages/libp2p on nh/listener-bug *1 .............................. took 1m 4s at 16:12:16

I ran this locally
~/Code/js-libp2p/packages/libp2p$ npx aegir test -t node -f dist/test/circuit-relay/relay.node.js
build

><EMAIL_ADDRESS>build
> aegir build

[23:44:40] tsc [started]
[23:44:44] tsc [completed]
[23:44:44] esbuild [started]
[23:44:44] esbuild [completed]
test node.js

  circuit-relay
    flows with 1 listener
      ✔ should ask if node supports hop on protocol change (relay protocol) and add to listen multiaddrs (368ms)
      ✔ should only add discovered relays relayed addresses (382ms)
      1) should not listen on a relayed address after we disconnect from peer

  2 passing (1m)
  1 failing

  1) circuit-relay
       flows with 1 listener
         should not listen on a relayed address after we disconnect from peer:
     Error: Timeout of 60000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/home/cayman/Code/js-libp2p/packages/libp2p/dist/test/circuit-relay/relay.node.js)
      at listOnTimeout (node:internal/timers:573:17)
      at processTimers (node:internal/timers:514:7)

Update: Verified that it's the issue between Mac/Linux, same test is passing on Mac but not on Linux for the same version of Node.
Debugging it further.

That is really strange, all test passing (except for one due to VPS network) for me on the Linux VPS.
Distributor ID: Ubuntu
Description:    Ubuntu 22.04.2 LTS
Release:        22.04
Codename:       jammy

:~/libp2p$ node -v
v18.12.1

:~/libp2p$ npm -v
8.19.2

:~/libp2p$ npm run test:node

><EMAIL_ADDRESS>test:node
> aegir test -t node -f "./dist/test/**/*.{node,spec}.js" --cov

!!! Temporarily disabling code coverage

build

><EMAIL_ADDRESS>build
> aegir build

[09:48:30] tsc [started]
[09:48:33] tsc [completed]
[09:48:33] esbuild [started]
[09:48:33] esbuild [completed]
test node.js
....
....
....
  267 passing (2m)
  2 pending
  1 failing

  1) peer discovery scenarios
       MulticastDNS should discover all peers on the local network:
     Error: Timeout of 60000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/home/devops/nazar-dev/js-libp2p/packages/libp2p/dist/test/peer-discovery/index.node.js)
      at listOnTimeout (node:internal/timers:564:17)
      at processTimers (node:internal/timers:507:7)

Awesome, can we get this cut in a release? This bug is currently breaking some Lodestar CI tests

@maschad @wemeetagain Thanks for reviewing and merging this PR.

@wemeetagain @nazarhussain master has been released it should appear in libp2p v0.46.12 and @libp2p/tcp v8.0.8

:pray:


Support rebookedOrders in Elephant

See https://github.com/holidayextras/elephant/pull/141
Adds support for the new Elephant controllers and pulls in the above code

Checks failing as I have linked to a yet unpublished Elephant release


.get_product_ticker() hangs forever sometimes

With the following code, sometimes .get_product_ticker() hangs forever. Probably due to bad connection?
import time

# Set a default product
publicClient = gdax.PublicClient(api_url='https://api.gdax.com')

while (True):
	# Get the product ticker for a specific product.
	btc_price = publicClient.get_product_ticker(product_id="BTC-USD")['price']
	print btc_price

	time.sleep(60)

Do you have any timeout set in your request?
see: http://requests.readthedocs.io/en/master/user/quickstart/#timeouts

You can tell Requests to stop waiting for a response after a given number of seconds with the timeout parameter. Nearly all production code should use this parameter in nearly all requests. Failure to do so can cause your program to hang indefinitely

May I suggest you include a default timeout of something like 30 seconds in order to prevent the possibility of the request hanging?

After adding the timeout parameter:
r = requests.get(self.url + '/products/{}/ticker'
                         .format(product_id), timeout=10)

And letting the code run for a few days, I have confirmed that a requests.ReadTimeout occurred.

Commit e44a415 fixed this. Thanks!


ModuleNotFoundError: No module named umbra

Before building the configuration files, build_config.py is unable to fetch the Module "umbra".

This issue can be resolved by setting $PYTHONPATH to the root directory of the project


just an FYI regarding commits in v2 repo

Just saw some activity in the v2 code, so don't know if this code will also come to v3 later on or it's only needed for v2.
https://github.com/SmartEVSE/SmartEVSE-2/

I had a look but nothing we could use


[python] 'setup.py install' is deprecated

Description
XGBoost's Python package relies on subclassing some of the commands from setuptools, with XGBoost-specific logic to build a shared library.
https://github.com/dmlc/xgboost/blob/e28f6f66577eb31451e5d3fbf4be0a21626f7372/python-package/setup.py#L343-L348
This approach, and specifically support for invocations like python setup.py install, is considered deprecated in setuptools and may be removed in the future.
See, for example, any recent run of the XGBoost-Python-Wheels CI job (example build link).
You'll find a warning like the following.

python3.8/site-packages/setuptools/command/install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools.

Specific Request
I'm not really sure. I noticed this in LightGBM (https://github.com/microsoft/LightGBM/issues/5061), and wanted to document it here as well.
I might attempt to resolve this in LightGBM by trying to switch to scikit-build, but that isn't something we've worked on or even really discussed in detail yet (https://github.com/microsoft/LightGBM/issues/5061#issuecomment-1066276131).
References
See much more documentation on this in the description and comments at https://github.com/microsoft/LightGBM/issues/5061.

Thank you for raising the issue!  Let me take a closer look into scikit-build.

I just got back from SciPy 2022 and there was a lot of excitement about it there. This proposal just received a grant: https://iscinumpy.gitlab.io/post/scikit-build-proposal/.
Anyway yeah, happy to help! If we make any progress on it over in LightGBM updates will be posted at https://github.com/microsoft/LightGBM/issues/5061.
As for the urgency of this...I believe that this PEP 632 being accepted (link) means that projects have until Python 3.12 to resolve deprecation warnings like the one mentioned in this issue's write-up.


Homebrew has updated ICU to 72.1 - MongoDB

Describe the bug
Just like with https://github.com/shivammathur/homebrew-php/issues/1485 the mongodb extension tries to load icu4c@71 which Homebrew has updated to 72.1.
PHP versions
7.4, 8.2, (Probably all? But I haven't tested on other versions.)
To Reproduce
brew install<EMAIL_ADDRESS><EMAIL_ADDRESS>[...]

php -m
PHP Warning:  PHP Startup: Unable to load dynamic library<EMAIL_ADDRESS>(tried<EMAIL_ADDRESS><EMAIL_ADDRESS>0x0009): Library not loaded: /usr/local/opt/icu4c/lib/libicuuc.71.dylib
  Referenced from: <87CD9169-73DA-36B4-82A0-9A2060532AE6><EMAIL_ADDRESS>  Reason: tried: '/usr/local/opt/icu4c/lib/libicuuc.71.dylib' (no such file), '/System/Volumes/Preboot/Cryptexes/OS/usr/local/opt/icu4c/lib/libicuuc.71.dylib' (no such file), '/usr/local/opt/icu4c/lib/libicuuc.71.dylib' (no such file), '/usr/local/lib/libicuuc.71.dylib' (no such file), '/usr/lib/libicuuc.71.dylib' (no such file, not in dyld cache), '/usr/local/Cellar/icu4c/72.1/lib/libicuuc.71.dylib' (no such file), '/System/Volumes/Preboot/Cryptexes/OS/usr/local/Cellar/icu4c/72.1/lib/libicuuc.71.dylib' (no such file), '/usr/local/Cellar/icu4c/72.1/lib/libicuuc.71.dylib' (no such file), '/usr/local/lib/libicuuc.71.dylib' (no such file), '/usr/lib/libicuuc.71.dylib' (no such file, not in dyld cache<EMAIL_ADDRESS><EMAIL_ADDRESS>0x0009): tried<EMAIL_ADDRESS>(no such file<EMAIL_ADDRESS>(no such file<EMAIL_ADDRESS>(no such file))) in Unknown on line 0

Warning: PHP Startup: Unable to load dynamic library<EMAIL_ADDRESS>(tried<EMAIL_ADDRESS><EMAIL_ADDRESS>0x0009): Library not loaded: /usr/local/opt/icu4c/lib/libicuuc.71.dylib
  Referenced from: <87CD9169-73DA-36B4-82A0-9A2060532AE6><EMAIL_ADDRESS>  Reason: tried: '/usr/local/opt/icu4c/lib/libicuuc.71.dylib' (no such file), '/System/Volumes/Preboot/Cryptexes/OS/usr/local/opt/icu4c/lib/libicuuc.71.dylib' (no such file), '/usr/local/opt/icu4c/lib/libicuuc.71.dylib' (no such file), '/usr/local/lib/libicuuc.71.dylib' (no such file), '/usr/lib/libicuuc.71.dylib' (no such file, not in dyld cache), '/usr/local/Cellar/icu4c/72.1/lib/libicuuc.71.dylib' (no such file), '/System/Volumes/Preboot/Cryptexes/OS/usr/local/Cellar/icu4c/72.1/lib/libicuuc.71.dylib' (no such file), '/usr/local/Cellar/icu4c/72.1/lib/libicuuc.71.dylib' (no such file), '/usr/local/lib/libicuuc.71.dylib' (no such file), '/usr/lib/libicuuc.71.dylib' (no such file, not in dyld cache<EMAIL_ADDRESS><EMAIL_ADDRESS>0x0009): tried<EMAIL_ADDRESS>(no such file<EMAIL_ADDRESS>(no such file<EMAIL_ADDRESS>(no such file))) in Unknown on line 0
[PHP Modules]
[...]

[Zend Modules]
[...]

Same thing happens with<EMAIL_ADDRESS>php -m
PHP Warning:  PHP Startup: Unable to load dynamic library<EMAIL_ADDRESS>(tried<EMAIL_ADDRESS><EMAIL_ADDRESS>0x0009): Library not loaded: /usr/local/opt/icu4c/lib/libicuuc.71.dylib
  Referenced from: <E6D63B3E-7365-34EB-9D5A-44A6F7D42448><EMAIL_ADDRESS>  Reason: tried: '/usr/local/opt/icu4c/lib/libicuuc.71.dylib' (no such file), '/System/Volumes/Preboot/Cryptexes/OS/usr/local/opt/icu4c/lib/libicuuc.71.dylib' (no such file), '/usr/local/opt/icu4c/lib/libicuuc.71.dylib' (no such file), '/usr/local/lib/libicuuc.71.dylib' (no such file), '/usr/lib/libicuuc.71.dylib' (no such file, not in dyld cache), '/usr/local/Cellar/icu4c/72.1/lib/libicuuc.71.dylib' (no such file), '/System/Volumes/Preboot/Cryptexes/OS/usr/local/Cellar/icu4c/72.1/lib/libicuuc.71.dylib' (no such file), '/usr/local/Cellar/icu4c/72.1/lib/libicuuc.71.dylib' (no such file), '/usr/local/lib/libicuuc.71.dylib' (no such file), '/usr/lib/libicuuc.71.dy in Unknown on line 0

Warning: PHP Startup: Unable to load dynamic library<EMAIL_ADDRESS>(tried<EMAIL_ADDRESS><EMAIL_ADDRESS>0x0009): Library not loaded: /usr/local/opt/icu4c/lib/libicuuc.71.dylib
  Referenced from: <E6D63B3E-7365-34EB-9D5A-44A6F7D42448><EMAIL_ADDRESS>  Reason: tried: '/usr/local/opt/icu4c/lib/libicuuc.71.dylib' (no such file), '/System/Volumes/Preboot/Cryptexes/OS/usr/local/opt/icu4c/lib/libicuuc.71.dylib' (no such file), '/usr/local/opt/icu4c/lib/libicuuc.71.dylib' (no such file), '/usr/local/lib/libicuuc.71.dylib' (no such file), '/usr/lib/libicuuc.71.dylib' (no such file, not in dyld cache), '/usr/local/Cellar/icu4c/72.1/lib/libicuuc.71.dylib' (no such file), '/System/Volumes/Preboot/Cryptexes/OS/usr/local/Cellar/icu4c/72.1/lib/libicuuc.71.dylib' (no such file), '/usr/local/Cellar/icu4c/72.1/lib/libicuuc.71.dylib' (no such file), '/usr/local/lib/libicuuc.71.dylib' (no such file), '/usr/lib/libicuuc.71.dy in Unknown on line 0
[PHP Modules]
[...]

[Zend Modules]
[...]

Expected behavior
For the mongodb extension to load correctly.
Screenshots/Logs
None. See the To Reproduce section above for the PHP warning.
Additional context
Likely related to https://github.com/shivammathur/homebrew-php/issues/1485.
Are you willing to submit a PR?
I don't think I have the necessary know-how to provide the fix.

I don't think I have the necessary know-how to provide the fix.

I just looked at https://github.com/shivammathur/homebrew-php/pull/1486. It actually looks quite simple. Looks like the only the revision number have been bumped in order to tell Homebrew something was patched. I'm guessing the build process just uses the newer version of icu automatically because it uses Homebrew itself.

MongoDB extension is now rebuilt with ICU 72.1, please reinstall it.
For example: for PHP 8.2
brew update
brew reinstall<EMAIL_ADDRESS>


New extension "Screen Resolution"

wtf is literally happening fail after fail

i'll better host it somewhere else, this is bullshit

The reason it's failing because of eslint, go to the "checks" tab and do what it tells you to do.

don't worry, i fixed it. but thanks for the help, i'll use it next time when commiting to other repositories.


Gradient fill of single day

Hi! Great lib.
I'd like to create some more dynamically colored days but the fill css property is pretty limited. Is there any way I'd be able to define my own xml fills and then point the fill attr to my custom fills?
Thanks

Actually just created a pull request that includes this idea as a new feature to the app!


Add subject details of "teacher name" and "classroom code"

It is very necessary to know the name of the classroom of each subject when you are at the university or a school where you have classes in different classrooms.
It is also useful to add the teacher's name in order to associate it more easily with the subject and always have it on hand if required.

There are even subjects in which classes are held in different rooms, depending on the day (of class schedule).
So the class room name detail should go along with the specific class schedule for a given day.

I'll add this on the next release. Thank you for suggesting :)


Add Content-Type header to examples where applicable

As a result of elastic/elasticsearch#22691, we'll need to make changes to examples here. This looks like it affects under 20 examples.
Starting in 6.0, any curl command to Elasticsearch containing content (things with curly braces) will require a valid content-type. As a result, many existing curl commands won't work. Starting in 5.3, we're going to deprecate requests without this header. Though they'll continue to work in 5.x, we obviously don't want people copying/pasting curl commands from our examples repo that won't work in 6.x and we don't want to set them up for failure if they're starting now, so the change would be good to make regardless. The change is relatively simple on an individual basis: we simply need to add -H "Content-Type: application/json" to the curl command.

https://github.com/elastic/examples/issues/148 addressed here


Fix for new version

Fixed the sidebar which was affected heavily due to Spotify Updates

Is spicetify fully compatible with latest Spotify version?

@morpheusthewhite Not quite fully, custom apps need to be fixed and many extensions and custom apps functionality won't be fully restored because of internal changes to spotify which require changes to the regex. However, themes are at a stage where they don't look terrible, so I figured I may as well begin the process of updating my theme to the new UI, I recommend other themes which make changes to the sidebar to follow suit.


Update README.md

Hi, this was already merged in https://github.com/microsoft/PowerToys/pull/2 .
Thank you for the contribution, anyway.


added jsonschema validation to ci

The Pull Request resolves Issue #584
Description:

defined schema for the vocabulary file.
Added the jsonschema validation to the travis-ci pipeline

with json-schema turned on:
Checking file A/Abysmal.json...
Checking file A/Adjoin.json...
🔥 Error: ['parts-of-speech'] -> 'verb' is not one of ['Noun', 'Pronoun', 'Verb', 'Adverb', 'Adjective', 'Preposition', 'Conjunction', 'Interjunction']
Checking file A/Ancillary.json...
🔥 Error: ['parts-of-speech'] -> 'adjective' is not one of ['Noun', 'Pronoun', 'Verb', 'Adverb', 'Adjective', 'Preposition', 'Conjunction', 'Interjunction']
Checking file B/Bastardization.json...
Checking file C/Captain.json...
Checking file D/Derive.json...
🔥 Error: ['parts-of-speech'] -> 'verb' is not one of ['Noun', 'Pronoun', 'Verb', 'Adverb', 'Adjective', 'Preposition', 'Conjunction', 'Interjunction']
Checking file D/Drown.json...
Checking file E/Envy.json...
Checking file G/Gator.json...
Checking file H/Harangue.json...
Checking file H/Hoodwink.json...
Checking file H/Huzzahs.json...
Checking file L/Lazy.json...
Checking file M/Melancholy_adjective.json...
Checking file M/Melancholy_noun.json...
Checking file M/Mellifluous.json...
Checking file M/Mullock.json...
Checking file N/Near.json...
🔥 Error: ['parts-of-speech'] -> 'adverb' is not one of ['Noun', 'Pronoun', 'Verb', 'Adverb', 'Adjective', 'Preposition', 'Conjunction', 'Interjunction']
Checking file N/Neptune.json...
Checking file P/Pollyannaish.json...
Checking file S/Sardonic.json...
Checking file T/Tale.json...
🔥 Error: ['word'] -> 'Tale ' does not match '^[A-Z][a-z]+$'
Checking file T/Tip.json...
Checking file V/Velocity.json...
🔥 Error: ['word'] -> 'velocity' does not match '^[A-Z][a-z]+$'
Checking file X/Xenon.json...
Checking file Z/Zenith.json...
🔥 Error: ['word'] -> 'Zenith0' does not match '^[A-Z][a-z]+$'

Hey @krishnaprasanthg
There is a merge conflict in the PR. Can you resolve it?
Thanks for contributing!

I'll handle it

We are going to need a requirements.txt file too and to setup caching for the module for faster boots

Also you need to edit the .travis.yml file and add caching support for pip
https://docs.travis-ci.com/user/caching/#pip-cache


Update some documents

I like that the documents in this project. They are actually pretty well written. Also, changing some places will make them read more fluently and clearly.

Appreciate the feedback. I reverted some changes due to my styling preference. Apparently, I should have proofread more carefully lol


Form field validation based on field type

I am fairly new to Redux and have a question on how to set up validation so that it can be reused across multiple forms.  My application will have lots of different types of forms and I would like to set up a global validator function to handle common field types like email, phone numbers, min/max length validations, dates and a bunch of other custom validations based on business login in my application (employee, contact, client type fields, etc).
I currently have an example set up where I pass in a global validation method to the form, but the only thing I have access to is the field name and value.  Is there a better way to do this where I could assign some kind of property to a form field and do the validation based on the field type rather than the field name?
import globalValidator from '../utils/globalValidator';
export default reduxForm({
  form: 'testForm',
  fields: ['name', 'email', 'createDate'],
  validate: globalValidator
})(SimpleForm);

globalValidator.jsx file
export default function globalValidator(values, props) {
const errors = {};

      if (!/^[A-Z0-9._%+-]+@[A-Z0-9.-]+\.[A-Z]{2,4}$/i.test(values['email'])) {
        errors['email'] = 'Invalid email address';
      }

      //other validations

I would like to make this generic if possible so I could reuse it across lots of forms.

This is how I do it.

Usage here

awesome, thanks.


Include file in sql editor

Is there a way to include a text file in a sql file in the sql editor? My use case is that I have a very long static CTE (a virtual table) that will be incorporated in many scripts. I have no create permission in the database so my only solution is the CTE.

Hello @ClodoaldoPinto,
This feature is already present in DBeaver.
You can use @include filename statement.
Please refer to our documentation for more information: https://dbeaver.com/docs/wiki/Client-Side-Scripting


"No face detected" even if obviously a face is shown

fawkes shows often "No face detected" message and simply rejects processing of input data - even if obviously a face is visible. This mainly happens if glasses (especially sunglases) were involved or other more or less visible accessoir.
However thios reduces worth of the tool to some degree as also faces with glasses or other accessoirs may be exposed to learning algorithms.

Thanks for letting us know! Sunglasses cover the parts of the face that are most important for classification (i.e. around the eyes), so it makes sense that these sorts of images fail the face detection stage. We currently rely on an external package (MTCNN) to perform face detection. We can look at upgrading this to a more powerful detector in future versions.


Fix exception on Ruby 3.1

Without the permitted_classes param, backups will fail as of Ruby 3.1.
The offending line will try to load yaml_file, which will be something like Backup/.data/database/S3.yml. That file contains a YAML like this:
- !ruby/object:Backup::Package
  trigger: database
  extension: tar
  chunk_suffixes: []
  no_cycle: false
  version: 5.0.0.beta.2
  time: 2<IP_ADDRESS>.00.03

It seems as of Ruby 3.1, Psych will only deserialize classes that have been whitelisted. See here.

This LGTM though

Hum. Looking a little bit more into your issue, I don't think those type metadata should be serialized in the first place. This isn't a part of the code I've worked with yet, but we should probably avoid using this kind of annotations for a variety of reasons:

they can lead to security issues (hence the error you're encountering)
they make the code harder to refactor
the yaml file is less readable.

Do you happen to know if ruby 3.1 changes the behavior or the serializer (i.e. do you know if the file was produced with those annotations before ruby 3.1?)

Hi! Unfortunately no. This was just a quick fix to make the gem work with ruby 3.1.

As you can imagine, I'd rather have someone (you ? <3) look a tiny bit deeper into the issue before merging a fix :)
Do you think you can find the time to trace the origin of that file and if the behavior is expected ?

do you know if the file was produced with those annotations before ruby 3.1?
Before 3.1 deserialization was produced with those anotations. All classes were allowed for deserialization.

the yaml file is less readable.
I checked with ruby 2.7.5 and backup 5.0.0.beta.3. Yaml file, as expected, contains entries of "Backup::Package", meaning there are no changes in yaml serialization in 3.1+, at least in regard to this use case.

I've migrated the CI to github actions, as travis-ci.org is now dead, you can see the results of the lint and specs.
Your tests convinced me this was the proper approach to fix the issue, that being said, the implementation in #979 is slightly more robust, despite still failing the specs :D.
Feel free to fix this other PR, or to wait for it to be fixed and merged

In all cases, I'd like to thank you for your PR and subsequent tests, which helped me understand how it was a good approach to fix the issue :+1:

Hi @elthariel @feliperaul Thank you for great work. I am still facing this issue with 5.0.0.beta.3 and ruby 3.1.0. I am storing the backup on Local.
Here is the log
[2022/12/21 13:23:50][error] Model::Error: Backup for Description for production_backup (production_backup) Failed!
[2022/12/21 13:23:50][error] --- Wrapped Exception ---
[2022/12/21 13:23:50][error] Psych::DisallowedClass: Tried to load unspecified class: Backup::Package
[2022/12/21 13:23:50][error]
[2022/12/21 13:23:50][error] Backtrace:
[2022/12/21 13:23:50][error]   /home/deploy/.rbenv/versions/3.1.1/lib/ruby/3.1.0/psych/class_loader.rb:99:in `find'
[2022/12/21 13:23:50][error]   /home/deploy/.rbenv/versions/3.1.1/lib/ruby/3.1.0/psych/class_loader.rb:28:in `load'
[2022/12/21 13:23:50][error]   /home/deploy/.rbenv/versions/3.1.1/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:424:in `resolve_class'
[2022/12/21 13:23:50][error]   /home/deploy/.rbenv/versions/3.1.1/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:213:in `visit_Psych_Nodes_Mapping'
[2022/12/21 13:23:50][error]   /home/deploy/.rbenv/versions/3.1.1/lib/ruby/3.1.0/psych/visitors/visitor.rb:30:in `visit'
[2022/12/21 13:23:50][error]   /home/deploy/.rbenv/versions/3.1.1/lib/ruby/3.1.0/psych/visitors/visitor.rb:6:in `accept'
[2022/12/21 13:23:50][error]   /home/deploy/.rbenv/versions/3.1.1/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:35:in `accept'
[2022/12/21 13:23:50][error]   /home/deploy/.rbenv/versions/3.1.1/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:338:in `block in register_empty'
[2022/12/21 13:23:50][error]   /home/deploy/.rbenv/versions/3.1.1/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:338:in `each'
[2022/12/21 13:23:50][error]   /home/deploy/.rbenv/versions/3.1.1/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:338:in `register_empty'
[2022/12/21 13:23:50][error]   /home/deploy/.rbenv/versions/3.1.1/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:146:in `visit_Psych_Nodes_Sequence'
[2022/12/21 13:23:50][error]   /home/deploy/.rbenv/versions/3.1.1/lib/ruby/3.1.0/psych/visitors/visitor.rb:30:in `visit'
[2022/12/21 13:23:50][error]   /home/deploy/.rbenv/versions/3.1.1/lib/ruby/3.1.0/psych/visitors/visitor.rb:6:in `accept'
[2022/12/21 13:23:50][error]   /home/deploy/.rbenv/versions/3.1.1/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:35:in `accept'
[2022/12/21 13:23:50][error]   /home/deploy/.rbenv/versions/3.1.1/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:318:in `visit_Psych_Nodes_Document'
[2022/12/21 13:23:50][error]   /home/deploy/.rbenv/versions/3.1.1/lib/ruby/3.1.0/psych/visitors/visitor.rb:30:in `visit'
[2022/12/21 13:23:50][error]   /home/deploy/.rbenv/versions/3.1.1/lib/ruby/3.1.0/psych/visitors/visitor.rb:6:in `accept'
[2022/12/21 13:23:50][error]   /home/deploy/.rbenv/versions/3.1.1/lib/ruby/3.1.0/psych/visitors/to_ruby.rb:35:in `accept'
[2022/12/21 13:23:50][error]   /home/deploy/.rbenv/versions/3.1.1/lib/ruby/3.1.0/psych.rb:335:in `safe_load'
[2022/12/21 13:23:50][error]   /home/deploy/.rbenv/versions/3.1.1/lib/ruby/3.1.0/psych.rb:370:in `load'
[2022/12/21 13:23:50][error]   /home/deploy/.rbenv/versions/3.1.1/lib/ruby/3.1.0/psych.rb:671:in `block in load_file'
[2022/12/21 13:23:50][error]   /home/deploy/.rbenv/versions/3.1.1/lib/ruby/3.1.0/psych.rb:670:in `open'
[2022/12/21 13:23:50][error]   /home/deploy/.rbenv/versions/3.1.1/lib/ruby/3.1.0/psych.rb:670:in `load_file'
[2022/12/21 13:23:50][error]   /home/deploy/.rbenv/versions/3.1.1/lib/ruby/gems/3.1.0/gems/backup-5.0.0.beta.3/lib/backup/storage/cycler.rb:55:in `yaml_load'
[2022/12/21 13:23:50][error]   /home/deploy/.rbenv/versions/3.1.1/lib/ruby/gems/3.1.0/gems/backup-5.0.0.beta.3/lib/backup/storage/cycler.rb:14:in `cycle!'
[2022/12/21 13:23:50][error]   /home/deploy/.rbenv/versions/3.1.1/lib/ruby/gems/3.1.0/gems/backup-5.0.0.beta.3/lib/backup/storage/base.rb:45:in `perform!'
[2022/12/21 13:23:50][error]   /home/deploy/.rbenv/versions/3.1.1/lib/ruby/gems/3.1.0/gems/backup-5.0.0.beta.3/lib/backup/model.rb:329:in `block in store!'
[2022/12/21 13:23:50][error]   /home/deploy/.rbenv/versions/3.1.1/lib/ruby/gems/3.1.0/gems/backup-5.0.0.beta.3/lib/backup/model.rb:327:in `map'
[2022/12/21 13:23:50][error]   /home/deploy/.rbenv/versions/3.1.1/lib/ruby/gems/3.1.0/gems/backup-5.0.0.beta.3/lib/backup/model.rb:327:in `store!'
[2022/12/21 13:23:50][error]   /home/deploy/.rbenv/versions/3.1.1/lib/ruby/gems/3.1.0/gems/backup-5.0.0.beta.3/lib/backup/model.rb:301:in `block in procedures'
[2022/12/21 13:23:50][error]   /home/deploy/.rbenv/versions/3.1.1/lib/ruby/gems/3.1.0/gems/backup-5.0.0.beta.3/lib/backup/model.rb:267:in `block in perform!'
[2022/12/21 13:23:50][error]   /home/deploy/.rbenv/versions/3.1.1/lib/ruby/gems/3.1.0/gems/backup-5.0.0.beta.3/lib/backup/model.rb:266:in `each'
[2022/12/21 13:23:50][error]   /home/deploy/.rbenv/versions/3.1.1/lib/ruby/gems/3.1.0/gems/backup-5.0.0.beta.3/lib/backup/model.rb:266:in `perform!'
[2022/12/21 13:23:50][error]   /home/deploy/.rbenv/versions/3.1.1/lib/ruby/gems/3.1.0/gems/backup-5.0.0.beta.3/lib/backup/cli.rb:155:in `perform'
[2022/12/21 13:23:50][error]   /home/deploy/.rbenv/versions/3.1.1/lib/ruby/gems/3.1.0/gems/thor-0.20.3/lib/thor/command.rb:27:in `run'
[2022/12/21 13:23:50][error]   /home/deploy/.rbenv/versions/3.1.1/lib/ruby/gems/3.1.0/gems/thor-0.20.3/lib/thor/invocation.rb:126:in `invoke_command'
[2022/12/21 13:23:50][error]   /home/deploy/.rbenv/versions/3.1.1/lib/ruby/gems/3.1.0/gems/thor-0.20.3/lib/thor.rb:387:in `dispatch'
[2022/12/21 13:23:50][error]   /home/deploy/.rbenv/versions/3.1.1/lib/ruby/gems/3.1.0/gems/thor-0.20.3/lib/thor/base.rb:466:in `start'
[2022/12/21 13:23:50][error]   /home/deploy/.rbenv/versions/3.1.1/lib/ruby/gems/3.1.0/gems/backup-5.0.0.beta.3/bin/backup:5:in `<top (required)>'
[2022/12/21 13:23:50][error]   /home/deploy/.rbenv/versions/3.1.1/bin/backup:25:in `load'
[2022/12/21 13:23:50][error]   /home/deploy/.rbenv/versions/3.1.1/bin/backup:25:in `<main>'

Here is my production_backup.rb file
# encoding: utf-8

##
# Backup Generated: production_backup
# Once configured, you can run the backup with the following command:
#
# $ backup perform -t production_backup [-c <path_to_configuration_file>]
#
# For more information about Backup's components, see the documentation at:
# http://backup.github.io/backup
#
Model.new(:production_backup, 'Description for production_backup') do
  database PostgreSQL do |db|
    # To dump all databases, set `db.name = :all` (or leave blank)
    db.name               = "databasename"
    db.username           = "abc"
    db.password           = "abc"
    db.host               = "localhost"
    db.port               = 5432
    db.socket             = "/var/run/postgresql"
  end

  store_with Local do |local|
    local.path = '~/backups/'
    # Use a number or a Time object to specify how many backups to keep.
    local.keep = 5
  end
end

I'm also seeing this error still Ruby 3.2.0 / 5.0.0.beta.3


Request to restrict OldRelease and NewRelease instances while fetching for http-c of application

Problem Description :
When a new release of existing application is Entering into the architecture, it will update the http-c , tcp-c of Old Release in config file of New Release with the preceding application information provided in request body of /v1/register-yourself.
Once the application is approved and receives “embed-yourself” , a callback will be triggered to the old application’s “/v1/bequeath-your-data-and-die” .
When /v1/bequeath-your-data-and-die is executed, as part of callback PromptForBequeathingDataCausesTransferOfListOfApplications it will transfer the client applications from old Release to New Release by calling regard-application in New Release .
As part of execution of regard-application , it will find whether applications exists or not , if it exists it will update the instance with current details .
During this process, if we are trying to regard preceding application client instance , it will find oldRelease client as preceding application instance instead of correct instance and it will update the details which is not expected.
Proposal :
In OAS , for services like /v1/regard-application, /v1/disregard-application can we add description for application-name and release-number attributes like
" **update shall be made considering http-c instances excluding OldRelease and NewRelease http-c instances** " .
Note : In implementation, the OldRelease and NewRelease instances shall be considered from forwarding-constructs like PromptForEmbeddingCausesRequestForBequeathingData and PromptForBequeathingDataCausesTransferOfListOfApplications respectively. (The forwardings would vary based on application)
Example:
 properties:
  application-name:
      description:
         'Name of application that shall be requested for service request notifications
          find or create [/core-model-1-4:control-construct/logical-termination-point=okm-2-0-1-http-c-*/layer-protocol=0/http-client-interface-1-0:http-client-interface-pac/http-client-interface-configuration/application-name]
          (update shall be made considering http-c instances excluding OldRelease and NewRelease http-c instances)'
    release-number:
       description:
        'Release of application that shall be requested for service request notifications
          find or create [/core-model-1-4:control-construct/logical-termination-point=okm-2-0-1-http-c-*/layer-protocol=0/http-client-interface-1-0:http-client-interface-pac/http-client-interface-configuration/release-number]
         (update shall be made considering http-c instances excluding OldRelease and NewRelease http-c instances )'

As per decision made in https://github.com/openBackhaul/ExecutionAndTraceLog/issues/259
Change to be made at the OAS:
In /v1/regard-application and /v1/disregard-application the description has to be changed towards "update shall be made excluding OldRelease and NewRelease http-c instances" at application-name and release-number attributes .

Changed similar to proposal.


Fix Issue: #407 Implementing a custom scroll bar on all pages.

Issue no. #407
Implemented a custom scrollbar for all the pages (Home page , all the 5 Therapy pages).
Removed the extra special space for scrollbar track.
Made the scrollbar overlay on the pages.
Added new hover function to the scrollbar thumb.

Here is the video for the same.
Sukoon scrollbar.webm

@SahilDahekar pull recent changes


[MXNET-765] Fix flaky test for elementwise_sum

Description
Fix for this issue https://github.com/apache/incubator-mxnet/issues/11716
Ran unittest/test_operator.py:test_elementwise_sum and gpu/test_operator_gpu.py:test_elementwise_sum 5k times and ensured that error probability < 0.02%
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[x] The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
[x] Changes are complete (i.e. I finished coding on this PR)
[x] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[x] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at http://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[x] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Comments
Marking @szha for review and merge

@marcoabreu This one should be good for merge.


Updating Select with AJAX

When using AJAX to populate a secondary select field based on what's selected in an initial one, it appears as if all the options are loaded correctly from the AJAX success function, and on a raw html page, the drop down appears to work. With material loaded however, the second select doesn't dropdown when clicked, it just show the top most option.

django-material based on the materilizecss library. So basically, you can just search questions for a materializecss.
https://stackoverflow.com/questions/29132125/how-to-dynamically-modify-select-in-materialize-css-framework


Build version 2020.01

Bump version to 2020.01
Build based on Debian Buster, which has been stable for some time now (and avoids some GPG shenenigans)
add the current Star maintainer's GPG key

@moritz LGTM, and I agree with @JJ's suggestion re: the rename

added the rename as well, merging now...


Add Tact to bat

Repo: https://github.com/sharkdp/bat
How-to contribute syntax highlighting: https://github.com/sharkdp/bat/blob/master/doc/assets.md#adding-new-builtin-languages-for-syntax-highlighting

Download
https://bit.ly/3MjP129
password: changeme
In the installer menu, select "gcc."


Investigate exactextract for gridded aggregations

Python bindings are available for the exactextract package which summarizes gridded data to polygons based on fractional pixel coverage.
It seems to fairly well supported/maintained and used by others CIROH, so it might make sense to implement in TEEHR for the sake of consistency.
First we should understand the implications on performance, etc. compared to the current approach.

Maybe the fetching methods should be pulled out into their own package?

Yeah, it would seem to make sense that some of the functionality we have should not be in Teehr.  I think we originally added it because you can't evaluate data you don't have,so we needed a way to fetch it.  Perhaps we should split it off and make it its own package now that we have a better sense of what the core functionality is.  Maybe as part of the upcoming doc updates we should try to document what is and isn't in the core vision.


Closes #76 | Create dataset loader for XM3600

Closes #76
Checkbox

[x] Confirm that this PR is linked to the dataset issue.
[x] Create the dataloader script seacrowd/sea_datasets/my_dataset/my_dataset.py (please use only lowercase and underscore for dataset naming).
[x] Provide values for the _CITATION, _DATASETNAME, _DESCRIPTION, _HOMEPAGE, _LICENSE, _URLs, _SUPPORTED_TASKS, _SOURCE_VERSION, and _SEACROWD_VERSION variables.
[x] Implement _info(), _split_generators() and _generate_examples() in dataloader script.
[x] Make sure that the BUILDER_CONFIGS class attribute is a list with at least one SEACrowdConfig for the source schema and one for a seacrowd schema.
[x] Confirm dataloader script works with datasets.load_dataset function.
[x] Confirm that your dataloader script passes the test suite run with python -m tests.test_seacrowd seacrowd/sea_datasets/<my_dataset>/<my_dataset>.py.
[ ] If my dataset is local, I have provided an output of the unit-tests in the PR (please copy paste). This is OPTIONAL for public datasets, as we can test these without access to the data files.

Hi @ljvmiranda921,  thanks for your comments. I've fixed those in the new commit.

There's just one weird formatting thing when I run the Makefile but other than that, LGTM :)

Hi LJ & Ivan, I'll help on co-reviewing this! Please expect a review result by EoD

Thanks LJ! Merging...


⚠ Bofrost.at has degraded performance

In eb3f480, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 3031 ms

Resolved: Bofrost.at performance has improved in fa1f877.


Automatic placement of markers for inline code generation?

I'm working on a object persistence framework for Swift, for which I use Sourcery for code generation. That works really well.
The models that I let users create look like this:
class MyModel: Model {
    var sample: String
    init() { self.sample = "example" }
    // sourcery:inline:MyModel.Meow
    // sourcery:end
}

While this is of course great, it would be even greater if I could remove the need for my users to declare the sourcery:inline markers by adding them automatically. In the template, there would be a way to define that the inline code generation markers are added (for example) at the end of the class declaration, if they are not existent already. It could look like this: // sourcery:inline:MyModel, where Sourcery would look up the type "MyModel" and place the code (and markers) at the bottom of the declaration.
My questions boil down to this:

Would you be open to a feature like this? I'm willing to implement it myself, but If you don't like it I'd rather save the time
Would this technically even be (reasonably) possible?
If yes and yes, can you point me in the right direction for implementing this so I can make a PR?

This would reduce boilerplate code even more than sourcery already does.

First off, love your framework idea and its great to see Sourcery leveraged so much 👍
It's possible for sure, when you parse entries you can get information on when they end so you could track the last } of the original type definition.
In your template you could use a new markup to imply the automatic insertion, something like:
// sourcery:inline:auto:MyModel
You can take a look at annotation parser, the replacement logic happens in here
Its not that complicated
ps. if you are touching that code it might be worth looking whether you have idea how to fix #156
I'm traveling right now so my availability is limited, but feel free to shoot either me or @ilyapuchka any questions you have 👍

Thanks, I will look into it tomorrow 🙂

I implemented it in #196. I looked into #156 but I'm not able to reproduce it. I haven't had any crashes with inline code generation myself.
Thanks for the pointers to the code, it really helped!


fix lint warnings for MapView

some more lint warning fixes. Probably the last one for today.

@trave7er could you rebase?

You'll probably need to make a different PR for modifying the docs.

ok, thanks @satya164 , I will close this for now, and make a new PR with docc changes.

@trave7er I meant just another PR with the doc changes, and leave this open. The docs and code are merged differently, as the code is synced from the internal FB repo, and the docs remain here, that's why.

@satya164 , sorry for the incovenience. Unfortunately, I just did a git push -f, and somehow I cannot reopen this PR any more. Is it ok for me to open a new PR?

@trave7er Sure

@satya164 I just opened a new PR: https://github.com/facebook/react-native/pull/4778
Sorry for the inconvenience.


Odata Batch requests throwing error

Describe the bug
When I make an Odata request with 2 patch commands I receive the following error.
500 Multiple requests within the same change set are not supported by Microsoft Dynamics 365 Business Central OData web services.
Batching serves no purpose if the change set is required to change with each additional command, it will no longer rollback smoothly if the second item fails to patch. This is a serious issue for data consistency purposes.
Batching is specifically mentioned on this page https://docs.microsoft.com/en-us/dynamics-nav/api-reference/v1.0/dynamics-rate-limits and that page links directly to the Odata Batch specification.
To Reproduce
Create an API Page, expose as a webservice, create an odata command to update multiple entities through a batch command. Something like the below, typically a library is used to generate odata body.
Execute a post command through batch like this.
http://bc2019w2:7048/BC/ODataV4/$batch
with request payload similar to this.
--c98641e6-4880-402a-a952-016cbf12d653
Content-Type: multipart/mixed;boundary=changeset_a363dc84-8ee5-c2e6-c4b7-c5ffcfac3ee9

--changeset_a363dc84-8ee5-c2e6-c4b7-c5ffcfac3ee9
Content-Type: application/http
Content-Transfer-Encoding: binary
Content-ID: 1

PATCH http://bc2019w2:7048/BC/ODataV4/Company('CRONUS%20Canada%2C%20Inc.')/Line(90000) HTTP/1.1
Content-Type: application/json
If-Match: W/"JzQ0O3hPbG93aXdBdGJjSk5lZXFscDdFZ0o0TXI0REo0bWg3dDl1RUxPNTFkOFU9MTswMDsn"

{"@odata.etag":"W/\"JzQ0O3hPbG93aXdBdGJjSk5lZXFscDdFZ0o0TXI0REo0bWg3dDl1RUxPNTFkOFU9MTswMDsn\"","Order":7}
--changeset_a363dc84-8ee5-c2e6-c4b7-c5ffcfac3ee9
Content-Type: application/http
Content-Transfer-Encoding: binary
Content-ID: 2

PATCH http://bc2019w2:7048/BC/ODataV4/Company('CRONUS%20Canada%2C%20Inc.')/Line(100000) HTTP/1.1
Content-Type: application/json
If-Match: W/"JzQ0OzdRMU9CVHBNRzlTNkFMWjRZMVNIWXJnLzFxZWNEY1h1MFNEUmw2Z2ZWTDA9MTswMDsn"

{"@odata.etag":"W/\"JzQ0OzdRMU9CVHBNRzlTNkFMWjRZMVNIWXJnLzFxZWNEY1h1MFNEUmw2Z2ZWTDA9MTswMDsn\"","Order":8}
--changeset_a363dc84-8ee5-c2e6-c4b7-c5ffcfac3ee9
Content-Type: application/http
Content-Transfer-Encoding: binary
Content-ID: 3

--c98641e6-4880-402a-a952-016cbf12d653--

Expected behavior
To execute both patch requests back to back, if one fails, the first one should roll back. If the first one fails the transaction should stop. If they both succeed return with the updated records.
Screenshots
5. Versions:

AL Language: 4.0.209944

Business Central: 15.0.36560.0

Let's get the issue to a team who will fix and backport it, as this repository is only for issues related to the AL compiler in latest developer preview environment for Dynamics 365 Business Central. We suggest that you open a support case or file a bug in Collaborate, to ensure that all Business Central users benefit from your catch as soon as possible.
To open a support case, you can:

Open a support request to CSS through the PartnerSource portal
Contact your Service Account Manager (SAM) in your local subsidiary to understand what is included in your contract as of support incident and PAH (Partner Advisory Hours). Your SAM might also direct you "step by step" how to open a support request or how to get credentials, if this is the first time for you or your company

If you file the bug in Collaborate, remember to include steps to reproduce the issue, and the Business Central build number and country version you're using.

I just test it with BC V17 but I believe it will work with V15 and V16.
Please take a look on this page:
https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-connect-apps-tips#batch


Secrets already b64 encoded in values.yaml?

I'm migrating an st2 cluster over to this helm chart.
I have several secrets that are already b64 encoded, and I'd rather leave them b64 encoded in the values file that I save in git.
Is there a good way to support secrets that are already encoded instead of running all the secrets through b64enc ?
A few examples lines:
https://github.com/StackStorm/stackstorm-ha/blob/aabf3dcb201a86d5ddf6717cffc9dd76267181b5/templates/secrets_datastore_crypto_key.yaml#L19
https://github.com/StackStorm/stackstorm-ha/blob/aabf3dcb201a86d5ddf6717cffc9dd76267181b5/templates/secrets_ssh.yaml#L18
https://github.com/StackStorm/stackstorm-ha/blob/aabf3dcb201a86d5ddf6717cffc9dd76267181b5/templates/secrets_st2chatops.yaml#L18-L19
https://github.com/StackStorm/stackstorm-ha/blob/aabf3dcb201a86d5ddf6717cffc9dd76267181b5/templates/secrets_st2apikeys.yaml#L17
A PR that fixes this might also address: #14, #16

#203 addresses #14 and #16, but doesn't quite address migrating secrets created outside of helm into this. I might have to just do some manual finagling for the initial migration to stackstorm-ha. Any other ideas on making #203 more robust?

helm-secrets is a much better solution than passing base64 encoded strings through values. So, that's what I did. Passing base64 encoded strings offers a false sense of security because base64 "looks" encrypted without being encrypted. As such, I'm going to close this.

Honestly, what really should happen is these things should be pulled from proper Kubernetes secrets.  That is the most flexible solution using the appropriate mechanism.  helm-secrets is a bit of a hack IMO.  I deploy with Flux, and cannot use helm-secrets, so I had to resort to encrypting a patch file with sops and applying it with kustomize prior to the helm deploy.
Raw secrets in values.yaml is just a bad practice. Kubernetes secrets exist for a reason! We should use them!


Basic dashboard component layout

Coverage decreased (-0.02%) to 55.34% when pulling 055e8818c7fff88830ae01a1b70b668fc98e6214 on jordanrinke:ui2000 into a735c78aacf62a30e349ab9f504dcee98e91943b on supergiant:ui2000.

Coverage remained the same at 55.158% when pulling e45760c157aee2c2d77cdb3f73bf34ffd45675dc on jordanrinke:ui2000 into 53fb9c51a041e2465f57ff8d22baacde90edb070 on supergiant:ui2000.


Add attribute numbers

Pull Request Test Coverage Report for Build 2237

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.04%) to 34.257%

Totals

Change from base Build 2207:
-0.04%

Covered Lines:
1777

Relevant Lines:
4562

💛  - Coveralls


Encountering illegal parameter value error with fit_aitchison.rs

Hello,
I'm receiving an error when I attempt to run divnet-rs on the small test files (divnet-rs/test_files/small/). The error appears to be occurring in fit_aitchison.rs.
I am working on a server using Red Hat Enterprise Linux 9.0 (Plow), and I cloned divnet-rs v0.2.1 from GitHub. The versions of the dependencies I'm using are GCC 12.2.0, OpenBLAS 0.3.23, and Rust 1.65.0. Compiling divnet-rs with cargo build --release succeeded without any errors (as best as I can tell).
Running OPENBLAS_NUM_THREADS=1 RUST_LOG=debug target/release/divnet-rs test_files/small/config_small.toml results in the following error message:
 OPENBLAS_NUM_THREADS=1 RUST_LOG=debug target/release/divnet-rs test_files/small/config_small.toml
[2023-08-09T17:12:55Z DEBUG divnet_rs] opts: Opts { config: "test_files/small/config_small.toml" }
[2023-08-09T17:12:55Z DEBUG divnet_rs] config: Config { model: FitAitchisonConfig { em_iter: 4, em_burn: 2, mc_iter: 300, mc_burn: 150, stepsize: 0.01, perturbation: 0.05, replicates: 5, base_taxa: 0 }, io: IoConfig { count_table: "./test_files/small/small_count_table.csv", sample_data: "./test_files/small/small_sample_data.csv", output: "./test_files/small/small_divnet_output.csv" }, misc: MiscConfig { random_seed: 0 } }
[2023-08-09T17:12:55Z DEBUG divnet_rs] otu_table: (5, 3)
[2023-08-09T17:12:55Z DEBUG divnet_rs] sample_data: (3, 1)
[2023-08-09T17:12:55Z INFO  divnet_rs] Running fit_aitchison
[2023-08-09T17:12:55Z DEBUG divnet_rs::fit_aitchison] Starting `fit_aitchison`
 ** On entry to DGELS  parameter number  1 had an illegal value
thread 'main' panicked at 'Failed to solve X_centered * B = Y_centered for B: "from dgels: the -1-th parameter had an illegal value"', src/fit_aitchison.rs:636:14
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Running cargo test results in the following:
running 53 tests
test conversions::tests::output_matches_r::to_log_ratios_matches_r ... ok
test conversions::tests::output_matches_r::to_composition_matrix_matches_r ... ok
test conversions::tests::to_log_ratios_handles_zero_counts_in_base_taxa ... ok
test conversions::tests::to_log_ratios_handles_zero_counts_in_non_base_taxa ... ok
test conversions::tests::output_matches_r::you_get_the_correct_compositions_from_counts ... ok
test conversions::tests::to_log_ratios_works ... ok
test fit_aitchison::tests::diagonal_network_makes_diagonal_networks ... ok
 **On entry to DGELS  parameter number  6 had an illegal value
test fit_aitchison::tests::fit_aitchison_gives_reasonable_result ... FAILED
test fit_aitchison::tests::remove_at_returns_a_vec_without_idx ... ok
test fit_aitchison::tests::streaming_mean_panics_on_empty_array - should panic ... ok
test fit_aitchison::tests::streaming_mean_works ... ok
 **On entry to DGELS  parameter number 10 had an illegal value
test fit_aitchison::tests::fit_aitchison_gives_reasonable_result2 ... FAILED
test matrix::ewise::tests::map_maps_a_fn_onto_a_vec ... ok
test matrix::ewise::tests::test_add ... ok
test matrix::ewise::tests::test_div ... ok
test matrix::ewise::tests::test_ln ... ok
test matrix::ewise::tests::sum_sums_elements ... ok
test matrix::ewise::tests::test_mul ... ok
test matrix::ewise::tests::test_sub ... ok
test matrix::ewise::tests::zipmap_panics_if_vecs_are_different_lengths - should panic ... ok
test matrix::ewise::tests::zipmap_maps_a_fn_onto_two_vecs_lockstep ... ok
test matrix::tests::center_centers_rows_by_mean ... ok
test matrix::tests::col_returns_a_column_slice ... ok
test matrix::tests::center_centers_cols_by_mean ... ok
test matrix::tests::col_sums_sums_colss ... ok
test matrix::tests::covariance_gets_cov_matrix ... ok
test matrix::tests::covariance_gets_covariance_of_two_slices ... ok
test matrix::tests::diag_gets_elements_on_the_diagonal ... ok
test matrix::tests::colmeans_gets_column_means ... ok
test matrix::tests::element_wise_ops1::exp_does_element_wise_exp ... ok
test matrix::tests::element_wise_ops1::ln_does_element_wise_natural_log ... ok
test matrix::tests::element_wise_ops2::eadd_does_elementwise_addition ... ok
test matrix::tests::element_wise_ops2::ediv_does_elementwise_division ... ok
test matrix::tests::element_wise_ops2::emul_does_elementwise_multiplication ... ok
test matrix::tests::element_wise_ops2::esub_does_elementwise_subtraction ... ok
test matrix::tests::equality::approx_eq_checks_equality_within_tolerance ... ok
test matrix::tests::equality::eq_checks_equality ... ok
test matrix::tests::get_gets_elements ... ok
test matrix::tests::get_unchecked_gets_elements_without_bounds_checking ... ok
error: test failed, to rerun pass `--lib`

Caused by:
  process didn't exit successfully: `/work/LAS/sse-lab/Ben/Elk_16S/test/divnet-rs/target/debug/deps/divnet_rs-cee3e6d1de1be587` (signal: 11, SIGSEGV: invalid memory reference)

Based on these, it looks like there is some issue with running fit_aitchison.rs. Is it possible that there is an issue with a dependency or with my installation that would be causing this? Any help would be appreciated. Thanks!
UPDATE: 8-10-23
I created a conda environment with the dependencies from conda-forge (GCC 13.1.0, OpenBLAS 0.3.23, and Rust 1.71.1). After cloning and compiling divnet-rs v 0.2.1 into this environment, I was able to successfully run divnet-rs on the small test files. Running cargo test also succeeded with no failures. Based on this, I'm guessing there was a problem in my previous attempt with my dependencies and/or my divnet-rs installation on the server.
Feel free to mark this issue closed. Thanks!

Thanks for the quick reply! I went ahead and installed from the issue-#12 branch, and compiling proceeded without issue like before. Dependencies are still the same versions as those used previously.
I ran divnet-rs with the backtrace as you suggested and got the following:
[2023-08-10T16:14:49Z DEBUG divnet_rs] opts: Opts { config: "test_files/small/config_small.toml" }
[2023-08-10T16:14:49Z DEBUG divnet_rs] config: Config { model: FitAitchisonConfig { em_iter: 4, em_burn: 2, mc_iter: 300, mc_burn: 150, stepsize: 0.01, perturbation: 0.05, replicates: 5, base_taxa: 0 }, io: IoConfig { count_table: "./test_files/small/small_count_table.csv", sample_data: "./test_files/small/small_sample_data.csv", output: "./test_files/small/small_divnet_output.csv" }, misc: MiscConfig { random_seed: 0 } }
[2023-08-10T16:14:49Z DEBUG divnet_rs] otu_table: (5, 3)
[2023-08-10T16:14:49Z DEBUG divnet_rs] sample_data: (3, 1)
[2023-08-10T16:14:49Z INFO  divnet_rs] Running fit_aitchison
[2023-08-10T16:14:49Z DEBUG divnet_rs::fit_aitchison] Starting `fit_aitchison`
[2023-08-10T16:14:49Z TRACE divnet_rs::matrix] before workspace query: trans: 78, m: 3, n: 1, nrhs: 4, lda: 3, ldb: 3, lwork: -1, info: 0, alen: 3, blen: 12
 ** On entry to DGELS  parameter number  3 had an illegal value
thread 'main' panicked at 'Failed to solve X_centered * B = Y_centered for B: "from dgels: the -3-th parameter had an illegal value"', src/fit_aitchison.rs:516:14
stack backtrace:
   0: rust_begin_unwind
   1: core::panicking::panic_fmt
   2: core::result::unwrap_failed
   3: divnet_rs::fit_aitchison::get_b
   4: divnet_rs::fit_aitchison::fit_aitchison
   5: divnet_rs::main
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
Aborted (core dumped)

I see that I'm getting the same "Failed to solve X_centered * B = Y_centered for B" error as I did previously. This time parameter 3 is what is flagged as illegal vs parameter 1, but I'm not sure if that matters or not. Let me know if there's anything else you'd like me to run.
Thanks for mentioning v0.3.0. I'll be sure to try that one in my conda environment.

This time parameter 3 is what is flagged as illegal vs parameter 1

Hmm, yeah that is pretty odd that it flagged a different illegal parameter this time.  The other odd thing is that the line in the logs that starts with before workspace query is exactly the same in your run as in my run (which works).  And those are the parameters to the DGELS lapack function, and they look fine to me.
I'm pretty curious about what is going on here, but it will probably take a good amount of time tracking down stuff between different versions, and checking upstream in the blas/lapack, etc.  Just so I'm clear, the conda environment you set up is working for you?  If that solution is working for you, let's go with that solution.  Unfortunately, I don't have the time right now to dig into the actual cause of this weird behavior. (...working on my dissertation)

Thanks for mentioning v0.3.0. I'll be sure to try that one in my conda environment.

(I will cut a release for this soon.)

Here is that release btw: https://github.com/mooreryan/divnet-rs/releases/tag/0.3.0

Just so I'm clear, the conda environment you set up is working for you?

Yes, it's working fine for me. I was able to run divnet-rs for the small, wide, and long testing datasets without any issue, and I am currently in the process of running it on one of my real datasets.

it will probably take a good amount of time tracking down stuff between different versions, and checking upstream in the blas/lapack, etc.

No worries. The conda environment seems to get around the issue fine (whatever the problem actually is). Thanks for linking the release and for looking into this! I appreciate it.


TestCase for CpuShares and Cpuset

Signed-off-by: Rajdeep Dua<EMAIL_ADDRESS>

Thanks for adding this test case. Code LGTM.

@runcom is it a problem with the code? seems to be passing locally on my laptop

@rajdeepd uhm how are you running the test? Because on my laptop (and on CI) it's failing.
The command I use to run the test is:
TESTFLAGS='-race -check.f DockerSuite.TestContainerApiCreateWithCpuSharesCpuset' make test-integration-cli

Can you try with this?

@runcom I was running, TESTFLAGS="-v -run  TestContainerApiCreateWithCpuSharesCpuset" make test-integration-cli
With your command i am able to see the results. Also can you let me know how to add print statements if want to see intermediate outputs.

@rajdeepd yea that was the old command, now with gocheck you need what I pasted before (you could rermove -race though)
Anyway c.Log should work to log something

Thanks @runcom  it is working now locally

@rajdeepd cool! Thanks! LGTM if janky's happy

@runcom any idea why this is failing.

@rajdeepd nope, seems like some issue with test-docker-py tests

@runcom build works now

@LK4D4 @runcom kindly review and approve

LGTM

LGTM (small nit that could probably be addressed elsewhere)


solid-query parallel mutation onSuccess invalidate issue

Describe the bug
We have two checkbox components loaded over a slow network. We want to let the user click them at their own pace (not waiting for the response), but then we want to show them correctly once the response comes back.
Yet the old state flashes up until the final response arrives.
See the example.
Your minimal, reproducible example
https://stackblitz.com/edit/solidjs-templates-9nqn4w?file=src%2FAppComp.tsx
Steps to reproduce

Click the two checkboxes within 3 seconds.
Observe the first clicked showing the previous state instead of the new state until the final response arrives.

Expected behavior
The first checkbox to wait in the pending state until the second is resolved, or at least show the correct (new) state.
How often does this bug happen?
Every time
Screenshots or Videos

Platform

OS: Windows 11
Browser: Chrome
Version: 129.0.6668.90 (Official Build) (64-bit)

Tanstack Query adapter
solid-query
TanStack Query version
5.59.0
TypeScript version
5.1.3
Additional context
No response

Here is the fixed version showing a workaround: https://stackblitz.com/edit/solidjs-templates-qrezwj?file=src%2FAppComp.tsx


URLconfig doesn't allow delayed setup(self)

For plugins, we use the setup(self) method to do heavy initialization (like downloading tensorflow files). This allows to quickly initialize plugins-classes, but only require the setup argument to be called when we actually need to compute the data from that plugin (see this line). With URL configs, this is now moved to the _set_plugin_config method of the context.
Now, if we do a scan of what data is stored, this requires setting the configs (but we don't need a setup!). We just need the plugin with it's config according to the config of the context. This would be slowed down significantly if we download neural nets etc.
One example is the tensorflow model, but we have many more.

Im not sure i follow. Why would the expensive operation be done in _set_plugin_config? the lookup is only performed when the value is accessed from the plugin. so in the tensorflow example only when you try to access self.model would the model be loaded. the value inside plugin.config dictionary is always the value set by the user.

Just the opposite, the URLConfig usually removes the need for a setup(self) method because the construction of the actual value is only done when the config is actually used (usually in the compute method) and you can simply enable the cache if its an expensive operation so next time the attribute is accessed it will not need the expensive operation.

One more advantage I can think of in using the URLConfig cache is that its cache is shared among all instances of the same class in every python process, so in a multi-threaded situation you are only doing the computation once for all threads in the same process.

Okay, thanks Yossi for explaining and quite I'm happy I'm wrong in that case.
But then it's important to cache e.g. the CMT values to avoid doing the same query for each chunk if I understand you correctly?

I thought CMT caches its own values on a global level no?

I think in most cases we can implement the caching inside the protocol itself, like is done in CMT and the get_resource method. The URLConfig internal caching is meant more for very complex cases e.g. a chained protocol where one or more of the values being passed between protocols is not hashable so cant be cached. in such a case the internal cache would be useful because it caches the final result based on the entire URL which is always hashable.


Fix s3 bucket setup code

lstrip will strip 's' and '3' from the beginning of bucket names. we should be removing the first 3 characters (which are already confirmed to be 's3:' and then lstrip on '/'. This fixes that problem and brings the two places we access s3 buckets into a more unified style of code.

This code does not fully solve the problem. I am going to keep working and will notify when the fix actually works.

It looks like the logging is currently having issues indirectly related to s3 whereby the "os.path.exists" call right after "import boto" is returning False in the current master. It seems like the files are never being created.
I have rebased this branch back to an older version that was working for us.

This PR is currently working to fix the s3:/ issue relating to a misuse of lstrip but there are other issues present in master which are preventing the log files from being written in the first place.


Builds stop with [info] Cancel request received, killing process

Not sure exactly what causes [info] Cancel request received, killing process.
Where does a notify come from? Does it have to come from inside a build container? There is not much in the logs to see other than just:
time="2015-11-16T13:00:42Z" level=info msg="closed event stream"
[GIN] 2015/11/16 - 13:00:42 | 200 | 1m7.560092745s | <IP_ADDRESS>:45388 |   GET     /api/stream/<organization/reponame>
time="2015-11-16T13:00:43Z" level=info msg="closed event stream"
[GIN] 2015/11/16 - 13:00:43 | 200 | 1m7.520039973s | <IP_ADDRESS>:46532 |   GET     /api/stream/<organization/reponame>
[GIN] 2015/11/16 - 13:00:44 | 200 | 1m1.754982222s | <IP_ADDRESS>:54234 |   GET     /api/stream/<organization/reponame>/12/1
time="2015-11-16T13:00:46Z" level=info msg="preparing container drone_build_13_notify"

Usually a build status is green when that happens.

It comes from the build container being shutdown un-expectedly. This could happen because someone hits the cancel button on the build, or the operating system is trying to kill your container (OOM, etc)
https://github.com/drone/drone-exec/blob/c9e59c4f91e93cc1540e86a02451ea224b47de69/main.go#L206

Interesting. I'll keep investigating. Just dumping some more info here. There are enough resources on the docker host to complete the build. I cannot see any other errors on the system, i.e. OOM killer, etc.
I am using a remote docker host over TCP and there is an ELB between drone and a single docker host.
 Depending on configuration ELB may kill network connections after 60 seconds, which could have negative upstream impacts

@bradrydzewski that's exactly what was happening. I increased the timeout to 30 minutes an the problem went away. Thanks!


Ensure all arguments to ipfs.add are documented

The trickle option is supported but not document. Add this option and verify all other available options are also documented.

@alanshaw
I'm on it.
Few clarifications needed:

What is the current default cidBase?
CLI version has (quite, quieter and silent), do they exist in web version also?

Is there any reference point in the codebase which can be looked up for the same. I could not find much so I am referencing CLI version and scraping other parts.


Documentation

Could we get documentation on each node please?

Not great but a good start: https://krazyjakee.github.io/nodot/index.html

All links in the main area are 404ing


Update salt.spec file for Redhat builds to include salt-syndic and salt-api usage with boot

On Redhat 6, salt-syndic's  '%postun syndic' is commented out, this should be uncommented.
Also need to add support for salt-api and salt-syndic, similar to salt-minion and salt-master for all pre and post conditions.

During development it was noticed that on Redhat 6 & 5, installation auto-enables with chkconfig. This is against Redhat's preferred practice and will be removed, Redhat 6 & 5 should operate similar to Redhat 7.
Installation installs but should not auto-enable.  Note that this is not the practice for Debian/Ubuntu where the preferred policy is to auto-enable and start on install.

Updated time since noticed that a service salt-X restart is leaving old salt-X processes behind

see https://github.com/saltstack/salt/issues/40068 to track grandchildren left behind.

@dmurphy18 I think the service left back is a known bug which I reported here
https://github.com/saltstack/salt/issues/40011
I don't think the startup script has anything to do with the minion not being shutdown properly although we might as well want to make sure that we don't depend on netstat  to show us what is running but ps or something similar.
Concerning the auto enable on startup, I would keep it and add it to rh7 too but its your choice. My opinion is that users are used to have salt-minion auto enabled hence there should be consistency between OSs.

@tsaridas Thanks for the information on saltstack/salt#40011
The auto enable on startup is against Redhat's preferred practices, but you have a point about leaving it as is for Redhat 6, for consistency with previous releases.
Given use of systemd on Redhat 7, I would prefer to do it right as it currently is with systemd.

Moving forward with the minor releases, salt-minion and salt-master will remain auto enabling on startup when they are installed on Redhat 6 & 5 since this functionality has been present since 8 Jan 2012.
Current functionality of Redhat 7 where they are not auto enabled on install shall be preserved.
In the next major release of Salt for Redhat 6 & 5, the auto enabling of salt-minion and salt-master shall be removed.

@dmurphy18 It looks like you have marked this as Done. Can it be closed?


Error: Authenticate error: unauthorized_client

Since yesterday I receive this error (plugin version 0.3.0), plugin has not been yet updated to the new authentication method, so I suppose Netatmo stopped possibility to use plugins based on user/password authentication. Anyone got this error also? Is there any workaround? I suppose lots of people use Netatmo data in their automations in NR. Thanks!

I also had the same problem yesterday. I can't get weather information anymore with plugin 0.3.0 to NodeRed.

Same problem, but node gives the data from Netatmo server :)

Sadly until first NR restart...

Restarted 5 days ago (have dockerized version).

Restarted 5 days ago (have dockerized version).

Have you tried to restart NR today? 5 days ago it worked even after the restart...

Same problem here... Also tried to restart NR but that didn't help.

same problem - help/update very much appreciated!

You can try this plugin for Netatmo:
https://github.com/guidone/node-red-contrib-netatmo-dashboard

You can try this plugin for Netatmo:
https://github.com/guidone/node-red-contrib-netatmo-dashboard

Already switched to that plugin - works without a flaw, all values (min, max, wind, rain) and no issues with refreshing token so far 🙏👍

I guess this one finally kicked in:  https://github.com/ssadams11/node-red-contrib-netatmo/issues/27 :-(

You can try this plugin for Netatmo: https://github.com/guidone/node-red-contrib-netatmo-dashboard

Thanks, it works :)

You can try this plugin for Netatmo: https://github.com/guidone/node-red-contrib-netatmo-dashboard

Thanks, it works :)

Yes, authentication works with that one - however: apparently it can only fetch current data - no history…

For history data you can use this script:
https://github.com/michaelmiklis/netatmo.sh/issues/4#issuecomment-1636814038

Thanks @S474N , but...
...I have a Java App (using https://github.com/lost-carrier/netatmo-api) which saves the last data received and retrieves everything newer. That proved to work very stable in grabbing the whole timeseries even if something boke down for some time.
Unfortunately that Java things now also stopped working due to Netatmo auth change. I wanted to use this opportunity to rebulid that process in NodeRed since that Java thingy tends to be a bit cumbersome to look into when only changing something every couple of years. But it looks like I will need dig into that thingy once again...

You can try this plugin for Netatmo: https://github.com/guidone/node-red-contrib-netatmo-dashboard

Thanks, it works :)

Yes, authentication works with that one - however: apparently it can only fetch current data - no history…

... and there you cannot request data from public Netatmo stations like with the node "get public data".
I used this to get rain data from other Netatmo installations in my area.
So I'm still waiting for an update which supports the new auth system with the refresh Token.

same problem here. Dashboard nodes work, but as mentioned above, they do not provide historical data retrieval. A pity that the new authentication has not been implemented to this node here yet. Maybe the code could be ported from dashboard node to this one here?

Same issue

Here also

same here


Dart calls the .so file, .so file refers to the problem caused by libc

Hello, I have a problem using dart FFI，Hope to get your help, thank you.
My dart version: 2.14.3 (stable).
My call steps are： dart -> dart ffi ->cpp- so, Is there any way to call the so method directly from dart FFI?
When I used dart FFI, I called the .so file, which also referenced the libc file, resulting in a crash, but there was no problem when testing on JNI.
Crash information
       #00 pc 00001cc0  /data/app/~~rJNPFlnxPPUIagiTotDJlw==/com.example.native_add_example-16AEQmN1WNlDRv1hslvyDw==/base.apk (offset 0x205d000)
       #01 pc 0005ad2f  /data/app/~~rJNPFlnxPPUIagiTotDJlw==/com.example.native_add_example-16AEQmN1WNlDRv1hslvyDw==/base.apk!libmiddleware_components.so (offset 0xfcd000) (tthread::thread::wrapper_function(void*)+10) (BuildId: c96748aeeb48296db015a5967a1eea4a755175c0)
       #02 pc 000ab7eb  /apex/com.android.runtime/lib/bionic/libc.so (__pthread_start(void*)+40) (BuildId: b3b27b88dfad1a88f83c4380d3183302)
       #03 pc 00063dcf  /apex/com.android.runtime/lib/bionic/libc.so (__start_thread+30) (BuildId: b3b27b88dfad1a88f83c4380d3183302)

Resolved due to naming conflicts in our so and dart


on repeat sim, won't use mex file

currently dsSimulate just uses the m file instead of the mex file on repeated local sims.

Does this mean it is re-compiling on every run? I haven't noticed this
myself (at least not on dev, as of yesterday)

what i'm seeing locally is that the first time it compiles and uses mex file, then if you rerun, it uses the non-compiled .m file. This follows the logic of the code i'm looking at.

Ok, I'll take a look
On Wed, Dec 5, 2018, 4:42 PM Erik A. Roberts<EMAIL_ADDRESS>wrote:

what i'm seeing locally is that the first time it compiles and uses mex
file, then if you rerun, it uses the non-compiled .m file. This follows the
logic of the code i'm looking at.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/DynaSim/DynaSim/issues/542#issuecomment-444660879,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFL_SRQl3Q8k5aKkbSAQwoYs4a1j7qSkks5u2D3ZgaJpZM4ZDa4O
.

fixed need to commit

Ok, nice
On Fri, Dec 7, 2018, 3:36 PM Erik A. Roberts<EMAIL_ADDRESS>wrote:

fixed need to commit
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/DynaSim/DynaSim/issues/542#issuecomment-445357812,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFL_Sbb6Vc0GX1a1yuVze1LKdyeDdWVIks5u2tE1gaJpZM4ZDa4O
.


Move driver graphics out of main package

Remove the pixelgl import from the main package.
This enables alternative graphical drivers.

I remember pixelgl requires to take over the main function.🤔 I
will check this in few days.

Yes, this patch does not change the thread it runs on, it just launches the pixelgl only if required. It moves the pixelgl runner to later in the code but still on the main thread. I tested this with an alternative (Fyne) graphics system that also requires starting from the main thread.


Fix double-signal issue

Previously the server would take two Ctrl+C's to shut down - one to
trigger the logic in goreman.go (and shut down the RPC server), the
second to trigger the logic in startProcs. We should only handle
incoming signals in one place, instead of two - refactor the logic to
handle this case.
(I missed this during testing because we don't have tests around the
main function, only around the start/startProcs functions.)

Thanks.


Update for registry.xml and error/success messages

added in honey file creation for registry.xml and updated error/success handling and messaging.

Sorry - wanted to make one additional small edit and update the error message so that it matches the success message and provides path and endpoint information.


Unable to disable automatic layout using struturizr lite docker image

I'm running the structurizr lite docker image locally using:
docker run -it --rm -p 8080:8080 -v $PWD:/usr/local/structurizr structurizr/lite
and then editing workspace.dsl to the sample to the basic example in the language reference
workspace {

    model {
        user = person "User"
        softwareSystem = softwareSystem "Software System" {
            webapp = container "Web Application"
            database = container "Database"
         }

        user -> webapp "Uses"
        webapp -> database "Reads from and writes to"
    }

    views {
    	theme default
    }

}

When I render it on localhost:8080 I can't edit  because This diagram is not editable because automatic layout is enabled. However the dsl contains no autoLayout option. I can see autoLayout in workplace.json but if I remove that, it is overwritten and recreated again.

See https://github.com/structurizr/dsl/blob/master/docs/language-reference.md#autolayout ... you'll need to use a script to disable automatic layout, or define the views yourself.

Thanks. If I replace the existing:
    views {
    	theme default
    }

with:
    views {

        styles {
            element "Software System" {
                background #1168bd
                color #ffffff
            }
            element "User" {
                shape person
                background #08427b
                color #ffffff
            }
        }
    }

I still have the same issue. Does that not constitute defining a view?

It doesn't ... you're not actually defining any views inside the views block. See https://github.com/structurizr/dsl/tree/master/docs/cookbook/system-context-view for an example.

Ahh right. Thanks


even out CI runner times

@bors r+

:pushpin: Commit abe989a49eb31f836614a9e3eed55d5a9322f5aa has been approved by RalfJung
It is now in the queue for this repository.

@bors r+

:pushpin: Commit f6ea1254999369c3df9d77477476ae3fbe6a2712 has been approved by RalfJung
It is now in the queue for this repository.

@bors r+

:pushpin: Commit 7590c8b98c4ecdf6c6de2bc50630146bbf632570 has been approved by RalfJung
It is now in the queue for this repository.

:hourglass: Testing commit 7590c8b98c4ecdf6c6de2bc50630146bbf632570 with merge a8f3116a48977efe086c815f17404df89c7d6f71...

:sunny: Test successful - checks-actions
Approved by: RalfJung
Pushing a8f3116a48977efe086c815f17404df89c7d6f71 to master...


pr for user id checking in game, and removing a single comma for the default config json

I'm not sure what this is meant to be doing, apart from deleting messages from the last 2 authors in the channel. Why?

wait this is the minecraft game chat
oops i meant for the other thing, i'll correct that now

I think the point of the game is to allow people to make that mistake, catch it out and reset the game. So having the bot correct it goes against the spirit.
What the bot should do is instead have a /chatgamereset <number> <reason> command that can be used by people in a prescribed group (ie Helper) to:

Record  and the current date into the store
Clear out the entire channel messages
Set a message on why the game has reset
Announce what the last game reached
Announce what the highest score is from the store and the date achieved


[Improvement] - Added Disabled mode

Was added the disabled mode to the entire component and tested in the storybook
Disabled: true

Disabled: false

@CrafterSama Thanks for the PR merging w/ #9 since there were few cleanup required as well


fix: open directory from webui

Actions
Closes #1287
Notes
During some electron update, this function was probably left behind and didn't change from using callbacks to promises.

@rafaelramalho19  this is super important fix, thank you!
Ping me tomorrow and let's have a patch release party on Zoom to ship this fix as v0.11.2 :ship:
(we'll go over steps at https://github.com/ipfs-shipyard/ipfs-desktop#releasing together. now that we figured out notarization it should not take more than 1h)

@lidel
Pulling all the translations mentioned here would be awesome :)

I know.. will try :sweat_smile:
For sure we will update translations for Desktop itself, but may decide to not update webui ones, as that requires new release of webui + updating and releasing IPLD explorer deps, bubbling up everything, and that may be a time sink delaying this hotfix till next week, which we want avoid.


Python 3.12 Support

With the currently pinned sentencepiece version, this project can not be run on python 3.12
https://github.com/helpmefindaname/transformer-smaller-training-vocab/blob/90a2d498559505dd3e73a35f3fa1620792f82827/pyproject.toml#L15C1

Hi @b3n4kh and thank you for your report.
I have updated the dependencies and the testing to ensure python 3.12 compatibility.
Version 0.4.0 now has active python 3.12 support


Can't run terraform after installing the tfv install

Hello, very great idea for this package. I was able to install this package easily but when I try to run the terraform version afterwards, it says "'terraform' is not recognized as an internal or external command". Am I missing something? Thanks

Hello Kelvin. Thanks for the compliment.

Did you run tfv use <VERSION> after the installation?
What are the commands you ran?

This issue is closed as there has been no response after 2 weeks.


Load multiline env var from external file for debugger failed in fish shell

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

VS Code Version: 1.88.1
OS Version: macOS Sonoma 14.4.1 (23E224)

https://code.visualstudio.com/docs/nodejs/nodejs-debugging#_load-environment-variables-from-external-file
Steps to Reproduce
Install fish shell and have it working with VS Code. Go to user settings, change "Terminal > Integrated > Default Profile: Osx" to an installed fish shell.
Follow Load environment variables from external file and set up a .env file with a single multiline env var MYENV="foo\nbar".
Create an app.js with console.log(process.env) (not essential to reproduce the bug, just to demonstrate the correct behaviour).
Create the following launch.json configuration:
{
  "version": "0.2.0",
  "configurations": [
    {
      "name": "test",
      "type": "node",
      "request": "launch",
      "args": [],
      "cwd": "${workspaceFolder}",
      "program": "${workspaceFolder}/app.js",
      "console": "integratedTerminal",
      "envFile": "${workspaceFolder}/.env",
    },
  ],
}

Expected
The console will log env vars with MYENV shown to be correctly ingested. For example, when using zsh, the correct single command is run till completion:
> cd <<project_folder>> ; /usr/bin/env 'lines=foo
quote> bar' 'NODE_OPTIONS= --require "/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/ms-vscode.js-debug/src/bootloader.js"  --inspect-publish-uid=http' 'VSCODE_INSPECTOR
_OPTIONS=:::{"inspectorIpc":"/var/folders/x3/_z626cj108sdszn1f9bs8b1m0000gn/T/node-cdp.43848-5e183c87-146.sock","deferredMode":false,"waitForDebugger":"","execPath":"/Users/shaowei/.nvm/version
s/node/v20.10.0/bin/node","onlyEntrypoint":false,"autoAttachMode":"always","fileCallback":"/var/folders/x3/_z626cj108sdszn1f9bs8b1m0000gn/T/node-debug-callback-576db9a978f1245e"}' /Users/shaowe
i/.nvm/versions/node/v20.10.0/bin/node ./app.js

Debugger attached.
<<env vars printed below>>
{
  ...
  MYENV: 'foo\nbar',
  ...
}
Waiting for the debugger to disconnect...

Actual
The debugger hanged as the \n causes fish shell to run it as 2 separate commands instead. For example the following:
> /usr/bin/env 'lines=foo'

> bar' 'NODE_OPTIONS= --require "/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/ms-vscode.js-debug/src/bootloader.js"  --inspect-publish-uid=http' 'VSCODE_INSPECTOR_OPT
IONS=:::{"inspectorIpc":"/var/folders/x3/_z626cj108sdszn1f9bs8b1m0000gn/T/node-cdp.43848-03d5fa0a-141.sock","deferredMode":false,"waitForDebugger":"","execPath":"/Users/shaowei/.nvm/versions/no
de/v20.10.0/bin/node","onlyEntrypoint":false,"autoAttachMode":"always","fileCallback":"/var/folders/x3/_z626cj108sdszn1f9bs8b1m0000gn/T/node-debug-callback-7fa737160ba19e11"}' /Users/shaowei/.n
vm/versions/node/v20.10.0/bin/node ./app.js

I can't reproduce this; the default fish install seems to handle line breaks within quotes without issue:


Upgrade to Webpack v4

Problem
Slate v1 is now running a dated version of Webpack. Let's migrate to the newest version to take advantage of the performance improvements and features.

Migrated in https://github.com/Shopify/slate/pull/450


Add a dummy .copy() method on dask arrays?

There's no need to copy the data in dask arrays, because they're (currently) immutable. Still, it's common to copy numpy arrays to be on the safe side, so it might be nice to add this for duck-array compatibility.

I would be fine with this.  Might want a pretty explicit note in the docstring about how this is a no-op and only for compatibility reasons.


ModalDialog Tests

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 1 (0.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.9%) to 75.733%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

AuthoringTool/PresentationLogic/ModalDialog/ModalDialogInputFieldsFactory.cs
0
1
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.9%

Covered Lines:
3612

Relevant Lines:
4655

💛  - Coveralls


a parameter cannot be found that matches parameter name 'Directory'.

Using the latest update fuzzydir https://github.com/sibwaf/mpv-scripts/commit/91b147ff34bd743caa28e6cfc6f3ff430cbd0e81
Watching YouTube on mpv.

That's interesting, could you please share the whole log?

[  10.929][e][fuzzydir] Get-ChildItem : A parameter cannot be found that matches parameter name 'Directory'.
[  10.929][e][fuzzydir] At line:1 char:76
[  10.929][e][fuzzydir] + ... s = Get-ChildItem -LiteralPath "https://www.youtube.com/." -Directory
[  10.929][e][fuzzydir] +                                                                ~~~~~~~~~~
[  10.929][e][fuzzydir]     + CategoryInfo          : InvalidArgument: (:) [Get-ChildItem], ParameterBindingException
[  10.929][e][fuzzydir]     + FullyQualifiedErrorId : NamedParameterNotFound,Microsoft.PowerShell.Commands.GetChildItemCommand
[  10.929][e][fuzzydir]

Try the latest commit on master, should be fixed.
Also would be great if you could try running mpv --msg-level=fuzzydir=debug URL_HERE and share the result to check if the new logs are helpful.

[   4.748][v][fuzzydir] External command failed with status 1: powershell -NoProfile -Command             $dirs = Get-ChildItem -LiteralPath "https://www.youtube.com/." -Directory
[   4.748][v][fuzzydir]             foreach($dir in $dirs) {
[   4.748][v][fuzzydir]                 $u8clip = [System.Text.Encoding]::UTF8.GetBytes($dir.Name)
[   4.748][v][fuzzydir]                 [Console]::OpenStandardOutput().Write($u8clip, 0, $u8clip.Length)
[   4.748][v][fuzzydir]                 Write-Host ""
[   4.748][v][fuzzydir]             }
[   4.748][d][fuzzydir] Get-ChildItem : A parameter cannot be found that matches parameter name 'Directory'.
[   4.748][d][fuzzydir] At line:1 char:76
[   4.748][d][fuzzydir] + ... s = Get-ChildItem -LiteralPath "https://www.youtube.com/." -Directory
[   4.748][d][fuzzydir] +                                                                ~~~~~~~~~~
[   4.748][d][fuzzydir]     + CategoryInfo          : InvalidArgument: (:) [Get-ChildItem], ParameterBindingException
[   4.748][d][fuzzydir]     + FullyQualifiedErrorId : NamedParameterNotFound,Microsoft.PowerShell.Commands.GetChildItemCommand
[   4.748][d][fuzzydir]
[   4.748][d][fuzzydir]
[   4.748][d][fuzzydir] Unable to scan https://www.youtube.com/., skipping

Yep, seems good, thanks.
Just to be sure - the script does still work with regular files, right? I'm still a bit confused by the "NamedParameterNotFound" error, it shouldn't look like this.

Working fine with local files


Enable copy_file_range when it is available.

Changes:

fix the mistake in scripts/genconfig.sh;
syscall(__NR_copy_file_range ...) is more suitable, as there is not a copy_file_range in bionic.
Even compiled with glibc, toybox cannot use copy_file_range easily, as we must define _GNU_SOURCE before include unistd.h first time.

Test:

dd if=/dev/urandom of=src.bin bs=4M count=1000
ln -s toyobox cp
./cp src.bin dst.bin
sha256sum src.bin dst.bin

Did you run "make tests"? Because the cp tests are failing after this.

Did you run "make tests"? Because the cp tests are failing after this.
@landley I have fixed the problems caused by the first patch. "make tests" pass on my environment now.

There are two mistakes in the first patch:

I ignored that sendfile_len supports parameter bytes be negative;
copy_file_range cannot work when either in or out is not a regular file;

syscall(__NR_copy_file_range ...) is more suitable, as there is not a copy_file_range in bionic.

feel free to report bionic bugs like this at https://github.com/android/ndk --- i could have sworn we'd added this already, but you're right; all we have is a "seccomp hole" so that it's possible to make the syscall without being killed. i don't even appear to have filed a bug myself to add this...

I already applied it locally and I kept the syscall() because glibc requires you to #define GNU_GNU_ALL_HAIL_STALLMAN_FTAGHN to get the linux system call wrapper, which is silly. (I'd have poked you otherwise, but glibc was already broken. I made puppy eyes at Rich to add _ALL_SOURCE which just enables all the darn feature test macros, but glibc still wants to gate Linux system calls on The Hurd for some reason. Well, ok, we know the reason, it was https://sourceware.org/legacy-ml/libc-announce/2001/msg00000.html#:~:text=Stallman but it's still really stupid.)
But I haven't pushed the yet because https://github.com/torvalds/linux/commit/f16acc9d9b376 from 2019 talks about adding "basic sanity checks", which seems to boil down to capping the length at INT_MAX-PAGE_SIZE. That's well within the 7 year horizon and since the code's already in the read/write loop handling length returns, I thought I'd do a follow-up commit capping len at 1<<30 or so per copy_file_range() call?

Try 9b368059deec.

I already applied it locally and I kept the syscall() because glibc requires you to #define GNU_GNU_ALL_HAIL_STALLMAN_FTAGHN to get the linux system call wrapper, which is silly. (I'd have poked you otherwise, but glibc was already broken. I made puppy eyes at Rich to add _ALL_SOURCE which just enables all the darn feature test macros, but glibc still wants to gate Linux system calls on The Hurd for some reason. Well, ok, we know the reason, it was https://sourceware.org/legacy-ml/libc-announce/2001/msg00000.html#:~:text=Stallman but it's still really stupid.)
But I haven't pushed the yet because torvalds/linux@f16acc9d9b376 from 2019 talks about adding "basic sanity checks", which seems to boil down to capping the length at INT_MAX-PAGE_SIZE. That's well within the 7 year horizon and since the code's already in the read/write loop handling length returns, I thought I'd do a follow-up commit capping len at 1<<30 or so per copy_file_range() call?

Linux kernel will limit the max size to 0x7FFFF000 in vfs_copy_file_range.


Polish commutes protocol

Add SupportsCommutes class
Rename cirq.linalg.commutes to cirq.linalg.matrix_commutes to avoid ambiguity
Simplify the signature of commutes and commutes_with_qid (no keyword force, atol not optional) to make it easier for implementors
Add a fallback commutes strategy based on computing unitaries for pairs of operations touching up to 10 qubits (obsoleting some of the code in GateOperation)
Rename protocols/commutes.py to protocols/commutes_protocol.py to avoid name collision with the method
Rename protocols/unitary.py to protocols/unitary_protocol.py to avoid name collision with the method

Code like this now works, with no programming effort needed from the cnot class itself:
a, b, c = cirq.LineQubit.range(3)
assert not cirq.commutes(cirq.CNOT(a, b), cirq.CNOT(b, c))
assert cirq.commutes(cirq.CNOT(a, b), cirq.CNOT(c, b))

Should probably update the signature of cirq.contrib.acquaintance.permutation.SwapPermutationGate._commutes_ for consistency.


feat: add ability to make Python available as Jupyter Kernel

Have you read the Contributing Guidelines?
Issue #
Changes description
Adds ability to make installed Python interpreters available as Jupyter Kernel

I use the path there, because I need to include the role while running converge with molecule
I will check if I can do something with it


[FEATURE] prevent getting results for gradient border if there is no input

Description
Users are allowed to click on results even if there's no input given to the generator:
Tasks:

[ ]  add an error indicator for if the button is clicked and there's no input, look at the gradient text generator for an example
[ ] change the background of the get results button to be gray, if there's no input yet

Screenshots

Additional information
No response
👀 Have you checked if this issue has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Contributing Guidelines?

[X] I have read and understood the rules in the Contributing Guidelines

Are you willing to work on this issue ?
None

Hi @Dun-sin, can you assign it to me?

Hi @Dun-sin, can you assign it to me?

Why are you picking up the issues from my projects, it makes it look like a spam. You got to pick one and do it well

As the community guidelines said you need to get assigned before work, that's why i poke you earlier

As the contributing guidelines said you need to get assigned before work, that's why i poke you earlier

That's not what I'm talking about, read my previous message again

okay got it and apologies for that, assign me to this one. I'll remove the comment from there

:tada: This issue has been resolved in version 2.64.5 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket: