ledscom.de light are added - can control on/off and dimming but I get error when changing color/temperature

Hello,
this is the output of the test python script
Getting devices
Got devices
{   'header': {'code': 'SUCCESS', 'payloadVersion': 1},
    'payload': {   'devices': [   {   'data': {   'brightness': '1000',
                                                  'color_mode': 'white',
                                                  'color_temp': 18718,
                                                  'online': True,
                                                  'state': 'true'},
                                      'dev_type': 'light',
                                      'ha_type': 'light',
                                      'icon': 'https://images.tuyaeu.com/smart/solution/33002/af6840901e01955c_cover.png',
                                      'id': '645232462----------',
                                      'name': 'Kitchen 1'},
                                  {   'data': {   'brightness': '1000',
                                                  'color_mode': 'white',
                                                  'color_temp': 36294,
                                                  'online': True,
                                                  'state': 'true'},
                                      'dev_type': 'light',
                                      'ha_type': 'light',
                                      'icon': 'https://images.tuyaeu.com/smart/solution/33002/af6840901e01955c_cover.png',
                                      'id': '46477000------------',
                                      'name': 'Kitchen 3'},
                                  {   'data': {   'brightness': '1000',
                                                  'color_mode': 'white',
                                                  'color_temp': 18329,
                                                  'online': True,
                                                  'state': 'true'},
                                      'dev_type': 'light',
                                      'ha_type': 'light',
                                      'icon': 'https://images.tuyaeu.com/smart/solution/33002/af6840901e01955c_cover.png',
                                      'id': '46477000---------------',
                                      'name': 'Kitchen 2'},
                                  {   'data': {   'brightness': '500',
                                                  'color_mode': 'white',
                                                  'color_temp': 18612,
                                                  'online': True,
                                                  'state': 'true'},
                                      'dev_type': 'light',
                                      'ha_type': 'light',
                                      'icon': 'https://images.tuyaeu.com/smart/solution/33002/af6840901e01955c_cover.png',
                                      'id': '464770002462ab4fbf82',
                                      'name': 'Bar'}],
                   'scenes': []}}

If I try to change the colour / temperature from homekit I get a "no response" error.
If there is anything to do in order to fix that I would appreciate.
Otherwise thanks for the amazing plug in.

Auth the very least, some logging output would be nice 🙂

12/5/2020, 4:06:47 PM [TuyaWebPlatform] [Bar] Characteristic.On - [SET] true 1
12/5/2020, 4:06:51 PM [TuyaWebPlatform] [Bar] - [SET] Invalid payload in response: {"payload":{},"header":{"payloadVersion":1,"code":"UnsupportedOperation"}}
12/5/2020, 4:06:51 PM [TuyaWebPlatform] [Bar] - [SET] Invalid payload in response: {"payload":{},"header":{"payloadVersion":1,"code":"UnsupportedOperation"}}
12/5/2020, 4:06:57 PM [TuyaWebPlatform] [Bar] Characteristic.ColorTemperature - [SET] 327 2852
12/5/2020, 4:07:03 PM [TuyaWebPlatform] [Bar] - [SET] Invalid payload in response: {"payload":{},"header":{"payloadVersion":1,"code":"UnsupportedOperation"}}
12/5/2020, 4:07:03 PM [TuyaWebPlatform] [Bar] - [SET] Invalid payload in response: {"payload":{},"header":{"payloadVersion":1,"code":"UnsupportedOperation"}}
12/5/2020, 4:07:07 PM [TuyaWebPlatform] [Bar] - [SET] Invalid payload in response: {"payload":{},"header":{"payloadVersion":1,"code":"UnsupportedOperation"}}
12/5/2020, 4:07:07 PM [TuyaWebPlatform] [Bar] - [SET] Invalid payload in response: {"payload":{},"header":{"payloadVersion":1,"code":"UnsupportedOperation"}}
12/5/2020, 4:07:18 PM

some colors seem to work and some do not. thanks for the swift response

It seems like you should be able to set the color but not the color temperature?

I am just tapping the default home kit lamp 6 colors

upeer right seems to work the rest seem to produce the error

FYI I can make the white cold or warm in the smart life app

What happens when you press the color in homekit twice to "edit" it? And from there select a color temperature instead of just a color?

Color temperature seems to work where colors do not work. Can I somehow define that the lamps only support temperature change?

You can't at the moment but that is a very welcome feature.
I started developing this plugin with the intention of minimising the amount of changes that users can make (the plugin should have sensible values and use its input to "configure" itself).
Slowly I am starting to figure out that this does not work and I'm adding more configuration options.
This will probably take some time though 🙂
You can speed this process up by providing a MR or donating 😄

What is an MR and how can I donate?
Again, thanks for this!

A MR is a Merge Request.
This is when somebody writes codes and asks me to put it in this plugin.
For donations please see this plugins GitHub page
Paypal Donation link

I have never written anything for homebridge (I am a Java developer myself). I don't think I can help with an MR but I did send a small donation your way. Regards.

Working out the last bugs on this one before I'll release a new beta release; expect that to land somewhere this week.

v0.5.4 is released as a pre-release version and has support for overwriting plugin decision.
You can now force hue to be enabled.
Overwrite your device to a lightbulb and enable color.
Please open another issue if you are still experiencing problems.


[Suggestion] Close input when the media muxer freed.

When I stop recording, the recorded file will be locked. I can't delete it. After I close the input context, the problem is solved. Please see the code.
protected override void Free()
{
    if (_ctx != null) {
        ffmpeg.av_write_trailer(_ctx);
++      fixed (AVFormatContext** c = &_ctx) ffmpeg.avformat_close_input(c);
        ffmpeg.avformat_free_context(_ctx);
        _ctx = null;

        if (!_iocLeaveOpen) {
            IOC?.Dispose();
        }
        _tempPacket?.Dispose();
    }
}

Fixed in v2.0.0, thank you!


Fallback from env

This adds fallback from env (useful for heroku)

This is the major change
https://github.com/BustByte/coronastatus/pull/359/commits/6b0697e05d06daaf6a41520b2b8007da809ba879

A few issues with the linter, could you fix those?

Could you also try to rebase on BustByte:master or reset? The commits are getting pretty messy at this point, hard to review :)

Going to fix everything


add changelog

can you please add changelog.
what is CHANGELOG ?

A changelog is available on the releases page.

oh.... it is part of release. hmm...
i was expecting in a separate file, helps me understand the direction and progress of project over a period of time.
something is better than nothing.

There is also a per-release changelog available in the fastlane directory, sorted by the current versionCode, for use with the F-Droid store. However, I prefer to have as few places as possible to store the changelog, that's why I recommend the releases page :-)


Integrate provider fileinfo

Fixes #961 .
Changes proposed in this PR:

integrate provider fileinfo function

don't bother with encrypt, already handled in the publish pr

Now after merging publish PR into v4 what we have in there right now all works, including the file check addressed in here. From what I see it would be a matter of which pattern to choose if we want to continue on here. In v4 for the file info we hit the provider API directly while for encrypt method we use ProviderInstance.encrypt so for consistency we also should use ProviderInstance.checkFileUrl for getFileInfo(). This should stay as individual method cause we need file info also in other places.
But I tried to implement the changes in here in my local v4 branch but I can't get ProviderInstance.checkFileUrl to return an actual response. The network response works but that method never gives me the actual response. Were you able to make this work in this branch? Meaning were you actually able to add a file in the UI with this change?

Were you able to make this work in this branch? Meaning were you actually able to add a file in the UI with this change?

I did, but using a local version of ocean.js which included a change  (discussed with @bogdanfazakas , bot not merged yet) that allowed market client to use an axios method, as a fetch method for ProviderInstance.checkUrlFile, in the idea that it would be more consistent to use only axios fetch methods.
I just converted the fetchMethod to fetch, so now it works.


Time complexity of TAPE

Thanks for sharing your work, it's very inspiring.
We noticed that you seem to be using OpenAI's API for per-node information extraction, which seems to be the main reason for the performance improvement. But multi-threaded use of the API is fast, so where are the time-consumption statistics you provide in your paper coming from? Is it a fine-tuning for downstream LM?

Hi, thanks for your interest in our work. As you have noticed, the multi-threaded use of the API is fast. Therefore, we didn’t take the time of ChatGPT API calls into consideration when calculating the time consumption. The time consumption statistics provided in our paper refer to the time for fine-tuning the LM (i.e., DeBERTa) and for training the GNN.


[IGNORE PLEASE] Azure SDK for C++: verify on VcPkg's CI/CD

Please ignore this PR - I am testing if a release we are going to publish relatively soon would have any problems, so we catch them early.

/azp run

@antkmsft Do we need to fix the SHA value?
The CI is failing with sha mismatch errors (surprisingly only on win x86). Any ideas why?
https://dev.azure.com/vcpkg/public/_build/results?buildId=48820&view=logs&j=0a61404f-5c45-5632-e83c-408b7fcca1d6&t=a3e8ae58-f7e4-5657-8106-10b6dc738157
Found the following errors:
Error: While reading versions for port azure-core-cpp from file: C:\a\1\s\versions\a-\azure-core-cpp.json
       File declares version `1.0.0-beta.5` with SHA: 1bcedf8a5777f656642f0a4f9ae6ad7352fa2087
       But local port with the same verion has a different SHA: c7b7a6dcc2fae649ddfe068fe48388ac3d4167fc
       Please update the port's version fields and then run:

           vcpkg x-add-version azure-core-cpp

Yes, as part of adding versioning support to the tool, we need to maintain a database of all previous versions of the port.
The procedure you probably want to use for automation is:
> generate files
> git commit -am "temp"
> vcpkg x-add-version azure-core-cpp
> vcpkg x-add-version azure-core-common-cpp
> ...
> git commit --amend -am "[azure-sdk-for-cpp] Automatic update to $version"

This double-commit process is needed because we reference the git tree object for the port in the version database; the first commit creates all the intermediate git objects so that x-add-version can read them.

Should this be closed?

Yes, we can close this draft PR. Thank you.


new! doesn't work well with string key maps

For example, define a struct named Test with a field called foo of type string:
defmodule Test do
  use Flint.Schema

  embedded_schema do
    field :foo, :string
  end
end

When calling new! with the atom key map Test.new!(%{foo: 1}), it will raise an exception:
** (ArgumentError) %Test{foo: ["is invalid"]}
    (flint 0.6.0) lib/schema.ex:445: Flint.Schema.new!/3
    #cell:5kooho4pfqmyzjah:1: (file)

When calling new! with the string key map Test.new!(%{"foo": 1}), it will raise another exception:
** (KeyError) key "foo" not found
    anonymous fn/2 in Test.__struct__/1
    (stdlib 6.0) maps.erl:860: :maps.fold_1/4
    (elixir 1.17.2) lib/kernel.ex:2463: Kernel.struct!/2
    (flint 0.6.0) lib/schema.ex:445: Flint.Schema.new!/3
    #cell:3pmvlnztbon6drwt:1: (file)

I think this is an unexpected behavior, the string key map input's exception should be align with atom key map.

I think this is expected. The first error is an error from the type different since you specified the field is a :string but you provided an int. The second error is because the string key is different from an atom key, which also makes sense.

@acalejos but new accept both string and atom key map.


Check if Metadata references a NoEcho parameter

Description of changes:
If a resource's metadata section contains a reference to a NoEcho parameter, CloudFormation will display the plaintext value of the parameter's description. This new rule will detect if any resource references a NoEcho parameter, and raise a warning.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Do we know why this is flagging NoEcho parameters in AWS::CloudFormation::Interface templates?
cfn-lint test/fixtures/templates/quickstart/nist_application.yaml --ignore-checks E3012 W3005
cfn-lint test/fixtures/templates/quickstart/vpc-management.json --ignore-checks E3012 W2509 W3005

https://github.com/aws-cloudformation/cfn-python-lint/blob/f209ddfef9bcc1a005adfebcfcc16220b18deddb/test/fixtures/templates/quickstart/nist_application.yaml#L68
https://github.com/aws-cloudformation/cfn-python-lint/blob/f209ddfef9bcc1a005adfebcfcc16220b18deddb/test/fixtures/templates/quickstart/vpc-management.json#L5-L42
and should it?

also crashing on this valid template:
Parameters:
  Parameter:
    Type: String
    NoEcho: true
Resources:
  Resource:
    Type: AWS::SNS::Topic
    Metadata:
      meta: data

E0002 Unknown exception while processing rule W4002: malformed node or string: <_ast.Name object at 0x112c11e50>

also crashing on this valid template:
Parameters:
  Parameter:
    Type: String
    NoEcho: true
Resources:
  Resource:
    Type: AWS::SNS::Topic
    Metadata:
      meta: data

Not sure where @PatMyron grabbed this template from but @Birds please ensure that it is a unit test :)

Parameters:
  Parameter:
    Type: String
    NoEcho: true
Resources:
  Resource:
    Type: AWS::SNS::Topic
    Metadata:
      meta: data

Valid and invalid unit tests are included! There was a variety of syntactical errors and lack of error catching which has been implemented.

Made a few suggestions and I know multiline suggestions aren't great.  Sorry about that.

not sure how customers should remediate this warning since dynamic references don't always work there:
https://github.com/aws-cloudformation/aws-cloudformation-coverage-roadmap/issues/179
https://stackoverflow.com/questions/53589880/dynamic-references-to-specify-secret-manager-values-in-aws-cloudformation
and cfn-init relies on metadata:
https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-init.html#aws-resource-cloudformation-init-syntax


Updating with the new futures examples. Also changing "samples-files"…

… directory on dartlang to "f".
@kwalrath
Kathy, I also have a CL ready to go, but first I want to update the tutorial example repo, and then I have to create new gist files and land the dartlang CL at the same time.

LGTM


feat(openamt): add AMT Devices information in Environments view [INT-8]

Closes INT-8
Show raw AMT RPC information in edit endpoint view  (only for Docker environments)

Show managed devices information in endpoint list view
disconnected:

connected:

except that my endpoints don't get the AMTDeviceGUID stored on the server side, it works on my now activated device.
I have to use the js debugger to set item.AMTDeviceGUID though (on that v9 device, the rpc-go code doesn't return a guid I'm reporting an issue upstream

except that my endpoints don't get the AMTDeviceGUID stored on the server side, it works on my now activated device.
I have to use the js debugger to set item.AMTDeviceGUID though (on that v9 device, the rpc-go code doesn't return a guid I'm reporting an issue upstream

I'm working on an initial version of INT-7  that will allow us to manually set the AMTDeviceGUID, at least for testing purposes


Prevent exit when connection attempt fails.

Check that the "error" event has any registered listeners before emitting it. This prevents the process from dying as that would be the default behaviour in node.
This PR resolves issue #219.

Fixed on master.


Unsolvable error

Hi.. following your repository..I encountered the following error
Traceback (most recent call last):
File "convert_torch.py", line 314, in <module>
torch_to_pytorch(args.model,args.output)
File "convert_torch.py", line 303, in torch_to_pytorch
lua_recursive_model(model,n)
File "convert_torch.py", line 64, in lua_recursive_model
copy_param(m,n)
File "convert_torch.py", line 44, in copy_param
if m.weight is not None: n.weight.data.copy_(m.weight)
RuntimeError: The expanded size of the tensor (3) must match the existing size (27) at non-singleton dimension 3

I am trying to convert vgg_face.t7 into pytorch model. Could you kindly assist me to solve this error.
Any sort of assistance would be highly appreciated.
Thanks in advance

I had the same error when I convert VGG-Face torch model to pytorch. It must be related to a Pytorch update (my Pytorch version is 0.5.0a0+7924530).
It says that tensor sizes (weights of Conv2d layers) are not matching. I changed line 44 like this:
if m.weight is not None:
	m.weight.data = m.weight.view(n.weight.size())
	n.weight.data.copy_(m.weight)

I did not look through the rest of convert_torch.py file, but at least it works in Aamir Khan's picture :)

@omersumer seems that this method solved the problem as @shashankvkt mentioned.

I had the same error @shashankvkt , and answer from @omersumer perfectly solved my problem.  :)

@omersumer  sorry for the late response. Thank you for your help. It worked.


Explicitly merge module augmentation members into the exports added by export * declarations

Fixes #35483
If this fix seems odd to anyone, we could also approach this by flagging the situation as likely an error (rather than merging into the targets of the export *), or by calling the current behavior "surprising but expected" and leaving it as-is. But given the mental model of augmentations (modifying the exports of another module), I think today's behavior of not actually augmenting exports introduced by export *'s is a little too surprising, so would rather see us change that behavior.

@typescript-bot user test this
@typescript-bot test this
@typescript-bot run dt

I just tried this out locally, but I changed the real exported symbol to an enum, and the one in the module augmentation to a namespace, and it seems like the enum got overwritten. I then tried making both declarations enums, and then the module augmentation got shadowed. (I’m guessing the order was dependent on my exact editing scenario, and might be unstable.)

Two interfaces worked fine, two namespaces did not.
An enum and an interface raised the appropriate error.
A class and an interface seemed to work

Maybe there are issues when both symbols have a value meaning?

@typescript-bot user test this
@typescript-bot test this
@typescript-bot run dt
just in case~


Update set-up-common-area-phones.md

updated the content of Setup common area phone article for content freshness

Closing and moved over to the private repo: https://github.com/MicrosoftDocs/OfficeDocs-SkypeForBusiness-pr/pull/12910


Narwhal Bot isn't triggering tests when it comments "/test all"

https://github.com/defenseunicorns/delivery-aws-iac/actions/runs/6184799976/job/16789130985?pr=352

yeah.. I think we may need to trigger it similarly to how we trigger update in that same workflow


Update iobench.sh

Wouldn't urandom be a better choice for a benchmark? Zeros can be cached easily and that could potentially distort the results.

I dont think this is a good idea because on slow systems random/urandom will be the bottleneck.
To implement this it should be optional (activate by an argument option) and the script must create a temporary file before the test starts. Otherwise you test the random/urandom performance and not the filesystem performance 1.


Fix - LoginScreen use email keyboard type and disable auto complete

@marcaaron
I have read the CLA Document and I hereby sign the CLA
Details

We are using the default react native text input props autoCompleteType={"off"} and keyboardType={"email-address"}.
Fixed Issues

Fixes #1524
Tests

Go to the login screen and click on the enter your phone or email field, email type keyboard will open and when user type the email auto correct is disabled.
QA Steps

Run the application
Login screen show
Click on the enter your phone or email field
Email type keyboard will show and auto correct is disabled

Tested On

[ ✅] Web
[ ] Mobile Web
[ ✅] Desktop
[ ✅] iOS
[ ] Android

Screenshots

Web

Mobile Web

Desktop

iOS

Android

Nice catch @HorusGoul

We could disable the html5 validation for this text field to solve this accessibility issue. Let me know what you think.

Any thoughts on how we can do this?

Nice catch @HorusGoul

We could disable the html5 validation for this text field to solve this accessibility issue. Let me know what you think.

Any thoughts on how we can do this?

I checked the react-native-web code to see if there's a way to set the input mode to email and use type=text but there's no way right now. https://github.com/necolas/react-native-web/blob/master/packages/react-native-web/src/exports/TextInput/index.js#L140
The easiest way right now would be to not use keyboardType when targeting the web platform so it renders using type="text".
Like this:
keyboardType={Platform.OS !== 'web' ? 'email-address' : 'default'}

@marcaaron  - Hi Marc, I am also think to put Platform check like @HorusGoul suggest. Please let me know I put the Platform check and commit my changes.

@HorusGoul nice, that seems reasonable to me. Just a small note that we are trying to avoid Platform usages in the code so that we are making few exceptions. There's some more guidance on how to handle this here -> https://github.com/Expensify/Expensify.cash/blob/main/README.md#platform-specific-file-extensions
@dharammachra The solution works for me, but the correct way to do it is something like a helper method
getEmailKeyboardType() with the following structures
.
└── libs/
    └── getEmailKeyboardType/
        ├── index.js        - return () => 'default'
        └── index.native.js - return () => 'email-address'

@marcaaron - I have committed the changes,  @HorusGoul so could you please review and merge the code.

@HorusGoul  - I fixed the lint errors and committed the code.

I believe this PR has caused a regression as I'm unable to run Android. I also see that we skipped testing for a couple of platforms (one of them Android). Please ensure all PRs are tested against all platforms. Thanks!

Gonna revert this so that Android is usable again.

@marcaaron @kadiealexander - Hi Marc, I have fixed the Android auto correct issue and committed the changes. Please find the attched screen shot. So could you please let me know the next step.

@HorusGoul  Hey mate! Since Marc's on leave, would you mind reviewing this PR?

@kadiealexander Sure!

Hey @dharammachra, you'll need to open a new PR with all the changes so we can review it again.


Type check failed for min, max on URange

Hi,
I have this Vue warn when setting min or max on URange component :
[Vue warn]: Invalid prop: type check failed for prop "min". Expected Number with value 0, got String with value "0".
I tried with and without quotes :
    <URange v-model="sourceSize" min="0" max="500" />
    <URange v-model="sourceSize" min=0 max=500 />

First is from the docs. Both versions raise the same Vue warn. My guess is props given with the min="0" or min=0 will still be STR type.
I tried with :min=0 and no Vue warn.
It's not a big deal, but maybe we should update the docs, or update the types in the component ?

Of course... Thanks a lot ! I don't know why I didn't see this one earlier 😅


Windows 11 (Defender): Trojan:Win32/Bearfoos.B!ml Trojan Virus

Hello,
there is an issue with app on windows 11. Windows Defender moves the app into quarantine and it is recognized as Trojan virus.
Should I add this app to exceptions list or is there better way how to handle it?

Also you can report this false positive to Microsoft from the defender app, if that's possible. That'll help them improve their detection.

See e.g. https://superuser.com/questions/1416678/my-own-backup-program-was-detected-as-win32-bearfoos-aml-virus


Add CDN Installation Instructions.

The PRs got merged with both the CDNs and the files are live :)
This PR Closes #19.
Also, I was thinking maybe we should update the CDN instructions like this, instead of the current one with version:

jsDelivr:

<script src="//cdn.jsdelivr.net/layzr.js/{version}/layzr.min.js"></script>

cdnjs:

<script src="//cdnjs.cloudflare.com/ajax/libs/layzr.js/{version}/layzr.min.js"></script>

Replace {version} with the library's version you want to use. Refer releases section for all the versions. Ex: 1.2.2.

So that way, You need not worry about updating the README on every release you do, otherwise you'd have to always update the version number in README.
@callmecavs What you think about this?

looks good to me! about to merge it and make some small copy edits.  thanks again for the pull requests, and this, huge help

Awesome, No problem :)

went ahead and used your version stuff from above. also gave you a shoutout in the release notes for 1.2.3 :+1: thanks again bud

Cool, Looks good now :+1:
Thanks for the shoutout :smile:


Text overflow is not caught at build or runtime if implicitly converting Guid to Text or Code, AND it changes MaxStrLen!

With this code:
pageextension 50100 Test extends "Customer List"
{
    trigger OnAfterGetCurrRecord()
    var
        TestCode: Code[20];
    begin
        TestCode := '';
        Message('MaxStrLen is %1 /  StrLen is %2', MaxStrLen(TestCode), StrLen(TestCode));
        TestCode := Rec.SystemId;
        Message('MaxStrLen is %1 /  StrLen is %2', MaxStrLen(TestCode), StrLen(TestCode));
    end;
}

The assignment of Guid to TestCode: Code[20] does an implicit conversion of the Guid to Text, but:

This is not warned at build time.
Nor does it cause an overflow error at run time! Only if we then use the Code[20] in another way, that will overflow, do we get a runtime error.

Worse... somehow the uncaught overflow of a 38-character string into the Code[20] causes the MaxStrLen() of said Code to change/increase to the overflowing length!!
The first Message(), before the offending assignment, shows:

The second, after the assignment, shows:

Pretty please... please fix so that

the implicit conversion of Guid causes code analysis warnings if the destination isn't long enough for the textual version;
said conversion will also cause runtime errors due to the overflow, instead of silently 'working';
the overflow should not be allowed, and certainly the MaxStrLen() of the destination shouldn't be increased to match!!

Thank you!

Name: AL Language
Id: ms-dynamics-smb.al
Description: AL development tools for Dynamics 365 Business Central
Version: 9.4.663067
Publisher: Microsoft
VS Marketplace Link: https://marketplace.visualstudio.com/items?itemName=ms-dynamics-smb.al

The fix for this issue has been checked in to the master branch. It will be available in the bcinsider.azurecr.io/bcsandbox-master Docker image starting from platform build number 23.0.10590.0 and VS Code Extension Version 12.0.790342.
If you don’t have access to these images you need to become part of the Ready2Go program: aka.ms/readytogo
For more details on code branches and docker images please read:
https://blogs.msdn.microsoft.com/nav/2018/05/03/al-developer-previews-multiple-releases-and-github/
https://freddysblog.com/2020/06/25/working-with-artifacts/


Fixed issues found while testing on Ubuntu Trusty 3.13 64 bits

Path in upstart script is wrong "cito" instead of "cito_plugin_server": cp /opt/cito/bin/upstart/cito-plugin-server.conf /etc/init/

distribute package 0.6.45 version failing to install even after upgrading setuptools (error: "NameError: name 'sys_platform' is not defined"), however modifying requirements file to instead use version 0.7.3 solved the issue.

cito-plugin-server.sh script is not launching the app, upon debugging found that "python manage.py run_gunicorn.." command is failing with "Unknown command: 'run_gunicorn'" error everytime even after confirming "gunicorn" package is there in "INSTALLED_APPS" in base.py. Able to launch app succesfully in development mode by running : "python manage.py runserver <IP_ADDRESS>:9000". Finally, found a workaround by editing the startup script file to launch the app like:

This is the workaround command for starting the app if run_gunicorn fails
gunicorn --workers=$NUM_WORKERS
--user $USER
--group $GROUP
--log-level=debug --log-file=$LOGFILE 2>>$LOGFILE --bind $BIND_IP
cito_plugin_server.wsgi

@OscarLopezEns: Thanks for bringing this up, it has really been a while since the plugin server was looked into. Can you please raise it against the develop branch?

Hi Cyrus,
Sure! Done.
https://github.com/CitoEngine/cito_plugin_server/pull/9
Oscar López | Service Manager
Softtek | Carretera Ensenada – Tecate KM 104 | Parque Industrial El Sauzal Nave 1 | Ensenada, Baja California, México, 22800
Tel: 52<PHONE_NUMBER> | www.softtek.comhttp://www.softtek.com
From: Cyrus Dasadia<EMAIL_ADDRESS>Sent: Tuesday, July 25, 2017 8:04 PM
To: CitoEngine/cito_plugin_server<EMAIL_ADDRESS>Cc: Oscar Alejandro Lopez Valencia<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [CitoEngine/cito_plugin_server] Fixed issues found while testing on Ubuntu Trusty 3.13 64 bits (#8)
@OscarLopezEnshttps://github.com/oscarlopezens: Thanks for bringing this up, it has really been a while since the plugin server was looked into. Can you please raise it against the develop branch?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/CitoEngine/cito_plugin_server/pull/8#issuecomment-317934204, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AXrcWb_Hd0MGT6DqrwyQIb0CRCwVhVi6ks5sRqyJgaJpZM4OjS15.


2 new zones added to azure, Canada Central & Canada East

Microsoft Azure just added 2 new zone to their infrastructure, Canada East and Canada Central.
It would be great if these zone were added to the speedtest.
You can see the 2 new regions here : https://azure.microsoft.com/en-us/regions/

thanks, yes, I'd like to add them in, however, they don't show up in my portal. I need someone in Canada to create a couple of storage accounts :¬)

Created both speedtestcae.blob.core.windows.net and speedtestcac.blob.core.windows.net for Canadian zone East and Central respectively.
Do i need to add files or something else ? do you know how much traffic/cost i can expect running these storage accounts ?

Awesome - thank you!
Could you:

Create a container in each blob storage account called $root.
Set the access permissions to public.
upload a file called cb.json to each container

The cb.json file should contain this text:
call("speedtestcae")

and
call("speedtestcac")

...respectively.
The cost to your azure account should be negligible. If at any time you wish to withdraw your storage accounts, let me know and I'll find an alternative.
Thanks!

speedtestcac.blob.core.windows.net/cb.json
and
speedtestcae.blob.core.windows.net/cb.json
should be working.

it's live, thanks for your help!


Properly handle opening files when OSX is default

userAgentClient is now attached to electron.app and we can use that as a global to determine state of the application startup, and simplify interfaces like in browser-window
Now handles opening via command line on OSX/Windows(?) via open -a Tofino https://mozilla.org needs confirmed in Windows
Windows should now be able to open links when it's the default if it's closed or open already -- needs confirmed

** To confirm on Windows **

[ ] Handles open -a Tofino https://mozilla.org or whatever the CLI equiv on Windows is
[ ] When set as default browser, should open a tab for a link while open
[ ] When set as default browser, should open a tab for a link while closed
[ ] When opening an incoming link, it should not create a new instance and open it in an existing window/create a new window

This does not ask Windows users if they want to set Tofino as a default browser, due to issues with Windows 10 defaults.

This also moves Deferred to a shared util, gets rid of the URL_QUEUE as we can now wait for app initialization, and removes the passing in of a callback for createBrowserWindow since it also returns a promise.

Fixes #1210

Migrating this to just handle the orchestration on OSX, and handle leaving implementing URL parsing only for non-OSX in a follow up in #1210


Client Apps (Preview) Options

[Enter feedback here]
Number 8 under "Create a Conditional Access policy" (https://docs.microsoft.com/en-us/azure/active-directory/conditional-access/howto-conditional-access-policy-location#create-a-conditional-access-policy) states to "set Configure to Yes" - however inside the Client Apps (Preview) there are several options under "Select the client app this policy will apply to" that would be worth reviewing in this documentation.
Also, Number 9 should be changed to "Access controls > Grant > Block Access" to reflect recent changes to the interface.

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

ID: 5815957c-cc37-2982-7a50-16e96c0378b8
Version Independent ID: 33f22bdb-1675-96b0-27ad-8d1ba7cc5a75
Content: Conditional Access - Block access by location - Azure Active Directory
Content Source: articles/active-directory/conditional-access/howto-conditional-access-policy-location.md
Service: active-directory
Sub-service: conditional-access
GitHub Login: @MicrosoftGuyJFlo
Microsoft Alias: joflore

@sanchezc10
Thanks for the feedback! We are currently investigating and will update you shortly.

Hello @sanchezc10, thanks for bringing this to our attention.
We have created a PR internally which will get merged soon.
We will now close this issue.


Broken on 1.2

The latest release (0.4.8) breaks apps using Angular ~1.2.0. Bower now resolves angular-animate to 1.3.0, which depends on angular#1.3.0. This introduces this issue;
Unknown provider: $$qProvider <- $$q <- $animate <- cfpLoadingBar <- $http <- $modal <- modals

Should've been a 0.5 release.

I think this issue is not valid anymore.


Can't validate challenge in --force update mode

Initial request goes well, certs are received. Restart with -c --force gives the following error:
 + Handling authorization for mail.*****.net
 + 1 pending challenge(s)
 + Deploying challenge tokens...
 + Responding to challenge for mail.*****.net authorization...
  + ERROR: An error occurred while sending post-request to http://mail.*****.net/.well-known/acme-challenge/cObz7GJQnfuChtfwBeqSSBL-_V1iPGQD4axGRsL403M (Status 301)

It seems that dehydrated tries to POST to my own server instead of ACME one. My own server uses redirect to HTTPS (that's why 301). It worked properly for initial request, doesn't work with --force.
--force is the reason. if I start it without certificates and use --force, it will fail too.
Ubuntu 18.04 LTS maintained version.
Dehydrated version: 0.6.1
GIT-Revision: unknown

OS: Ubuntu 18.04.1 LTS
Used software:
 bash: 4.4.19(1)-release
 curl: curl 7.58.0
 awk: GNU Awk 4.1.4, API: 1.1 (GNU MPFR 4.0.1, GNU MP 6.1.2)
 sed: sed (GNU sed) 4.4
 mktemp: mktemp (GNU coreutils) 8.28
 grep: grep (GNU grep) 3.1
 diff: diff (GNU diffutils) 3.6
 openssl: OpenSSL 1.1.0g  2 Nov 2017

This issue was already fixed, you just need to update dehydrated to the newest version.

Thank you.
In that case we need to ask maintainer of ubuntu packages to update as well.
I just checked again, it seems that the version installed from ubuntu package repository is still with that bug.


livez and readyz are missing from the api_server

Hello,
I am trying to deploy an LLM model using vLLM on Kubernetes. However, for K8, the readinessProbe and livenessProbe are needed to indicate the health of the api-server  and these endpoints are missing from the api_server.py
For that reason I have raised a simple PR to include the needed endpoints: https://github.com/vllm-project/vllm/pull/1244
Regards,
Petros Baltzis

one health endpoint was added https://github.com/vllm-project/vllm/pull/1540

Thanks for that! We already started using it!


Keep the workflow runtests.jl up to date!!

Title says it all, communicate your changes.

I fixed the error from the hydrogen mass. And I added a test to see whether the Unitful units are available to users. The way the test works is that if the units are not available, an error will be thrown and the test would fail.

The changes are in my lastest pull request.


Add fuzzing harness, in order to find panics through invalid input

This adds support for fuzzing the library input using https://github.com/rust-fuzz/cargo-fuzz, as a way to find bugs by looking for invalid input that causes the library to panic.
This library isn't really security sensitive, but even so, fuzzing it can find parser errors and other areas where it can panic when you wouldn't expect it to.

This is great, thank you!


Improve redability of config_statement.rs

Which component is your feature related to?
Forge
Feature Request
As in title. Reference https://github.com/foundry-rs/starknet-foundry/pull/2044#discussion_r1704031268

@ksew1 can you please assign this issue to me?


Find & Filter pattern feature request

Summary
Please describe your request in one or two sentences.
Clarify if you are asking for design, development, or both design and
development.
We have designed how this system would work and are requesting Carbon approval/integration.
Find & Filter allows users to locate individual or groups of items in a scalable way when working through large data sets. This includes a combination of a search field with auto-complete, a filter bar with maximum flexibility, and interoperability between the two components so that users with different mental models can achieve the same results. Find & Filter accommodates dynamic ways to filter their data with customizable dialogue menus, plus supports AND/OR operations. Find & Filter search with autocomplete makes relevant suggestions of categories or individual items that might match a user's partial entry. Finally, the two work together to seamlessly merge finding and filtering, allowing the user to type in a filter expression (or from an autocomplete suggestion) and easily apply filters from either component.
Justification
Provide the business reasons for this request.
Within IBM's Edge Application Manager, we noticed four needs that were not met by Carbon's current components and patterns:

A scalable dropdown/filter pattern that allows for large numbers of user-defined filter values. The existing solutions buckle under the infinite scale of user-defined filter categories.
A filter pattern that can display three-tiers of categories (e.g. Properties > Colors > Green)
When selecting multiple filters, a pattern that allows for a user to search for items that match ALL the filtering criteria, or ANY of the filtering criteria (referred to as "AND/OR Filtering'
A search bar with autocomplete for both individual items as well as filter categories, freeing the user from always typing in the complete query

The proposed Find & Filter pattern addresses all these needs in a way that potentially could be used across other IBM products.
Desired UX and success metrics

Describe the full user experience for this feature. Also define the metrics by
which we can measure success/failure for the user.
You can check out three user flows which highlight three different features in our InVision board here: https://ibm.invisionapp.com/share/THO13439ENU
Success: The user is able to successfully find results and sift through data using the new Find & Filter components.
Failure: The user continues to rely solely on string searches without using any of the new Find & Filter components (auto-complete, the filter menu dropdown, etc.)
Our team will also be conducting user research and usability testing on the proposed pattern to check the NPS score, functionality of the tool, and to understand our users' mental model.

"Must have" functionality
Highlight any "must have" needs and functionality for the request.
This should not be a full list of functionality; the Carbon team will work with
you to define functionality based on the desired UX.
Specific timeline issues / requests

Do you want this work within a specific time period? Is it related to an
upcoming release?
This pattern is related to a 2P release (May/June 2021).

NB: The Carbon team will try to work with your timeline, but it's not
guaranteed. The earlier you make a request in advance of a desired delivery
date, the better!
Available extra resources
What resources do you have to assist this effort?
We have developer buy-in to build the Find & Filter pattern out for both our product and for Carbon.
Carbon is a collaborative system. We encourage teams to build components and
submit them for integration as either add-ons or core components.

Hey @Unnati-Shukla 👋🏽 thanks for opening this issue. It seems your team has done a lot to prepare for this proposal and we appreciate it. Unfortunately, right now new pattern proposals aren't a priority for us since we're working on v11. If you wanted to try to get going on the next steps of what the process would be, this page will help you write out the documentation for the pattern: https://carbondesignsystem.com/contributing/pattern/#how-to-write-a-pattern


Update AIP File To Compile Under Freeware Version

By updating this file, you remove the line (Evaluation Version) from being added to all the binaries, making them smaller, and you also prevent Advanced Installer from prompting you to start a license trial and thinking that you need a valid license or license trial to compile the MSI when in reality you aren't using any of the paid features and Advanced Installer is just reading this part of the XML file and going "Oh the file says this so we must need a valid license file or trial to compile the product".
Don't ask me why the product doesn't have a better way of determining the requirements for licensing, I really have no idea why it decided that a line in an XML file is the primary determinant of what feature are required as I know there are better ways to do things, but it is what it is.
This also allows people to be compliant with the license requirements which state that:
2.2 Trial Period License. You may download and use the Software for free for thirty (30) days after installation ("Trial Period"). During the Trial Period, Caphyon grants You a limited, non-exclusive, non-transferable, non-renewable license to copy and use the Software for evaluation purposes only and not for any commercial use. At Caphyon's discretion, Caphyon may provide limited support through email or discussion forums at Caphyon web site. The evaluation copy of the Software contains a feature that will automatically disable the Software at the end of Trial Period. Caphyon will have no liability to you if this feature disables the Software.

Note that it explicitly states for evaluation purpose only and not for commercial use, whereas the freeware version states:
2.1 Freeware Features License. Caphyon grants you an unlimited license to use the Freeware Features of the Software. The install packages created using only the Freeware Features can be freely redistributed and used both in commercial and non-commercial purpose.

Or as a TLDR: we aren't using any paid features but due to this file it thinks we are. Since the freeware version doesn't impose any restrictions and we aren't using any paid features that require a paid license this kills two birds with one stone by complying with licensing and also prevents people accidentally starting a trial when they don't need to.

Thanks @gwillcox-r7 !


PR template small fix

Overview

Definition of Done

[ ] There are no TODOs left in the code
[ ] Change is covered by automated tests
[ ] The coding guidelines are followed
[ ] Public API has Javadoc
[ ] Method preconditions are checked and documented in the Javadoc of the method
[ ] Changelog is updated if needed (in case of notable or breaking changes)
[ ] The continuous integration build passes

I don't know why Grammarly marks me this sentence as red  🤕

Maybe it doesn't know TODO word and thinks that TODOs is singular.


Remoting Dependency Tracking Reporting Very Long Durations?

I'd like to better understand the numbers being reported by the dependency tracking for this package. After implementing it in our fabric cluster, it is working and we see all the requests in the cluster. What we're finding strange is the time to make remoting V2 requests between services that makes little sense. For example here's a snapshot of what that looks like for 1 request to our service.

From what I can tell, it is telling me that the remoting calls are taking ~1.2s each way for a request and its response to travel between 2 services in our cluster. Is this what it's telling me, because this seems extremely odd for remoting V2. Our cluster is running .NET Core 2.2 micro services on the latest version of service fabric.

Hi @ththiem,
When you said it's odd, do you mean 2.5 seconds round trip is unreasonable long and you believe it's not measuring correctly?
As a quick experiment, you can log separate before and after the call and see if the duration agree.

Sorry I haven't been able to return to this issue the last few days. I'm going through and trying a before & after log to check now.

We've been running a lot of tests to poke at this, and there is clearly something that doesn't make sense with what we're seeing in the logs, or something we don't understand. As a simple example, we tracked an event with a start and end time before and after an await call that just makes a RPC request to another service in our fabric (all of which is awaited), and we see conflicting timestamps between our custom events and the automatic dependencies. Here's a (simplified) snippet of our code:
`public async Task StartReadAsync()
{
using (var dataOperation = telemetry.StartOperation($"ProcessingBufferData"))
{
try
{
var timeTelemetry = new EventTelemetry("ProcessTime");
timeTelemetry.Properties["StartTime"] = DateTime.UtcNow.ToString("o");
...
await ProcessBinaryData(streamData).ConfigureAwait(false);
...
timeTelemetry.Properties["EndTime"] = DateTime.UtcNow.ToString("o");
telemetry.TrackEvent(timeTelemetry);
}
catch (Exception ex)
{
dataOperation.Telemetry.ResponseCode = "500";
telemetry.TrackException(ex);
}
}
}
public async Task ProcessBinaryData(CallStreamData streamData)
{
var timedEventTelemetry = new EventTelemetry("BinaryCall");
timedEventTelemetry.Properties["Start"] = DateTime.UtcNow.ToString("o");
		await SendBinaryDataByRemoting(streamData).ConfigureAwait(false);

		timedEventTelemetry.Properties["End"] = DateTime.UtcNow.ToString("o");
		telemetry.TrackEvent(timedEventTelemetry);
	}

private async Task SendBinaryDataByRemoting(StreamData streamData)
{
try
{
var service = ServiceProxy.Create(RemoteUri);
await service.SendStreamDataAsync(streamData).ConfigureAwait(false);
}
catch (Exception e)
{
telemetry.TrackException(e);
}
}`
And what the logs show:

Somehow, somewhere, 3 seconds is just "lost." Start and end times are within ~30ms of each other, but the actual call to the other service doesn't start until 3s later, even though the calls are awaited

@ththiem So which telemetry makes more sense to you, the automatic dependency with 3 sec or your manual telemetry with 40ms? I'm wondering whether the automatic/manual telemetry you're looking at are for the same transaction, e.g., it might be slow for the first call to initialize something (3s) but fast (40ms) afterwards.

Yes they're the same transaction, all under the same operation Id. We have full correlation illustrating this problem. Right now, neither of the telemetry make any sense. It's not queuing the remoting call to run in a background thread and continue without waiting. It is awaiting it, the code should run serially. The end timestamp should be recorded after the awaited remoting call completes. Instead it's timestamped before the call is even made? It makes no sense, and is making the metrics rather useless to look at since the numbers don't appear to be accurate nor reliable.

This is weird. The simplified code you posted here just looks fine. If you can create a simple project that reproduce this issue, I can take a look and do some debugging.


Year 2038 problem in message class

As i see, fields date_ and edit_date_ in class message declared as std::int32_t, this shold be fixed until the year 2038 problem occurred.

It will be fixed before 2038.


Aloha_Pineapple model changes

This project is part of a doctoral research on pineapple cultivation, cultivar MD-2 in Costa Rica.
The files contained therein are those that to this date have been modified from the original Aloha_Pineapple model files, and others contained in the InputModule and Genotype folders, with the following purposes:

To add more phenological stages to the existing ones in the Aloha_Pineapple Model available in version <IP_ADDRESS> of DSSAT.
To add more cultivar coefficients.
To calibrate the model with data from 3 contrasting natural conditions in terms of temperature and solar radiation.

Additionally, the executable file compiled in Microsoft Visual Studio Community 2019 Version 16.7.1 has been added.
To observe the differences between this compilation and the one currently available in DSSAT, one must run one of the experiments available for pineapple and for example open the Overview.out file. Subsequently replace the PIALO047.CUL file in the Genotype folder with the one in this repository and then replace the dscsm047.exe file that is in the DSSAT folder with the one in this compilation, run the same experiment and compare the differences in the new Overview.out. Note that more stages have been added, which are vegetative and reproductive phenological stages.
Currently the work has focused on creating a structure in the Aloha_Pineapple model compatible with the additional data that will be collected in the research. The author is not an expert in programming and all this work has been possible thanks to the instructions shared by the DSSAT foundation. Any help and advice will be very welcome.

these changes were brought in through chporter's pull request.

these changes were brought in through chporter's pull request.


License mismatch between repo and extension

MIT in the repo -> https://github.com/banditoth/maui-archiver-vscode/blob/main/LICENSE
GPLv3 in the package.json -> https://github.com/banditoth/maui-archiver-vscode/blob/main/banditoth-VSCode-MAUI-Archive/package.json#L22

Hey @spouliot . Thanks for noticing it. I will fix that soon!

Fixed in https://github.com/banditoth/maui-archiver-vscode/pull/8/commits/c577072cc5da57c3a98a390883dc646a15dcb8d8
Available in version 1.0.0


JSON: use enums instead of symbols

This changes JSON::Lexer and JSON::PullParser to expose enums instead of symbols for token kinds and pull parser state kinds. Symbols work but they are not type-safe. Plus enums gives enumerate (duh) all possible states.
The PullParser has already proven to be very useful but moving forward I wouldn't like to keep the Symbols interface so it's better now or never.
This is a breaking change:

JSON::Lexer::Token#type : Symbol is replaced by JSON::Lexer::Token#kind : JSON::Lexer::Token::Kind
JSON::PullParser#kind : Symbol is replaced by JSON::PullParser#kind : JSON::PullParser::Kind

To make it easy to upgrade I kept JSON::Lexer::Token#type : Symbol as deprecated and also made JSON::PullParser::Kind be comparable to symbols, with a deprecation notice. That way we don't actually break anything but if you run the compiler with --warnings=all then you can fix things at your time.
Once merged, in a subsequent PR I'll try to document all of these types, including the ones in the YAML module.
I also added JSON::Builder#next_is_object_key? because I think it's useful and I at least needed it for optimizing one thing in https://github.com/Blacksmoke16/oq (though I didn't send a PR there yet).

Even the Token class could be avoided, see https://github.com/j8r/con/blob/master/src/lexer.cr .
I was planning to do it, but never get enough time to.

I'm not so sure about the symbol compatibility using ==, it seems very limited in the code which it will not cause a breaking change in. But I might be wrong.

You mean it might cause a breaking change after all?

Maybe? The only way to tell would be to find a corpus of projects which use these classes

Even if it's not completely backwards compatibility I'd move forward with this. Upgrading it should be relatively straight forward.


Allow uploading profile photo

A lot of CFPs (OpenCFP for example) asks for a profile photo when submitting talks.
It would be nice to be able to grab it from Symposium instead of Twitter or LinkedIn or whatever when submitting to a conference, so that everything you need for a submission is all in one place.

Agreed! This is captured in an earlier issue but we can just close the earlier one (will try to find it later to close)

Duplicate was #2. Second issue ever, probably time we get around to it. :) Closing #2 because there's more explanation/context in this one.


Squashed commit

This branch was misnamed. It is really assignment 6.2 (Quickstart). I have hopefully successfully squashed the commits that deleted the Overview topic I started, and two mystery files that got created in the api folder. I modified to-do-db-source.json for my Quickstart, but could not see how to revert it. Crossing my fingers that I am at least getting my Quickstart in here.
Deleted Extra files (api/-H and api/-d)
Don't know how these got here
Assignment6.2-WUF
Quickstart
Delete overview_WUF.md

Updated PR to sort out the commit list and rebase the branch so that the new commits from this change come after the current main branch. Squashed new commits to single commit for this PR.


feat: fedimint-dummy-tests

This PR also adds basic CI (copied from fedimint and updates flake.lock.

No checks are required yet but they do run so we'll merge and fix the checks in future PRs


check if context has a deadline

When compiling with specifying a timeout, the displayed timeout is a very large negative duration. Fix the display by checking whether there is a deadline.

Thanks! Yeah it did look ugly.


Entities remain unknown after Frigate setup

Version of the custom_component
Frigate: 0.12.1
Frigate Integration: 4.0.0
Configuration
mqtt:
  host: 192.x.x.2
  topic_prefix: frigate
  user: mqttuser
  port: 1883
  password: password

detectors:
  cpu1:
    type: cpu
  cpu2:
    type: cpu

cameras:
  driveway_cam:
    ffmpeg:
      inputs:
        - path: rtsp://admin:XXXXX@192.x.x.253:554/h264_stream
          roles:
            - detect

    detect:
      enabled: True
      width: 1280
      height: 720
      fps: 5

    snapshots:
      enabled: true
      timestamp: false
      bounding_box: true
      retain:
        default: 3

    objects:
      track:
        - person
        - car
      filters:
        car:
          threshold: 0.6

    motion:
      mask:
        - 371,720,367,664,47,667,51,720
        - 417,45,420,167,993,364,1063,147,883,0,421,0
    zones:
      driveway_gate:
        coordinates: 333,177,415,167,415,74,33,100,42,189,44,247
      driveway_near:
        coordinates: 89,545,139,720,438,720,1185,720,1280,720,1280,308,1107,0,794,285

Describe the bug
Setup frigate in Home Assistant and successfully detects cars and persons. When trying to setup the integration all goes well but all the entities remain unavailable. I suspect it might be a MQTT issue but I'm not sure.

Debug log

MQTT LOGS:
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/mosquitto.sh
[14:38:24] INFO: SSL is not enabled
cont-init: info: /etc/cont-init.d/mosquitto.sh exited 0
cont-init: info: running /etc/cont-init.d/nginx.sh
cont-init: info: /etc/cont-init.d/nginx.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun mosquitto (no readiness notification)
services-up: info: copying legacy longrun nginx (no readiness notification)
[14:38:24] INFO: Starting NGINX for authentication handling...
s6-rc: info: service legacy-services successfully started
[14:38:24] INFO: Starting mosquitto MQTT broker...
1689683904: Loading config file /share/mosquitto/solar_assistant.conf
2023-07-18 14:38:24: Warning: Mosquitto should not be run as root/administrator.
[14:38:25] INFO: Successfully send discovery information to Home Assistant.
[14:38:26] INFO: Successfully send service information to the Supervisor.
2023-07-18 14:38:24: mosquitto version 2.0.15 starting
2023-07-18 14:38:24: Config loaded from /etc/mosquitto/mosquitto.conf.
2023-07-18 14:38:24: Loading plugin: /usr/share/mosquitto/go-auth.so
2023-07-18 14:38:24:  ├── Username/password checking enabled.
2023-07-18 14:38:24:  ├── TLS-PSK checking enabled.
2023-07-18 14:38:24:  └── Extended authentication not enabled.
2023-07-18 14:38:24: Opening ipv4 listen socket on port 1883.
2023-07-18 14:38:24: Opening ipv6 listen socket on port 1883.
2023-07-18 14:38:24: Opening websockets listen socket on port 1884.
2023-07-18 14:38:24: Connecting bridge SolarAssistant (<IP_ADDRESS>:1883)
2023-07-18 14:38:24: mosquitto version 2.0.15 running
2023-07-18 14:38:25: Expiring client local.core-mosquitto.SolarAssistant due to timeout.
2023-07-18 14:38:25: New connection from <IP_ADDRESS>:39764 on port 1883.
2023-07-18 14:38:25: Client <unknown> closed its connection.
2023-07-18 14:38:26: New connection from <IP_ADDRESS>:56682 on port 1883.
2023-07-18 14:38:26: New client connected from <IP_ADDRESS>:56682 as frigate (p2, c1, k60, u'mqttuser').
2023-07-18 14:38:49: New connection from <IP_ADDRESS>:52780 on port 1883.
2023-07-18 14:38:49: Client <unknown> closed its connection.
2023-07-18 14:40:39: Client frigate disconnected.
2023-07-18 14:40:49: New connection from <IP_ADDRESS>:44298 on port 1883.
2023-07-18 14:40:49: Client <unknown> closed its connection.
2023-07-18 14:40:58: New connection from <IP_ADDRESS>:56570 on port 1883.
2023-07-18 14:40:58: New client connected from <IP_ADDRESS>:56570 as frigate (p2, c1, k60, u'mqttuser').
2023-07-18 14:42:49: New connection from <IP_ADDRESS>:33402 on port 1883.
2023-07-18 14:42:49: Client <unknown> closed its connection.
2023-07-18 14:44:49: New connection from <IP_ADDRESS>:50164 on port 1883.
2023-07-18 14:44:49: Client <unknown> closed its connection.
2023-07-18 14:46:49: New connection from <IP_ADDRESS>:42596 on port 1883.
2023-07-18 14:46:49: Client <unknown> closed its connection.
2023-07-18 14:48:49: New connection from <IP_ADDRESS>:50786 on port 1883.
2023-07-18 14:48:49: Client <unknown> closed its connection.
2023-07-18 14:50:49: New connection from <IP_ADDRESS>:58120 on port 1883.
2023-07-18 14:50:49: Client <unknown> closed its connection.
2023-07-18 14:52:49: New connection from <IP_ADDRESS>:59394 on port 1883.
2023-07-18 14:52:50: Client <unknown> closed its connection.
2023-07-18 14:54:50: New connection from <IP_ADDRESS>:47772 on port 1883.
2023-07-18 14:54:50: Client <unknown> closed its connection.
2023-07-18 14:56:50: New connection from <IP_ADDRESS>:60620 on port 1883.
2023-07-18 14:56:50: Client <unknown> closed its connection.
2023-07-18 14:58:50: New connection from <IP_ADDRESS>:42652 on port 1883.
2023-07-18 14:58:50: Client <unknown> closed its connection.
2023-07-18 15:00:41: Client frigate disconnected.
2023-07-18 15:00:50: New connection from <IP_ADDRESS>:42160 on port 1883.
2023-07-18 15:00:50: Client <unknown> closed its connection.
2023-07-18 15:00:56: New connection from <IP_ADDRESS>:54110 on port 1883.
2023-07-18 15:00:56: New client connected from <IP_ADDRESS>:54110 as frigate (p2, c1, k60, u'mqttuser').
2023-07-18 15:02:50: New connection from <IP_ADDRESS>:50452 on port 1883.
2023-07-18 15:02:50: Client <unknown> closed its connection.
2023-07-18 15:04:50: New connection from <IP_ADDRESS>:38268 on port 1883.
2023-07-18 15:04:50: Client <unknown> closed its connection.
2023-07-18 15:06:50: New connection from <IP_ADDRESS>:39902 on port 1883.
2023-07-18 15:06:50: Client <unknown> closed its connection.
2023-07-18 15:08:25: Saving in-memory database to /data//mosquitto.db.
2023-07-18 15:08:50: New connection from <IP_ADDRESS>:53086 on port 1883.
2023-07-18 15:08:50: Client <unknown> closed its connection.
2023-07-18 15:10:50: New connection from <IP_ADDRESS>:55864 on port 1883.
2023-07-18 15:10:50: Client <unknown> closed its connection.
2023-07-18 15:12:50: New connection from <IP_ADDRESS>:59222 on port 1883.
2023-07-18 15:12:50: Client <unknown> closed its connection.

This is usually due to running multiple instances of frigate without changing the client id https://docs.frigate.video/troubleshooting/faqs#on-connect-called

How would I know if I have more than one instance? I just followed the instructions on the site for installation on Home Assistant.

if for example the standard and full access addons were installed.

I only have the standard frigate addon installed at this point.

not sure then, something seems wrong with the mqtt broker

i have exactly the same issue. i got a bunch of errors in the frigate log like this:
2023-07-31 08:11:33.145281810  [2023-07-31 10:11:33] frigate.comms.mqtt             ERROR   : Unable to publish to Wohnzimmer/person: client is not connected
2023-07-31 08:11:33.145430660  [2023-07-31 10:11:33] frigate.comms.mqtt             ERROR   : Unable to publish to Wohnzimmer/all: client is not connected
2023-07-31 08:11:37.844315112  [2023-07-31 10:11:37] frigate.comms.mqtt             ERROR   : Unable to publish to Schafstall/all: client is not connected
2023-07-31 08:11:38.180726196  [2023-07-31 10:11:38] frigate.comms.mqtt             ERROR   : Unable to publish to Schafstall/motion: client is not connected
2023-07-31 08:11:38.468941388  [2023-07-31 10:11:38] frigate.comms.mqtt             ERROR   : Unable to publish to events: client is not connected
2023-07-31 08:11:43.419552661  [2023-07-31 10:11:43] frigate.comms.mqtt             ERROR   : Unable to publish to events: client is not connected
2023-07-31 08:11:45.368433546  [2023-07-31 10:11:45] frigate.comms.mqtt             ERROR   : Unable to publish to Stall/all: client is not
As @NeillHerbst i have followed the installation guide useing HassOs and Frigate add-on plus the frigate integration. In the freegate UI it works finde, i can toggle recording / dection and so on. But in the integration all enteties are not available.
The mqtt section of my frigate.yalm:
mqtt:
host: 192.xxx.xx.132
port: 1883
user: mqtt-user
password: my_password
stats_interval: 60
My mqtt server seems to be working, but i am not shure under with topic frigate is pulishing. But using the testpage in the mqtt integration works just fine.
Is their any solution? Getting the enteties work is for me a core feature.

@JensJackowski Frigate is not connected so check the beginning logs where frigate will say why it failed to connect. Also check the mqtt logs

the problem is solved, i had a blocked port 1883 in my firewall. Verry hard to find the problem, but it was defently not frigate fault. Now it is working correct.


Add the ability to copy the result to clipboard.

Makes it easier so that we don't actually "see" the result, but have it already copied to clipboard.
Can be optional argument.

Unsure about this one. There's a WIP library for clipboard usage, but obviously it's not stable. And it'd be wise to limit usage of third-party libraries.


Updated to 0.264.0

Hey @aviflombaum! Thanks for contributing! Did something went wrong? :(

Ya, it broke the build. I had run the command to update the icons to the latest version thinking it would just work but then got an error about passing too many arguments into lucide_icon. I didn't have time to take a look but didn't want broken code to get merged. I'll look today.

ahhh, I see! Let me know in case you need a helping hand! 🙌🏻

Hey - ya, just discovered that, missed this comment. I tried a bunch of things but the best I came up with is:
      @memory = data.split("\x00").each_with_object({}) do |element, result|
        key, value = element.match(/^([^,]*),(.*)$/).captures
        result[key] = value
      end

or
      @memory = data.split("\x00").each_with_object({}) do |element, result|
        key, *value_parts = element.split(",")
        value = value_parts.join(",")
        result[key] = value
      end

I can push whichever you think is more elegant but if you find an easier way, go for it, please.

@aviflombaum Fixed by https://github.com/heyvito/lucide-rails/commit/0b50525b722fbe72f2144ba68a20e149c0780875#diff-801eb78c3d10048c0033c094aebe7498b512135d55fa1015a7d1b40939405da8R30 ✨
Feel free to reopen this PR or create a new one! I'm also merging some dependabot PRs, so don't forget to update your fork! 🙌🏻

Just finished merging security updates! I'll make sure to merge this one before next ones!

Sorry, was trying to figure out if I needed to push the updates from upstream to this PR but I don't.

I think GitHub now has a "sync" button on your fork page that allows changes to be fetched automagically... I'm not sure whether it would work due to that conflict, tho.
If it is unable to correctly sync, you can amend eaeb0f9 and drop changes to that lock file, force-push, and then try the sync. Let me know in case you need help with that and I can provide specific steps 🙌🏻

Oh! Just forgot about the "Maintainers can edit this PR" feature as well! I can try to fix that conflict for you if you'd like! It's ezpz! :)
Let me know and I can try to give it a whirl.
(I apologise for the multiple messages!)

Superseded by #11


Starting assets

Find and add first temporary assets int the project. Basic stuff like wall, floor and a prisoner, maybe new player too.

Page with assets: https://limezu.itch.io/
Interesting set of assets: https://limezu.itch.io/moderninteriors (full package for $1.50)


Update README.md

To reflect how makefile works

Looks good follows how we used the makefile in class :)


Is json-smart a mandatory dependency?

Is json-path supposed to work without access to json-smart classes? For example, I may use Jackson as the json provider. Should it be possible to exclude the json-smart dependency in this case?
If yes, are you interested in pull requests that fix code that prevents this use case?
My use case is: I develop a framework and want to force as little a number of dependencies on the user as possible.

See #274

Okay, thanks.


6.1; Change Proposals

This is a high level ticket to track any major changes to the core code base which require a change proposal before commencing with work.
Any submitted proposal should fit the following criteria:

You are willing to suggest the change, as well as implement it.
A proposal should be raised via new github issue and explained in full what the suggested change is, and how it benefits the project.
Any docs reflecting a change or addition should be updated.
Unit test coverage should be to a high standard.

Fluent builder and move away from Singletons; https://github.com/DozerMapper/dozer/issues/375

Pipelines for Mapping Processor; https://github.com/DozerMapper/dozer/issues/377

Another suggestion - #400.

I would suggest #94


Updated the rake gem to 10.3.2

rake has been successfully updated from version 0.9.2 to version 10.3.2.

Hi bsbodden,
You have already activated rake 0.9.6, but your Gemfile requires rake 10.4.2.
So i tried to uninstall 0.9.6 with from command line using gem uninstall rake -v 0.9.6, faced an ERROR: gen "rake" cannot be uninstalled because it is a default gem.
I was trying to install code review plugin 0.7.2 in windows 7 PC (CLIENT) for SVN repository (SERVER)which is running in Windows.
Thanks in advance,


Fix !search and Improve feature

Doesn't appear to correctly pull data anymore.
While fixing we should probably use embeds so we can directly link to the page.
Limit description length to reduce spam potential, mayybe reduce max results from 5 to 3.
Alternatively we could try DM the user the results, or only return 1 result to the channel?

Fixed command, and uses embeds now #20 . Could use more improvement. Maybe send DM if user is on mobile?

Closed as #20 which fix this has been merged


[CLOSED] Upgrade Bootstrap to 3.3

 Issue by fofr
Tuesday 02 December 2014 at 09:38 GMT
Originally opened as https://github.com/alphagov/specialist-publisher/pull/338

Bump admin gem to pick up Bootstrap 3.3 (see https://github.com/alphagov/govuk_admin_template/pull/53)
For testing, everything on this branch should look and behave as it did before.
Also:

Add missing app_title variable to layout

fofr included the following code: https://github.com/alphagov/specialist-publisher/pull/338/commits

 Comment by fofr
Thursday 04 December 2014 at 16:25 GMT

@tommyp I haven't come across any visible changes in any of the apps with the exception of a slightly lighter grey for navbar text (which improves the contrast). It's a bugfix release.

 Comment by tommyp
Thursday 04 December 2014 at 16:22 GMT

Any big frontend changes in the Bootstrap diff we should be aware of?

 Comment by tommyp
Thursday 04 December 2014 at 16:26 GMT

Happy to merge this then :+1:


Explicitly select the features that will be supported (initially)

Routes as data
Route compilation (conflict errors)
Support multiple route data structures (see https://cljdoc.org/d/metosin/reitit/0.7.0-alpha7/doc/advanced/different-routers)
Define a small set of map keys and associated values (or types of values, e.g., 'handler key should have a value that is a function)
Support basic type validation of defined map keys' values
Support arbitrary map keys as options in routes
Web server specific adaptors (route data -> function dispatch)

All of these are defined here:

https://cljdoc.org/d/metosin/reitit/0.7.0-alpha7/doc/basics


Flow: Cannot call compose because a callable signature is missing

recompose version 0.30.0
flow version 0.89.0
I'm not sure what this is a result of but I only get it with react-redux's connect() as an argument of compose()
Flow: Cannot call composebecause a callable signature is missing in statics ofStoreSetup[1] but exists inStatelessComponent [2]

There are new HOC type definitions after upgrade to flow 0.89.0.


fix: sitemap entries

Consider the following vuepress page with the default locale en located at / and a second locale de located at /de/:
index.md
/de/index.md

Currently, vuepress-plugin-sitemap will generate the following sitemap entry:
  <url>
    <loc>https://example.com/index.html</loc>
    <changefreq>monthly</changefreq>
    <xhtml:link rel="alternate" hreflang="en" href="https://example.com/index.html"/>
    <xhtml:link rel="alternate" hreflang="de" href="https://example.com/de/index.html"/>
  </url>

However, Google is unhappy with this, because the hreflang links reference pages that have no back reference in the sitemap. Google notifies webmasters about a problem in their sitemap. Please refer to the corresponding Google support page  on this topic.
This PR ensures that each hreflang references an existing location in sitemap. For our example page, the sitemap will look like this:
  <url>
    <loc>https://example.com/index.html</loc>
    <changefreq>monthly</changefreq>
    <xhtml:link rel="alternate" hreflang="en" href="https://example.com/index.html"/>
    <xhtml:link rel="alternate" hreflang="de" href="https://example.com/de/index.html"/>
  </url>
  <url>
    <loc>https://example.com/de/index.html</loc>
    <changefreq>monthly</changefreq>
    <xhtml:link rel="alternate" hreflang="en" href="https://example.com/index.html"/>
    <xhtml:link rel="alternate" hreflang="de" href="https://example.com/de/index.html"/>
  </url>

The new code iterates over all pages and normalizes their URL by stripping the locale's prefix from the URL. The loop builds a map with the normalized URL as a key and a list of locale prefixes as value.
When sitemap data is assembled in pageMap, the mapping used to determine the hreflang links for the current page.

Thanks!

Thank you for taking care of this so quickly! Looking forward to the next release :)
I'd also be willing to provide test cases for this PR, if you intend to add automated tests at some point. Just ping me.

That's great!

Eh, I invited you as collaborator as I am busy this month.


Unable to connect to registration server, please try again later

The following happened by trying to login as<EMAIL_ADDRESS>and using the corresponding password. The wallet is newly installed.

Wrong repo


UPDATED: fastlane - secrets iAPS:

changed env variables to allow different secrets per repo for loop apps

:+1:


Add Dark Mode Javascript Toggle

We need a dark mode javascript switch for those who don't have a system wide switch. We also need to save this preference (cookies?).

#13


add LICENCE.txt from the main codebase

Fix missing LICENCE
Installation sequence for tool-installers

[ ] Test using @galaxybot test this
[ ] Inspect CI output for expected changes
[ ] Deploy using @galaxybot deploy this if test install was successful
[ ] Merge this PR

These are just config files. If you insist on a license it would be the MIT license that applies to the scripts, though I doubt they'd be useful for anyone but us.

@mvdbeek https://github.com/galaxyproject/usegalaxy-tools/pull/891 is an alternative with MIT only license.

Thanks, I merged that one.


JWS has no anti-replay nonce

Hi,
I use Dehydrated to deploy certificates in a private environment (local Boulder install).
I have no problem except today on a server which was already configured with 1 domain in domains.txt, I added a second one.
And Dehydrated throws me that error for this second domain :

INFO: Using main config file /etc/dehydrated/config
Processing git2.priv.company.net

Checking domain name(s) of existing cert... unchanged.
Checking expire date of existing cert...
Valid till Jun 30 23:41:35 2018 GMT Certificate will not expire
(Longer than 30 days). Skipping renew!
Processing docker.priv.company.net
Signing domains...
Generating private key...
Generating signing request...
Requesting authorization for docker.priv.company.net...
ERROR: An error occurred while sending post-request to https://acme-v01.api.priv.company.net/acme/new-authz (Status 400)

Details:
HTTP/2 400
boulder-requester: 1005
cache-control: public, max-age=0, no-cache
content-type: application/problem+json
replay-nonce: Sl0aksakzPWJZN2Xtocr6o5Ybh6UIz1cF1vN5KyR9F8
content-length: 100
date: Wed, 09 May 2018 15:13:53 GMT
{
"type": "urn:acme:error:badNonce",
"detail": "JWS has no anti-replay nonce",
"status": 400
}

Do I hit a "bug" when first domain does not need renew and second one is new ?
Tell me which information do you need to debug this.
Boulder is up-to-date, and functional (signed certificates this morning) and I just upgraded dehydrated to 0.6.2 with same error.
Thank you.

The only thing that changed on that server is Debian upgrade few days ago, from Jessie to Stretch. To you think that could be the problem ?


Fluid added mass

🎉 New feature

Part of https://github.com/gazebosim/gz-sim/issues/1462
Requires

https://github.com/gazebosim/gz-math/pull/459
https://github.com/gazebosim/sdformat/pull/1077
https://github.com/gazebosim/gz-physics/pull/384
https://github.com/gazebosim/gz-msgs/pull/271

Summary

Uses the APIs added as part of the Fluid Added Mass Proposal.
TODO

[ ] Check that added mass is correctly passed to physics engine
[ ] Create example world that demonstrates the added mass effect
[x] Display added mass on component inspector
[ ] Add tests

Test it

Check out the example world once the PR is ready.
Checklist

[x] Signed all commits for DCO
[ ] Added tests
[ ] Added example and/or tutorial
[ ] Updated documentation (as needed)
[ ] Updated migration guide (as needed)
[ ] Consider updating Python bindings (if the library has them)
[ ] codecheck passed (See contributing)
[ ] All tests passed (See test coverage)
[x] While waiting for a review on your PR, please help review another open pull request to support the maintainers

Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining Signed-off-by messages.
🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸

@osrf-jenkins retest this please


Review register to waitlist

On project detail pages you must be able to register your evm address for the upcoming auction

duplicate of #71


Support for webpack resolution

As request in #23, a new issue tracking support for webpack.
Use stats? Or just consume the config from webpack?

Does webpack have an api that lets you give it a module path and a webpack config and it'll tell you the absolute path of that module/file?

As far as I know there isn't. I think you have to print out the build information afterwards. But @sokra probably knows. Or you can ask on Gitter? https://gitter.im/webpack/webpack

webpack's resolve is powered by https://github.com/webpack/enhanced-resolve

Thanks Tobias! Appreciate the help.
On Wed, Oct 28, 2015 at 2:21 PM, Tobias Koppers<EMAIL_ADDRESS>wrote:

webpack's resolve is powered by
https://github.com/webpack/enhanced-resolve
—
Reply to this email directly or view it on GitHub
https://github.com/mrjoelkemp/node-dependency-tree/issues/27#issuecomment-151940925
.

@SimenB Webpack support has landed! I used the awesome enhanced-resolve module that Sokra linked to.
I just cut a minor release. Please let me know if you have any issues.


Add Timeout::unregister

This is useful if you are keeping a persistent Timeout object which
may or may not be active at any time.
Closes #280
r? @alexcrichton

Thanks! So reading over the docs/implementation here the purpose is to basically avoid a task notification, right? Out of curiosity, does that bring perf improvements locally? Or is this done mostly out of "seems like the right thing to do"?

We avoid the task notification already by using reset - that's important since an extra notification will cause a new timeout to start up without a read/write call actually being made.
I kind of doubt that there'd be a huge performance difference, especially in a traditional IO bound workflow. This is mostly just a "right thing to do" kind of PR - I don't want to reschedule the timeout, but just deregister the task from it.

Given that the timer in tokio-core is deprecated as it is being moved out of the crate, should we hold off this PR?

Sure - is the new implementation in a place that I should start poking at/using or is that a tokio 2.0 thing?

The impl was extracted to: http://github.com/alexcrichton/futures-timer

Cool, I'll close this and poke at futures-timer.


[CI] Disable SimVerb test for 14 days

Description
Disable SimVerb test for 14 days. people.ds.cam.ac.uk/dsg40/paper/simverb/simverb-3500-data.zip is currently offline.
cc @dmlc/gluon-nlp-team

Job PR-953/1 is complete.
Docs are uploaded to http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR-953/1/index.html

@eric-haibin-lin added a commit to disable the horovod tests for 1 week. Hopefully can be fixed https://github.com/apache/incubator-mxnet/issues/16193 by then

Job PR-953/2 is complete.
Docs are uploaded to http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR-953/2/index.html


messages.android.com

Anyone know of a similar project reverse engineering the messages.android.com API?

Not releven to the API!


Fix docstrings for streamlit and recommender files

Pull Request
Title
Add module docstrings for streamlit files, recommenders and simulator
Description
Fix docstring for streamlit files, recommenders and simulator
https://github.com/microsoft/vasim/issues/96
Type of Change

📝 Documentation update

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

Project coverage is 77.65%. Comparing base (e3d456a) to head (3f0a5c9).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #118   +/-   ##
=======================================
  Coverage   77.65%   77.65%
=======================================
  Files          24       24
  Lines        1083     1083
  Branches      137      137
=======================================
  Hits          841      841
  Misses        190      190
  Partials       52       52

Flag
Coverage Δ

unittests
77.65% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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


Raise "MissingWhenCase" while all cases all applied

Expected Behavior
No error should be raised
Observed Behavior
with Jenkins build it report next error
 When expression is missing cases: CANCELLED, COMPLETED. Either add missing cases or a default `else` case. [MissingWhenCase]`

these  CANCELLED, COMPLETED not cases from our enum.
Your Environment
detekt_plugin_version = '1.19.0'

Could you provide a way to reproduce it?

what is strange is detekt locally not raise this error, but with Jenkins it does.
is sharing enum, would help to get the cause?

🤔 that's strange for sure... do you use the same version of detekt in both cases? JVM version?

they are the same, I will try to reproduce it as it blocks CI/CD.

A reproducer would be great! I'm afraid that without a reproducer we will not be able to help you.
My 2 cents: It seems like some sort of problem in the classpath/gradle cache. Did your enum have the values CANCELLED and COMPLETED at any moment in the past? The only explanation I could think of is that detekt is getting the information from an outdated .class that, for some reason, gradle is not recompiling. You could try to check what happend if you execute detekt with the flag --rerun-tasks on your Jenkins.

@BraisGabin thanks for the notice, I will try and back to you when got any updates.

Thanks @BraisGabin issue solved.
We can close the issue now.


Remove Mono.Cecil dependency

This could make the compiler package lighter, and run faster. Related changes:

Move WIG into its own NuGet package, uses separate compiler tool and keeps Mono.Cecil
For F# use FCS emit to include WS resources, for C# the analyzer could create the resource files which csc.exe embeds.
Add MSBuild property WebSharperUseLocalMacros (and related console tool flag) to specify when compilation needs current assembly loaded for activating macro instances or reflection. Default should be off.

for C# the analyzer could create the resource files which csc.exe embeds.

Not sure that's a good idea, this is basically forcing people to use VS. The analyzer should be optional.

@Tarmil Roslyn analyzers are special project references and they are called by csc.exe too


Regsitering Audit annotations

adding annotation:

apiserver.latency.k8s.io/etcd,

apiserver.latency.k8s.io/decode-response-object,

apiserver.latency.k8s.io/apf-queue-wait

Also corrected the description of annotation : k8s.io/removed-release
In the page Audit Annotations

Partially fixes: https://github.com/kubernetes/website/issues/29479

/kind feature
/sig auth
/sig docs

JFYI : annotation apiserver.latency.k8s.io/apf-queue-wait
was added in k/k repository in this release cycle only. If not required right now , i can remove it.
Ref: https://github.com/kubernetes/kubernetes/pull/123919/

/sig api-machinery
/remove-sig auth

@sftim @katcosgrove PTAL

/retitle Register some audit annotations

Thanks. I have some comments and suggestions.
Sorry it took a while; we're short on reviewers.

No worries, I understand.


Custom taglist validation error only shows up when you focus out

Reproduction
Repro
Describe the bug
If I use a taglist field, with allowNewValues, and custom validation, the validation errors don't show up as I add a new tag. The errors only show up when I focus out of the field. This is kinda inconvenient for our users, since they will never know that a problematic tag was added until they click away from the field itself.
I debugged it and the validation does happen with every tag added, but it's just the error label that doesn't render.
Environment
• OS: Ubuntu
• Browser: Firefox, Chrome
• Version: 1.6.0, 1.5.9

You can set validation-visibility="live".
Here's the updated playground: https://formkit.link/55bcf4e3721115242eddde4709dee50a
Here's the docs: https://formkit.com/essentials/validation#showing-errors.


Prune unused deps and run cargo-machete in ci

Sync. Thank you dear sir.

Where was it synced? I'm not seeing cargo machete here:

https://github.com/cloudflare/pingora/blob/main/.github/workflows/build.yml


countUp on orientation change

hi thank before to awesome libraries
i want to make app to count down but i will to count up when phone orientation change .
like hourglass timed. can i do it with countdownVIew ? i not find that in documentation
thanks for help

i mean how to do if i want to count Up


QScript fails to merge through a mapped sort

The QScript for the query select distinct city from zips where pop <= 10 order by pop contains an unnecessary ThetaJoin. (It should contain no ThetaJoins at all.)
The cause of the problem is clear if we look at a subset of the LogicalPlan.
      ╰─ Let('__tmp5)
         ├─ Sort
         │  ├─ Free('__tmp4)
         │  ├─ ObjectProject('__tmp4{"__sd__0"})
         │  ╰─ LogicalPlan(Ascending)
         ╰─ Invoke(Take)
            ├─ Invoke(DeleteField)
            │  ├─ Invoke(DistinctBy)
            │  │  ├─ Free('__tmp5)
            │  │  ╰─ Invoke(DeleteField)
            │  │     ├─ Free('__tmp5)
            │  │     ╰─ Str("__sd__0")
            │  ╰─ Str("__sd__0")
            ╰─ Constant(Int(11))

We attempt to merge the QScript forms of __tmp5 and DeleteField(__tmp5, "__sd__0"). In QScript this is merging a Sort(Map(Hole, _), _, _) and a Map(Sort(Hole, _, _), _). This merge currently fails in QScript, returning a ThetaJoin.
One solution to this problem is to add an additional parameter to Sort (and Filter) which is a a MapFunc operation that we perform after the Sort (or Filter). This would allow us to fold a Map(Sort, _) into just a Sort node, thus allowing the sources in the example to cleanly merge. This partially addresses #1545 as well.
Another idea is to interleave identity Map nodes before performing source merging in QScript to allow cases like this to merge. I don't think we need to do this yet, and shouldn't without examples showing why we need it, but I just wanted to mention it.

Should also note that the query select distinct zips.pop from zips where pop <= 10 order by pop will also hit this bug until #1923 is fixed.

@sellout tested this query on the local mongoq branch, and it still hits the same bug even though we use GroupBy in place of Distinct/DistinctBy (which are deleted).


Update casper params

Pull Request Test Coverage Report for Build 12

0 of 0 (NaN%) changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 95.798%

Totals

Change from base Build 10:
0.0%

Covered Lines:
72

Relevant Lines:
75

💛  - Coveralls


Flow and index.js imports

This is not a bug but something I suggest including in the documentation for flow as I can see others running into a similar problem.
If you do not add // @flow to index.js files you have that are re-exporting your components, the type checking will not work on any imports from those index.js files.
Of course this makes perfect sense once I knew what the cause was. it was losing the types since it importing from a file that was not set up for flow (even though the source file was). It is very easy to forget those index.js files even exist though, and it caused some serious frustration and almost made me give up on flow before I found out what was happening.
I highly suggest mentioning this in the documentation to save others from that headache and wasted time.

I feel like this isn't a common enough issue to put in the FAQ - in general if you haven't enabled Flow in a file it isn't going to type-check, I don't think we need to have this additional specific example


Update commit_button documentation

When button was added to the array in Formtastic::Helpers::ButtonHelpers#commit_button_wrapper_html_css the documentation was never updated to reflect the changes. I changed the output html to include the new class.
Might I ask why button was added? We reuse a button class for all buttons, even those that are not in a form and we don't always wrap li's around it. I monkey patched it in the formtastic initializer, would this be the preferred method of overriding this behavior?

Hi, thanks for the doc change, will merge in. The button wrapper was added as a sibling to input. I think we have a general issue where the class names we provide may clash with other classes. error and hint are other great examples.
I'm reluctant to remove the button class (breaking backwards compatibility), but I'd like to revisit a lot of the class names in 3.0 (where I'm happier to break things a bit). In the meantime, monkey patching in the initialiser is the recommended approach, and any internal code refactorings that make this easier are welcome.
Thanks!

Thanks for the explanation and help!


When the process of run a pipeline finished, all the timers are set to 0

When the process of run a pipeline finished, all the timers are set to 0 and that is not correct:

All timers should display the time of the last run
The status of the general pipeline run should not go to Waiting

This is still not working:

General timer continues in 0 when the pipeline finished

There is mismatch between the timer in the pipeline and the timer in the Terminal dialog


Error: Generator at prisma-json-schema-generator could not start

Hi,
Was going to try your generator but faced this error:

Here is my schema.prisma:
// This is your Prisma schema file,
// learn more about it in the docs: https://pris.ly/d/prisma-schema

datasource db {
  provider          = "postgresql"
  url               = env("DATABASE_URL")
  // needed only when using heroku
  shadowDatabaseUrl = env("SHADOW_DATABASE_URL")
}

generator client {
  provider = "prisma-client-js"
}

generator jsonSchema {
  provider = "prisma-json-schema-generator"
}

model Car {
  id           Int    @id @default(autoincrement())
  manufacturer String
  model        String
  bodyType     String
  engineType   String
  transmission String
  year         Int
  generation   String
  vin          String
  odometer     Json
}

Versions I'm using:
"prisma": "2.17.0",
"prisma-json-schema-generator": "1.2.1"
Any ideas why this is happening?
Thanks in advance for any tips 👍🏻

@MikeYermolayev I will take a look! :)

@MikeYermolayev The issue is connected with the way you are calling prisma.
Currently, you call prisma directly like this:
$ ./node_modules/.bin/prisma generate

Instead, if you are using yarn, just call prisma like this:
$ yarn prisma generate

This will call prisma the node way, which will also respect the bin folder within the node_modules. Actually, this is very important:
"Within the bin folder, the binaries (executables) from your node modules are located. Executables are linked into {prefix}/bin on Unix, or directly into {prefix} on Windows. When in local mode, executables are linked into ./node_modules/.bin so that they can be made available to scripts run through npm. (For example, so that a test runner will be in the path when you run npm test.)"
When you directly try to run prisma without yarn or npm, the bin folder is not made available to prisma. Therefore prisma-json-schema-generator also cannot be found.
If you don't use yarn, but npm, just place a generate command in the scripts section of your package json and run npm run generate:
...
scripts: {
  ...
 generate: "prisma generate"
  ...
}
...

Hopefully, I could help you! :)

Thanks, makes sense👍🏻
Will try the provided advices and reopen if they won't help


CURL it's ok but not working on code

I print my curl request through debugPrintln and it's working (with a 200 status code) when I'm try it in my Terminal :
curl -i \
	-u YOUR_TOKEN:api_token \
	-H "Accept-Language: en;q=1.0" \
	-H "Accept-Encoding: gzip;q=1.0,compress;q=0.5" \
	-H "User-Agent: TogglGoogleCalendar/com.cappie.TogglGoogleCalendar (1; OS Version 10.10.2 (Build 14C109))" \
	"https://www.toggl.com/api/v8/me"

But it's not working in my code (status code 403). Here's my (really) simple code :
let request = Alamofire
            .request(.GET, "https://www.toggl.com/api/v8/me", parameters: nil, encoding: ParameterEncoding.JSON)
            .authenticate(user: "YOUR_TOKEN", password: "api_token")
            .responseJSON { (request, response, data, error) in
                println(" -- RESPONSE -- ")
                println(response)
            }

println("-----------------------")
debugPrintln(request)

Did you ever had an issue like this ?

For usage questions, please try Stack Overflow. If you believe that this is a bug, please open a new issue with an example project that reproduces the behavior in question.

Came here from google, cause I had a similar issue like @nicolas-besnard. So just for the record: don't use .authenticate(...) but add authorization header, as described here toggl_api_docs. For setting it, see https://github.com/Alamofire/Alamofire/issues/32


Define message for non-Error errors

Description

If a non-Error error is thrown from within a RPC handler, the message field would be undefined. This would result in the message field (which is expected to be present) be omitted, breaking the parsing step.
This PR addresses that by wrapping that in a nicer message. For example, if we do throw 123, the message becomes 'Non-error class Number was thrown'. If we do throw new ReadableStream(), then the message becomes 'Non-error class ReadableStream was thrown'. You get the idea.
Issues Fixed

Relates to PR https://github.com/MatrixAI/Polykey/pull/838

Tasks

[x] 1. If the message does not exist, substitute it with something else
[x] 2. Run tests to ensure this behaviour is consistent

Final checklist

[x] Domain specific tests
[x] Full tests
[x] Updated inline-comment documentation
[x] Lint fixed
[ ] Squash and rebased
[x] Sanity check the final build

I was able to make the message guessing function more complex, so now it should return something like this:
// For a number 123
> console.log(composeMessage(e));
Non-error literal 123 was thrown

// For regular messages
> console.log(composeMessage(e));
this was the error message

// For objects, like ReadableStream or Array
> console.log(composeMessage(e));
Non-error object ReadableStream was thrown

I'm not too happy about needing to make a separate function to handle this logic as it won't fit in one line, and is required to be repeated, so this can't be defined where needed. Rather, I had to define composeMessage inside the RPCServer.ts itself. I didn't export it, so it becomes like a private utility function.
Thoughts, @tegefaulkes?

All the tasks have been completed, and this PR has been approved. Merging.

Generally I prefer not to make application concerns a library functionality. The exact reporting of a message - specifically it's template or toString impl should be generic and allowed to be overridden by the downstream user. This is how you ensure reusable modules/libraries.

Should I make an issue to track this?

If you think about the levels of genericity:

js-errors is generic to any error usage
js-rpc is generic to any rpc usage - but now we know the error is specific to RPC
Polykey is generic to any Polykey usage - but now we know the error is specific to Polykey
... ladder of consumption


Depth Pipeline Collision [usb/ethernet]

Required Info

client
server

Camera Model
d435i
l515

Firmware Version
upadated
updated

Operating System & Version
Fedora32
Jetpack 4.4

Kernel Version (Linux Only)
5.8.16-200.fc32.x86_64
4.9.140-tegra

Platform
x86_64
arm64

SDK Version
2.39
2.39

Product
realsense-viewer
rs-server

Segment

Depth Frame pipeline collision
Running 435i locally and l515 remotely in realsense-viewer the depth frames collide
example
If you look in the sidebar, you'll notice it calls the lidar, stereo.
extra detail :  remote camera is networked through a usb connection

@3dsf
Interesting setup and configuration.
Are you still having issues or were you able to get past them?
*If we don’t hear from you in 7 days, this issue will be closed.

@RealSenseSupport
Honestly, I haven't played with them since.  I was just letting you know that you likely have a hastily copied class; that was the conclusion I came to back then.  I would've looked at fixing it, but my c isn't what it should be.
If I remember correctly, cuda processing is only implemented for display; are there plans for further implementations?
Also, I might recommend that you include a script in the library to produce automated output of specifications as seen in the main post comment.  I feel less inclined to make issue posts when I have to complete similar.   Yes, I understand that may be the point...

Thanks for the feedback.  We will keep this in mind for the future.

Thanks for the feedback.  We will keep this in mind for the future.


NPS office location feature flag

Added a feature flag for nps office location selection; this is defaulted to false.

It can be overridden by setting the value in helm_deploy.

The reason why that has been disabled is because there are some issues with delius returning conflicts when rescheduling appointments with different locations but with the same time.

Thanks. I created the following ticket: https://dsdmoj.atlassian.net/browse/IC-2164