Github API deprecation of access_token

I got an email from Github:

Hi @kolaente,
On February 15th, 2020 at 09:04 (UTC) your application (Kolaente's git-server) used an access token (with the User-Agent Go-http-client/1.1) as part of a query parameter to access an endpoint through the GitHub API:
https://api.github.com/user
Please use the Authorization HTTP header instead as using the access_token query parameter is deprecated.
Depending on your API usage, we'll be sending you this email reminder on a monthly basis.
Visit https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param for more information about suggested workarounds and removal dates.

I have set up my gitea instance so that people can use their github login to authenticate. If Github changes their api, this would need patching. Not sure though if it is only a third-party library we're using for this or if this is pure Gitea code.

Thanks for the report. We've been getting these emails too. Just waiting on https://github.com/markbates/goth/pull/314 to get merged.

closed with #10444


Merge Autohotspot setup into main install script

The feature to setup a hotspot automatically if no known network is available lives currently in a separate install script (https://github.com/MiczFlor/RPi-Jukebox-RFID/pull/967). This script is a duplication of the main install script and misses a few recent changes.
To lower the maintanence effort and make the feature generally available, i merged the changes regarding the autohotspot into the main install script.
Additionally i added a config step, so the user can choose if it shall be activated (defaults to NO). Also the default values for the hotspot can now be changed (non interactive mode is covered).
I would also remove this page https://github.com/MiczFlor/RPi-Jukebox-RFID/wiki/Access-Phoniebox-without-Router as it describes the manuell steps covered by this feature and is also outdated.
Some old sample files have been removed.

Cool!

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.09%) to 76.727%

Files with Coverage Reduction
New Missed Lines
%

GPIODevices/two_button_control.py
1
71.43%

Totals

Change from base Build<PHONE_NUMBER>:
-0.09%

Covered Lines:
633

Relevant Lines:
825

💛  - Coveralls

Good Idea 👍

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
633

Relevant Lines:
824

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
-0.03%

Covered Lines:
632

Relevant Lines:
823

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
633

Relevant Lines:
824

💛  - Coveralls

The main installation script currently doesn't perform a "deconfiguration" if run again and choose a different settings (eg. for Wifi or Service activation). So the autohotspot feature is aligned with that.
To support it anyway (and also the later activation) the needed setup is entirely moved into a separat script "scripts/helperscripts/setup_autohotspot.sh" and can be run manually by the user to "de-/configure"

@AlvinSchiller, ready to merge?

@AlvinSchiller, ready to merge?

Yep. Nothing more from my side.


'FastRCNNFocalLoss' object has no attribute 'box_reg_loss'

Error Message
/home/.../anaconda3/envs/detectron2/lib/python3.7/site-packages/torch/_tensor.py:575: UserWarning: floor_divide is deprecated, and will be removed in a future version of pytorch. It currently rounds toward 0 (like the 'trunc' function NOT 'floor'). This results in incorrect rounding for negative values.
To keep the current behavior, use torch.div(a, b, rounding_mode='trunc'), or for actual floor division, use torch.div(a, b, rounding_mode='floor'). (Triggered internally at  /opt/conda/conda-bld/pytorch_1631630742027/work/aten/src/ATen/native/BinaryOps.cpp:467.)
return torch.floor_divide(self, other)
Exception during training:
Traceback (most recent call last):
File "/home/.../task/ActiveTeacher/activeteacher/engine/trainer.py", line 167, in train_loop
self.run_step_full_semisup()
File "/home/.../task/ActiveTeacher/activeteacher/engine/trainer.py", line 266, in run_step_full_semisup
label_data_q, branch="supervised")
File "/home/.../anaconda3/envs/detectron2/lib/python3.7/site-packages/torch/nn/modules/module.py", line 1051, in _call_impl
return forward_call(*input, **kwargs)
File "/home/.../task/ActiveTeacher/activeteacher/modeling/meta_arch/rcnn.py", line 32, in forward
images, features, proposals_rpn, gt_instances, branch=branch
File "/home/.../anaconda3/envs/detectron2/lib/python3.7/site-packages/torch/nn/modules/module.py", line 1051, in _call_impl
return forward_call(*input, **kwargs)
File "/home/.../task/ActiveTeacher/activeteacher/modeling/roi_heads/roi_heads.py", line 96, in forward
features, proposals, compute_loss, compute_val_loss, branch
File "/home/.../task/ActiveTeacher/activeteacher/modeling/roi_heads/roi_heads.py", line 123, in _forward_box
losses = self.box_predictor.losses(predictions, proposals)
File "/home/.../task/ActiveTeacher/activeteacher/modeling/roi_heads/fast_rcnn.py", line 108, in losses
num_classes=self.num_classes,
File "/home/.../task/ActiveTeacher/activeteacher/modeling/roi_heads/fast_rcnn.py", line 143, in losses
"loss_box_reg": self.box_reg_loss(),
AttributeError: 'FastRCNNFocalLoss' object has no attribute 'box_reg_loss'
Environment

python=3.7
CUDA=10.2
PyTorch=1.9.1
torchvision=0.10.1
detectron2=0.6+cu102 (tried v0.5 but also failed)

Possible Problem
The FastRCNNOutputs class you refactored here has no box_reg_loss implementation.
Could you help with it? Many thanks!

I have fixed this file, thanks for the feedback.

It worked. Thanks for your quick reply.
Besides, could you provide config files for the VOC dataset to reproduce your results? Thanks in advance :)

Hi, we have released our VOC07+VOC12 configs. NOTICE THAT PLEASE!!! WE DID NOT FINE TUNE THIS.


Request for Training Code

Hi,
Thank you for your amazing work on SplatFlow. I noticed that the repository currently only contains the inference code. Could you please provide the training code or any guidance on how to train the model from scratch?
This would be very helpful for further research and applications.
Thanks in advance!

Thank you for noticing our work and for your suggestions!🥰
We are commencing the organization of the training code.
The release of the training code is scheduled for June. If circumstances allow, it may be released sooner. Stay tuned!

@Hanxingzhuang111
The training and testing code is released! I hope it can be helpful for your work. If you have any queries, please don't hesitate to contact me~

@Hanxingzhuang111
If there are no other questions, I will close this issue.
Best wishes to you.


updating chunkwm

Which is the best way to make sure that we are updated to the latest commits?
I am assuming rebuilding from source.

You can use the brew formula and install the HEAD version.
brew uninstall chunkwm
brew install --HEAD --with-ffm chunkwm

This builds and installs the latest commit.
To update and rebuild the head version after first install:
brew upgrade chunkwm

@crisidev thanks for the instructions.

I got this error after using brew upgrade chunkwm
The error is Error: crisidev/chunkwm/chunkwm HEAD-2424ef1 already installed

Mmmm maybe you cannot upgrade an HEAD formula. I think you need to uninstall and reinstall it every time. I honestly suggest you to use the stable release. I will keep it updated.

2424ef1 is the latest commit.

Mmmm maybe you cannot upgrade an HEAD formula.

That is indeed the case, but you can use brew reinstall chunkwm --HEAD --with-ffm if yiou want to have a single command.

Thanks everyone.. it is pretty sorted.


freebase: MqlreadCall.Do() is useless

dathead on 4 Mar 2013 at 8:50:
What steps will reproduce the problem?
1. call := client.Mqlread(query)
2. err := call.Do()
3. ... Where are the results?

What is the expected output? What do you see instead?
A return value containing the response bytes so that I can use encoding/json to
decode them would be nice.  Instead the result appears to be thrown away.

What version of the product are you using? On what operating system?
I am looking at the head revision (43ee29020514).

Please provide any additional information below.

Successfully auto-migrated from code.google.com:
https://code.google.com/p/google-api-go-client/issues/detail?id=24

The freebase:v1 API no longer has a Mqlread method.
It looks like they fixed their API.  Closing.


Potentialspawn Is Creating Hundreds of Mobs with no Cap

Someone else posted a similar topic regarding passive mobs, but I am unsure if the mob spawning rule is different, or if changes have been made since that issue.  When I add some mobs, like Blazes or Ghasts to spawn in the overworld, they spawn nonstop until hundreds of them are filling your screen.  See the attached screenshot.

It also completely ignores the other two mobs in the syntax... in my case it isn't spawning any Ender Dragon Zombies or Ghast mobs... just tons and tons of Blaze... despite the weight for both of these mobs being higher than Blaze.
This is my potentialspawn file:
[
{
"dimension": 0,
"mobs": [
{
"mob": "Blaze",
"weight": 5,
"groupcountmin": 1,
"groupcountmax": 2
},
{
"mob": "armorplus.ender_dragon_zombie",
"weight": 15,
"groupcountmin": 1,
"groupcountmax": 2
},
{
"mob": "Ghast",
"weight": 25,
"groupcountmin": 1,
"groupcountmax": 2
}
]
}
]

Well without additional restrictions in spawn.json there is nothing preventing the blazes from keeping spawning. So you will want to add some restrictions to that.
Also is "armorplus.ender_dragon_zombie" the right name? Shouldn't that be a : instead of a .?

Got it working, thanks!

How did you get this to work?  What are the restrictions that you added?


Is there a way to show row "detail-view" ?

I want to get the functionality of, when i click on a row, it should expand and display some detail information (detail view) just below that clicked row.
Is there a way to get that functionality?

That sounds like cool functionality and unfortunately, it's not built in to Griddle. In a future version it will be possible to override the table row (this is a bit different than the custom row component) to where this functionality could be added.
I'm closing this for now because it's something that is on the roadmap. Thanks!


support parsing datetime format for dmesg

Problem
Log file dmesg has unsupported datetime format parsing
[    0.000000] kernel: Linux version 5.15.0-48-generic (buildd@lcy02-amd64-080) (gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #54-Ubuntu SMP Fri Aug 26 13:26:29 UTC 2022 (Ubuntu 5.15.0-48.54-generic 5.15.53)
[    0.000000] kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=136735fa-5cc1-470f-9359-ee736e42f844 ro console=tty1 console=ttyS0 net.ifnames=0 biosdevname=0
[    0.000000] kernel: KERNEL supported cpus:
[    0.000000] kernel:   Intel GenuineIntel
[    0.000000] kernel:   AMD AuthenticAMD
[    0.000000] kernel:   Hygon HygonGenuine
[    0.000000] kernel:   Centaur CentaurHauls
[    0.000000] kernel:   zhaoxin   Shanghai

dmesg format is on most Linux platforms, including in X.Org.log, among other places.
Solution
Add support for the datetime format.  Add built-in tests to datetime.rs and comment which test cases are that format.
Support dmesg format is a big undertaking, as it requires correlating the first log line to a datetime, and then re-processing.  The implementation will need to follow a similar approach as processing syslog files without a year.

Relates to Issue #4

Closing this duplicate.


[Linear] Add comment to issue from anywhere

Extension
https://www.raycast.com/raycast/linear
Description
I'd like to be able to highlight text and trigger Raycast to add a comment to a Linear issue from anywhere.
So for example, if someone sends me a message in Slack or on Gmail about an open issue, I could just highlight it and do:
Raycast -> Linear: Add Comment To Issue -> (search for issue to add it to) -> (option to edit text, default highlighted text)
Who will benefit from this feature?
I think this would be powerful for any users of Linear that use the comments feature to post updates to Issues. In my company we use this feature frequently to post updates from emails, share relevant URLs, or important discussion points from Slack so that they can all be found in Linear.
Anything else?
An alternative would be a way to link a particular Gmail thread to a Linear issue such that every email in the thread comes as a new comment. That was my original thought, but I think it might be more difficult to do and in some ways less powerful.

That's actually a cool idea. It could use a dropdown to search the issues and put the highlighted text into a text area below.

@thomaslombart how do you feel about this? Any thoughts on how to best integrate it UX-wise?

@coffenbacher I wonder if a similar command would be handy to use the selected text as a description in an issue.

given you have to search for the issue, wouldn't it be enough to add an action to add a comment?
The flow would be:

open "Search Issues"
find your issue
press the keyboard shortcut to add a comment
A form gets pre-populated with the selected text

It does add a step from:

open "Add comment to issue"
A form gets pre-populated with the selected text
find your issue

but it feels a bit more "integrated" to me 🤔

@mathieudutour I actually didn't realize how powerful the Search Issues action is - it looks like I can already add a comment from there? That's cool! Definitely better than my current workflow.
The following might not be exact but is kind of how I am thinking about it now? This is a workflow I do all the time so saving even a single step feels really good. So just a highlight to pre-populate would be a great addition I think.
Without Raycast:

copy text
open Linear using Raycast
open Linear search
find your issue
press the keyboard shortcut to add a comment
paste text
edit

With Raycast - Search Issues (current)

copy text
open "Search Issues"
find your issue
press the keyboard shortcut to add a comment ( shift+option+command+n - this is a little gnarly but I guess I can get used to it 😅)
paste text
edit

With Raycast - Search issues (highlight text to prepopulate proposed improvement)

open "Search Issues"
find your issue
press the keyboard shortcut to add a comment
A form gets pre-populated with the selected text

With Raycast - Add Comment (dedicated flow proposed improvement)

open "Add Comment to issue"
A form gets pre-populated with the selected text
find your issue

For sure we could pre-populate the comment field yes, that sounds like a good improvement 👍

I agree with @mathieudutour, going through the search issues command seems like a better solution. Generally speaking, I think it's better to have actions on list items than the other way around (Search Issues > Action (comment, assign to, etc.) > Perform the action instead of Action > Search Issues > Perform the action).
That being said, this feature request sounds like a perfect use-case for a no-view command with command arguments such as Create Issue for Myself. The command would have two arguments: the issue key + the comment. That may be not the best UX since it's not possible to dynamically retrieve all the issues on command arguments but if you happen to know the issue key, it may be even quicker for your use case.

Otherwise, populating the selected text on the comment form may be a good idea as well. I'm just wondering if this wouldn't require setting a preference for that. Let's say I don't want the form to get populated when adding a new comment, then I'll have to remove the text from the text area which can be annoying.

Slick prototype! 😍 At first I was thinking that I'm unlikely to know the issue key off the top of my head, but then I realized that in most of the contexts I'd want to be quick adding a comment, there will be a link to the Linear issue or mention of the issue key. Usually it's from an email or Slack thread in my case. So that might actually be pretty viable / slick.
As for pre-populating the text, I agree that might be annoying if unwanted, I guess it depends on how often people do commands with text highlighted unintentionally? In my case (and I think most people's) it's essentially never, but there are surely some people that do.

The best would be to be able to have some sort of typeahead search on the issue key command argument but it's not possible at the moment and this sounds like a complex feature to implement (since command arguments are defined statically in package.json). (by the way, @thomaspaulmann, adding such a feature would be awesome. This would feel like quick links on steroids!)

I guess it depends on how often people do commands with text highlighted unintentionally?

I honestly have no idea about the data behind that. It sounds like a good improvement but at the same time, I could see it being annoying in certain use cases. That's the problem with these kinds of tools/extensions. They're so flexible that users have lots of workflows (with some strange edge cases sometimes), so we have sometimes to be careful not to break their ways of working 😄
What do you think of the quick-add solution? Should we implement it?

Typeahead version of your mockup would be the dream! Combined with selecting text to pre-populate the comment content, that would be about as slick as adding comments to an issue could possible be. And probably something that would be widely used I have to guess.
I would use the quick-add solution as it is, but I worry a little bit that it's narrowly fit to my particular use case and I don't want to waste your guys' time. Same with pre-populating Add Comment text on the Search Issues -> Add Comment flow - it would save me some time, but I'm not sure if it's compelling enough to spend your time on.

This use case could benefit others. Quick-adding a comment to a Linear issue from Raycast seems like a nice feature. As far as it looks, it's OK for me to build it. However, I'm on vacation right now, so I'll get back to that in two weeks 😊

Sweet! Thanks @thomaslombart , just tried it out, thanks!


Fixing the index page

Fix the index page,

Hey, I will try to fix the page. Please assign this issue to me :)

I ain't understanding what you want on the index.html page ?? Because I saw your repo, it already has sevenwonders.html file in which you tried to display seven wonders. Do I need to display 7 wonders' pictures on the index.html page ??

hey @sahilsingh7735 , please assign it to me.

heyy @sahilsingh7735  is the issue still open I would like to contribute?

if the issue is open i am trying to contribute in it


build: bump the version to 0.4.9

Changes since previous release:

coreos-postinst: add torcx-profile-populate logic

I pushed a corresponding signed tag for this: https://github.com/coreos/update_engine/releases/tag/v0.4.9


Validators

Drawing inspiration from experience + paddle's data provider, we can implement validation as a reusable map operation.

Pasting in my scratch example, here's a design that I kinda like.  It matches the callback interface i sketched out in #85:
class Validator(object):

    def __init__(self, **kwargs):
        self.fields = kwargs

    def __call__(self, streamer, strict=True):

        return Streamer(self.validate, self.fields, streamer, strict=strict)

    def validate(cls, fields, streamer, strict=True):

        for data in streamer:
            if data.keys() != fields.keys():
               raise ValidationError(...)
            for key in fields:
                # Check shape and dtype
                if strict:
                    raise ValidationError(...)
                else:
                    warn('Validation error...')
            yield data

v = Validator(x=((10,4), float), y=((10), int))

p = Streamer(my_streamer, filename)

for data in p:
    pass

for data in v(p):
    pass

for data in v(p, strict=False):
    pass

So Validator is an object that can construct streamers when applied to other streamers.

Circling back on this: I wonder if it would make more sense to use data classes here?  I'm thinking that if a dataclass is defined in advanced, and a streamer is supposed to generate data according to that format, then validation simplifies to a type-check on the iterate, and validate can just become a map:
def validate(stream, dc):
    for x in stream:
        if isinstance(x, dc):
            yield x
        else:
            raise ...

Where this could get a little interesting is in other stream filters (tuples, buffer_stream, etc).  Dataclasses can convert to tuples and dicts easily, but buffering would have to know the data class to construct a new DC from the iterates.
Overall, I think this might be a good direction to go in general, and we should encourage data classes over dicts for streamer outputs whenever possible.

yes, though DataClasses are >=3.7

yes, though DataClasses are >=3.7

Indeed.  the validate pattern above is really just a type-agnostic checker though, so it doesn't have to know what dc's are to work.  It could just as easily be validate(stream, np.ndarray) (though that's not so useful).  Maybe a more interesting validator pattern would be
def validate(stream, callable):
    for x in stream:
        if callable(x):
            yield x
        else:
            raise ...

data = validate(stream, lambda x: isinstance(x, my_favorite_type))

Then you could put any arbitrary checker logic into the callable without having to write the exception handling boilerplate.

Iterating on this one more time: I think this actually makes the most sense as a filter pattern with an optional raise flag.
def filter(stream, callable, error=True):
    for x in stream:
        if callable(x):
             yield x
        elif error:
             raise PescadorError(f'Failed check: {callable}({x})')

This way, you can either error out (default) when a check fails, or simply remove it from the stream.  Both are reasonable actions depending on circumstances, and this pattern makes it easy to do both.

Thinking more on this, do we actually want to implement anything here?
You should be able to get the same overall behavior as follows:
def cond(x):
    if not isinstance(x, MyType):
        raise TypeError
    return True

itertools.ifilter(cond, stream)  # Throw an exception when validation fails
itertools.ifilter(lambda x: isinstance(x, MyType), stream)  # Filter without throwing exceptions

I see no benefit to reimplementing itertools functionality here, as it will only be slower and more work to maintain.


Manual Deploy gets stuck in Build

We recently started working on Amplify. When we try to deploy front end using Zip(which is actually S3 content), is taking forever to deploy.

@prasaddattu478  Sorry that you are facing this issue, would you mind provide your appID and region? Don't put you accountID here.(console->App setting-> App ARN (arn:aws:amplify:${region}:${accountID}:apps/${appID})

HI Aws-Amplify/Amplify-Console/Joyce,
Here is the appID: apps/d3px7gwvqi6isz
On Mon, Feb 10, 2020 at 3:06 PM Joyce Hao<EMAIL_ADDRESS>wrote:

@prasaddattu478 https://github.com/prasaddattu478 Sorry that you are
facing this issue, would you mind provide your appID and region? Don't put
you accountID here.(console->App setting-> App ARN
(arn:aws:amplify:${region}:${accountID}:apps/${appID})
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/aws-amplify/amplify-console/issues/425?email_source=notifications&email_token=AGBTANGZ3BXSZFDY3C6RH7LRCG6XBA5CNFSM4KSU5HLKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELKIT5Y#issuecomment-584354295,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGBTANFVTAJRYOJVH3F3YSLRCG6XBANCNFSM4KSU5HLA
.

--
Regards,
Krishna Prasad,
+91<PHONE_NUMBER>

Can we deploy Sapper application(which is in S3) to Amplify?.

@prasaddattu478 We are investigating the manual deploy issue now. For Sapper application deployment, did you see any error message when you build it?

Hi Joyce,
I have not seen any error in the console or in the log.
On Mon, Feb 10, 2020 at 6:48 PM Joyce Hao<EMAIL_ADDRESS>wrote:

@prasaddattu478 https://github.com/prasaddattu478 We are investigating
the manual deploy issue now. For Sapper application deployment, did you see
any error message when you build it?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/aws-amplify/amplify-console/issues/425?email_source=notifications&email_token=AGBTANBDO7J5PHBUAHGX24TRCHYV3A5CNFSM4KSU5HLKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELK3DZA#issuecomment-584430052,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGBTANBH5PMSTKEADVO6IXLRCHYV3ANCNFSM4KSU5HLA
.

--
Regards,
Krishna Prasad,
+91<PHONE_NUMBER>

Hi Joyce,
I have just deployed a sample app to amplify to see how does it run. Deployment was successful but when I try to access domain I am getting error "Access Denied" from Cloudfront. you can refer below the issue about the error.
Good Part is that Deployment is successful for sample app with you getting stuck in the middle.
https://github.com/aws-amplify/amplify-console/issues/427

@prasaddattu478 Can you re-deploy your app? If you still face this issue, please let us know.

Hi, I am also experiencing this same issue. Tried to re-deploy as you mentioned and nothing. I am trying to deploy on Oregon dp7ullmksghe and d2mpy2rjd2n3ss. They are pretty much the same, just different attempts.

Hi Joyce,
I just did a deployment and it got stuck again.

Hi @prasaddattu478 , I think that is a bug on our console. We cut a ticket in our team backlog, will investigate a fix.
A temporal workaround for manual deployment: Are you interested in drag and drop? (https://aws.amazon.com/blogs/mobile/deploy-files-s3-dropbox-amplify-console/)
or you could deploy your app from git providers.

@prasaddattu478 What is the size of your zip file?

The ZIP file size is around 300MB. We tried deploying from S3, drag & drop method. Both ways of deployment got failed. For initial POC we try using the manual process from S3 or drag & drop the zip whichever works. We have a complete pipeline setup in our CICD process which generates a zip file in S3. From S3 we would like to deploy to Amplify.

@Joycehao19 - hey, we already have our infrastructure to build out the contents in place. Integrating via git connection to GitLab really does not make sense for us since we have an investment in EC2 and Faregate instances to handle our builds.
Additionally, we can not paralyze the builds within Amplify the way that we can externally. So for all purposes, we are just a flat-file site. The zip archive contains just HTML, CSS, JS, SVG Icons, and JSON files basically.
The maximum depth of the zip folder is 4 folders currently.
/foo/bar/baz/quz/index.html
The size of the zip file is less than 300MB. We expect this to grow a little as we finish building.
@prasaddattu478 is on my team. We are trying to figure this issue out. Our deploy deadline is the end of March, and we need a working POC before then, otherwise, we will have to go with a different service.
Is there anything we can do to help you test and determine the problem?
Thanks for the support @Joycehao19

@Joycehao19 - any update?

I was just about to open an issue. I'm having this issue too. 3 environments now ALL stuck.

Can someone investigate these apps?

d2gjth6penmdga
d23s8pc8j554l3
d1i11wkf7q4v95

Bump...

@Joycehao19 any update on this issue?.

same issue. d13ktqqgv1z4ps

Same issue. d13ktqqgv1z4ps

Same issue as well d1mdmm8asbc6gf

Same issue d1ajpgmfqkxwzo

I contacted AWS support and they've been very responsive. They're investigating this thread now.

If you paste your appId please also paste the region i.e. "us-east-1" for example this will help us look into the issue you're facing.

Here is the appID: apps/d3px7gwvqi6isz
Region: us-east-2
@Joycehao19, We have raised raised this issue two months back but we have not heard any thing from your team. Can you please let us know what is the status on it?.

Hi @grudra7714 , Did you build fail in Build#4?

@Joycehao19 Looks like its stuck in the deploy stage again like the other 3 builds and some before that

@grudra7714 Do you mean all 4 builds fail? Would you mind send the logs from your console?

Hi @prasaddattu478 , sorry for waiting. We are currently investigating the issue. I'll keep updating  the progress from our team.

@Joycehao19, do we have ETA on it?.

@prasaddattu478 @grudra7714 @connorford2 @khrome83 @bakersemail @foragerr we have root caused the issue and are working on a fix. Will update you when it is ready.

Heads up to everyone on this thread. AWS support reached out to me and acknowledged that this is indeed an issue on their end. I haven't tested it out yet, but this is the temporary fix I got from them:

It looks like there's a bug in our code when customers try to upload a zip in a nested folder within an s3 bucket. They have requested that you not upload their zip in a folder for now until this is resolved. i.e. the S3 url should look like s3://customer-bucket/build.zip (vs.what it looks like now which is s3://customer-bucket/nestedFolder/build.zip)

Thanks for the update @connorford2.
@Joycehao19, I have tried using S3 url as suggested using zip file at root still deployment got struck at line number 27373(may vary). Please take a look at it as soon as possible. Our dead lines are close by. Please provide a fix at the earliest.

@Joycehao19 - we still have not received any updates on this...

same issue for me +

any development about this issue?

Same issue here

As far as I can see that this issue has sth to do with folder structure. If the build artefacts are two storey or more deeper from amplify root. Amplify does not proceed as expected.

When you do the manual deploy and you zip the folder are you zipping the top level folder? Or are you navigating into the build folder output and selecting all the files and then zipping?
Ref: https://docs.aws.amazon.com/amplify/latest/userguide/manual-deploys.html - "When you create the zip folder, make sure you zip the contents of your build output and not the top level folder. For example, if your build output generates a folder named “build” or “public”, first navigate into that folder, select all of the contents, and zip it from there. If you do not do this, you will see an “Access Denied” error because the site's root directory will not be initialized properly."

We did the later, since the output is already built elsewhere.
On Aug 7, 2020, 11:08 AM -0500, ganipcanot<EMAIL_ADDRESS>wrote:

When you do the manual deploy and you zip the folder are you zipping the top level folder? Or are you navigating into the build folder output and selecting all the files and then zipping?
Ref: https://docs.aws.amazon.com/amplify/latest/userguide/manual-deploys.html - "When you create the zip folder, make sure you zip the contents of your build output and not the top level folder. For example, if your build output generates a folder named “build” or “public”, first navigate into that folder, select all of the contents, and zip it from there. If you do not do this, you will see an “Access Denied” error because the site's root directory will not be initialized properly."
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

Wait, are you serious you just closed a bug that you committed to fix, and then didn’t fix and didn’t give any updates on?

@khrome83 @gkdg my mistake on closing without a comment, so sorry! It was supposed to link to #115 which we're rolling out as a fix as we speak. Again, sorry for the confusion!

Thanks @litwicki for the info. Much appreciated.

I'm seeing a similar problem.
This screen shot is taken about 1 hour after starting the deployment. It usually takes less than a minute:

Somehow it's building and deploying simultaneously? On the build tab, it seems to have completed the build. It's not deploying.

A similar problem is occurring to me also

After letting it run all night, it finished the deployment, but is still stuck on "verify". Weird.

There was an unrelated AWS event yesterday in US-EAST-1 that was causing some issues. Please try a fresh build and let us know if you have any issues.

Yes, it was resolved now :-)

Mine is now stuck on the provision step. How long is that usually supposed to take? Using the default image.

@rudolfbyker if you have more than 5 concurrent builds going on in any one account any additional will get stuck in the provisioning step. This is a bug we are working on prioritizing as soon as we can.

Closing this ticket for now - if anyone is still having issues please re-open the ticket!

Closing this ticket for now - if anyone is still having issues please re-open the ticket!

same, the build never ends

tried amplify version 7.4.4 , 7.4.2  also get stuck

Still happening. Unacceptable for production builds.

experiencing this as well on backend


Fixed most of cargo audit issues.

Bumped crates versions, changed Rust edition to newest.
Still 3 issues exist:

time crate version - never directly used, chrono crate is using old version, nothing we can do with that.
owning_ref (libp2p dep) has unfixed problem - again, nothing we can do.
xcb crate version - also never directly used, clipboard crate is using old version, we'll update if new version will arise

Also - changed the code in few places to accommodate the new version of pickledb


where is api?

where is api?

Please use https://discourse.gohugo.io/ for questions/troubleshooting. Also see  Hugo Documentation.


Attribute order

Hey Wojtpl2,
your Project is really nice and useful, but what I need to do is to define the order of the Attributes in the XML. You wrote that the ExtendedXmlSerializer 1.4.0 support "XmlElement", so I try [XmlElement(Order = 1)], but it doesn't work for me.
Is there any other way to define the order of the Attributes?
Now the order of the Attributes is the order how the Properties are defined in the C# class.
Examples:
how it works now:
C# class
class Test{
string B {get; set;}
string A {get; set;}
}
XML Output:

What I would like to do:
C# class
class Test{
[XmlElement(Order = 2)]
string B {get; set;}
[XmlElement(Order = 1)]
string A {get; set;}
}
XML Output:

Thank you in advance for your answer!

Thank. Ok, I can support Order parameter too. I will add this function in version 1.4.1. I'll try make it today or tomorrow.

Thank you.
I forgot something to ask you. In my Case one Property is in the Base-class and the other Property is in the derived class.
Is this also possible?
Example what I would like to do:
class BaseTest{
[XmlElement(Order = 1)]
string B;
}
class Test : BaseTest{
[XmlElement(Order = 2)]
string A
}

I published version 1.4.1. This version support Order parameter.
You can set Order on property in Base Class and Sub class too. But in your example you don't need any attribute becouse new version of ExtendedXmlSerializer write first all property from base class then all property from sub class. If you want you can reverse order, like this:
class BaseTest{
[XmlElement(Order = 2)]
string B;
}
class Test : BaseTest{
[XmlElement(Order = 1)]
string A
}


fix local FAQ URL

Signed-off-by: Frédéric Harper<EMAIL_ADDRESS>

Won't need that as I'm merging the FAQ


[TypeScript] Added support for const enums

As described here:
https://www.typescriptlang.org/docs/handbook/enums.html#const-enums

I think const enums are not supported by babel/typescript-preset like namespaces :/
https://babeljs.io/docs/en/babel-plugin-transform-typescript


Polling interval difference per network

[X] I have looked through the existing issues

First, big thanks to @sverps and @blahkheart for #615! This responds to a comment from that as a new issue, instead of discussing further improvement on that closed PR.

When multiple networks configured, pollingInterval will for all networks be the one from the config (if anyone has an idea to keep polling interval to 4000 while on hardhat, while at the same time use a slower polling for other networks, let me know)

https://github.com/scaffold-eth/scaffold-eth-2/pull/615#issuecomment-1820639836 says this is OK as the config files can differ on dev machines, but we can do better and allow more similarity in dev/prod environments (which is good as a matter of practice).
It seems like the best way to do this would be to add an optional pollingInterval property to the chain configuration, perhaps even to the RPC endpoint configuration, and if the property isn't there, fall back to the default in the overall config file.  I would then set the default in the config file to a fairly high value and put a lower starting value in there for Hardhat specifically in its chain-specific configuration.

The main issue I came across was that the pollingInterval is a common config when creating the available app chains with wagmis configureChainsinwagmiConnectors`, so there doesn't seem to be a mechanism to pass different polling intervals based on chain there.
So unless there's a simple way to do it that I didn't find, I'm afraid a solution to provide this (by recreating the whole wagmi config on network switch and putting it in some global context or so) might get too complex considering the benefit it would bring.

Hey thanks @wbt for suggestion 🙌
Completely agree with Samuel, I think it would be great if its handled on the wagmi side rather than creating a workaround / patchy solution in SE-2
Btw, In Wagmi V2 I think they are planning to allow to configure pollingInterval on per chain basis: https://beta.wagmi.sh/react/api/createConfig#pollinginterval
Lets wait until main version of Wagmi V2, closing this for now thanks 🙌


Federation only partially working

We are on Office365 (small company - using the Business account).  Our colleagues are still on Skype for Business in a large company.  They are already Office365 and are moving (slowly) to Teams.
We setup federation - External access is enabled on our side. And it seems it is enabled on their side.  From our organization, we can chat with them.  And they can reply to those chat messages.  But if they attempt to initiate a chat with us, it never comes through.  They get a message about the user being unavailable or offline.  I have set External Access as on for anyone - I haven't set a specific permission for the partner organziation. From what I've read, that shouldn't matter.

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

ID: 59900927-5e5f-77a4-04be-e05a91330fca
Version Independent ID: 1e4d6b87-f57c-fa45-1630-3c32b821d93c
Content: Communicate with Teams users in another organization
Content Source: Teams/let-your-teams-users-communicate-with-other-people.md
Service: msteams
GitHub Login: @tonysmit
Microsoft Alias: tonysmit

I think the best way forward is if you can open a service ticket in your tenant so this can get resolved ASAP. Based on outcome let me know if it is something that can be called out in the docs.
Here is a quick video on opening a ticket: https://www.youtube.com/watch?v=puuOy0sEg1Y
If you don't mind please keep us posted here on the resolution and I really want to get this information you are discovering back into the docs.

FYI.  Heard back from the helpful support team on Office365.  This is a known issue between organizations already on Teams and those still in Skype for Business.
Quote from support desk:

As per consulting this is a known issue under the communication platform of Microsoft Teams and Skype for Business. Microsoft are encouraging as users will soon be forced to shift to the Teams services. as the Skype for Business will be decommissioned soon.
For your reference this would be a official road map of Microsoft to transition to Teams:
https://skypeandteams.blob.core.windows.net/artefacts/Skype for Business to Teams Capabilities Roadmap.pdf
Rest assured that the back end Engineers are working on this known issue but as of the moment there's no estimated time of completion. Sincerely I apologize for the inconvenience and thank you so much for your patience!


MQTT: Server not configured

I have this issue where no data is sent to MQTT:
My broker is well configured, as I use it for Zigbee2MQTT also.
Any extra config step needed?
2023-12-07 11:33:13 DEBUG    Starting new HTTP connection (1): <IP_ADDRESS>:80
2023-12-07 11:33:14 DEBUG    http://<IP_ADDRESS>:80 "GET /device/getParam?dev_id=1&dev_type=35&dev_code=3351&type=3&param_addr=5035&param_num=10&param_type=1&token=419e2a77-b8c0-458f-b3f5-8615fbdf0d27&lang=en_us&time123456=1701945193 HTTP/1.1" 200 149
2023-12-07 11:33:14 DEBUG    HTTP Status code 200
2023-12-07 11:33:14 DEBUG    Payload Status code 1
2023-12-07 11:33:14 DEBUG    Payload Dict: {'result_code': 1, 'result_msg': 'success', 'result_data': {'param_value': 'FF FF 00 55 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF '}}
2023-12-07 11:33:14 DEBUG    Data length: 20
2023-12-07 11:33:14 DEBUG    Changing transaction state from 'SENDING' to 'WAITING FOR REPLY'
2023-12-07 11:33:14 DEBUG    Modbus payload: ['00', '5b', '00', '00', '00', '17', '01', '03', '14', 'FF', 'FF', '00', '55', 'FF', 'FF', 'FF', 'FF', 'FF', 'FF', 'FF', 'FF', 'FF', 'FF', 'FF', 'FF', 'FF', 'FF', 'FF', 'FF']
2023-12-07 11:33:14 DEBUG    Requested Size: 8, Returned Size: 8
2023-12-07 11:33:14 DEBUG    Modbus payload: ['14', 'FF', 'FF', '00', '55', 'FF', 'FF', 'FF', 'FF', 'FF', 'FF', 'FF', 'FF', 'FF', 'FF', 'FF', 'FF', 'FF', 'FF', 'FF', 'FF']
2023-12-07 11:33:14 DEBUG    Requested Size: 21, Returned Size: 21
2023-12-07 11:33:14 DEBUG    Changing transaction state from 'WAITING FOR REPLY' to 'PROCESSING REPLY'
2023-12-07 11:33:14 DEBUG    RECV: 0x0 0x5b 0x0 0x0 0x0 0x17 0x1 0x3 0x14 0xff 0xff 0x0 0x55 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff
2023-12-07 11:33:14 DEBUG    Processing: 0x0 0x5b 0x0 0x0 0x0 0x17 0x1 0x3 0x14 0xff 0xff 0x0 0x55 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff
2023-12-07 11:33:14 DEBUG    Factory Response[ReadHoldingRegistersResponse: 3]
2023-12-07 11:33:14 DEBUG    Adding transaction 91
2023-12-07 11:33:14 DEBUG    Getting transaction 91
2023-12-07 11:33:14 DEBUG    Changing transaction state from 'PROCESSING REPLY' to 'TRANSACTION_COMPLETE'
2023-12-07 11:33:14 DEBUG    Using Inverter Time: 2023-12-7 11:33:12
2023-12-07 11:33:14 INFO     Inverter: Successfully scraped in 2.486299 secs
2023-12-07 11:33:14 WARNING  MQTT: Server Error; Server not configured
MQTT: Server Error; Server not configured

Hi, I'm having the same issue. Any update here ?

I am also having the same issue.
new install of the latest HA full OS, installed the MQTT from the addons, setup the MQTT integration, setup another addon that uses this setup (core-mosquitto) and it works fine, but this addon keeps throwing this error. When I look at the logs in MQTT it shows it is connecting, but it doesn’t seem to be working properly.
Any ideas?

Managed to get it working, but it doesn’t seem to do what i expected it to do. I expected it to discover the model of my inverter, but if you let it do this, it seems to not discover the model and throws this error. If you specify the model number exactly, it started fine and no errors about the MQTT server. It appears the model and subsequently the serial number must be discovered before it can publish to MQTT which causes this error.


How recognition.continuous really works?

I'm trying to understand the logic behind how the continuous feature of recognition really works behind the scenes. I have a kaldi decoder but I want to code the same logic of automatically recognizing words as soon as there's a pause from the user just like web speech API's continuous feature allows. How is this really working?
Does the recognizer start decoding after a few seconds and if so how many seconds? Or does its recorder have the ability to differentiate when it is getting some form of input and when it's not? If so, does it consider background noise to be user's silence and perform a decoding? There has to be a recorder and recognizer as two separate entities. If it's not, then how do they work as a single entity?

Hey @Varsha-Rao! Thank you for opening this issue. Have you looked at https://developer.mozilla.org/en-US/docs/Web/API/SpeechRecognition/continuous? Also, perhaps having a look at the specification could help shed some light? Another place to post this question might be StackOverflow.
Also, note that we are combining some of our repositories to enable us to triage pull requests and issues more effectively. Therefore, this specific repository will be merged into the more prominent dom-examples repository. Thank you.


Site Suggestion

Did some tweaking to my site
the page: https://wito.bar
the results: https://yellowlab.tools/result/gpz80veecm

Oh no, I pressed THE BUTTON!
Welcome to the 250kB Club! Your sub-page will be https://250kb.club/wito-bar !


Imagery offset database support

Instead of moving tiles, move all objects! Also, cache the data and update like once a day.


feat: add message delete and edit

Add an option to delete and edit user messages, small bug that messages don't update visually but have confirmed they update in the official client.

To update the messages in the TextView widget, the messages need to be redrawn to the widget.


Potential bugs/bad style in example for _getdiskfree

Hi, the example for _getdiskfree() bothered me in a couple of ways:
Use of non-literal format string in printf()
There are several places where the example calls printf() with a single argument.  For example, "printf(g_szBorder);" or "printf(szMsg);".  This is generally bad style, because the argument could contain a "%", which would then cause printf() to try to consume arguments which aren't there.
Technically, this should be safe for cases such as "printf(g_szBorder);" since the string literals are defined above and do not contain a "%".  Even though it's okay, it's a "code smell" for me personally, since the literal is located in a different place than the call to printf(), so it requires a little bit of effort to verify.
The most troubling case is "printf(szMsg);" since in that case the format string comes from FormatMessage().  I don't know how likely it is that FormatMessage() would return a string containing a "%" character, but I'm not aware of any guarantee that it won't happen.
Generally, I would recommend doing either:
printf("%s", str);

or
fputs(str, stdout);

in order to make it obvious that there won't be any misbehavior if str contains "%".
Removal of terminating NUL byte from result of FormatMessage()
In the error case, after calling FormatMessage(), the code does the following:
            szMsg[uLen+6] = '  ';
            szMsg[uLen+7] = '  ';
            szMsg[uLen+8] = '  ';

My understanding is that 6 and 7 are to remove the "\r\n" at the end of the string, and 8 is to remove the terminating NUL from the end of the string.
This will work just fine, as long as the length of the string returned by FormatMessage() plus 8 fits within the length of g_szLine[], because then the NUL byte at the end of g_szLine[] will terminate the string.
However, the call to FormatMessage() specifies a maximum length of 4100 characters:
            uLen = FormatMessage(FORMAT_MESSAGE_FROM_SYSTEM, NULL,
                            uErr, 0, szMsg+8, 4100, NULL);

Therefore, if the message is long, FormatMessage() could easily overwrite the NUL byte at the end of the version of g_szLine[] which has been copied into szMsg[].  If that happens, there does not appear to be any guarantee that a NUL byte will be reached before reaching the end of szMsg[] when printing the message.  (Since szMsg[] is uninitialized, beyond the first sizeof(g_szLine) bytes.)
A simple fix would be to add:
         memset(szMsg, 0, sizeof(szMsg));

before the existing
         memcpy(szMsg, g_szLine, sizeof(g_szLine));

although there would be other ways to fix it, as well.
Thanks!

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

ID: b3a07ec8-b631-20f0-c072-a03144c96487
Version Independent ID: a49a780a-cb33-4ddd-8a7a-52bfea658e60
Content: _getdiskfree
Content Source: docs/c-runtime-library/reference/getdiskfree.md
Product: visual-cpp
Technology: cpp-ucrt
GitHub Login: @TylerMSFT
Microsoft Alias: twhitney

I've suggested one possible way to fix these two problems in my pull request #3851.

Hi @ppelleti,
Thank you for taking an interest in fixing the docs. I agree with your assessment but don't think the fix is to patch up the existing output code. I think it was a mistake to include all that table formatting code in the first place. I've removed it and replaced it with simple output which doesn't obscure the point of the topic, which was to demonstrate _getdiskfree(), not how to do print formatting.
The updates to the topic should be live by 5/12/2022.


added message about 15 character limit

Why:
Closes 15969

What's being changed:
Added a note to bring attention to the 15 character limit for prefix and prefix-development options.

Check off the following:

[x] I have reviewed my changes in staging (look for "Automatically generated comment" and click Modified to view your latest changes).
[x] For content changes, I have completed the self-review checklist.

Writer impact (This section is for GitHub staff members only):

[ ] This pull request impacts the contribution experience

[ ] I have added the 'writer impact' label
[ ] I have added a description and/or a video demo of the changes below (e.g. a "before and after video")

@cmwilson21
Thanks so much for opening a PR! I'll get this triaged for review :zap:


[KOGITO-6769] Removing generic type

Many thanks for submitting your Pull Request :heart:!
Please make sure that your PR meets the following requirements:

[ ] You have read the contributors guide
[ ] Your code is properly formatted according to this configuration
[ ] Pull Request title is properly formatted: KOGITO-XYZ Subject
[ ] Pull Request title contains the target branch if not targeting main: [0.9.x] KOGITO-XYZ Subject
[ ] Pull Request contains link to the JIRA issue
[ ] Pull Request contains link to any dependent or related Pull Request
[ ] Pull Request contains description of the issue
[ ] Pull Request does not include fixes for issues other than the main ticket

How to replicate CI configuration locally?

Build Chain tool does "simple" maven build(s), the builds are just Maven commands, but because the repositories relates and depends on each other and any change in API or class method could affect several of those repositories there is a need to use build-chain tool to handle cross repository builds and be sure that we always use latest version of the code for each repository.
build-chain tool is a build tool which can be used on command line locally or in Github Actions workflow(s), in case you need to change multiple repositories and send multiple dependent pull requests related with a change you can easily reproduce the same build by executing it on Github hosted environment or locally in your development environment. See local execution details to get more information about it.

How to retest this PR or trigger a specific build:

Run all builds
Please add comment: Jenkins retest this

Run (or rerun) specific test(s)
Please add comment: Jenkins (re)run [kogito-runtimes|optaplanner|kogito-apps|kogito-examples|optaplanner-quickstarts|optaweb-employee-rostering|optaweb-vehicle-routing] tests

Quarkus LTS checks
Please add comment: Jenkins run LTS

Run (or rerun) LTS specific test(s)
Please add comment: Jenkins (re)run [kogito-runtimes|optaplanner|kogito-apps|kogito-examples|optaplanner-quickstarts|optaweb-employee-rostering|optaweb-vehicle-routing] LTS

Native checks
Please add comment: Jenkins run native

Run (or rerun) native specific test(s)
Please add comment: Jenkins (re)run [kogito-runtimes|optaplanner|kogito-apps|kogito-examples|optaplanner-quickstarts|optaweb-employee-rostering|optaweb-vehicle-routing] native

Full Kogito testing (with cloud images and operator BDD testing)
Please add comment: Jenkins run BDD
This check should be used only if a big change is done as it takes time to run, need resources and one full BDD tests check can be done at a time ...

It would be great to add a test, to the issue this is fixing.
Test added

(tests) - kogito-apps job #1085 was: FAILURE
Possible explanation: Pipeline failure or project build failure
Please look here: https://eng-jenkins-csb-business-automation.apps.ocp-c1.prod.psi.redhat.com/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-runtimes.tests.downstream.kogito-apps/1085/display/redirect or see console log:

Console Logs
[Pipeline] tool[Pipeline] envVarsForTool[Pipeline] withEnv[Pipeline] {[Pipeline] script[Pipeline] {[Pipeline] echo[2022-02-11T19:43:22.213Z] [INFO] Getting build-chain version from composite action file[Pipeline] readFile[Pipeline] echo[2022-02-11T19:43:24.350Z] [INFO] build-chain version recovered '2.3.29'[Pipeline] sh[2022-02-11T19:43:24.651Z] + npm install -g<EMAIL_ADDRESS>-registry=https://repository.engineering.redhat.com/nexus/repository/registry.npmjs.org/[2022-02-11T19:48:46.166Z] npm WARN notsup Unsupported engine for<EMAIL_ADDRESS>wanted: {"node":">= 12.18.0"} (current: {"node":"12.16.3","npm":"6.14.4"})[2022-02-11T19:48:46.166Z] npm WARN notsup Not compatible with your version of node/npm: @kie/build-chain-action@2.3.29[2022-02-11T19:48:46.166Z] npm WARN<EMAIL_ADDRESS>requires a peer of @octokit/core@>=3 but none is installed. You must install peer dependencies yourself.[2022-02-11T19:48:46.166Z] [2022-02-11T19:48:46.166Z] npm ERR! network timeout at: https://repository.engineering.redhat.com/nexus/repository/registry.npmjs.org/universal-user-agent/-/universal-user-agent-6.0.0.tgz[2022-02-11T19:51:07.645Z] [2022-02-11T19:51:07.645Z] npm ERR! A complete log of this run can be found in:[2022-02-11T19:51:07.645Z] npm ERR!     /home/jenkins/.npm/_logs/2022-02-11T19_48_43_994Z-debug.log[Pipeline] }[Pipeline] // script[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Build projects)Stage "Build projects" skipped due to earlier failure(s)[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Sonar analysis)Stage "Sonar analysis" skipped due to earlier failure(s)[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (check space after build)Stage "check space after build" skipped due to earlier failure(s)[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Declarative: Post Actions)[Pipeline] script[Pipeline] {[Pipeline] sh[2022-02-11T19:51:08.493Z] + wget --no-check-certificate -qO - https://eng-jenkins-csb-business-automation.apps.ocp-c1.prod.psi.redhat.com/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-runtimes.tests.downstream.kogito-apps/1085/api/json[Pipeline] readJSON[Pipeline] sh

Jenkins rerun kogito-apps tests

@tiagodolphine @MarianMacik Please take a look to this "quick" fix


Neomake stops running linter after period of time

I consistently have issues where neomake will work fine (using eslint for javascript), and then at some point will stop working in an extended neovim session (30 mins to a few hours) - there is no status message that the linter is run like there was when neovim was initially opened. Restarting always fixes this - and neither the run on save or the :Neomake seems to work. I haven't been able to isolate to a particular thing that I do.
Has anyone has ever faced this? What would be the best way to debug?

Set neomake_verbose=3.
If it still happens, please create a new issue using the issue template.


Revert "[CWS] fix rare event corruption"

The fix for this event corruption was merged, since we have confirmed that this was the issue, we can now revert this temporary PR.
Reverts DataDog/datadog-agent#23354

/merge


permission denied for mkdir '/usr/local/lib/node_modules/@imove'

while running npm install (without root or sudo permission), it raise exception as blow
Error: EACCES: permission denied, mkdir '/usr/local/lib/node_modules/@imove'

why need to create a global command for a local project?

this project need a service imove -d。you can use nvm.sh install node to user home dir. or change /package.json postinstall use sudo permission.
we will refact with umi mock @SmallStoneSK

this project need a service imove -d。you can use nvm.sh install node to user home dir. or change /package.json postinstall use sudo permission.
we will refact with umi mock @SmallStoneSK

I've got the answer as mentioned below:

this project need a service imove -d。you can use nvm.sh install node to user home dir. or change /package.json postinstall use sudo permission.

I've got the answer as mentioned below:

this project need a service imove -d。you can use nvm.sh install node to user home dir. or change /package.json postinstall use sudo permission.


Regarding the old_location options

If old_location has not been specified, then relative_path should be required.
If old_location has not been specified, it's not necessarily an error for relative_path to match the value for another, already-registered dataset.  This actually can happen for GCRCatalogs datasets.   The code should perhaps put out a warning but should go ahead and register the new dataset.

Started addressing this in #158

If old_location has not been specified, then relative_path should be required.

I have added this check in the PR (if location_type=dataregistry, as all other types dont handle data)

If old_location has not been specified, it's not necessarily an error for relative_path to match the value for another, already-registered dataset. This actually can happen for GCRCatalogs datasets. The code should perhaps put out a warning but should go ahead and register the new dataset.

It only raises this error when location_type=dataregistry, to make sure people can't over write other peoples data. I'm not sure what you mean by GCR datasets in this sense

When registering a GCRCatalog-type catalog, the code gets as much information as it can from its config file.  There are various keywords in those files which can be used to say "the dataset is in this directory".  But there are also ways in the config file to narrow down exactly which files constitute the dataset.  See for example
https://github.com/LSSTDESC/gcr-catalogs/blob/master/GCRCatalogs/catalog_configs/dc2_redmagic_run2.2i_dr6_wfd_v0.8.1_highdens.yaml and
https://github.com/LSSTDESC/gcr-catalogs/blob/master/GCRCatalogs/catalog_configs/dc2_redmagic_run2.2i_dr6_wfd_v0.8.1_highlum.yaml
They they have the same value for the keyword catalog_root_dir, which is essentially our relative_path, but there is another keyword catalog_path_template which can be used to select a subset of the files in the directory.  I thought of three different ways we could handle this, but the simplest by far is just to say that, when dataregistry is not copying files, we assume the user knows what they're doing and allow them to use the same relative_path.


ANCM: Inprocess: If App fails becasue hostfxr.dll does not exist, we should make error event that the hostfx file not found

Rename hostfxr.dll with a different file name such as C:\Program Files\dotnet\host\fxr\2.1.0-preview1-26110-02_hostfxr.dll

Send a request

EXPECTED:
There is an windows event error which explains the hostfx.dll file not found.
ACTUAL:
There is an error event but that does not explain the root cause.
For example, I got this error but this does not give any hint on the root cause.
Application '/LM/W3SVC/1/ROOT/Test123' with physical root 'C:\inetpub\wwwroot\Test123' hit unexpected managed background thread exit, ErrorCode = '0x0.

@jkotalik #533 is merged. Please verify if this can be closed.


Setting tab Active with $scope disables other tabs

I am using Angular 1.4.6 and ui-bootstrap 0.13.4.  I have a tab that is disabled.  When the user clicks a button, I want to enable the tab and make it active (I am using $scope.noView = true/false and active = noView).  This works fine, accept that once it becomes Active all other tabs are non-clickable.  The don't show as being disabled, but clicking on them does nothing.  Am I missing something?

https://github.com/angular-ui/bootstrap#found-a-bug


auto refresh

i have a big problems with claude dev auto refresh, while sending some request, or maybe i hat to approve some changes, it refresh the ui and lose everything. Than i had to submit again analyze to the intire project etc.. and cost a lot of tokens to do this again and again. need the history buttuns.

Task history is currently in development, but I recommend you export your task conversation using the 'EXPORT .MD' button and use that as context for future tasks. Be sure to strip out any irrelevant information to keep token count low.


No external pull-up/pull-down resisters on board

Problem Summary
There are no external pull resisters on any of the main board's output signals (include the I2C bus as stated in #3). This can lead to dangerous situations where a crashed program and floating output can cause one of the AC components (heater, pump, solenoid) to get stuck in the on position.
Proposed Solution
Add 4.7KΩ pull up resisters to all the output signal lines on the RaspberryLatte main board.

Fixed with new version of main board


iOS unit tests crashing when the tests are randomized

This appears to be a memory corruption since it is showing up in weird places like so:
#0	0x0000600021c300b0 in fml::WeakPtr<flutter::PlatformView>::operator->() const at /Users/aaclarke/dev/engine/src/flutter/fml/memory/weak_ptr.h:112
#1	0x0000600021c993c1 in -[FlutterViewController surfaceUpdated:] at /Users/aaclarke/dev/engine/src/flutter/shell/platform/darwin/ios/framework/Source/FlutterViewController.mm:587
#2	0x0000600021c9a401 in -[FlutterViewController applicationWillResignActive:] at /Users/aaclarke/dev/engine/src/flutter/shell/platform/darwin/ios/framework/Source/FlutterViewController.mm:707
#3	0x00007fff23ac2c1c in __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ ()
#4	0x00007fff23ac20a5 in _CFXRegistrationPost1 ()
#5	0x00007fff23ac1e0f in ___CFXNotificationPost_block_invoke ()
#6	0x00007fff23bbffe3 in -[_CFXNotificationRegistrar find:object:observer:enumerator:] ()
#7	0x00007fff23ac1776 in _CFXNotificationPost ()
#8	0x00007fff2564d429 in -[NSNotificationCenter postNotificationName:object:userInfo:] ()
#9	0x0000600021bca8d7 in -[FlutterPluginAppLifeCycleDelegateTest testWillResignActive] at /Users/aaclarke/dev/engine/src/flutter/shell/platform/darwin/ios/framework/Source/FlutterPluginAppLifeCycleDelegateTest.m:48

Steps to reproduce:

Check out master
Run the unit tests in random order, eventually you'll get a crash

Here is the other place it seems to show up:
#1	0x000060002365b1d7 in flutter::SamplingProfiler::SampleRepeatedly(fml::TimeDelta) const at /Users/aaclarke/dev/engine/src/flutter/shell/profiling/sampling_profiler.cc:33
#2	0x000060002365dc8c in flutter::SamplingProfiler::SampleRepeatedly(fml::TimeDelta) const::$_0::operator()() const at /Users/aaclarke/dev/engine/src/flutter/shell/profiling/sampling_profiler.cc:63
#3	0x000060002365da3d in decltype(std::__1::forward<flutter::SamplingProfiler::SampleRepeatedly(fml::TimeDelta) const::$_0&>(fp)()) std::__1::__invoke<flutter::SamplingProfiler::SampleRepeatedly(fml::TimeDelta) const::$_0&>(flutter::SamplingProfiler::SampleRepeatedly(fml::TimeDelta) const::$_0&) at /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/type_traits:3545
#4	0x000060002365d9ed in void std::__1::__invoke_void_return_wrapper<void>::__call<flutter::SamplingProfiler::SampleRepeatedly(fml::TimeDelta) const::$_0&>(flutter::SamplingProfiler::SampleRepeatedly(fml::TimeDelta) const::$_0&) at /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/__functional_base:348
#5	0x000060002365d9bd in std::__1::__function::__alloc_func<flutter::SamplingProfiler::SampleRepeatedly(fml::TimeDelta) const::$_0, std::__1::allocator<flutter::SamplingProfiler::SampleRepeatedly(fml::TimeDelta) const::$_0>, void ()>::operator()() at /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/functional:1546
#6	0x000060002365c7ae in std::__1::__function::__func<flutter::SamplingProfiler::SampleRepeatedly(fml::TimeDelta) const::$_0, std::__1::allocator<flutter::SamplingProfiler::SampleRepeatedly(fml::TimeDelta) const::$_0>, void ()>::operator()() at /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/functional:1720
#7	0x0000600021f08a35 in std::__1::__function::__value_func<void ()>::operator()() const at /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/functional:1873
#8	0x0000600021f089f5 in std::__1::function<void ()>::operator()() const at /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/functional:2548
#9	0x00006000224e4b21 in fml::MessageLoopImpl::FlushTasks(fml::FlushType) at /Users/aaclarke/dev/engine/src/flutter/fml/message_loop_impl.cc:130
#10	0x00006000224e49da in fml::MessageLoopImpl::RunExpiredTasksNow() at /Users/aaclarke/dev/engine/src/flutter/fml/message_loop_impl.cc:143
#11	0x00006000225043f5 in fml::MessageLoopDarwin::OnTimerFire(__CFRunLoopTimer*, fml::MessageLoopDarwin*) at /Users/aaclarke/dev/engine/src/flutter/fml/platform/darwin/message_loop_darwin.mm:75

void SamplingProfiler::SampleRepeatedly(fml::TimeDelta task_delay) const {
  profiler_task_runner_->PostDelayedTask(
      [profiler = this, task_delay = task_delay, sampler = sampler_]() {
        // TODO(kaushikiska): consider buffering these every n seconds to
        // avoid spamming the trace buffer.
        const ProfileSample usage = sampler();

FlutterEngine.1.profiler (14): EXC_BAD_ACCESS (code=1, address=0x60009266efb8)

(0x60009266efb8 = &this->profiler_task_runner_)
cc @iskakaushik

It looks like there is no way to safely shut down a SamplingProfiler, so that may be the problem.

I fixed the SamplingProfiler problem.  It looks like there were 2 different memory issues, the other related to PlatformViews.

I think both of the crashes have been resolved with https://github.com/flutter/engine/pull/23012 and https://github.com/flutter/engine/pull/23037


[WIP] RealmSwift.podspec

This closes #1705 and supersedes #1510.
This is blocked by the (full public) release of CocoaPods/CocoaPods#3420.
Local Testing
:warning: Those instructions are only thought for development on Realm. Please wait until the release of RealmSwift before trying to consume the podspec.
# Preconditions
cd realm-cocoa
git fetch
git checkout mr-swift-podspec

# `pod --version` ~> 0.37.0.beta.1
gem install --pre cocoapods

# Setup a local private repo
mkdir -p ~/.cocoapods/bare-repos
git init --bare ~/.cocoapods/bare-repos/realm-private
pod repo add realm-private ~/.cocoapods/bare-repos/realm-private

# Change the source of Realm.podspec to point to this branch
# otherwise the changes in build.sh wouldn’t be applied
sed -i "s/:tag => \"v#{s.version}/:branch => \"mr-swift-podspec/" Realm.podspec

# Push Realm.podspec with modulemap to private local repo
pod ipc spec Realm.podspec > Realm.podspec.json
pod repo push --verbose realm-private Realm.podspec.json --allow-warnings

# Lint RealmSwift.podspec
pod ipc spec RealmSwift.podspec > RealmSwift.podspec.json
pod spec lint --verbose RealmSwift.podspec.json --sources=realm-private

@mrackwitz can you please verify that this is still working in swift 1.2?

I can confirm that this works with RealmSwift 1.2. But CocoaPods 0.37 has a bug in the downloader cache, which blocks this for now.

Can you recommend a work-around? A link to the CocoaPods bug in question would be nice too.

The only possible workaround is disabling the cache via setting the environment var COCOAPODS_SKIP_CACHE. This must be also done for pod spec lint.

Having a working podspec is a pretty important requirement to releasing Realm Swift. What can be done to resolve this? I can't find the relevant CocoaPods issue.

I'm working on CocoaPods/CocoaPods#3498 to fix that.

Ok, let's wait for that before releasing Realm Swift then.

After rebasing (and using Marius' PR branch to lint), Realm.podspec passes lint, but RealmSwift.podspec yields a warning:
- WARN  |  <module-includes>:1:1: warning: umbrella header for module 'Realm' does not include header 'Target Support Files/Pods-Realm/Pods-Realm-umbrella.h'

Otherwise, everything works!

After https://github.com/CocoaPods/CocoaPods/pull/3509 and https://github.com/CocoaPods/CocoaPods/pull/3498 are merged and released, this PR is good to merge and ship.

:+1: great work @mrackwitz and @segiddins!

With https://github.com/CocoaPods/CocoaPods/releases/tag/0.37.1, I think this is good to go!
\c @mrackwitz @tgoyne

:+1: assuming it works and stuff.

Just confirmed that it appears to be working!

I just upgraded to Cocoapod 0.37.1 to try this because the manual approach didn't work.
But I got the following error:
/Users/marcvano/dev/cameo/Cameo2/Pods/RealmSwift/RealmSwift/List.swift:21:8: error: no such module 'Realm.Private'
import Realm.Private

@marcvanolmen you need to also do the following in your podfile:
pod 'Realm', git: 'https://github.com/realm/realm-cocoa.git'

Ok thanks that worked also I was able to use RealmSwift now


Routes typescript

npm install @types/react-router-dom does not have Routes supported as far

Those types aren't maintained here. We don't have types for v6 yet.

Sorry to chime in. Is anyone working on types yet or are you waiting for release? I have a good app that sits between medium and large and would love to test this out.

Nevermind. I found the open PR to add @6 - https://github.com/DefinitelyTyped/DefinitelyTyped/pull/44015

Why don't you just add typescript support directly into react-router?
This is such a basic react library and it's a shame that it does not support typescript directly which should be a must have for any good react library.

@olee We plan to do so in v6. Michael is working on it.

If any of you could help with my PR to make it pass I would highly appreciate it. Me and 2 other guys did almost everything but due to braking changes I cannot pass the tests and it makes it impossible to quickly enable all TypeScripters to use v6.

Looks like they are putting types right into the project - https://github.com/ReactTraining/react-router/commit/ad470c3efdabdb8a9fe2229a31d3e32e99546d4c


sequence number should never overflow

Incrementing sequence number on an object can fail due to overflow.
This will be a violation (the only violation I can think of) of the property that even failed transaction should consume gas (hence some object is mutated). This also creates opportunities for DOS because someone can keep using this almost-overflowed gas object and trigger tx failures without paying gas.
We could make a rule that when am object is at this max version we automatically rule it immutable. And be done with it.
Our version counters are 64 bits and all versions will have to be the result of transactions on chain. This is an astronomical number of transactions, on a single object.

@lxfind I'm happy with the 2nd option, do not allow a tx with u64:MAX.

This is done.


Fototoon svg alignment to text in warning box

#1596 @llaske The Cancel and Continue button is now aligned to the icon.

Thanks.


issue #280 - put nullable constructor args at the end

Coverage Report

Totals

Statements:
96.88% ( 4007 / 4136 )

Methods:
93.8% ( 711 / 758 )

Lines:
97.57% ( 3296 / 3378 )


Allow functions to work with strings

Strings are treatable as lists of characters. Having functions such as with, map, ChainableSequence, and so on support strings, makes it easy to loop over them or perform other operations on them.
Converting a string to an array is straightforward:
$charList = [];

for ($i = 0; $i < mb_strlen($yourString); ++$i) {
    $charList[] = mb_substr($yourString[$i], $i, 1);
}

This should also support Unicode characters. Optionally, if you want to treat strings as a list of bytes (I would not make this the default, though, since it's not intuitive):
$byteList = [];

for ($i = 0; $i < strlen($yourString); ++$i) {
    $byteList[] = $yourString[$i];
}

Thanks!

We would need to convert the result value back to string each time, which doesn't make much sense. One can convert string to an array on their own if needed:
$string = with(str_split('hello world'))
    ->map(function($char) {
        if (in_array($char, ['a', 'e', 'i', 'o', 'u'])) {
            return strtoupper($char);
        }

        return $char;
    })
    ->reduce(\nspl\op\concat);

Doh, I forgot that str_split already exists.
In any case, it was not my intention to have the result convert back to a string automatically, but your proposed solution solves that elegantly, too, thanks!
Now I just need implicit cast operator overloads in PHP so I can have my strings coerce to arrays automatically without requiring str_split 😄...


Updated io-sim & typed-protocols

Description
Updated io-sim, io-classes and strict-stm.
TODO:

[x] update typed-protocols once input-output-hk/typed-protocols#16 is merged.

Checklist

Branch

[x] Commit sequence broadly makes sense
[ ] Commits have useful messages
[ ] New tests are added if needed and existing tests are updated
[ ] If this branch changes Consensus and has any consequences for downstream repositories or end users, said changes must be documented in interface-CHANGELOG.md
[ ] If this branch changes Network and has any consequences for downstream repositories or end users, said changes must be documented in interface-CHANGELOG.md
[ ] If serialization changes, user-facing consequences (e.g. replay from genesis) are confirmed to be intentional.

Pull Request

[ ] Self-reviewed the diff
[ ] Useful pull request description at least containing the following information:

What does this PR change?
Why these changes were needed?
How does this affect downstream repositories and/or end-users?
Which ticket does this PR close (if any)? If it does, is it linked?

[ ] Reviewer requested

bors merge


App Service slot deployment gives "Site with name  already exists" error when slot originated from Bicep file

Bicep version
Bicep CLI version 0.8.9 (33a85174de)
Describe the bug
Running the following bicep file works fine when it's creating the resources net-new, but subsequent runs throw the following:
{
    "status": "Failed",
    "error": {
        "code": "DeploymentFailed",
        "message": "At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.",
        "details": [
            {
                "code": "Conflict",
                "message": "{\r\n  \"status\": \"Failed\",\r\n  \"error\": {\r\n    \"code\": \"ResourceDeploymentFailure\",\r\n    \"message\": \"The resource operation completed with terminal provisioning state 'Failed'.\",\r\n    \"details\": [\r\n      {\r\n        \"message\": \"Conflict\\r\\nDetail: Site with name <app service name>(stage) already exists.\\r\\nExtendedCode: 04008\\r\\n   at Microsoft.Web.Hosting.Administration.Csm.Common.Clients.GeoClientBase.GetResponse[T](HttpWebRequest request, Boolean reThrowOnHostUnavailability, HttpStatusCode[] supressLogForHttpCodes)\\r\\n   at Microsoft.Web.Hosting.Administration.GeoScale.Sql.WebSiteCloneManager.StartRestoreFromBackup(SiteClone clone, Operation cloneOperation)\\r\\n\"\r\n      }\r\n    ]\r\n  }\r\n}"
            }
        ]
    }
}

To Reproduce
param appInsightsName string
param location string
param environment string
param tenant string
param appServicePlanName string
param sqlServerName string
param databaseName string
param databaseAppUser string
@secure()
param databaseAppPassword string

resource appServicePlan 'Microsoft.Web/serverfarms@2022-03-01' existing = {
  name: appServicePlanName
}

resource applicationInsights 'Microsoft.Insights/components@2020-02-02' existing = {
  name: appInsightsName
}

resource sqlServer 'Microsoft.Sql/servers@2021-11-01-preview' existing = {
  name: sqlServerName
}

resource database 'Microsoft.Sql/servers/databases@2021-11-01-preview' existing = {
  name: databaseName
}

var appInsightsExtensionSettings = [
  {
    name: 'APPINSIGHTS_PROFILERFEATURE_VERSION'
    value: '1.0.0'
  }
  {
    name: 'APPINSIGHTS_SNAPSHOTFEATURE_VERSION'
    value: '1.0.0'
  }
  {
    name: 'ApplicationInsightsAgent_EXTENSION_VERSION'
    value: '~2'
  }
  {
    name: 'Diagnostics_EXTENSION_VERSION'
    value: '~3'
  }
  {
    name: 'InstrumentationEngine_EXTENSION_VERSION'
    value: '~1'
  }
  {
    name: 'SnapshotDebugger_EXTENSION_VERSION'
    value: '~1'
  }
  {
    name: 'XDT_MicrosoftApplicationInsights_BaseExtensions'
    value: '~1'
  }
  {
    name: 'XDT_MicrosoftApplicationInsights_Mode'
    value: 'recommended'
  }
  {
    name: 'XDT_MicrosoftApplicationInsights_PreemptSdk'
    value: 'disabled'
  }
]

var connectionStringList = [
  {
    name: 'VendorManagementConnection'
    connectionString: 'Server=tcp:${sqlServer.properties.fullyQualifiedDomainName},1433;Initial Catalog=${database.name};Persist Security Info=False;User ID=${databaseAppUser};Password=${databaseAppPassword};MultipleActiveResultSets=True;Encrypt=True;TrustServerCertificate=False;Connection Timeout=30;'
    type: 'SQLAzure'
  }
]

var internalAppServiceName = '<app service name>'
var appSettingsList = [

]
var tags = {
  environment: environment
  location: location
  tenant: tenant
}

resource internalApiService 'Microsoft.Web/sites@2022-03-01' = {
  name: internalAppServiceName
  location: location
  kind: 'app'
  tags: tags
  properties: {
    serverFarmId: appServicePlan.id
    clientAffinityEnabled: true
    httpsOnly: true
  }
  resource web 'config' = {
    name: 'web'
    properties: {
      numberOfWorkers: 1
      netFrameworkVersion: 'v6.0'
      use32BitWorkerProcess: false
      webSocketsEnabled: false
      alwaysOn: true
      managedPipelineMode: 'Integrated'
      http20Enabled: true
      minTlsVersion: '1.2'
      ftpsState: 'FtpsOnly'
      appSettings: union(appSettingsList, [
          {
            name: 'APPINSIGHTS_INSTRUMENTATIONKEY'
            value: applicationInsights.properties.InstrumentationKey
          }
          {
            name: 'APPLICATIONINSIGHTS_CONNECTION_STRING'
            value: applicationInsights.properties.ConnectionString
          }
        ], appInsightsExtensionSettings)
      connectionStrings: connectionStringList
    }
  }

  resource stage 'slots' = {
    name: 'stage'
    location: location
    kind: 'app'
    properties: {
      serverFarmId: appServicePlan.id
      clientAffinityEnabled: true
      httpsOnly: false
      cloningInfo: {
        appSettingsOverrides: {
          APPLICATIONINSIGHTS_CONNECTION_STRING: ''
          APPINSIGHTS_INSTRUMENTATIONKEY: ''
          APPINSIGHTS_PROFILERFEATURE_VERSION: ''
          APPINSIGHTS_SNAPSHOTFEATURE_VERSION: ''
          ApplicationInsightsAgent_EXTENSION_VERSION: ''
          Diagnostics_EXTENSION_VERSION: ''
          InstrumentationEngine_EXTENSION_VERSION: ''
          SnapshotDebugger_EXTENSION_VERSION: ''
          XDT_MicrosoftApplicationInsights_BaseExtensions: ''
          XDT_MicrosoftApplicationInsights_Mode: ''
          XDT_MicrosoftApplicationInsights_PreemptSdk: ''
        }
        sourceWebAppId: internalApiService.id
      }
    }
  }
}

Additional context
I have tried this with a couple of different names, no joy. I will note, the app service plan this is getting deployed to hosts some .NET Framework apps and this one is meant to be .NET 6, not sure if that is an issue but I couldn't find anything in the docs about hosting different stacks on the same plan, and I would expect a different error if that were the problem. It is a Windows App Service Plan.

I think the problem here is the cloningInfo property. Subsequent deployments should not use it but rather be setting properties. If we had ability to determine if the resource already exists or not (#4023) , we could use conditional to use a different property set on the resource

I will remove the cloningInfo property and see if I can run my template idempotently. Thanks for the tip, will respond with the results.

Looks like cloningInfo was the culprit. I have had to add explicit slot settings configurations and a separate Microsoft.Web/sites/config item to get the end result I wanted, which isn't ideal but it's a workaround for now. Thank you for the help!


Is this a bug?

Some instructions entered, there will be an error, the command will not play a role.

#1957 :^)


fix(fastify-template): fix for subscriptions in fastify template

Fix for #2174
Types of changes
What types of changes does your code introduce to Graphback?

[x] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Update (if none of the other choices apply)
[ ] Other (please specify)

Checklist

[x] I have read the CONTRIBUTING document.
[ ] Lint and unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)

Further comments
As discussed I've added resolvers in the plugin options of mercurius which should fix the issue.

Verification
I tried verifying this by enabling the fastify template and then using the updated cli (by running node dist/index.js in the create-graphback folder) but I received this error due to which the template didn't load and I wasn't able to test it. Please let me know if there are some other steps I can take to test if the subscriptions are working or not. Thanks.

Let's start this year with this small PR. Looking at it now

Let's start this year with this small PR. Looking at it now

 ! [remote rejected]       pr/RinkiyaKeDad/2248-1 -> pr/RinkiyaKeDad/2248-1 (permission denied)
error: failed to push some refs to 'git@github.com:RinkiyaKeDad/graphback'

I cannot fix issues in PR. Can you add me to fork :) THX

 ! [remote rejected]       pr/RinkiyaKeDad/2248-1 -> pr/RinkiyaKeDad/2248-1 (permission denied)
error: failed to push some refs to 'git@github.com:RinkiyaKeDad/graphback'

I cannot fix issues in PR. Can you add me to fork :) THX

I tried verifying this by enabling the fastify template and then using the updated cli (by running

How about running this from the code:
cd templates/ts-fastify-mongodb-backend
docker-compose up -d
yarn develop

PS: This doesn't seem to be working for me.

I tried verifying this by enabling the fastify template and then using the updated cli (by running

How about running this from the code:
cd templates/ts-fastify-mongodb-backend
docker-compose up -d
yarn develop

PS: This doesn't seem to be working for me.

I think resolvers should include noteResolvers as in

Thanks for pointing that out 😅 I've added them now @machi1990.

Can you add me to fork :) THX

Added you @wtrocki :)

PS: This doesn't seem to be working for me.

Same. It doesn't give an error in the terminal like last time, but shows that localhost refused to connect on the browser.

I think resolvers should include noteResolvers as in

Thanks for pointing that out 😅 I've added them now @machi1990.

Can you add me to fork :) THX

Added you @wtrocki :)

PS: This doesn't seem to be working for me.

Same. It doesn't give an error in the terminal like last time, but shows that localhost refused to connect on the browser.

How about running this from the code:

Okay so this way of testing the template works if I don't specify the noteResolvers and simply leave the code like this:
  app.register((mercurius as any), {
    schema,
    resolvers,
    graphiql: true,
    context: contextCreator,
    subscription: true
  });

But even with this when I tested the subscriptions they were not working. Could it be because makeExecutableSchema is not creating the schema in a way acceptable by mercurius?
Will have to look for some other way to fix this then I guess 🤔

How about running this from the code:

Okay so this way of testing the template works if I don't specify the noteResolvers and simply leave the code like this:
  app.register((mercurius as any), {
    schema,
    resolvers,
    graphiql: true,
    context: contextCreator,
    subscription: true
  });

But even with this when I tested the subscriptions they were not working. Could it be because makeExecutableSchema is not creating the schema in a way acceptable by mercurius?
Will have to look for some other way to fix this then I guess 🤔

Would it be a good idea to switch from mercurius to apollo-server-fastify?

Would it be a good idea to switch from mercurius to apollo-server-fastify?

Sounds good?

Sounds good?

Closing this since we're shifting to apollo-server-fastify. See #2256

Closing this since we're shifting to apollo-server-fastify. See #2256


Add migrations for support-refund

Migrations for https://github.com/saleor/saleor/pull/10350
Impact

[ ] New migrations
[ ] New/Updated API fields or mutations
[ ] Deprecated API fields or mutations
[ ] Removed API types, fields, or mutations
[ ] Documentation needs to be updated

Pull Request Checklist

[ ] Privileged queries and mutations are guarded by proper permission checks
[ ] Database queries are optimized and the number of queries is constant
[ ] Database migration files are up to date
[ ] The changes are tested
[ ] GraphQL schema and type definitions are up to date
[ ] Changes are mentioned in the changelog

Should we merge saleor/payment/migrations/0040_migrate_renamed_fields_transaction_item.py with saleor/payment/migrations/0041_migrate_renamed_fields_transaction_event.py?

I wasn't sure if I should mix that data migrations of two different models.
@korycins @maarcingebala any opinions?

Regarding

Should we merge saleor/payment/migrations/0040_migrate_renamed_fields_transaction_item.py with saleor/payment/migrations/0041_migrate_renamed_fields_transaction_event.py?

IMO we can merge it, but separately it's more clear to me.


Disable VNC Password

How can i disable the VNC password?

Hi,
it would be possible by providing an empty password to docker run, something like this:
docker run -e VNC_PW="" ...

However, in the current version is the password enforced by the code in the file docker\xfce\src\startup\vnc_startup.rc. You would need to remove the line || [ -z "${VNC_PW}" ] \ from the following block of code (starting at line #18) and to build your own image:
### VNC requirements
    if [ -z "${DISPLAY}" ] \
    || [ -z "${VNC_PORT}" ] \
    || [ -z "${VNC_PW}" ] \
    || [ -z "${VNC_COL_DEPTH}" ] \
    || [ -z "${VNC_RESOLUTION}" ] ; then
        cleanup "ERROR: Not all required environment variables are set: DISPLAY, VNC_PORT,VNC_PW, VNC_COL_DEPTH, VNC_RESOLUTION"
    fi

Maybe I could remove this enforcement by default and rebuild the images on Docker Hub.
Why do you want to use it without a password? It would be less secure.
Regards,
accetto

One more thing...
Please be aware that even if you will set the VNC password to an empty one, as it has been described above, the password for sudo will still be set to headless. If you want to change also that one, then you would need to change the line VNC_PW=${ARG_VNC_PW:-headless} \ in  the following part of the Dockerfile (starting at line #223):
RUN \
    chmod 664 /etc/passwd /etc/group \
    && echo "headless:x:1001:0:Default:${HOME}:/bin/bash" >> /etc/passwd \
    && adduser headless sudo \
    && echo "headless:${VNC_PW}" | chpasswd \
    && ${ARG_FEATURES_USER_GROUP_OVERRIDE/*/chmod a+w /etc/passwd /etc/group} \
    && chmod +x "${STARTUPDIR}"/*.sh \
    && "${STARTUPDIR}"/set_user_permissions.sh "${STARTUPDIR}" "${HOME}"

However, the sudo password must not be empty and you cannot change it simply by docker run, because its default value is embedded into the image. If you want to change it, you have to re-build the image. You can change it afterwards inside the container, of course.

I like to use without password because it will run inside a VPN and protected by a LDAP password.
So the vnc password became redundant.
Currently i'm extending this image using a Dockerfile and installing the apps we will need

I see. I think I can remove the enforcement and publish a new release. The images on Docker Hub will be re-built automatically. They should be available soon.

I've try with the new version and keep asking for password.
It's possible to activate the autoconnect to not open the password screen?
docker run -P -e VNC_PW="" -p 26901:6901 accetto/ubuntu-vnc-xfce-g3

Sorry, it seems I've missed this comment.

It's possible to activate the autoconnect to not open the password screen?

I'm afraid not, if you use the TigerVNC Viewer. At least not that I would know.
However, by noVNC access you can put your password into the link. Something like this:
http://mynas:26901/vnc_lite.html?password=headless
http://mynas:26901/vnc.html?password=headless
In that case you should not be prompted for the password.

I would like the functionality for not using the password as well. Is there any update for this?


Sope function with return

I'm new to ng-React and I'm trying to run function from scope in my react component and get the return value from that function. I've managed to run scope function by adding this my view:
<cell get-data="getSomething"/>

And by making this in my react class:
var ReactTableRow = React.createClass({
    propTypes: {
        getData: React.PropTypes.func
    },
    render: function() {
        var foo= this.props.getData(400);
        return (
            React.DOM.div(null, foo)
        )
    }
});

And my controller:
$scope.getSomething = function(number) {
    return number + 10;
}

So, when i debug i can see that my function is being called but the return is not working. Any ideas how to make that possible?

@RudmanMario thanks for you question.
The return value from passed in functions isn't available. You generally want data to flow into React component through the probs. So if the data needs to be calculated based on some action, I would let that action recalculate the data "bound" to the probs. In your example that would be something like this:
Angular View:
<cell recalc="recalc" data="data"/>

React Component
var ReactTableRow = React.createClass({
    propTypes: {
        recalc: React.PropTypes.func,
        data: React.PropTypes.object
    },

    render: function() {
        return (
            React.DOM.div( {onClick: this._handleOnClick}, data)
        )
    },

   _handleOnClick: function() {
     this.props.recalc( 400 );
  }
});

Angular controller
$scope.recalc = function(number) {
    $scope.data = number + 10;
}

$scope.data = $scop.recalc( 400 )

Thank you for the response. At least now I know that it's not possible to get the return value so I can focus on trying something else. Your solution is fine, but I'm trying to avoid generating new watchers which was the reason I decided to work with react. Thanks again, I'll try some different approach for my problem.


Missing field "organization" in connector config

When trying to use Terraform to set up the new Gladly preview connector, I get the following error. The Fivetran API for Gladly requires the "organization" config, but that doesn't seem supported in Terraform yet.
╷
│ Error: Unsupported argument
│
│   on fivetran_gladly.tf line 28, in resource "fivetran_connector" "gladly":
│   28:     organization = var.gladly_organization
│
│ An argument named "organization" is not expected here. Did you mean
│ "organizations"?
╵

Please add the field "organization" to the fivetran_connector config nested schema.
Here's my Terraform code:
variable "gladly_username" {
  description = "To be passed in during CI/CD as the username to connect to Gladly."
  type        = string
}

variable "gladly_api_token" {
  description = "To be passed in during CI/CD as the API token to connect to Gladly."
  type        = string
}

variable "gladly_organization" {
  description = "To be passed in during CI/CD as the organization to connect to Gladly."
  type        = string
}

resource "fivetran_connector" "gladly" {
  group_id          = fivetran_group.group.id
  service           = "gladly"
  sync_frequency    = 60 # minutes
  paused            = false
  pause_after_trial = true  # <-- SET TO FALSE BEFORE MERGING TO MAIN
  destination_schema {
    name = "gladly"
  }
  config {
    username = var.gladly_username
    api_token = var.gladly_api_token
    organization = var.gladly_organization
  }
  depends_on = [
    fivetran_destination.snowflake,
  ]
}

Created an internal ticket for this issue.

Update included into the next version v0.6.13, release planned at March 1.


Support newest guzzle version

Is your feature request related to a problem? Please describe.
Cannot use this package with the newest guzzle version (6.4.1)
Describe the solution you'd like
Change composer.json require allowing guzzle 6.4
Describe alternatives you've considered
Additional context
https://github.com/googleapis/google-cloud-php/blob/master/composer.json#L48

The current version constraint allows Guzzle versions between 5.3 and 7.0.
Something like this:  5.3.0 <= [current version] < 7.0.0
In my tests, cloning the repository and running composer install results in guzzlehttp/guzzle installed at 6.4.1.
Do you receive an error or are you simply locked at a lower version?

You are right lol. Sorry maybe miss looked at package :see_no_evil:  Sorry! :blush:


Lucas.liseth/time travel logging

What does this PR do?

This PR creates a new verbose logger that logs all logs below the configured level (configured with the log_level option). For example, if the configured log level is log_level: INFO, the verbose logger will store DEBUG and TRACE logs. Logs are stored in the same directory as the normal agent.log file, however the file is suffixed with -verbose. For example, if the agent logs are stored in /var/log/datadog/agent.log, verbose logs will be stored in /var/log/datdog/agent-verbose.log.
Motivation

The purpose of this PR is to aid in diagnosing issues with the agent.
Additional Notes

There are still a couple things to do, namely adding file rotation when the file gets too large or logs become stale.
Possible Drawbacks / Trade-offs

Performance testing is still ongoing.
Describe how to test/QA your changes

Build the agent normally. Set logs_config.verbose_logging: true. When you start the agent it should now create a new file with logs below the configured log_level in the same directory as the agent.log file.
Reviewer's Checklist

[ ] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[ ] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
[ ] A release note has been added or the changelog/no-changelog label has been applied.
[ ] Changed code has automated tests for its functionality.
[ ] Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
[ ] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[ ] If applicable, the need-change/operator and need-change/helm labels have been applied.
[ ] If applicable, the k8s/<min-version> label, indicating the lowest Kubernetes version compatible with this feature.
[ ] If applicable, the config template has been updated.

As this draft hasn't seen activity in over 6 months, I'm going to close this.
Thank you @soberpeach, and please feel free to reopen or create a new PR when you want the team to take a look at this again.


Failed to mkdir "/var/www/mediawiki/w/sitemap/"

I saw error message canasta log:
PHP Warning:  failed to mkdir "/var/www/mediawiki/w/sitemap/" mode 0777 [Called from wfMkdirParents in /var/www/mediawiki/w/includes/GlobalFunctions.php at line 1918] in /var/www/mediawiki/w/includes/debug/MWDebug.php on line 430
It was ghcr.io/canastawiki/canasta:1.35.6-20220414-80

It looks like we need to mkdir $MW_HOME/sitemap in Dockerfile line 75
line 652 symlinks the volume directory $MW_VOLUME/sitemap to $MW_HOME/sitemap (which doesn't exist).
Testing
Set
MW_ENABLE_SITEMAP_GENERATOR=true in your .env file and docker-compose up
Note: I have not tested this.


Example setup using Lazy package manager

It would be great to have an example using lazy

Bump. Cant seem to get it working in lazy for some reason


cf mgmt Pipeline to update-space-user is failing

Error syncing users for org xxx, space test, role developer: adding ldap users: User xxxxx with origin ldap: cfclient error (CF-UnprocessableEntity|10008): User 'xxxxx' already has 'space_developer' role in space 'test'.]

@niteshpa This issue should have been fixed in 1.0.85 - https://github.com/vmware-tanzu-labs/cf-mgmt/releases/tag/v1.0.85 let me know if this is persisting once you have updated to this version or beyond.

We upgraded to 1.0.85, but still this issue is persisting.

@niteshpa will need you to provide full debug and trace output to further triage this.  This can be done by setting LOG_LEVEL to debug and in a different run set it to trace.  Debug provides cf-mgmt level logging and trace provides raw http request / response information.  If unable to cleanse the data and a VMware / Broadcom customer can open a support ticket and upload the information which I can then retrieve it.
Other alternative is to delete this user and see if this resolves the problem with “cf delete-user” command