Blacklist function

Allow users to send a command to prevent the bot from interacting with them in any way. Allow the owner to do this for others.
Also support blocking subreddits so users don't get denied messages by posting there.

Still need to,

[ ] Don't send reminders if blacklisted
[ ] Add link for public comment and message in response to public comment offering to blacklist


Add "kid" field to the generated JWT

Add a key id field ("kid") to the generated JWT.  To calculate the key
id, we:

Load the public key that's associated with the signing key.
Convert the public key to a JWK.
Calculate the thumbprint of the JWK, as specified in RFC 7638.

Opening another PR.


Update cross-tenant-mailbox-migration.md

The name of the script was incorrect, changed it to SetupCrossTenantRelationshipForResourceTenant.ps1 matching the script in Github.

@JohanFreelancer9 Please copy review

@JohanFreelancer9 Please copy review

Issue#https://github.com/MicrosoftDocs/microsoft-365-docs/issues/3962

Issue#https://github.com/MicrosoftDocs/microsoft-365-docs/issues/3962


move DB update functions to dispatcher

[ ] I have added the tests to cover my changes.
[ ] I have updated the documentation and CHANGELOG accordingly.
[x] I have read the CONTRIBUTING document.

@scottwn we just pulled develop branch and noticed that we could not dispatch workflows and traced them back to this PR. I just wanted to know if this is happening on your side as well. Kindly let me know if this is the case.

#1322 is tracking the resolution


fix(Types): fix received component prop types

The received component should not have HookRet as part of its initial props. HookRet should only be added to the resulting component

Codecov Report

Merging #2 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master     #2   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           1      1
  Lines           7      6    -1
  Branches        1      1
=====================================
- Hits            7      6    -1

Impacted Files
Coverage Δ

src/index.tsx
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Suppress/fix compiler warnings

This resolves #467

Merged w/https://github.com/spring-cloud/spring-cloud-stream/commit/6c442b7421c58b963cdf10ede9e52f16214a9a5b


DYN-6628 Update sign in button tool tip on sign in/sign out

Did we lose these changes somehow?

No. In my earlier work I added the tootip but they would not update with change in sign in status. With this change the tooltip should update with sign in status.


allowChangeCamera(false) this method is not available.I want hide camera change image

[ ] I have verified there are no duplicate active or recent bugs, questions, or requests
[ ] I have verified that I am using the latest version of Material Camera.
[ ] I have given my issue a non-generic title.

Include the following:

Material Camera version: 0.2.13
Device OS version: 7.0
Device Manufacturer: Huawei
Device Name: Nexus 6P

Also, please wrap Java with correct syntax highlighting.
System.out.println("Hello, world!");

Reproduction Steps

Expected Result
Actual Result

Any updates on this?

me too facing this.

me too...


Feature/allow component url to be set per site ams

Description
Please include

a summary of the changes
relevant motivation and context
a list of any dependencies that are required for this change

Issue reference
Fixes # (issue)
Type of change
Is it a new feature, bug fix, code improvement, etc.
If it is a breaking change what needs to be done to fix that
Documentation
Is the documentation updated, maybe a link
Tests
(How) has the change been tested
Branch
If the branch to merge to is not development

https://github.com/openstad/openstad-frontend/pull/419


Consider putting bucket paths outside the script

Relates to #1
Maybe as env variable. Maybe target path (workspace) also deserves that.

Done due to change in approach for handling workflow


Client requests cause assertion error

Details
When I tried to run test_client example I got following assertion error

Assertion failed: c && c->htp && c->request && c->parser && bev (htp__connection_writecb_: libevhtp/evhtp.c:2165)

Seems the reason of this is that a client connection is every time created with evhtp_t equal to NULL, like on line 5173 in evhtp.c
  if (!(conn = htp__connection_new_(NULL, -1, evhtp_type_client)))
  {
      return NULL;
  }

And there is an assertion in evhtp.c on line 2165
evhtp_assert(c && c->htp && c->request && c->parser && bev);
So with client request c->htp is every time NULL and assertion fails.
Steps or code to reproduce the problem.
Simply run test_client.c
Version
Latest libevhtp version.

Client support has always been lacking; I know I know. @errzey was fairly upfront about libevent having a better client API. But I think this should change :)
I am handing this off to a great engineer who will be assisting me in further development. And will have you a fix ASAP!
Thank you very much!

I'll get on this, and include test cases to validate the fix.
Thanks,
Dan

Thanks a lot for this! I'm also able to work on a solution if you need any help.

Thanks @sftwrngnr! Going to review the pull request tonight and have a release made.

#46 has now turned into a refactor due to this issue :)

OK, changes have been merged into develop. Thank you for your input!


Merge remote-tracking branch 'origin/CB-2.34.0'

See detailed description in the commit message.

just sending this to CB-2.35.0 instead of master


common/model/tests: the transaction test case is incomplete.

testing read/write action is needed on the transaction object.

Closed by #818


doNothing() cannot be used on suspend Unit functions

Mocking Unit method where the first call should doNothing() and then 2nd doThrow(), produces the following error:
Only void methods can doNothing()!
Example:
doNothing().doThrow(RuntimeException::class.java).whenever(mock).foo() where foo() is suspend fun foo().

Mockito.doNothing() and its related Stubber functions are provided as a workaround for "rare occasions when you cannot use Mockito.when(Object)". One example is stubbing methods that return Void: the Java compiler doesn't allow Void inside brackets.
In this case, you're not returning Void, you're returning Unit, and you're better off returning to the non-workaround solutions: whenever(mock.foo()).thenThrow(RuntimeException::class.java) is allowed.

Oh yeah, I can't believe I missed that. Unit after all is just an object...
Thanks a lot! :)

i did something like this
when(foo.save("key", "value")).thenReturn(Unit)

@nhaarman In my case, when a suspend function of a mocked or spied object is called, I don't want it to do whatever it has inside. So its like doNothing but that now for functions that return a Unit. But now it does not work as specified above. Any workaround for this?

@iadcialim could you please share you gist?

@radityagumay I believe this is the problem that @iadcialim is facing:
class StubSuspendingTest {
    @Test
    fun `stubbing on suspending unit`() = runBlocking {
        val testSubject: SomeClass = spy(SomeClass()) // NOTE: spy vs mock

        whenever(testSubject.suspendingUnit()) // this calls the actual method impl
            .thenReturn(Unit)
            .thenThrow(RuntimeException("Foo"))

        assertEquals(Unit, testSubject.suspendingUnit())
        try {
            testSubject.suspendingUnit()
        } catch (error: Throwable) {
            assertEquals("Foo", error.message)
        }
    }
}

interface SomeInterface {
    suspend fun suspendingUnit(): Unit
}

class SomeClass : SomeInterface {
    override suspend fun suspendingUnit() {
        TODO("not implemented")
    }
}

@iadcialim You can use
doReturn(Unit).whenever(spy).functionReturningUnit()

which does not execute functionReturningUnit() as
whenever(spy.functionReturningUnit()).thenReturn(Unit)

would.


Fix function-no-unknown false negatives for functions with namespace

Since Stylelint 15.8.0, the built-in function-no-unknown rule has ignored SCSS functions with namespace.
For example, the following code unexpectedly passes with Stylelint 15.8.0:
a { color: color.unknown(#fff); }

Notes:

This change keeps backward compatibility. This means not to change peerDependencies.stylelint in package.json.
This change may bring performance penalty to keep backward compatibility.
Run npm i<EMAIL_ADDRESS>&& npm t to test this change with newer versions of Stylelint.

See also:

https://github.com/stylelint/stylelint/releases/tag/15.8.0
https://github.com/stylelint/stylelint/pull/6921

This Pull Request should resolve the CI failure in PR #873.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

24 of 25 (96.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.008%) to 91.954%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/rules/function-no-unknown/index.js
24
25
96.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.008%

Covered Lines:
2960

Relevant Lines:
3136

💛  - Coveralls


C6 Migration

One of our last tasks for Q4 OKRs!
After some back and forth with Stripe, here's the best way to make this happen. Order of operations is important to avoid accounting confusion.

[x] Switch host of all existing collectives from cID9805 to cID11004

[x] run query to update HostCollectiveId in Collectives table where currently it's 9805
[x] run query to update MemberCollectiveId in Members table where role is HOST

[x] (Immediately after the first task) Run our script to move all existing Shared Customer subscriptions to new Host

-- Rest of tasks can happen with some delay --

[x] Ask Stripe to move CustomerIds over for remaining subscriptions
[x] Stripe copies customerIds over
[ ] Run another script to move all non-shared customer subscriptions to new Host

Quick update:

Moved all open source projects to new host.
Migrated 570 subscriptions over
Waiting on Stripe to migrate the rest (1455 remaining)

Most of the subscriptions are moved over. 13 subscriptions remaining on old account. Will investigate over the weekend.

Deleted 13 subs both in Stripe and our db that didn't transfer over to c6.
Moved 230 subscriptions back to original connected account (for hostCollectiveId 8674) - these were subscriptions for non-open source projects like Rails girls, chsf, etc.
Through the migration, we lost around 20 or so legitimate subscriptions (where credit card had expired or was declined).
Also discovered lots of edge cases like subs that were cancelled in our db but not on stripe. $0 subscriptions, $0.01 subscriptions, etc.
As far as I can tell, this is complete. Now we'll monitor stripe webhooks in next couple of days to make sure everything is running smoothly.


gnupg22: fix reproducibility issue by applying a debian patch

Motivation for this change
Fix reproducibility issue https://r13y.com/diff/5ae313d84d3caae035453d7e836ff94edd138fcff46e7016f41af21449903bc8-0e93c0924922147c281f79a1639de83aeb0a20ca4ecc9791ac0cdbd9fc1a8363.html
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

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

@GrahamcOfBorg eval

@fridh it seems this causes a lots of rebuilds - should I target this for the staging branch?

go for it

there seems to be another PR https://github.com/NixOS/nixpkgs/pull/87908/files, not sure of it but a patch sounds nicer

Rebased to staging

Let's use the SOURCE_DATE_EPOCH approach instead.


scan-build doesn`t get the null pointer

ubuntu16.04, scan-build ver 3.8
in 04-static-analysis/clang-analyzer, cmake is normal, but in make progress, the expected "null pointer" didn`t get out, instead there is a "iostream file not found"

Anybody knows why?

It's possible that different versions of scan build report different errors. Once you can call scan build and see results from it then your project is setup correctly


Friends can't connect

Friend cmd:
[Warning: Unity Log] [Netcode] NetworkObject (4) children not resolved to parents by the end of frame [Info   : Unity Log] soumdmanager: True; False
My cmd:
[Info   : Unity Log] Connection approval callback! Game version of client request: 10000,76561198371569085 [Info   : Unity Log] Joining client id: 1; Local/host client id: 0 [Info   : Unity Log] Approved connection?: True. Connected players #: 1 [Info   : Unity Log] Disapproval reason: [Warning: Unity Log] [Netcode] Deferred messages were received for a trigger of type OnSpawn with key 0, but that trigger was not received within within 1 second(s).
This happened after updating to: 2.0.9

Hey, could you reply with your profile code so I'm able to replicate and fix this?
The messages look unrelated to the changes, but I can take a look in case I did inadvertedly added this bug in.

seems not only yours mod makes this error. We disabled all then enabled one by one.
018f9721-355b-3fa9-2868-f2b575accb70

I'm unable to replicate this on my end after using that profile code, adding in my mod + dependencies, and trying to host + join a lobby (no errors in console either).
I did notice dependencies were missing from some mods like no CSync and ToystoreInterior for Wesley's moons. Perhaps it's caused by this?
Unless it's narrowed down to this mod in particular, I'm closing this issue for now, since like I said, the logs you've shown don't seem to be related to the code affected by this mod anyway. Do let me know if this is shown to be worng ofc, with logs like you've done before, and I'll reopen if it looks like there is an issue after all.


pythonPackages.pytesseract: init at 0.2.5

Motivation for this change
Simple python wrapper for Tesseract, an OCR engine to detect and read
text from images.
See https://pypi.org/project/pytesseract/
cc @divb
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

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

@GrahamcOfBorg build pythonPackages.pytesseract python3Packages.pytesseract

Success on x86_64-linux (full log)
Attempted: pythonPackages.pytesseract, python3Packages.pytesseract
Partial log (click to expand)
reading manifest template 'MANIFEST.in'
writing manifest file 'pytesseract.egg-info/SOURCES.txt'
running build_ext

----------------------------------------------------------------------
Ran 0 tests in 0.000s

OK
/nix/store/4hxkpz36r5207lws8zmrqmd19qsy6qi3-python2.7-pytesseract-0.2.5
/nix/store/pf7zsg5q1kqarkl3bw5cm30rpw905rxm-python3.7-pytesseract-0.2.5

Success on x86_64-darwin (full log)
Attempted: pythonPackages.pytesseract, python3Packages.pytesseract
Partial log (click to expand)
reading manifest template 'MANIFEST.in'
writing manifest file 'pytesseract.egg-info/SOURCES.txt'
running build_ext

----------------------------------------------------------------------
Ran 0 tests in 0.000s

OK
/nix/store/n74qiy3ym38p895bm2mhxw7h296yhj0a-python2.7-pytesseract-0.2.5
/nix/store/1m9ai1lv2h8jkwv53r27nx62833q74vm-python3.7-pytesseract-0.2.5

Success on aarch64-linux (full log)
Attempted: pythonPackages.pytesseract, python3Packages.pytesseract
Partial log (click to expand)
reading manifest template 'MANIFEST.in'
writing manifest file 'pytesseract.egg-info/SOURCES.txt'
running build_ext

----------------------------------------------------------------------
Ran 0 tests in 0.000s

OK
/nix/store/fq78m03sjf80hvhwfrmgm1jgypnf0by7-python2.7-pytesseract-0.2.5
/nix/store/vxn8nxgwvwrnxkhxpwmyfmkqmbaaj0ry-python3.7-pytesseract-0.2.5

Ran 0 tests in 0.000s

No tests are found. Either the test runner cannot find tests and needs to be patched, or there simply are no tests in which case the tests need to be disabled. Do include a comment explaining why the tests are disabled.

@FRidh thanks, fixed :)


Minikube deploy_doc uses undefined phases

It's using undefined deploy_doc phases!
See this section of the documentation for which phases are supported (and why these are needed in the first place)

I think it makes more sense to merge minikube into the k8s docs, otherwise subsequent steps might get lost and it'll be harder to keep them in sync.

plus I don't think we can test minikube on travis or aws, but if we know the other k8s deploy doc works than we can be pretty sure minikube will


Disable sampling when temperature=0

Feature request
As discussed, temperature=0 should be equivalent to disabling sampling
Motivation
As a way to get deterministic results
Your contribution
/

Hi! I'm a new contributor looking to get started with this issue. I had a few small questions about the scope of the changes before I get started.
First, to clarify I'm on the right track, sampling is referring to choosing the next token according to the appropriate logit/probability distribution. This makes me think the changes would go in the NextTokenChooser (and possibly HeterogeneousNextTokenChooser?) classes.
Secondly, would it be best to implement this by changing the setting of flags like sampling (Line 78, server/lorax_server/utils/tokens.py and the do_sample flags (Lines 255-261, same file) to have logic checking for if temperature == 0 ?
Let me know if this seems like a good starting approach.

Hey @akelch11, thanks for looking into this!
I believe you're on the right track. Here are few things off the top of my head we would want to change:

I would change the temperature check in tokens.py to include a check for temperature != 1 or temperature != 0 when setting has_warpers.
Just below line 78, If sampling and temperature == 0 then I would raise a warning saying that sampling will be disabled due to setting temperature == 0, then I would override sampling = False.
Changing the checks for lines 255-261 is a good catch! I agree that would also need to be changed to check x != 1 or x != 0.
The temperature validation check in validation.rs would need to change to temperature < 0.

There might be a few other gotchas, but those should be the main ones. Thanks for contributing!


Enhance Transactional Methods for Improved Request Queue Handling

Motivation:
The current Transaction Methods implementation lacks consideration for the request queue, resulting in potential undefined behavior and issues.
Modifications:
Transaction Methods properly respect the request queue.
Result:
Bug resolved.
Enhanced stability and reliability.

Maybe we should check the state in RequestQueue instead, I created a ticket #183 for that.


Stuck at Solving Captcha

After i solve the captcha, it wont continue. i believe it cant detect the selector

I just tested it and didn’t encounter any issues. Please try again, and if the problem persists, send some screenshots or provide more details.

ima clone the source one more time and try again, if it still wont work i can record a video

any news?

The captchas are so hard and so long for me. I don't even have time to solve them.

If the captchas are excessively difficult or too frequent, don't bother solving them. In any case, the account will likely be of low quality due to evident issues with the IP, browser, or fingerprint. I just tested the bot and encountered no problems with captchas


Checksum in scan4all-*-checksums.txt for 2.8.5 is incorrect

Thank you for your great project!
I found the checksum in scan4all-linux-checksums.txt is incorrect.
cdc1088016c0b15519710de186bd8d57f8de693049e9279f45c6f5d5993a1396  scan4all_2.8.5_linux_amd64.zip

scan4all_2.8.5_linux_amd64.zip
$ sha256sum scan4all_2.8.5_linux_amd64.zip
b34508789f73990ff11989c3bede26a47114c9d5b8f8de12fbf73a7c7ecc1daa  scan4all_2.8.5_linux_amd64.zip

The checksum in scan4all-linux-checksums.txt is different from the checksum of scan4all_2.8.5_linux_amd64.zip.
Expected content of scan4all-linux-checksums.txt is
b34508789f73990ff11989c3bede26a47114c9d5b8f8de12fbf73a7c7ecc1daa  scan4all_2.8.5_linux_amd64.zip

Not only scan4all-linux-checksums.txt, but also scan4all-mac-checksums.txt is incorrect.
$ sha256sum scan4all_2.8.5_macOS_amd64.zip scan4all_2.8.5_macOS_arm64.zip
ccd874a283defad6a0deb11377cb9d6024cb5946b46f61f36008e0afe9db4950  scan4all_2.8.5_macOS_amd64.zip
73028ba0042fa0fdc59b535bff50ffbf003f9f086bf41e0112869ed7903f375c  scan4all_2.8.5_macOS_arm64.zip

$ cat scan4all-mac-checksums.txt
2c5baf458432810098fd6c41c9ee64be9627051a5769c078d142b32e10e96959  scan4all_2.8.5_macOS_amd64.zip
76c08a33bf6a3fee51f83bd72d7416a6afb15f4676a2341ad3bd4fa05aedfe92  scan4all_2.8.5_macOS_arm64.zip

Thanks, the hash check has been updated now
grateful


feat: support SCM API to worker host

Types

[x] 🎉 New Features

Background or solution

Changelog
support SCM API to worker host

Codecov Report

Merging #596 (368f60d) into main (58b998d) will decrease coverage by 0.11%.
The diff coverage is 57.14%.

@@            Coverage Diff             @@
##             main     #596      +/-   ##
==========================================
- Coverage   59.09%   58.98%   -0.12%
==========================================
  Files        1207     1208       +1
  Lines       74402    74618     +216
  Branches    15436    15461      +25
==========================================
+ Hits        43971    44014      +43
- Misses      27742    27900     +158
- Partials     2689     2704      +15

Impacted Files
Coverage Δ

...sion/src/hosted/api/worker/worker.host.api.impl.ts
94.52% <50.00%> (-5.48%)
:arrow_down:

...ion/src/browser/vscode/api/main.thread.api.impl.ts
40.56% <60.00%> (+0.46%)
:arrow_up:

packages/extension/src/common/vscode/index.ts
100.00% <100.00%> (ø)

...on/src/browser/vscode/api/main.thread.quickopen.ts
33.89% <0.00%> (-20.95%)
:arrow_down:

...ension/src/hosted/api/vscode/ext.host.quickopen.ts
7.26% <0.00%> (-3.97%)
:arrow_down:

packages/quick-open/src/browser/quick-title-bar.ts
54.68% <0.00%> (-1.77%)
:arrow_down:

...ages/file-service/src/node/file-service-watcher.ts
71.18% <0.00%> (-1.70%)
:arrow_down:

packages/core-browser/src/quick-open/index.ts
79.72% <0.00%> (ø)

...ages/quick-open/src/browser/quickInput.inputBox.ts
10.25% <0.00%> (ø)

...xtension/src/browser/vscode/api/main.thread.scm.ts
7.14% <0.00%> (+2.52%)
:arrow_up:

... and 4 more

Continue to review full report at Codecov.

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


chore(example): add pr action to art boards

🚀  Deployed your composable app @art-boards/zima-blue:

https://d1s8oi6ouy9ssm.cloudfront.net/__art_boards_zima_blue/example-art-boards-pr/browser/index.html

🚀  Deployed your composable app @art-boards/dashboard-app:

https://d1s8oi6ouy9ssm.cloudfront.net/__art_boards_dashboard_app/example-art-boards-pr/browser/index.html

🚀  Deployed your composable app @art-boards/zima-blue:

https://d1s8oi6ouy9ssm.cloudfront.net/__art_boards_zima_blue/example-art-boards-pr/browser/index.html

🚀  Deployed your composable app @art-boards/chat-app:

https://d1s8oi6ouy9ssm.cloudfront.net/__art_boards_chat_app/example-art-boards-pr/browser/index.html


Status page doesnt show the updated firmware version

I was on v.6
saw the .6.1 update, wanted to give it a try via the web ui.
downloaded the firmware, named "firmware (2).bin" and applied.
Upon completion there is no feedback, is it supposed to redirect or do something?
manually refreshed and status page shows "esp-rfid Access Control  v0.6" not the .6.1 like in the demo url https://bitadvise.com/esp-rfid/
Is there a way to manually restart the esp via the web ui?

Feedback after completion would be nice. I will add it. Also you are right about version, i will fix it in next release.
There is no manual restart. I will add it on Backup & Restore page.
Thank you for feedback. Have a nice day.


suggestion: colorthief alternative

maybe test this lib if its faster, more stable etc.
https://github.com/thephpleague/color-extractor

I already tried that one, but performance and memory usage also do not seem to be very good. Still thinking of better ways of how to handle this, but the main issue remains the same for all of those libs: They have to load the whole image into memory and analyse a whole lot of pixels. Same problem I also got for testing whether an image has an alpha channel or not (takes painfully long on the server, but speeds up placeholder rendering in the frontend a lot). For larger images, I already started to create temporary thumbnails, because it reduces memory usage dramatically. Largest speed bump would be possible by creating the temporary thumbnail faster.
Only solution I stumbled upon: VIPS would allows way faster image processing from the command-line, than imagemagick or GD, but is an extra tool a user has to install on his/her server in order to make it work. Not sure yet, if it’s worth the effort …

my usual setup is photos directly from camera and clients perfer color preview over blured image. but thier servers (about 10€/month) are not fast/memory strong enogh to handle color extraction from raw file.
you mentioned using a thumb for detection instead of raw file. that would be great. is there a setting to define its max width/scale yet?
i have a lot of image focused projects lately so looking into vibs might be worth it. i will check if i can install it on a current project and report back.

I got an experimental (untested VIPS) driver for Kirby, wanna try it?

sure. but i can not do any testing before 17.7.

can do testing now. where do i find your VIPS driver?

Here it is. But please be careful, I just wrote that down without testing it a single time. The driver installs as a separate plugin.
vips.zip


call to readUInt32LE results in RangeError for empty buffer

While writing a lot of data to eventstore, I experienced a range error here:
https://github.com/bmavity/ges-client/blob/master/tcp/lengthPrefixMessageFramer.js#L54
Should we account for empty buffers or is an empty buffer a sign of a deeper issue?

Here's the full stacktrace
buffer.js:582
    throw new RangeError('Trying to access beyond buffer length');
    ^
RangeError: Trying to access beyond buffer length
    at checkOffset (buffer.js:582:11)
    at Buffer.readUInt32LE (buffer.js:642:5)
    at Object.getContentLength (/Users/leroix/deepthought/node_modules/ges-client/tcp/lengthPrefixMessageFramer.js:54:16)
    at MessageReceiver.processData (/Users/leroix/deepthought/node_modules/ges-client/tcp/messageReceiver.js:25:30)
    at MessageReceiver._handleMultiplePackets (/Users/leroix/deepthought/node_modules/ges-client/tcp/messageReceiver.js:58:8)
    at MessageReceiver.processData (/Users/leroix/deepthought/node_modules/ges-client/tcp/messageReceiver.js:31:9)
    at MessageReceiver._handleMultiplePackets (/Users/leroix/deepthought/node_modules/ges-client/tcp/messageReceiver.js:58:8)
    at MessageReceiver.processData (/Users/leroix/deepthought/node_modules/ges-client/tcp/messageReceiver.js:31:9)
    at MessageReceiver._handleMultiplePackets (/Users/leroix/deepthought/node_modules/ges-client/tcp/messageReceiver.js:58:8)
    at MessageReceiver.processData (/Users/leroix/deepthought/node_modules/ges-client/tcp/messageReceiver.js:31:9)
    at MessageReceiver._handleMultiplePackets (/Users/leroix/deepthought/node_modules/ges-client/tcp/messageReceiver.js:58:8)
    at MessageReceiver.processData (/Users/leroix/deepthought/node_modules/ges-client/tcp/messageReceiver.js:31:9)
    at MessageReceiver._handleMultiplePackets (/Users/leroix/deepthought/node_modules/ges-client/tcp/messageReceiver.js:58:8)
    at MessageReceiver.processData (/Users/leroix/deepthought/node_modules/ges-client/tcp/messageReceiver.js:31:9)
    at MessageReceiver._handleMultiplePackets (/Users/leroix/deepthought/node_modules/ges-client/tcp/messageReceiver.js:58:8)
    at MessageReceiver.processData (/Users/leroix/deepthought/node_modules/ges-client/tcp/messageReceiver.js:31:9)
    at MessageReceiver._handleMultiplePackets (/Users/leroix/deepthought/node_modules/ges-client/tcp/messageReceiver.js:58:8)
    at MessageReceiver.processData (/Users/leroix/deepthought/node_modules/ges-client/tcp/messageReceiver.js:31:9)

Whoops, I just saw this. It got buried in a flood of io.js messages. I will check into it in the next day or two.

Question: Which version of the server are you using which method are you using on the connection? After looking at the stack trace closer, it seems to error when reading the content length of a message from the server, but I do not think that should ever happen so there must be some issue with the multiple packet handling code. I will see if I can reproduce.

I was using v3.0.1 of the server, and I was using appendToStream to do 1000s of writes in a very short time.

Any possibility you could put the code up in a gist so I can reproduce?
On Mon, Jan 19, 2015 at 11:05 AM, leroix<EMAIL_ADDRESS>wrote:

I was using v3.0.1 of the server, and I was using appendToStream to do
1000s of writes in a very short time.
—
Reply to this email directly or view it on GitHub
https://github.com/bmavity/ges-client/issues/34#issuecomment-70527196.

I actually deleted it like a dummy. It was just a tiny wrapper around the client that takes lines from stdin and uses appendToStream to save them to eventstore.
Something like
var stream = process.stdin.pipe(split())

stream.on('data', ....)

Split can be found here. It just splits stdin lines by '\n'.

Ok. Will take a look at some point this week. Hopefully my schedule will
clear up a bit.
On Mon, Jan 19, 2015 at 11:23 AM, leroix<EMAIL_ADDRESS>wrote:

I actually deleted it like a dummy. It was just a tiny wrapper around the
client that takes lines from stdin and uses appendToStream to save them to
eventstore.
Something like
var stream = process.stdin.pipe(split())
stream.on('data', ....)
Split can be found here https://www.npmjs.com/package/split. It just
splits stdin lines by '\n'.
—
Reply to this email directly or view it on GitHub
https://github.com/bmavity/ges-client/issues/34#issuecomment-70529980.

I;d be interested in seeing a curl outout from the call having issues.
There is another thread going about null events and embed=content. I have
not yet been able to reproduce the issue where content is not delivered in
the atom feed but would not be surprised if there is some edge case it can
happen in
On Mon, Jan 19, 2015 at 7:40 PM, Brian Mavity<EMAIL_ADDRESS>wrote:

Ok. Will take a look at some point this week. Hopefully my schedule will
clear up a bit.
On Mon, Jan 19, 2015 at 11:23 AM, leroix<EMAIL_ADDRESS>wrote:

I actually deleted it like a dummy. It was just a tiny wrapper around
the
client that takes lines from stdin and uses appendToStream to save them
to
eventstore.
Something like
var stream = process.stdin.pipe(split())
stream.on('data', ....)
Split can be found here https://www.npmjs.com/package/split. It just
splits stdin lines by '\n'.
—
Reply to this email directly or view it on GitHub
https://github.com/bmavity/ges-client/issues/34#issuecomment-70529980.

—
Reply to this email directly or view it on GitHub
https://github.com/bmavity/ges-client/issues/34#issuecomment-70532461.

--
Studying for the Turing test

The client is tcp only for now. Are you asking me to do a curl that matches
what the tcp client is doing? Sorry if I am confused about something
obvious. :)
On Mon, Jan 19, 2015 at 1:49 PM, Greg Young<EMAIL_ADDRESS>wrote:

I;d be interested in seeing a curl outout from the call having issues.
There is another thread going about null events and embed=content. I have
not yet been able to reproduce the issue where content is not delivered in
the atom feed but would not be surprised if there is some edge case it can
happen in
On Mon, Jan 19, 2015 at 7:40 PM, Brian Mavity<EMAIL_ADDRESS>wrote:

Ok. Will take a look at some point this week. Hopefully my schedule will
clear up a bit.
On Mon, Jan 19, 2015 at 11:23 AM, leroix<EMAIL_ADDRESS>wrote:

I actually deleted it like a dummy. It was just a tiny wrapper around
the
client that takes lines from stdin and uses appendToStream to save
them
to
eventstore.
Something like
var stream = process.stdin.pipe(split())
stream.on('data', ....)
Split can be found here https://www.npmjs.com/package/split. It
just
splits stdin lines by '\n'.
—
Reply to this email directly or view it on GitHub
https://github.com/bmavity/ges-client/issues/34#issuecomment-70529980.

—
Reply to this email directly or view it on GitHub
https://github.com/bmavity/ges-client/issues/34#issuecomment-70532461.

--
Studying for the Turing test
—
Reply to this email directly or view it on GitHub
https://github.com/bmavity/ges-client/issues/34#issuecomment-70550209.

oh sorry I was thinking it was over atom.
In that case just the protobuf exchange works :)
On Mon, Jan 19, 2015 at 11:16 PM, Brian Mavity<EMAIL_ADDRESS>wrote:

The client is tcp only for now. Are you asking me to do a curl that
matches
what the tcp client is doing? Sorry if I am confused about something
obvious. :)
On Mon, Jan 19, 2015 at 1:49 PM, Greg Young<EMAIL_ADDRESS>wrote:

I;d be interested in seeing a curl outout from the call having issues.
There is another thread going about null events and embed=content. I
have
not yet been able to reproduce the issue where content is not delivered
in
the atom feed but would not be surprised if there is some edge case it
can
happen in
On Mon, Jan 19, 2015 at 7:40 PM, Brian Mavity<EMAIL_ADDRESS>

wrote:

Ok. Will take a look at some point this week. Hopefully my schedule
will
clear up a bit.
On Mon, Jan 19, 2015 at 11:23 AM, leroix<EMAIL_ADDRESS>wrote:

I actually deleted it like a dummy. It was just a tiny wrapper
around
the
client that takes lines from stdin and uses appendToStream to save
them
to
eventstore.
Something like
var stream = process.stdin.pipe(split())
stream.on('data', ....)
Split can be found here https://www.npmjs.com/package/split. It
just
splits stdin lines by '\n'.
—
Reply to this email directly or view it on GitHub
<https://github.com/bmavity/ges-client/issues/34#issuecomment-
70529980>.

—
Reply to this email directly or view it on GitHub
https://github.com/bmavity/ges-client/issues/34#issuecomment-70532461.

--
Studying for the Turing test
—
Reply to this email directly or view it on GitHub
https://github.com/bmavity/ges-client/issues/34#issuecomment-70550209.

—
Reply to this email directly or view it on GitHub
https://github.com/bmavity/ges-client/issues/34#issuecomment-70562299.

--
Studying for the Turing test

I've been abusing this code pretty heavily over the past couple of weeks and have not seen this crop up. I am going to close this for now, can reopen with code to reproduce if necessary.


Attempting to access restricted files results in a 500 response

See Slack.
Attempting to fetch a restricted file via https://api.wellcomecollection.org/text/alto/ results in a 500 response.
I do not know whether:
a) This should be 401 (i.e. it is caused by an unauthorised user trying to fetch the file and it is currently rightly refusing, but giving the wrong response)
b) There is actually something wrong (i.e. an authorised user is trying to fetch the file)

There may be something else at play here.  It is unlikely that a user has constructed the URLs I'm seeing by themselves, so are we incorrectly presenting links to restricted content? Perhaps someone has an old version of a page before the restriction was added?


Error on go run main.go"

@hsluoyz Can You help with this?
ERROR DESCRIPTION
I am getting an error on doing go run main.go while running backend.

hey @aryamanpuri can you show your logs.

2020/02/21 23:45:10.796 [I] [parser.go:112]  generate router from comments
panic: Error 1698: Access denied for user 'root'@'localhost'
goroutine 1 [running]:
github.com/casbin/casbin-dashboard/object.(*OrmManager).open(0xc00017e900)
/home/aryaman/go/src/github.com/casbin/casbin-dashboard/object/orm_manager.go:60 +0x131
github.com/casbin/casbin-dashboard/object.NewOrmManager(0xb468dc, 0x5, 0xc000024880, 0x1d, 0x1d)
/home/aryaman/go/src/github.com/casbin/casbin-dashboard/object/orm_manager.go:39 +0x7d
github.com/casbin/casbin-dashboard/object.InitOrmManager()
/home/aryaman/go/src/github.com/casbin/casbin-dashboard/object/orm_manager.go:14 +0x73
main.main()
/home/aryaman/casbin-dashboard/main.go:13 +0x26
exit status 2

Hello, @aryamanpuri  actually the problem is with mysql server not with go main server.
Make sure to start your mysql server.

@aryamanpuri
Just go to your Terminal and enter into MY-SQL by entering
sudo mysql -u root
Now switch your root user's plugin from auth_socket to mysql_native_password and change password to 123 by entering the following SQL statement
ALTER USER 'root'@'localhost' IDENTIFIED WITH mysql_native_password BY 123;
then
exit;
now run your go server again by
go run main.go
If you still face issues feel free to text on the Casbin Gitter channel

Ensure your SQL server is up and running on port 3306. By default root user is tried to log in using '123' as password but as mentioned in Readme that's configurable as per your will. Just update the configs in the app.conf file that's located at https://github.com/casbin/casbin-dashboard/blob/master/conf/app.conf . Also ensure you put this file in .gitignore so as to avoid commiting it.

@aryamanpuri can you update us on the status of this issue so that we can close it if no more action is needed.


Remove internal testing text from release notes

Removed clause noting new internal testing feature, since that feature has been pulled from 8.0
Update some wording in buildSrc clause, specifically to avoid a run-on sentence.

@bot-gradle test bd

I've triggered the following builds for you:

BuildDistributions build

@ljacomet please merge at your discretion, if you are happy with the new wording.

@bot-gradle test bd

I've triggered the following builds for you:

BuildDistributions build

Looks like the removal of the example from the docs was not needed. project() is still a valid dependency. What was removed is projectInternalView() and that was removed in #23281.
And since we plan more improvements to release notes, closing this PR.


removeEmptyRanks - replace _.has() method with more generic check

Since lodash v 3.9.0 _.has treats sparse arrays as dense which is why I get error using dagre-d3 with browserify (I have separate js bundle with latest lodash I use so I excluded v 2.4.1 that comes with dagre/dagre-d3).
This replaces _.has method with more generic falsy check on array. Comparison test here and here.

Thanks! For grins I tried upgrading lodash, but I still see a few test failures. Haven't had a chance to look at them, but maybe similar issues.


Urgent - problem with existing multiple choice pages and Xerte X

Hi all
I mentioned this to @torinfo by email recently but now it has become clear that it's a difinite issue and potentially affecting lots of existing LO's.
I've had reports from two different organisations about LO's with MC pages. e.g. "sometimes don’t have the Check box, if we do and click check, it doesn’t give us feedback and when you click the forward arrow, it doesn’t go forward - the slide goes blank".
When I look at the console I see an Uncaught Error: Syntax error, unrecognized expression: …
I think I’ve found where the problem lies or at least roughly where it lies.
This was a long existing LO rather than a new LO. I created a new MCQ page in the same LO and populated that with the same text and settings etc and that question worked fine. When I compare the xml of the working mcq page and the faulty mcq page the latter is missing multiWong multiRight singleWrong and singleRight
I’m guessing they were later additions and causing an error with existing pages built with previous versions?

Those bits of info being missing from the xml shouldn't cause a problem as the code checks to see if they are undefined before continuing (see lines 182-185).
Doesn't the error in the console say which line the error is on?

@FayCross just sent you a direct email with a link to a page types example on one of my installations where this is happening too. Here's a link to a quick demo with just the mc page and a plain text page after it. The page in this case was imported from an existing LO rather than created new because if created new all is fine. https://training.mitchellmedia.co.uk/xot/play.php?template_id=347

Could you test this possible fix please @ronm123 ? Thanks

Thanks @FayCross. @torinfo can you pull this into the release asap?
Should we notify users somehow? Potentially there are lots of LO's with faulty MC pages until this fix is applied?

Do we know at what version this would have become an issue?

@ronm123 Done

From 7th September - not sure what version that would be

@ronm123, @FayCross That would be X-v3.7.1.
@ronm123 Yes we apparently did. This is mentioned at the top of the registration form:

Use this form to register your organisation and installation as part of the official Xerte community.
When you register your site: You are added to a low-volume mailing list for important notifications such as security alerts and new releases of Xerte. Basic info like Organisation name and Country will be added to our publicised list of users worldwide.

@torinfo so how do we post to that list? :-)
and should we post details of bugs like this that we have fixed or wait until people discover them?


Setting temperature

Hi. Thanks for creating this - looks like a great start. Connected to our Panasonic aircon straight away.
Do you have any plans to add the ability to turn it on/off and set the temperature?
It would then be REALLY useful.....

Hi. Thanks for showing interest in this module. I have no immediate plans for this feature, but since you are asking, I will take a look at it and do some research into the topic. I cannot guarantee a quick resolution, but will try to move it up on my list.
If you are familiar with node.js development, feel free to submit a pull request.
Regards,
André

Thanks, André. I wish I was a programmer, but am not - some web design and
sql is about my limit.
Happy to look through protocols though - where you able to find it
documented, or did you have to wireshark it?
Regards
Simon
Simon Maddox
[image: maddox_new_logo_wide_trans_500h.png]
t: 01737 887 657   |   mob: 07785 504 340   |   w: maddox.co.uk   |
e: @.***
On Tue, 30 Nov 2021 at 18:27, André Biseth @.***> wrote:

Hi. Thanks for showing interest in this module. I have no immediate plans
for this feature, but since you are asking, I will take a look at it and do
some research into the topic. I cannot guarantee a quick resolution, but
will try to move it up on my list.
If you are familiar with node.js development, feel free to submit a pull
request.
Regards,
André
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/bisand/node-red-contrib-panasonic-comfort-cloud/issues/5#issuecomment-982903584,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABIEEXTS3TOX2AMTQ2ZENJ3UOUJRZANCNFSM5JB3DN7Q
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Looks like marc2016 has already created an npm node that includes setting would this help?
https://github.com/marc2016/panasonic-comfort-cloud-client

You are right about that. That is exactly the module I'm using in "node-red-contrib-panasonic-comfort-cloud". I will certainly try to find some time to implement setting of values. Feel free to suggest features you want me to prioritize first.

I think if you could create a 3rd node-red node that is the command one with the 8 functions Marc has implemented (e.g. the taking command as the topic and the value as the payload) that would be ideal. I see he has also created the enums for 'Auto', 'High' etc.
If you wanted to do them 1 at a time the most important it turning it on & off ;)

I have now published a new version of "node-red-contrib-panasonic-comfort-cloud" (v1.0.1). This includes a command node that takes a JSON object for payload and sets the applicable config values for the selected device. I have also updated the readme to contain some kind of documentation on how to use the new node. It would be nice if you have time to take it for a spin and let me know what you think. I have tested it on my heat pump and it works for me.
Don't hesitate to submit bugs or improvements, for nodes and/or documentation.
Good luck!

That's amazing! Thank you so much for putting some time into this.
It's not working for me at the moment, but I'm sure we're close!
If I store account credentials, they work for the previous 2 nodes, but the new command one does not seem to be using them properly - I get this if I hook a debug node onto its output:

Another (much smaller) thing is your naming of the Device ID configuration field - it's the same on the Device status and the command nodes. Maybe rename the label to Device ID or GUID?

Thanks

I have done some more testing, and it seems to be working on my setup.. Could it be a faulty payload? Can you please provide the JSON object you injected in the payload. It should be in JSON format, not text.
Use the JSON example below as a starting point. The Device ID could be set in either the JSON object or the node.
I have also changed the label to Device ID
{
"deviceId": "CS-XXXXXXX+1234567890",
"operate": "On",
"operationMode": "Heat",
"ecoMode": "Auto",
"temperatureSet": 22,
"airSwingUD": "Mid",
"airSwingLR": "Mid",
"fanAutoMode": "AirSwingAuto",
"fanSpeed": "Auto"
}

Strange. I was just sending the GUID and operate JSON, using an inject node set to JSON payload.
{
"deviceId": "CS-XXXXXXX+1234567890",
"operate": "On",
}
I also tried adding the Device ID at the command node, but this did not work either.
I have just tried injecting the same packet that you did (with the guid updated to that of my A/C unit) but I'm still getting the 'tried 3 times' error.
When I look at the device status the responses are mainly starting with underscores. Is this the same for you?
07/12/2021, 23:20:10node: 74714f31.9e4aa
msg : Object
object
_msgid: "302963a4.8d04ec"
topic: ""
payload: object
_operate: 0
_operationMode: 3
_temperatureSet: 22
_fanSpeed: 0
_fanAutoMode: 1
_airSwingLR: 2
_airSwingUD: 2
_ecoMode: 0
_actualNanoe: 1
_ecoNavi: 0
_nanoe: 2
_iAuto: 0
_airDirection: 1
_ecoFunctionData: 0
_insideTemperature: 22
_outTemperature: 5
lastSettingMode: 0
airQuality: 0
I'm using Node-Red v1.0.2 on a RPi - maybe that's the issue?

It seemed to be a problem with the payload validation. Earlier versions of Node-Red was a little bit more picky when it comes accepting payloads in the flows, so the payload you sent contained an invalid JSON string (see comma after "on",). This made the JSON parsing to fail on your version.
I have improved that logic and tested in on Node-Red 1.0.2, and it seems to be running OK. I have also improved the error handling, so the error messages should be a little bit better now.
The underscores just indicates that the returned object is using private variables. That should be OK.

Thanks for the update. I've spent quite some time today trying to get the new version installed - with not much success.
I have switched to another instance of node-red - version 2.1.3 running on a RPi. The nodes install fine from Manage Palette, but when I configure and deploy the Command node disappears - missing from the flows tab and the library.

Any ideas?

I suspect the new problems you are experiencing is probably because I used optional chaining (?.) in an expression and that was not supported until Node.js until version 14, and I suspect your installation is using an earlier version. This expression has now been replaced by a more supported one. My bad!
Try to install the new version (1.0.4) and see if it works now.

Hi André. Firstly, thanks again for putting time into this - I know how difficult this can be - especially if it is working for you!
The nodes install now and deploy fine, but I'm still getting the connection issue - just on the Command node:

I've checked and the command is of course not getting through. I'm using your example json - just with the GUID line removed and with the Device ID put into the node configuration. It works on the Device status node.
There is 1 other thing I have noticed and don't understand. If I connect a debug node to the Device node with the debug set to show msg.payload it indicates an object, but is unable to expand it:

If I configure the debug node to show full msg object it works fine:

Using msg.payload on the Groups status node works fine too. Not a big deal, but there must be something different in the Device Status node.
I'm using node-red within Docker (IOTStack build for RPi). Here is a dump of the log:
9 Dec 10:22:07 - [info] [mqtt-broker:Local] Connected to broker: mqtt://<IP_ADDRESS>:1883
9 Dec 10:22:14 - [info] [pcc-device:896b8e0501d6f750] true
9 Dec 10:23:08 - [info] [pcc-device:896b8e0501d6f750] true
9 Dec 10:23:28 - [info] [pcc-command:5f0e30c4443206f6] [object Object]
9 Dec 10:23:30 - [info] [pcc-command:5f0e30c4443206f6] 1
9 Dec 10:23:30 - [info] [pcc-command:5f0e30c4443206f6] 3
9 Dec 10:23:30 - [info] [pcc-command:5f0e30c4443206f6] 0
9 Dec 10:23:30 - [info] [pcc-command:5f0e30c4443206f6] 22
9 Dec 10:23:30 - [info] [pcc-command:5f0e30c4443206f6] 2
9 Dec 10:23:30 - [info] [pcc-command:5f0e30c4443206f6] 2
9 Dec 10:23:30 - [info] [pcc-command:5f0e30c4443206f6] 0
9 Dec 10:23:30 - [info] [pcc-command:5f0e30c4443206f6] 0
9 Dec 10:23:34 - [info] [pcc-command:5f0e30c4443206f6] Obtained a new access token.
9 Dec 10:23:34 - [info] [pcc-command:5f0e30c4443206f6] [object Object]
9 Dec 10:23:36 - [info] [pcc-command:5f0e30c4443206f6] 1
9 Dec 10:23:36 - [info] [pcc-command:5f0e30c4443206f6] 3
9 Dec 10:23:36 - [info] [pcc-command:5f0e30c4443206f6] 0
9 Dec 10:23:36 - [info] [pcc-command:5f0e30c4443206f6] 22
9 Dec 10:23:36 - [info] [pcc-command:5f0e30c4443206f6] 2
9 Dec 10:23:36 - [info] [pcc-command:5f0e30c4443206f6] 2
9 Dec 10:23:36 - [info] [pcc-command:5f0e30c4443206f6] 0
9 Dec 10:23:36 - [info] [pcc-command:5f0e30c4443206f6] 0
9 Dec 10:23:40 - [info] [pcc-device:896b8e0501d6f750] true
9 Dec 10:23:40 - [info] [pcc-command:5f0e30c4443206f6] Obtained a new access token.
9 Dec 10:23:40 - [info] [pcc-command:5f0e30c4443206f6] [object Object]
9 Dec 10:23:42 - [info] [pcc-command:5f0e30c4443206f6] 1
9 Dec 10:23:42 - [info] [pcc-command:5f0e30c4443206f6] 3
9 Dec 10:23:42 - [info] [pcc-command:5f0e30c4443206f6] 0
9 Dec 10:23:42 - [info] [pcc-command:5f0e30c4443206f6] 22
9 Dec 10:23:42 - [info] [pcc-command:5f0e30c4443206f6] 2
9 Dec 10:23:42 - [info] [pcc-command:5f0e30c4443206f6] 2
9 Dec 10:23:42 - [info] [pcc-command:5f0e30c4443206f6] 0
9 Dec 10:23:42 - [info] [pcc-command:5f0e30c4443206f6] 0
9 Dec 10:23:45 - [info] [pcc-command:5f0e30c4443206f6] Obtained a new access token.
9 Dec 10:23:45 - [error] [pcc-command:5f0e30c4443206f6] Error: Reached max retry count 3. Please check your credentials, or read the logs for more information.
9 Dec 10:24:34 - [info] [pcc-device:896b8e0501d6f750] true
9 Dec 10:25:21 - [info] [pcc-command:5f0e30c4443206f6] [object Object]
9 Dec 10:25:22 - [info] [pcc-command:5f0e30c4443206f6] 1
9 Dec 10:25:22 - [info] [pcc-command:5f0e30c4443206f6] 3
9 Dec 10:25:22 - [info] [pcc-command:5f0e30c4443206f6] 0
9 Dec 10:25:22 - [info] [pcc-command:5f0e30c4443206f6] 22
9 Dec 10:25:22 - [info] [pcc-command:5f0e30c4443206f6] 2
9 Dec 10:25:22 - [info] [pcc-command:5f0e30c4443206f6] 2
9 Dec 10:25:22 - [info] [pcc-command:5f0e30c4443206f6] 0
9 Dec 10:25:22 - [info] [pcc-command:5f0e30c4443206f6] 0
9 Dec 10:25:26 - [info] [pcc-command:5f0e30c4443206f6] Obtained a new access token.
9 Dec 10:25:26 - [info] [pcc-command:5f0e30c4443206f6] [object Object]
9 Dec 10:25:28 - [info] [pcc-command:5f0e30c4443206f6] 1
9 Dec 10:25:28 - [info] [pcc-command:5f0e30c4443206f6] 3
9 Dec 10:25:28 - [info] [pcc-command:5f0e30c4443206f6] 0
9 Dec 10:25:28 - [info] [pcc-command:5f0e30c4443206f6] 22
9 Dec 10:25:28 - [info] [pcc-command:5f0e30c4443206f6] 2
9 Dec 10:25:28 - [info] [pcc-command:5f0e30c4443206f6] 2
9 Dec 10:25:28 - [info] [pcc-command:5f0e30c4443206f6] 0
9 Dec 10:25:28 - [info] [pcc-command:5f0e30c4443206f6] 0
9 Dec 10:25:32 - [info] [pcc-command:5f0e30c4443206f6] Obtained a new access token.
9 Dec 10:25:32 - [info] [pcc-command:5f0e30c4443206f6] [object Object]
9 Dec 10:25:34 - [info] [pcc-command:5f0e30c4443206f6] 1
9 Dec 10:25:34 - [info] [pcc-command:5f0e30c4443206f6] 3
9 Dec 10:25:34 - [info] [pcc-command:5f0e30c4443206f6] 0
9 Dec 10:25:34 - [info] [pcc-command:5f0e30c4443206f6] 22
9 Dec 10:25:34 - [info] [pcc-command:5f0e30c4443206f6] 2
9 Dec 10:25:34 - [info] [pcc-command:5f0e30c4443206f6] 2
9 Dec 10:25:34 - [info] [pcc-command:5f0e30c4443206f6] 0
9 Dec 10:25:34 - [info] [pcc-command:5f0e30c4443206f6] 0
9 Dec 10:25:39 - [info] [pcc-command:5f0e30c4443206f6] Obtained a new access token.

Ok, I will have to do some research and maybe spin up a RPi with the same environment as you. Could you provide some details on the RPi environment you are using. Could you also try to spin up a Node-Red instance on your own PC with the latest Node.js LTS to see if you get the same result as on the Pi. What version of Node.js is running on the Pi?
In the meantime, I will conduct some analyzing and testing on my side to see if I can get the same results as you are getting.

@smadds, I've released a new version with (hopefully) improved error logging. Could you please try to install it to see if you get some more informative error messages?
I really appreciate your help and patience on this matter.
Thanks! :)

I think we're getting there - and I really appreciate the effort you are putting in.
The Device node now returns a recognisable object in msg.payload
The command node is still returning an error:

This happens when I inject the demo json you supply (less the guid, which is in the node) or just a simple single command:

Logs:
10 Dec 15:23:22 - [error] [pcc-command:5f0e30c4443206f6] Error: An error ocurred while trying to set device parameter: ServiceError: Adapter internal error,
10 Dec 15:23:17 - [info] [pcc-command:5f0e30c4443206f6] [object Object],
10 Dec 15:23:19 - [info] [pcc-command:5f0e30c4443206f6] 1

These are the versions I am using:
NODE_RED_VERSION	v2.1.3
NODE_VERSION	12.22.7

Strange! I have also tested with node.js v12.22.7 with success.. Just a thought.. Could it be a firewall or something on your side that could be blocking HTTP POST calls?

I don't think its a firewall issue. I'm running the node-red from home on a domestic broadband - and the app works fine on my phone on the same wifi network. I can control the device from the phone app then see the status change from your device node.
I would be interested to see if you can connect to our aircon successfully. Happy to share the Comfort Cloud login privately with you. My Whatsapp is +447785504340

This is my test config:
[
{
"id": "adc583949d87ddd2",
"type": "pcc-groups",
"z": "a5b7afd8.59ad6",
"name": "",
"comfortCloudConfig": "706049c58d4f7494",
"x": 490,
"y": 240,
"wires": [
[
"2af5cbb33e0c537a"
]
]
},
{
"id": "896b8e0501d6f750",
"type": "pcc-device",
"z": "a5b7afd8.59ad6",
"name": "",
"comfortCloudConfig": "706049c58d4f7494",
"deviceId": "CZ-CAPWFC1+B8B7F1B3E188",
"x": 490,
"y": 320,
"wires": [
[
"aa12c69fb92fa59c"
]
]
},
{
"id": "5f0e30c4443206f6",
"type": "pcc-command",
"z": "a5b7afd8.59ad6",
"name": "",
"comfortCloudConfig": "706049c58d4f7494",
"deviceId": "CZ-CAPWFC1+B8B7F1B3E188",
"x": 500,
"y": 400,
"wires": [
[
"eb40479f8efc1bab"
]
]
},
{
"id": "4e5343a98f8ba96c",
"type": "inject",
"z": "a5b7afd8.59ad6",
"name": "",
"props": [
{
"p": "payload"
},
{
"p": "topic",
"vt": "str"
}
],
"repeat": "",
"crontab": "",
"once": false,
"onceDelay": 0.1,
"topic": "",
"payload": "true",
"payloadType": "bool",
"x": 290,
"y": 240,
"wires": [
[
"adc583949d87ddd2"
]
]
},
{
"id": "2af5cbb33e0c537a",
"type": "debug",
"z": "a5b7afd8.59ad6",
"name": "",
"active": true,
"tosidebar": true,
"console": false,
"tostatus": false,
"complete": "false",
"statusVal": "",
"statusType": "auto",
"x": 730,
"y": 240,
"wires": []
},
{
"id": "7e62452fda91d936",
"type": "inject",
"z": "a5b7afd8.59ad6",
"name": "",
"props": [
{
"p": "payload"
},
{
"p": "topic",
"vt": "str"
}
],
"repeat": "",
"crontab": "",
"once": false,
"onceDelay": 0.1,
"topic": "",
"payload": "true",
"payloadType": "bool",
"x": 290,
"y": 320,
"wires": [
[
"896b8e0501d6f750"
]
]
},
{
"id": "aa12c69fb92fa59c",
"type": "debug",
"z": "a5b7afd8.59ad6",
"name": "",
"active": true,
"tosidebar": true,
"console": false,
"tostatus": false,
"complete": "payload",
"targetType": "msg",
"statusVal": "",
"statusType": "auto",
"x": 730,
"y": 320,
"wires": []
},
{
"id": "eb40479f8efc1bab",
"type": "debug",
"z": "a5b7afd8.59ad6",
"name": "",
"active": true,
"tosidebar": true,
"console": false,
"tostatus": false,
"complete": "false",
"statusVal": "",
"statusType": "auto",
"x": 730,
"y": 400,
"wires": []
},
{
"id": "c2f11c7f373258f4",
"type": "inject",
"z": "a5b7afd8.59ad6",
"name": "On",
"props": [
{
"p": "payload"
},
{
"p": "topic",
"vt": "str"
}
],
"repeat": "",
"crontab": "",
"once": false,
"onceDelay": 0.1,
"topic": "",
"payload": "{"operate":"On"}",
"payloadType": "json",
"x": 290,
"y": 400,
"wires": [
[
"5f0e30c4443206f6"
]
]
},
{
"id": "2eb27b87980b5b92",
"type": "inject",
"z": "a5b7afd8.59ad6",
"name": "Off",
"props": [
{
"p": "payload"
},
{
"p": "topic",
"vt": "str"
}
],
"repeat": "",
"crontab": "",
"once": false,
"onceDelay": 0.1,
"topic": "",
"payload": "{"operate":"Off"}",
"payloadType": "json",
"x": 290,
"y": 460,
"wires": [
[
"5f0e30c4443206f6"
]
]
},
{
"id": "706049c58d4f7494",
"type": "pcc-config",
"name": "CC Panasonic Account"
}
]

@smadds, Before going down the road of exchanging credentials, I would like you to try one more time. I have switched out the old API client with my own implementation, which also give me a lot more control over the different elements. This client leverages the built in https client in Node.js to communicate with the API.
The command node will now try to do some validation on the provided parameters and only send the parameters you define to the Comfort Cloud API. That will most likely rule out some incompatibility issues (I hope).
It would be nice if you could test it one more time.
Thanks!

Looks like we have some success here!
I'll do more testing tomorrow, but I am not getting errors and I can see that I'm able to change operate mode between 0 and 1 with my test setup.
Thanks!

Can we close this?

I've tried, but looks like the Panasonic server is down at the moment!

Panasonic Comfort Cloud server working again today...
Yes, this looks good now - thanks for all the time you've put into it.

Perfect! Thank you for doing all the testing. Have a wonderful Christmas!


validate service parameter in client side to avoid api call in docker service scale

- What I did
This PR adds parameter validation in the client side of command docker service scale ...
Since in the original implementation, docker cli first fetch service object via api call, then validate parameters. It will add workload in the daemon side and this kind of load is unnecessary.
This PR adds a cli test as well.
Signed-off-by: allencloud<EMAIL_ADDRESS>

@vdemeester PTAL 🐯


[SPARK-18518][ML] HasSolver supports override

What changes were proposed in this pull request?
1, make param support non-final with finalFields option
2, generate HasSolver with finalFields = false
3, override solver in LiR, GLR, and make MLPC inherit HasSolver
How was this patch tested?
existing tests

Test build #69226 has started for PR 16028 at commit ae74a3e.

Test build #69226 has finished for PR 16028 at commit ae74a3e.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69226/
Test FAILed.

Test build #69298 has started for PR 16028 at commit 5901525.

Test build #69298 has finished for PR 16028 at commit 5901525.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69298/
Test FAILed.

Merged build finished. Test FAILed.

Test build #69305 has started for PR 16028 at commit 74cb363.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69305/
Test FAILed.

Jenkins, retest this please

Test build #69314 has started for PR 16028 at commit 74cb363.

Test build #69314 has finished for PR 16028 at commit 74cb363.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69314/
Test PASSed.

Test build #69318 has started for PR 16028 at commit bad1735.

Test build #69318 has finished for PR 16028 at commit bad1735.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69318/
Test PASSed.

cc @yanboliang

Test build #71658 has started for PR 16028 at commit 617bdbd.

Test build #71661 has started for PR 16028 at commit 49bcbf2.

Test build #71658 has finished for PR 16028 at commit 617bdbd.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71658/
Test PASSed.

Test build #71661 has finished for PR 16028 at commit 49bcbf2.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71661/
Test FAILed.

Test build #71694 has started for PR 16028 at commit adddd95.

Test build #71694 has finished for PR 16028 at commit adddd95.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71694/
Test PASSed.

Merged build finished. Test PASSed.

ping @yanboliang ?

Test build #74709 has started for PR 16028 at commit c0eba75.

Test build #74709 has finished for PR 16028 at commit c0eba75.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74709/
Test PASSed.

Test build #77928 has started for PR 16028 at commit c0eba75.

Test build #77928 has finished for PR 16028 at commit c0eba75.

This patch fails from timeout after a configured wait of `250m`.
This patch does not merge cleanly.
This patch adds no public classes.

Build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77928/
Test FAILed.

Test build #78045 has started for PR 16028 at commit de88ac9.

Test build #78045 has finished for PR 16028 at commit de88ac9.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/78045/
Test PASSed.

Merged build finished. Test PASSed.

Test build #78675 has started for PR 16028 at commit 6311934.

Test build #78675 has finished for PR 16028 at commit 6311934.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/78675/
Test FAILed.

Test build #78679 has started for PR 16028 at commit b3683c1.

Test build #78681 has started for PR 16028 at commit 5e85dc6.

Test build #78679 has finished for PR 16028 at commit b3683c1.

This patch fails due to an unknown error code, -10.
This patch merges cleanly.
This patch adds the following public classes (experimental):
  final val thresholds: DoubleArrayParam = new DoubleArrayParam(this, \"thresholds\", \"thresholds in multi-class classification to adjust the probability of predicting each class. Array must have length equal to the number of classes, with values > 0 excepting that at most one value may be 0. The class with largest value p/t is predicted, where p is the original probability of that class and t is the class's threshold\", (t: Array[Double]) => t.forall(_ >= 0) && t.count(_ == 0) <= 1)

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/78679/
Test FAILed.

Merged build finished. Test FAILed.

Test build #78681 has finished for PR 16028 at commit 5e85dc6.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/78681/
Test PASSed.

Test build #78687 has started for PR 16028 at commit 759b036.

Test build #78687 has finished for PR 16028 at commit 759b036.

This patch fails PySpark pip packaging tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
      ParamDesc[String](\"probabilityCol\", \"Column name for predicted class conditional\" +
      ParamDesc[Array[Double]](\"thresholds\", \"Thresholds in multi-class classification\" +
  final val probabilityCol: Param[String] = new Param[String](this, \"probabilityCol\", \"Column name for predicted class conditional probabilities. Note: Not all models output well-calibrated probability estimates! These probabilities should be treated as confidences, not precise probabilities\")
  final val thresholds: DoubleArrayParam = new DoubleArrayParam(this, \"thresholds\", \"Thresholds in multi-class classification to adjust the probability of predicting each class. Array must have length equal to the number of classes, with values > 0 excepting that at most one value may be 0. The class with largest value p/t is predicted, where p is the original probability of that class and t is the class's threshold\", (t: Array[Double]) => t.forall(_ >= 0) && t.count(_ == 0) <= 1)

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/78687/
Test FAILed.

Jenkins, retest this please

Test build #78689 has started for PR 16028 at commit 759b036.

Test build #78689 has finished for PR 16028 at commit 759b036.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
      ParamDesc[String](\"probabilityCol\", \"Column name for predicted class conditional\" +
      ParamDesc[Array[Double]](\"thresholds\", \"Thresholds in multi-class classification\" +
  final val probabilityCol: Param[String] = new Param[String](this, \"probabilityCol\", \"Column name for predicted class conditional probabilities. Note: Not all models output well-calibrated probability estimates! These probabilities should be treated as confidences, not precise probabilities\")
  final val thresholds: DoubleArrayParam = new DoubleArrayParam(this, \"thresholds\", \"Thresholds in multi-class classification to adjust the probability of predicting each class. Array must have length equal to the number of classes, with values > 0 excepting that at most one value may be 0. The class with largest value p/t is predicted, where p is the original probability of that class and t is the class's threshold\", (t: Array[Double]) => t.forall(_ >= 0) && t.count(_ == 0) <= 1)

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/78689/
Test PASSed.

Jenkins, retest this please

Jenkins, retest this please

Test build #78743 has started for PR 16028 at commit 759b036.

Test build #78744 has started for PR 16028 at commit 759b036.

Test build #78743 has finished for PR 16028 at commit 759b036.

This patch fails PySpark pip packaging tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
      ParamDesc[String](\"probabilityCol\", \"Column name for predicted class conditional\" +
      ParamDesc[Array[Double]](\"thresholds\", \"Thresholds in multi-class classification\" +
  final val probabilityCol: Param[String] = new Param[String](this, \"probabilityCol\", \"Column name for predicted class conditional probabilities. Note: Not all models output well-calibrated probability estimates! These probabilities should be treated as confidences, not precise probabilities\")
  final val thresholds: DoubleArrayParam = new DoubleArrayParam(this, \"thresholds\", \"Thresholds in multi-class classification to adjust the probability of predicting each class. Array must have length equal to the number of classes, with values > 0 excepting that at most one value may be 0. The class with largest value p/t is predicted, where p is the original probability of that class and t is the class's threshold\", (t: Array[Double]) => t.forall(_ >= 0) && t.count(_ == 0) <= 1)

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/78743/
Test FAILed.

Test build #78744 has finished for PR 16028 at commit 759b036.

This patch fails PySpark pip packaging tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
      ParamDesc[String](\"probabilityCol\", \"Column name for predicted class conditional\" +
      ParamDesc[Array[Double]](\"thresholds\", \"Thresholds in multi-class classification\" +
  final val probabilityCol: Param[String] = new Param[String](this, \"probabilityCol\", \"Column name for predicted class conditional probabilities. Note: Not all models output well-calibrated probability estimates! These probabilities should be treated as confidences, not precise probabilities\")
  final val thresholds: DoubleArrayParam = new DoubleArrayParam(this, \"thresholds\", \"Thresholds in multi-class classification to adjust the probability of predicting each class. Array must have length equal to the number of classes, with values > 0 excepting that at most one value may be 0. The class with largest value p/t is predicted, where p is the original probability of that class and t is the class's threshold\", (t: Array[Double]) => t.forall(_ >= 0) && t.count(_ == 0) <= 1)

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/78744/
Test FAILed.

retest this please

Test build #78778 has started for PR 16028 at commit 759b036.

Test build #78778 has finished for PR 16028 at commit 759b036.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
      ParamDesc[String](\"probabilityCol\", \"Column name for predicted class conditional\" +
      ParamDesc[Array[Double]](\"thresholds\", \"Thresholds in multi-class classification\" +
  final val probabilityCol: Param[String] = new Param[String](this, \"probabilityCol\", \"Column name for predicted class conditional probabilities. Note: Not all models output well-calibrated probability estimates! These probabilities should be treated as confidences, not precise probabilities\")
  final val thresholds: DoubleArrayParam = new DoubleArrayParam(this, \"thresholds\", \"Thresholds in multi-class classification to adjust the probability of predicting each class. Array must have length equal to the number of classes, with values > 0 excepting that at most one value may be 0. The class with largest value p/t is predicted, where p is the original probability of that class and t is the class's threshold\", (t: Array[Double]) => t.forall(_ >= 0) && t.count(_ == 0) <= 1)

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/78778/
Test PASSed.

Test build #78857 has started for PR 16028 at commit d84bb21.

Test build #78857 has finished for PR 16028 at commit d84bb21.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/78857/
Test PASSed.

Test build #78886 has started for PR 16028 at commit 3a54e1d.

Test build #78886 has finished for PR 16028 at commit 3a54e1d.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/78886/
Test PASSed.

Merged build finished. Test PASSed.

Test build #78902 has started for PR 16028 at commit 21d3b95.

Test build #78902 has finished for PR 16028 at commit 21d3b95.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/78902/
Test PASSed.

Test build #78953 has started for PR 16028 at commit b907314.

Test build #78953 has finished for PR 16028 at commit b907314.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/78953/
Test FAILed.

Test build #78956 has started for PR 16028 at commit 39ea8e1.

Test build #78956 has finished for PR 16028 at commit 39ea8e1.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/78956/
Test FAILed.

Merged build finished. Test FAILed.

Test build #78960 has started for PR 16028 at commit 6bb1daf.

Test build #78960 has finished for PR 16028 at commit 6bb1daf.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/78960/
Test FAILed.

retest this please

Test build #78966 has started for PR 16028 at commit 6bb1daf.

Test build #78966 has finished for PR 16028 at commit 6bb1daf.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/78966/
Test PASSed.

Merged build finished. Test PASSed.

Test build #78983 has started for PR 16028 at commit d15ea65.

Test build #78983 has finished for PR 16028 at commit d15ea65.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/78983/
Test PASSed.

Merged build finished. Test PASSed.

Test build #79013 has started for PR 16028 at commit 2e280d5.

Test build #79013 has finished for PR 16028 at commit 2e280d5.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79013/
Test PASSed.


Partyline Javascript Module/Class

get a list of all parties
create a chat function
create a new repo
create a list of all the parties a user is subscribed to
display the title of the party


chore(js): output packages to ESM only

These packages are only used as binaries, they are not meant to be imported. We also require Node 18+, so ESM by default should work for everyone.
Closes TURBO-1568

This might take a little more effort. Current blockers:

importing some files without file extensions, which doesn't work in ESM (may be possible with some config in tsconfig or tsup)
importing fs-extra and using various sync methods that are not available on fs-extra/esm entrypoint

Closing this down as it uncovered some issues with underlying libraries. We'll likely have to do this one package at a time.


Protein Vector object

Please complete the following checklist:

[x] I have read the contribution guidelines.

[x] I have documented all public-facing changes in the changelog.

[ ] This pull request includes code, documentation, or other content derived from external source(s). If this is the case, ensure the external source's license is compatible with scikit-bio's license. Include the license in the licenses directory and add a comment in the code giving proper attribution. Ensure any other requirements set forth by the license and/or author are satisfied.

It is your responsibility to disclose code, documentation, or other content derived from external source(s). If you have questions about whether something can be included in the project or how to give proper attribution, include those questions in your pull request and a reviewer will assist you.

[x] This pull request does not include code, documentation, or other content derived from external source(s).

Note: This document may also be helpful to see some of the things code reviewers will be verifying when reviewing your pull request.
There are a few linting issues that need to be addressed -- the major modification here was updating the embedding format to handle both protein embeddings and protein vectors (vectors here will allow for fast queries), in addition to conversion utilities discussed in https://github.com/scikit-bio/scikit-bio/issues/2006
This is the last pull request that would need top be merged into skbio before we start putting together the tutorials.

I wonder if codecov doesn't like it when there are multiple files with the same name (i.e. skbio.io.format._embedding.py and skbio.embedding._embedding). Renaming these files to confirm.
If so, then the same logic would apply to skbio.embedding._protein since there is also skbio.sequence._protein.

Waiting on feedback regarding codecov. Otherwise, this pull request is ready for review.
Major changes since https://github.com/scikit-bio/scikit-bio/pull/2008

Adding in support for ProteinVector objects. This will allow for consuming the output of pLMs like TMvec for rapid remote homology search and light-weight protein function annotation. Furthermore, there are a number of conversion mechanisms in place to allow for easy manipulation of these objects.
Renamed skbio.io.format.embedding -> skbio.io.format.embed for consistency. It also helps distinguish between the file format embed and the object embedding
We defined a bytes() ABC method to further simplify hdf5 conversion. That way, every class inherienting from Embedding already has bytes() defined and can write to HDF5
We added additional flexibility to the HDF5 format to allow for more relaxes string length requirements. In the previous PR, the string length was required to be equal to the embedding length (which is the case with the ProteinEmbedding object). But this is not the case with the ProteinVector object and other potential downstream objects (i.e. MolecularEmbedding objects).  That being said, we have enabled backwards compatibility, since the increased flexibility slightly increases the HDF5 memory footprint (by adding extra pointers).
Fixed exception import that was missed in the previous pull request

Hi all, thanks for the comments.
After carefully scrutinizing the type signatures, I realized that there is an edge case that could complicate the incorporating of non-sequence vector objects (i.e. molecular vectors).
I've created an intermediate class called EmbeddingVector that primarily serves to (1) address this future edge case and (2) enabling better type checking of vector objects (i.e. checking to make sure that all conversion methods accept iterables of objects that subclass EmbeddingVector).
I realize that this is complicating the hierarchy : Embedding -> EmbeddingVector -> SequenceVector -> ProteinVector, but this will be the last change to the hierarchy, and will avoid short-circuiting ourselves if we wanted to add in additional types in the future.

@mortonjt I see the logic of EmbeddingVector and I like that. I wonder if this term should be called "vector embedding" instead?
One thing to note, which is somehow relevant but shouldn't affect the design here: scikit-bio's Sequence only support ASCII characters, which is a big limitation (e.g., you can't easily represent methylated nucleotides), but also grants performance since all underlying data are np.uint8. In comparison, Biotite's sequence can contain any custom values (any immutable and hashable)


no outlines txt created, mask png only black

Hello!
I created a new cellpose environment in conda, using the provided environment.yml and forcing pytorch from the pytorch channel (pytorch::pytorch).
It works, which makes me happy, but sadly does not save the outlines in a txt like before (--save_png flag). Also the mask pngs are all black.
Did somebody run into the same issue?

edit: I was able to save the outlines by adding --save_outlines, the masks remain black/empty. Is there a way to solve this issue?
Thank you!

sorry for the delay in getting back to you, are things working for you now, is that what you mean? Going to close this issue for now, but please let us know if you're still having problems


how to read csv file with other encoding

In azure Databricks , I  read a CSV file with multiline = 'true' and charset= 'IOS 8859-7'. But I cannot shows some words.  It seems that charset option is being ignored. If i use multiline option spark use its default encoding that is UTF-8, but my file is in IOS 8859-7 format. Is it possible that I  use the two options at the same time. If it is possible, how to implement it.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: e8a0a4f7-4656-6597-db51-36f9f0f4bae6
Version Independent ID: 873513b5-4bce-89e6-1d4c-900bfafcf257
Content: Apache Spark Quickstart - Azure Databricks
Content Source: databricks/getting-started/spark/quick-start.md
Service: azure-databricks
GitHub Login: @mamccrea
Microsoft Alias: mamccrea

@test123114, Thank you for sharing the query. We are looking into this and would get back to you soon on this thread.

Might be a typo, but is it ISO not IOS?  ISO 8859-7

@test123114 Thanks for reaching out to us , but at this time it does not look like you are referring to a document but to a specific scenario . If that's the case we request you to please post your question on MSDN , SO and other forums , we have our engineers and others who are monitoring them and will be happy to help .
If you have a document which you are following and if you think it needs  an update , please let us know about that here .

@test123114 We will now proceed to close this thread. If there are further questions regarding this matter, please comment and we will gladly continue the discussion.


breadcrumbs feature?

it might seem a bit off topic but, I couldn't find any other place to ask my question.
Is there any breadcrumbs feature available or will it be in future?

The issue template that you deleted to write this mentioned https://forum.ghost.org multiple times. Please use the forum. Github is for bug reports only.

@ErisDS This is a bug honey, it is a blog script that does not have breadcrumbs, that is a bug, very big bug, bigger than your CTO position at Ghost!
Stop hiring white people please!


canal networking questions

There are a number of questions unresolved after the Canal PR.  They were deemed large enough to follow up on but small enough to not impede the PR.

ask Canal team what the appropriate resource restrictions are.  these applications run inside of k8s so we should have some accounting for them ahead of time
why is the tool install not an init container?  one less container running forever

closed, answers were received.


build, tag and push semver

allow build of specific package version
allow package version to be set

Related:

Closes #3

Docs: https://terraspace.cloud/docs/install/docker/versioning/


Integrate the AdMobMediationAdapterFlurry into a swift podspec

I'm creating a library that will depend on the AdMobMediationAdapterFlurry.
I did the following
pod lib create xxxxxxxxxx

Everything as default (language: SWIFT)
Then I added the following line to my podspec:
s.dependency 'AdMobMediationAdapterFlurry'

Then I run the following command
pod lib lint

 -> xxxxxxxxxx (0.1.0)
    - ERROR | [iOS] unknown: Encountered an unknown error (The 'Pods-App' target has transitive dependencies that include static binaries: (/private/var/folders/8_/1pw469513kv9s8dz8rv1z84m0000gn/T/CocoaPods-Lint-20171213-1923-sl5tv4-xxxxxxxxxx/Pods/AdMobMediationAdapterFlurry/FlurryAdapter/libFlurryAdapter.a)) during validation.

[!] xxxxxxxxxx did not pass validation, due to 1 error.
You can use the `--no-clean` option to inspect any issue.

This currently seems to be a bigger issue for several podspecs using swift.
However it could be resolved by adding the flurry adapter as a vendored framework.
For example, Google offers the following way:
s.vendored_frameworks = 'YieldloveAdIntegration/Pods/Google-Mobile-Ads-SDK/Frameworks/frameworks/GoogleMobileAds.framework'

I got it to lint by using the following setup:
	s.subspec 'AdMobMediationAdapterFlurry' do |ss|
		ss.source_files =  'Extras/FlurryAdNetworkExtras.h'
		ss.public_header_files = 'Extras/FlurryAdNetworkExtras.h'
		ss.vendored_libraries = 'Extras/libFlurryAdapter.a'
		ss.dependency 'Flurry-iOS-SDK/FlurrySDK'
		ss.dependency 'Flurry-iOS-SDK/FlurryAds'
		ss.dependency 'Google-Mobile-Ads-SDK', '~> 7.12'
	end


Updating Realm object without primary key?

Hi, I'd like to ask what's the correct way to update a Realm Object that doesn't have primary key in 1 closure? I tried remove + insert but it gave me error, i have to change the insert function to update: false only it works, maybe should include another function for insert without primary key?

Good idea @Tj3n we'll add it.

on the same topic, looks like we cant use update: true in teh insert action... you guys found any way?

I end up change the whole insert function with the update: Bool added, so that it will use that parameter for the Realm one inside, cant find extension solution for that since the function is based on extension and protocol already

@Tj3n which branch are you using? Cant really find this mantioned change anywhere

@thepelican it haven't been implemented yet in the lib, i changed it for my own use only, this depends on the author, he might create another function for that

@Tj3n feel free to propose your solution. I'm more than open to discuss it and merge it into the repository. I haven't started working on it yet 😛

This is actually a critical for Realm user but it's pretty easy to fix, since CoreData's NSManagedObjectContext: Context doesnt seems to do anything with the insert function, i just change it to func insert<T: Entity>(entity: T, update: Bool) throws and use the update param to pass to the Realm's add function inside it

this issue its been closed but its not being resolved


MSID: 90634 Version: 2 DOI: 10.1101/2<IP_ADDRESS>87656

MSID: 90634
Version: 2
Preprint DOI: https://doi.org/10.1101/2<IP_ADDRESS>87656
Step 1. Awaiting reviews
Editorial to post reviews via hypothesis
Useful links:

DocMap: https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v2/by-publisher/elife/get-by-manuscript-id?manuscript_id=90634
New model tracking: https://docs.google.com/spreadsheets/d/1_fHaoOy7hjyocptKtVJRijeNpUY4hBS7Ck_aVmx6ZJk/
Reviews on sciety: https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>87656

For trouble shooting (e.g. no Docmaps available):

DocMap issue addressing: https://miro.com/app/board/uXjVNCwK6EI=/
Explore DataHub DocMaps API: https://lookerstudio.google.com/reporting/4c2f0368-babb-4beb-b5b3-497e7e7b0f08/page/ejphD
Unmatched submissions and preprints: https://lookerstudio.google.com/u/0/reporting/9f86204f-3bf7-477c-9b18-5c5ef141bf69/page/p_gxi57ha93c
Unmatched manuscripts spreadsheet: https://docs.google.com/spreadsheets/d/15QcK8w-ssB7109RQEDtFpJPZ0J5HTGxoHa_2TtpMBbg/edit#gid=1336081641

Step 2. Preview reviewed preprint
Production QC content ahead of publication
Instructions:

QC preview: https://prod--epp.elifesciences.org/previews/90634v2
Update ticket with any problems (add blocked label)
When QC OK, add QC OK label to ticket and add publication date and time to https://docs.google.com/spreadsheets/d/1amAlKvdLcaDp5W8Z8g77NmkwbMF5n_u89ArSqPMO8jg
Move card to next column
(At end of the day post link in #enhanced-preprint and ask for PDF to be generated)

Useful links:

Preprint DOI :  https://doi.org/10.1101/2<IP_ADDRESS>87656
Confirm reviews returned by EPP: https://prod--epp.elifesciences.org/api/reviewed-preprints/90634/v2/reviews
To update the MECA path in the docmap: https://docs.google.com/spreadsheets/d/1mctCQuNFBjSn97Lihy7_vBO6z7-N-oqyLv4clyi6zHg

Step 3: Awaiting search reindex
This step adds the reviewed preprint to the homepage: https://elifesciences.org
The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.
Useful links:

Jenkins pipeline to reindex search can be triggered sooner or monitored here: https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 4: Published! PDF requested
Waiting for PDF to be generated
Useful links:

PDF tracking: https://docs.google.com/spreadsheets/d/106_XeDjmuBae7gexOTNzg60lapeqjl2aRn9DzupGyS8/

Step 5: Introduce PDF to data folder and git repo
Upload PDF to relevent folder in git repo https://github.com/elifesciences/enhanced-preprints-data/
Step 6: Done!

[ ] Kettle is on!

warn: Content of <title> element is entirely in upper case: Is that correct? 'RL'
warn: Content of <title> element is entirely in upper case: Is that correct? 'KF'
warn: Content of <title> element is entirely in upper case: Is that correct? 'ACKOWLEDGEMENTS'


Cannot override getActivity of FlutterFragment

Steps to Reproduce

class TestFlutterFragment : FlutterFragment(){
override fun getActivity(): Activity? {
return activity
}
override fun getContext(): Context {
return context
}
override fun getLifecycle(): android.arch.lifecycle.Lifecycle {
return lifecycle
}
}

...

...

Target Platform:
Target OS version/browser:
Devices:
Logs

'getActivity' in 'FlutterFragment' is final and cannot be overridden |

Unresolved reference: arch |
-- | --

You cannot override the getActivity method of a Fragment.  This is an Android thing, not specific to Flutter.
There's really no action for us to take on this bug - you can read more here: https://developer.android.com/reference/android/app/Fragment#getActivity() (notice it's declared as final).

@dnfield the issue is that it's using android.arch.lifecycle.Lifecycle instead of androidx.lifecycle.Lifecycle. I'm having the same issue and is blocking me atm

@oth-libs that should habe a new bug tracking it


Fix closure issue in statement expressions

Purpose
Fixes #21806

Codecov Report

Merging #22473 into master will decrease coverage by 0.12%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #22473      +/-   ##
==========================================
- Coverage   14.72%   14.59%   -0.13%
==========================================
  Files          51       51
  Lines        1399     1411      +12
  Branches      214      219       +5
==========================================
  Hits          206      206
- Misses       1177     1189      +12
  Partials       16       16

Impacted Files
Coverage Δ

tool-plugins/vscode/src/core/extension.ts
27.23% <0.00%> (-1.14%)
:arrow_down:

tool-plugins/vscode/src/extension.ts
0.00% <0.00%> (ø)

Continue to review full report at Codecov.

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


Port view_compaction test to elixir

Overview
This PR ports view_compaction.js test into the elixir test suite
I've modified the tests to use 1.000 docs and not 10.000 docs like the original one. With this change, the execution time is reduced in 10 seconds.

Testing recommendations
 make elixir tests=test/elixir/test/view_compaction_test.exs

Related Issues or Pull Requests
N/A

Checklist

[X] Code is written and works correctly
[X] Changes are covered by tests
[ ] Any new configurable parameters are documented in rel/overlay/etc/default.ini
[ ] A PR for documentation changes has been made in https://github.com/apache/couchdb-documentation

Thanks! @dottorblaster


URL SHORTENER

URL SHORTENER
A URL shortener is a website that shortens a long URL (Uniform Resource Locator) into a shorter, unique link. The shortened URL redirects to the original long URL when clicked.
I have completed this project by using html, css and javascript.
Screenshots (optional)

I am a contributor in OSEN open source programme
I am a contributor in HACTOBERFEST 2023

@Geeks-Arpan please fill up the issue properly

@apu52 ok

@Geeks-Arpan Welcome to Metaverse!!!!!!!
Please go through contributing.md before contributing


Update config crd

What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #109
Special notes for your reviewer:

Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.

Release note:

/lgtm
/approve

Fixed https://github.com/IBM/operand-deployment-lifecycle-manager/issues/109


[API Reference docs] Lack of images

Some images are not rendered correclty in the documentation, and a process needs to be set regarding the contribution of assets to the repository.

Agree with you that building and viewing the docs offline would be ideal. Right now the images are hosted somewhere else than in the documentation, for example here: https://huggingface.co/datasets/huggingface/documentation-images/tree/main
The reason why it's not the case right now:

Images can end up weighing a significant amount and cannot be removed from the git history once merged into main, resulting in an unnecessarily long git clone
I understand there may be issues related to serving objects coming from repositories (cc @mishig25 @Pierrci)

It'll be the website repo which gets large, not a repo which is cloned by people, so clone time shouldn't be an issue, and in CI we can shallow clone which fixes the size issue.
Once in a while, if the website repo gets too large, we can collapse its history, since it's not important (ref: https://github.com/scikit-learn/scikit-learn/issues/21171)


UI glitch showing transparent dropdown menu

Expected Behaviour:
in the section to set up coupons, the windows should be displayed correctly.
Actual behaviour:
the window to select which category to assign the coupons to is transparent as shown in the image.
Reproduce steps:
Go to the "coupons" section, create a new coupon, set which categories the coupon is valid for.
Version:
v.3.0.4-beta.24.2

Use issues to report bugs, please start a discussion on the forums or better still search the forums for existing solutions.

But @sampoyigi this is a bug the drop-down should NOT be displayed in this way


[REQ] add HyMPS

Hi there,
thanks for this interesting list !
We've added in the Collections page under the AUDIO section of our HyMPS project !
Please check it out and, if you like, please add it both in your More lists page and Open Source Plugins & Software page \ More lists section.
Thanks in advance !

Awesome, looks great! Added it in c9162d3e7e19d160ab5b49a0f4684f75202de0c9

Thanks for the add.
If possible we ask you to use the official link to the project (https://www.forart.it/HyMPS) which correctly+transparently redirects to the repository and at the same time allows us to monitor how many peoples choose to visit it.
Thanks again.

Alright, updated the link in e50c968136ebcb7ef2853db59fdd5f5315f21443