refactor: Calendar page refactored

This is part of #43.
Important changes:

Removed percent height from the calendar screen. It's dynamic now.
Removed fixed height and width from the day container as well. Added padding.
Since, widgets were getting immediately built, there was no point in using a loading indicator for each day widget. So removed that. In the future, maybe we can show a shimmer indicator. Current refactor will aid in that.
There was a bad state error due to parsing error. Suppressed that for now.

Video:
https://user-images.githubusercontent.com/26508767/186742244-8fa78ffb-ca95-4d89-8387-4381031ffde7.mp4

@jorre127 and @KalleHallden this is a bit sensitive. Please pull and test the calendar screen.

I get overflow error on iPhone 12

I get overflow error on iPhone 12

I think we need to reference this in a new issue. And it's better if we switch to existing calendar package instead of using our own. But for now, I reduced 20 extra paddings. Giving more room.

I get overflow error on iPhone 12

I think we need to reference this in a new issue. And it's better if we switch to existing calendar package instead of using our own. ~But for now, I reduced 20 extra paddings. Giving more room.~

yeah it would probably be more stable to switch to a package, but then we would lose the customisability we have not I think. would depend on how the new design would look I guess.

I get overflow error on iPhone 12

What about putting the entire widget inside a FittedBox?

I get overflow error on iPhone 12

What about putting the entire widget inside a FittedBox?
iPhone 12 looks okay

I get overflow error on iPhone 12

What about putting the entire widget inside a FittedBox?

Was able to reproduce to the issue in android by changing the display size to large. And fitted box works like magic. Thanks


Will there ever be a release?

Some of us write software for a living and we have a "definition of done" which won't be done if we are always running dependencies out of somebody's source code respository.
Will there be releases of keras-contrib?  Or can I just expect that I will always get the same thing when I check out of git because this project is abandoned?

I'm currently working on making this project come back to life. I am very confident that there will be releases in the future.

We'll upload to pypi and have a online documentation when we release the v1.0. You can track the progression with the milestone 1.0. I'll be closing this issue in the favor of the milestone. https://github.com/keras-team/keras-contrib/milestone/1
btw, help is welcome :)


Website redesign using Markdown & VitePress default theme

Formal PR to close #20
interesting reading on documentation design https://diataxis.fr/
PREVIEW IT HERE
These PRs should be merged first:

https://github.com/fontist/formulas/pull/174
https://github.com/fontist/fontist/pull/358

This PR would:

revamp the website to be an index site (with a blog tacked on)
have a dark mode
support syntax highlighting (in the blog)
REMOVE docs for https://github.com/fontist/fontist and expect them to be hosted via https://fontist.org/fontist/ via GitHub Pages from https://github.com/fontist/fontist

Advantages of VitePress over current Jekyll theme:

uses Markdown -- MUCH more popular (~83x more popular to be exact md vs adoc)
no layouts; using premade theme
syntax highlighting

Disadvantages of VitePress over current Jekyll theme:

might not match the bland plain look of other https://open.ribose.com/ stuff
built more for docs, less for blogs 🤷♂ (at least what's included by default; there are plugins/themes/scripts/etc)

Advantages of using in-repo GitHub Pages sites:

strong coupling of behaviour to docs (they're in the same repo VS in separate repos)
makes it wayyy easier too manage changes to the docs & code in one PR vs two prs on separate repos

Depending on whether or not you care about maintaining link-compatibility with the old site you could simplify things a bit more and get rid of all the files that are essentially just this (ripped from the Rollup.js website https://github.com/rollup/rollup/blob/master/docs/guide/en.md?plain=1)
Redirecting...

<script setup>
import { useRouter } from "vitepress";

if (typeof window !== "undefined") {
  const { go } = useRouter();
  go(`/guide/en/${location.hash}`);
  // OR
  location.replace("https://fontist.org/other-project/sub-page.html");
}
</script>

Depending on how much complexity you want, there are other fancier ways to do a VitePress blog to varying degrees of "bloggy-ness" (vs just page-ness)

(current) manually add entries to index page (ok for very small very sparse blogs like this one)
https://vitejs.dev/blog basic build script https://github.com/vitejs/vite/blob/main/docs/.vitepress/buildEnd.config.ts 👈 this is what I'd recommend if you realllllly want a bloggy blog
https://vitepressblog.dev/ complex theme

Given how sparse the current blog is I'd just rely on manual editing until/unless you really get blogging. Right now there is one post lol 😂
pssst! "Allow edits by maintainers" is checked; feel free to edit
open and edit in Codeflow (in browser Node.js IDE) https://pr.new/https://github.com/jcbhmr/fontist.github.io

Depending on whether or not you care about maintaining link-compatibility with the old site

No, we don't really care at this point...

@jcbhmr The PRs have been merged and now deployed! Thank you for the amazing work!


BaseOptimisticRebalanceAuctionModule for use with the BaseManager in existing products

coverage: 46.089% (-0.8%) from 46.877%
when pulling 8fc395a278a472d6f86cd87fe8611c4be1b78133 on ckoopmann/optimistic-auction-rebalance-extension
into d5ab03004853f068528a1962d9d0b025dd8ef0e5 on master.

LGTM 💯
We may want to peek the flaky optimism integration test

Seems to be an issue on alchemy side for the optimism rpc.
Let's keep an eye on it. Not much we can do about it though beyond considering an alternative rpc provider.


Add published paper

I found that the preprint link did not work, and figured it might be better to link to the published manuscript anyways.

Perfect, thank you!


Allow multiline input with custom lexer

This should be enough for quick multiline answers where possibly the editor question type is too much.

It looks like this:

It seems travis' failure isn't related to my branch.


Functionality to zip data from memory

The purpose of this change is to add functionality for zipping data
from memory rather than files. This removes the necessity to write a
generated data to disk before being able to archive, thus saving lots of
disk i/o.
The struct ArchiveFile represents the same data that is loaded from a
file.
The new method zipData allows an array of ArchiveFiles to be passed
rather than file URLs and are zipped accordingly. Other functionality
remains identical.

I like this idea, thanks for the suggestion @ryanmeasel


Update ALPACA.py

Fixed typos that prevent pointDensity parameters from being updated in the bath processing tab.
Also substituted pycpd for cpdalp, a modified version of pycpd containing the low_rank implementation of the cpd algorithm.

Fixed a few typos and update pycpd to match the paper. It uses the low rank implementation of cpd, which is faster and generally more accurate.


recreatePlatformViewController shouldn't create new metal contexts before use

We're making one metal context in recreatePlatformViewController in initWithName, one in a recreatePlatformViewController in FlutterEngine createShell and our normal metal context through createShell starting in https://github.com/flutter/engine/pull/22016. Looks like all 3 are persisted too. These things are expensive. We shouldn't need to create all 3 if platform views aren't being used.

Tentatively assigning to @iskakaushik. Feel free to re-assign. cc @gaaclarke

ah looks like this was refactored again in https://github.com/flutter/engine/pull/22353? Let me test again

woohoo, this is fixed on head


How to calculate the block size ?

One block can have multiple transactions. So i want to calculate the size of the block.
Is it possible ? Kindly guide me.
Thank you !!

I think it's a viable solution
		block ,err := ledgerClient.QueryBlock(uint64(0))
		if err != nil{
			fmt.Println(err)
		}
		buf := new (bytes.Buffer)
		err = protolator.DeepMarshalJSON(buf, block)
		fmt.Println(len(buf.Bytes()))

more detail you can refer https://github.com/iamlzw/fabric-sdk-go-samples/blob/master/setup.go queryLedger function.

Okay Thank you . I will check this.


RequestError: send request failed

If you have a bug report please let us know the following:

Operating system: OS X 10.10.5
Apex Version: 0.10.3

Hi ..
I am following instruction at https://apex.run/#getting-started
when I run apex deploy or apex invoke i got below error ..
Error: log "/aws/lambda/apex-lambda-suman_hello": RequestError: send request failed
caused by: Post https://logs.Oregon.amazonaws.com/: dial tcp: lookup logs.Oregon.amazonaws.com: no such host
When appropriate please also paste the debug log output using -ldebug or --log-level debug.

What value did you put in for your region? It looks like we don't validate those region values (not sure that we should) and that you put in Oregon as the region which isn't a valid region. Instead it should be us-west-2 for the region. You can find the valid regions here.

Thanks It worked

detailed solution ...
I updated region value to us-west-2  in ~/.aws/config and it worked (y)


Document That FloatOrd Implements Hash and Eq Too

Objective

Slight documentation tweak to make it more clear that FloatOrd also implements Hash and Eq, not just Ord.
I know that it does show that Hash is implemented in the docs, but I had missed it after reading the description and assuming it didn't do it, so hopefully this helps other people who might miss it like I did. :)

Solution

Just mention in the Hash and Eq implementation in the docstring.

There you go, pushed an update.

I updated the docstring again, and I think it satisfies the review comments.


AttributeError: 'ConfigDict' object has no attribute 'log_level'

Hello everyone! I have the mistake
File "tools/train.py", line 189, in
main()
File "tools/train.py", line 133, in main
logger = get_root_logger(log_file=log_file, log_level=cfg.log_level)
File "/opt/conda/envs/ssp/lib/python3.7/site-packages/mmcv/utils/config.py", line 507, in getattr
return getattr(self._cfg_dict, name)
File "/opt/conda/envs/ssp/lib/python3.7/site-packages/mmcv/utils/config.py", line 48, in getattr
raise ex
AttributeError: 'ConfigDict' object has no attribute 'log_level'
please help me!

Hello everyone! I have the mistake File "tools/train.py", line 189, in main() File "tools/train.py", line 133, in main logger = get_root_logger(log_file=log_file, log_level=cfg.log_level) File "/opt/conda/envs/ssp/lib/python3.7/site-packages/mmcv/utils/config.py", line 507, in getattr return getattr(self._cfg_dict, name) File "/opt/conda/envs/ssp/lib/python3.7/site-packages/mmcv/utils/config.py", line 48, in getattr raise ex AttributeError: 'ConfigDict' object has no attribute 'log_level' please help me!

It looks like the version of  mmdetection problems


fix: damping error

throwing dumping error in example

@Simek, it seems like a bug in React Native.
Using create() does not work, using objects work.
I created a new issue in the React Native Repo

Closing as duplicate of #2959.


Add disclaimer for memory cache when storing mutable objects

Memory backend with default serializer allows to store ANY python object. This is dangerous because you can do:
my_list = [1, 2, 3]
await cache.set(key, my_list)
print(await cache.get(key)) # will print [1, 2, 3]
my_list.append(4)
print(await cache.get(key)) # will print [1, 2, 3, 4]

We need to add a big disclaimer in the docs or do some kind of checking and only allow to store immutable objects?...

Instead of allowing this behavior, when storing/retrieving a copy should be done when the object is immutable.


No unsolicited status updates from Qubino Flush 1 Relays ZMNHAA

Is your problem within Home Assistant (Core or Z-Wave JS Integration)?
NO, my problem is NOT within Home Assistant or the ZWave JS integration
Is your problem within ZWaveJS2MQTT?
NO, my problem is NOT within ZWaveJS2MQTT
Checklist

[X] I have checked the troubleshooting section and my problem is not described there.

[X] I have read the changelog and my problem was not mentioned there.

Describe the bug
I’m not receiving any unsolicited updates from my Qubino Flush 1 Relays (ZMNHAA), no energy reports or status updates when manually operating a switch.
(Similar behaviour as in https://github.com/zwave-js/node-zwave-js/issues/2012)
Device information
Manufacturer: Qubino
Model name: Flush 1 Relay (ZMNHAA), Z-Wave chip firmware versions 1.12, Z-Wave protocol version 3.28
Node ID in your network: <3, 4, 7, 9, 10, 22, 24, 28, 29, 30, 41, 48, 49, 51, 58, 62, 67, 71>
How are you using node-zwave-js?

[ ] zwavejs2mqtt Docker image (latest)
[ ] zwavejs2mqtt Docker image (dev)
[ ] zwavejs2mqtt Docker manually built (please specify branches)
[ ] ioBroker.zwave2 adapter (please specify version)
[ ] HomeAssistant zwave_js integration  (please specify version)
[ ] pkg
[ ] node-red-contrib-zwave-js (please specify version, double click node to find out)
[ ] Manually built from GitHub (please specify branch)
[X] Other (please describe)

Which branches or versions?
Home Assistant Community Add-on: Z-Wave JS to MQTT ver. 0.28.0
(zwavejs2mqtt ver. 5.10.1, Z-wave JS ver. 8.6.1).
Did you change anything?
no
If yes, what did you change?
No response
Did this work before?
Yes (please describe)
If yes, where did it work?
Migrated from Fibaro Home Center 2 (where all Qubino devices worked just fine) to running Home Assistant on a NUC with an AEON Labs Gen5 USB Z‐Stick Controller.
Attach Driver Logfile
zwavejs_2021-11-05.log

Ok at least Node 3 seems to be contradicting itself:
2021-11-05T13:26:34.186Z CNTRLR « [Node 003] node info received
                                  supported CCs:
[...]
                                  · Association
[...]

and later:
2021-11-05T13:26:37.717Z DRIVER « [Node 003] [REQ] [ApplicationCommand]
                                  └─[VersionCCCommandClassReport]
                                      CC:      Association
                                      version: 0
2021-11-05T13:26:37.718Z CNTRLR   [Node 003]   does NOT support CC Association (0x85)

This means you're not getting a lifeline association automatically set up and therefore no automatic reporting. We can override that with a compat flag in the config file.

@Mr-Hell please try this config file: https://raw.githubusercontent.com/zwave-js/node-zwave-js/90b9e676c2a66bd76de381c9143386c106089d61/packages/config/config/devices/0x0159/zmnhaa.json
https://zwave-js.github.io/zwavejs2mqtt/#/device-support/custom-device-files describes how to test a custom device file.
After re-interviewing the lifeline association should be created automatically.

@Mr-Hell please try this config file: https://raw.githubusercontent.com/zwave-js/node-zwave-js/90b9e676c2a66bd76de381c9143386c106089d61/packages/config/config/devices/0x0159/zmnhaa.json
https://zwave-js.github.io/zwavejs2mqtt/#/device-support/custom-device-files describes how to test a custom device file.
After re-interviewing the lifeline association should be created automatically.

I tried adding the custom config file, but received this error:
2021-11-05T20:03:43.198Z DRIVER   loading configuration...
2021-11-05T20:03:43.204Z CONFIG   Using external configuration dir /data/db
2021-11-05T20:03:43.205Z CONFIG   version 8.6.1
2021-11-05T20:03:43.834Z CONFIG   Error parsing config file zmnhaa.json: Could not parse config file /data/store
/config/templates/master_template.json: ENOENT: no such file or directory, ope
n '/data/store/config/templates/master_template.json'
Import stack:
in #state_after_power_failure_prev_off
in /data/store/config/zmnhaa.json (ZW0340)
2021-11-05T20:03:43.871Z DRIVER   beginning interview...

Ahh damn.... Take this file and put it in a subdirectory templates in the same location as the test config.

Thanks, this worked a bit better, but the lifeline association was not created automatically when I re-interviewed a node.
However, it's now possible to manually add associations. Previously, there were no groups available to choose from when trying to add an association.
After I manually added the lifeline association, the binary sensor and energy meter seems to work correctly!

Ok can you share a log of the re-interview?

Yep, I re-interview nodes 28 & 3 + manually added the lifeline association, see attached log.
zwavejs_2021-11-06.log
I started doing the same to the rest of my ZMNHAA nodes, but now they seem to flood the network with energy reports...

Ok I think the auto-assignment didn't work because of a bug I fixed in 8.7.3
https://github.com/zwave-js/node-zwave-js/blob/master/CHANGELOG.md#873-2021-11-03
About the energy reports, that's usually an issue of device configuration (report intervals and thresholds that are set too low).

Ok, thanks. I will check this when I update ZwaveJS.
I've already adjusted the reporting thresholds for the energy reports. The values fluctuated so much that I had to increase the threshold substantially to avoid excessive reporting.
Many thanks for the quick resolution of my problem, you're doing a fantastic job! Keep up the good work!


Derivation for class with collection field

Trying to derive Show instance from test sources for a case class with List field ends up in compilation error.
In tests.scala
case class Attributes(a: String)
case class Entry(attributes: Attributes)
case class Response(entries: List[Entry])

test("construct a Show product instance") {
  val res = Show.derived[Response]
}

outputs:
[error] java.lang.AssertionError: assertion failed: <notype> class dotty.tools.dotc.ast.Trees$TypeTree -1

Oh no - that sounds like lampepfl/dotty#13406 - unfortunately I don't think anyone is working on it.

@joroKr21 Thanks for linking the issues - I've voted on it, if it makes any difference :)


Use posix-spawn instead of Kernel

The posix-spawn gem removes process forking overhead by using special
process spawning interfaces (posix_spawn(), vfork(), etc.).

This gem can keep your application's heap from being copied when
forking command line processes

Closing, since JRuby support prevents this from landing.
https://github.com/rtomayko/posix-spawn/pull/41#issuecomment-89401569


$_.Identity cause a failure on large accounts with users that have the same name

I had to modify the command as follows, using the Alias to ensure unique names
$mbx = Get-Mailbox -RecipientTypeDetails UserMailbox -ResultSize Unlimited
$mbx | foreach {Get-TextMessagingAccount -Identity $.Alias | where {($.NotificationPhoneNumberVerified -eq $true)} | Format-Table Identity,NotificationPhoneNumber}

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

ID: 786aa766-5ad7-082f-53bb-0b953224f412
Version Independent ID: 2cdcbfda-01b4-2859-14d2-268cd9cb51bd
Content: Get-TextMessagingAccount (exchange)
Content Source: exchange/exchange-ps/exchange/client-access/Get-TextMessagingAccount.md
Service: exchange-powershell
GitHub Login: @chrisda
Microsoft Alias: chrisda

@mwilliams7247 this issue was fixed in PR #3299, although the person used $.Identity instead of $.Alias. Both values require uniqueness. Did you find $.Identity didn't work?

It crashes on both actually which is odd as alias is unique

From: Chris Davis<EMAIL_ADDRESS>Sent: Monday, April 29, 2019 1:28 PM
To: MicrosoftDocs/office-docs-powershell
Cc: Michael Williams; Mention
Subject: Re: [MicrosoftDocs/office-docs-powershell] $_.Identity cause a failure on large accounts with users that have the same name (#3313)
@mwilliams7247https://github.com/mwilliams7247 this issue was fixed in PR #3299https://github.com/MicrosoftDocs/office-docs-powershell/pull/3299, although the person used $.Identity instead of $.Alias. Both values require uniqueness. Did you find $.Identity didn't work?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/office-docs-powershell/issues/3313#issuecomment-487670424, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AL6JVKYJ3EEJITWBMMPGR2DPS4V4FANCNFSM4HJDO3PQ.

@mwilliams7247, I changed the value from $.Identity to $.Alias.


Adding Snap package

This will allow Linux users, with snap package manager installed, to install helm with
snap install helm

This change is

LFCLA signed

Ooo... this is an interesting one! We don't currently have any policies about whether we can put config for external package managers in the repo. Does anyone object to this?

I'm all for this as long as @joedborg is the maintainer for the helm snap package. :)

Hey guys, thanks for the positive notes on this.
In terms of maintainence, it should be a change of "volume" and "source".  You can then register this repository at https://build.snapcraft.io and new releases will auto build.
I can take care of this if necessary but would be nice to see it taken over if possible.

Do we need to add some documentation into the docs/install.md to explain this?

@joedborg I think we are ok with adding this in so long as we have some documentation in docs/install.md to describe the new functionality. Is there any way you could add that in?

This appears to be located at snap/. Should we create a  community/packages or similar to hold artifacts like these?

@jascott1 I think @adamreese said he was going to go around and explain what we had decided to do with package management stuff in our developer meeting

hey @thomastaylor312, yes I can add that in.  Just FYI, the "upstream" version is here (for now) https://github.com/snapcrafters/helm

So as far as I remember what we discussed in the developer call, we were not going to move forward with hosting "package-manager-specific" code in Helm core. We cannot keep up with the maintenance of an endlessly sprawling number of ways to install Helm. However, third party package managers are more than welcome to create repositories at kubernetes-helm as part of the community shift.
I still think @adamreese had more opinions on this topic, but from memory I recall the story moving forward would be:
a) The community will be responsible for supporting the infrastructure of their own package manager
b) Helm Core Maintainers can create repositories at https://github.com/kubernetes-helm for hosting these package manager-specific code repositories (upon request/approval)
c) We will continue to release Helm as necessary, circling in package manager maintainers into upcoming Helm releases through the roadmap, emails, weekly Helm dev calls etc.
The TL;DR is that it's up to the community to maintain these third party packages. We will continue to distribute releases through our usual release process, but alternative installation methods are up to the community to support.

Hey @bacongobbler thanks for the feedback!  Just a couple of questions based on them.

I think the community is more than happy to maintain these (as has been done in this case).  However, I believe it's l better from upstream for 2 reasons. First is that all the docs etc point to the right place.  Second is that cadence of release is matched with the package manager.  I do completely understand that this is more work for you guys though.

I've just pushed the latest helm version to snap, so if anyone fancies trying to break it, please feel free to sudo snap install helm

I do completely understand that this is more work for you guys though.

At the end of the day, this is the core reason why we're deciding against merging this. We don't have the time to maintain all the things we don't use.
You are more than welcome to host it at the kubernetes-helm org and get some snap users to support the snap package for Helm. Feel free to reach out during one the weekly dev calls if you want to get help with setting that repo up, and perhaps see if you can round up some users in the #kubernetes-helm channel in Slack to take over maintenance.
Thanks!


RO-Crate Provenance from Snakemake

Capture workflow run crate provenance from Snakemake workflows similar to existing CWL.  Note that WfExS already is doing something similar (but to figure out workflow structure)

Now tracked in https://github.com/eScienceLab/RO-Crate_Issues/issues/7

Decided on writing a snakemake plugin to do this. Discussions are ongoing on the fine details. Going to loop in the Snakemake developers during August to get help from them on how to get information out of the relevant snakemake objects.


support for pdf format output

Fix #282.
@dwertent, remember to enable printer/v2 to test the functionality.

@alegrey91 Great job!


Durring installation process script is trying to access http://360/drive_c/users/mkulik05/Downloads

After mkdir -p "$HOME/.config/fusion-360/bin" && cd "$HOME/.config/fusion-360/bin" && wget -N https://raw.githubusercontent.com/cryinkfly/Autodesk-Fusion-360-for-Linux/main/files/builds/stable-branch/bin/install.sh && chmod +x install.sh && bash install.sh && exit installation started, but after a while it freezed with this error

Desktop :

nvidea videocard and build-in amd ryzen
Operating system - manjaro
Desktop environment - kde
DXVK Mode

How to fix it?

Usual restart helped

Nope, swithing to openGL helped


Error Component formValue not equal to current form

Hello,
I am trying to have errors from the Error component show on a failed submit.  I am doing this like so:
    <Errors
        model='forms.signup.username'
        show={(field, form) => (field.touched || form.submitFailed)}
        component={(props) => {props.children}}
        messages={{
            required: 'This field is required'
        }}
    />

The formValue is in the props of the error component here - https://github.com/davidkpiano/react-redux-form/blob/c5be6cd8fd50506bd1d517f516398e91d31e71db/src/components/errors-component.js#L165
and passed into the show function prop of the error component - https://github.com/davidkpiano/react-redux-form/blob/c5be6cd8fd50506bd1d517f516398e91d31e71db/src/components/errors-component.js#L19
But the form variable passed into the show function is not the form state of the model in question "signup" in my example, but is a generic form with model="forms" rather than the expected model="forms.signup".
I feel this could be because there is an error in the get-form.js getFormStateKey function - https://github.com/davidkpiano/react-redux-form/blob/01d9a40add10978feaa03985803185b4ff37a5c0/src/utils/get-form.js#L11
Or it could just be something wrong with my state? My forms are declared in my rootReducer like so:
    export const rootReducer = combineReducers({
        user: user,
        forms: combineForms({
            user: {},
            signup: {
                username: "",
                email: "",
                password: "",
                passwordConfirmation: ""
            }
       }, 'forms')`

Something that I also found puzzling that may or may not be related to this issue is that I originally discovered it because I noticed that while each field on a model e.g. 'forms.signup.username' has the submitFailed attribute in the state, it is never updated to True, even when the submit has failed and the 'forms.signup' state object submitFailed attribute is True.

But the form variable passed into the show function is not the form state of the model in question "signup" in my example, but is a generic form with model="forms" rather than the expected model="forms.signup".

@KevinBrolly This is probably be fixed with #455. When I release a patch soon, can you verify?

Something that I also found puzzling that may or may not be related to this issue is that I originally discovered it because I noticed that while each field on a model e.g. 'forms.signup.username' has the submitFailed attribute in the state, it is never updated to True, even when the submit has failed and the 'forms.signup' state object submitFailed attribute is True.

I noticed this as well in 1.0.8; when validating a form on submit and the validation fails, the submitFailed value at the $form level is set to true, but the fields themselves remain false. @davidkpiano, would you expect the fix you mention to fix this as well?

@davidkpiano 1.0.9 does indeed fix the main issue, the show function now has access to the correct form.
I noticed that other fields as I mentioned, such as 'forms.signup.username' still do not have form values such as "submitFailed" correctly set (which is why I had to access the form in the show function in the first place.  How can I get the fields to contain the correct value for "submitFailed"?

How can I get the fields to contain the correct value for "submitFailed"?

Would you mind filing a separate issue for this, for tracking purposes? This is a bug that I can quickly fix.


[hotfix] populate fangorn renaming folder fix [OSF-7151]

Purpose
Fangorn doesn't auto populate rename text due to an earlier bug.

Changes
This fixes that and how folder creation naming works, since the previous version broke that.

Side effects
None known

Ticket
[#OSF-7151]
https://openscience.atlassian.net/browse/OSF-7151

QA Notes
Check that all fangorn inputs work properly (filter, rename, folder create)
Check that renaming works
Check that there were no regressions (] and " ' all work, etc)
Also check for regressions of the last letter disappearing bug on mouse out

Passed on my osf branch, failed on a random test on varnish here.

@alexschiller Could you rebase on develop, please?


HTTPAltValidator not triggered with multiple concurrent calls

Bug Report
This bug affect both the 0.9.x (pre-releases) and the new 1.0.0.
The bug avoid HTTPAltValidator to be triggered when multiple concurrent calls are calling the same validator. This happens because numberOfAltRequestExecuted is incremented even when no alt-request is triggered so it reach very fast the limit (maxAltRequestsToExecute).
This check should be moved right before returning the alt call.
open func validate(response: HTTPRawResponse, forRequest request: HTTPRequestProtocol) -> HTTPResponseValidatorResult {
        if let statusCode = response.error?.statusCode, triggerHTTPCodes.contains(statusCode) {
            return .passed
        }

        // If error is one of the errors in `triggerHTTPCodes`

        // If we reached the maximum number of alternate calls to execute we want to cancel any other attempt.
        if let maxAltRequestsToExecute = maxAltRequestsToExecute,
              numberOfAltRequestExecuted > maxAltRequestsToExecute {
            let error = HTTPError(.maxRetryAttemptsReached)
            return .failWithError(error)
        }

        guard let altOperation = requestProvider(request, response) else {
            return .passed // if no retry operation is provided we'll skip and mark the validation as passed
        }

        numberOfAltRequestExecuted += 1
        return .retryAfter(altOperation)
    }

Q
A

BC Break
yes

Version
0.9.x and 1.0.x

fixed in 0.9.18 - pre-release


Add SQL Data Warehouse DR Guidance

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/resiliency/disaster-recovery-azure-applications.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/checklist/resiliency-per-service.md
:white_check_mark:Succeeded
View

docs/resiliency/disaster-recovery-azure-applications.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

#Sign-off

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/mspnp/architecture-center, working directory: W:\i0ag-s, target branch: master, target branch commit: 46ed67297e6247f9a80027cfe891a5e51ee024b4, source branch: ccdea6f88aa487daaafe4a89f6c7c110/patch-1, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/checklist/resiliency-per-service.md
:white_check_mark:Succeeded
View

docs/resiliency/disaster-recovery-azure-applications.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/checklist/resiliency-per-service.md
:white_check_mark:Succeeded
View

docs/resiliency/disaster-recovery-azure-applications.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


add cheat sheet for v0.4 release

[ ] release a 1-page pdf cheat sheet
[ ] add it into the doc
[ ] create an issue to track the questions

need to add it into v0.4 release milestone


Upgrade @actions/core to v1.2.6 or higher

Actions lower than 1.2.6 are vulnerable to a moderate security exploit. The current add-path command has been disabled by GitHub.
See https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/

@adambkaplan Fixed in v1.1.3. You can keep using v1 tag.

@adambkaplan Fixed in v1.1.3. You can keep using v1 tag.


Refactor: unify task script

we're using makefile、js scritps、shell、xtask to manual tasks and it's kind of messy and cause confusions for outside contributors, so we should unify all the task scripts.
there are some requirements for task scripts:

cross platform compatible
easy to maintain
easy to debug

there are some options now:

https://github.com/google/zx
npm scripts
js scripts
shell

Rome uses https://github.com/casey/just.
This looks kind of nice: https://github.com/rome/tools/blob/main/justfile

Hi,
For the calls to './x' would it make sense to replace them by 'node x' or it causes trouble ?
I can open a PR for it if it makes sense to you

Hi,
For the calls to './x' would it make sense to replace them by 'node x' or it causes trouble ? I can open a PR for it if it makes sense to you

We are going to remove ./x soon/next week, which causes many cross-platform problems and so on. We would switch to npm scripts + zx to have consistent experiences for any platform.

Hi,
For the calls to './x' would it make sense to replace them by 'node x' or it causes trouble ? I can open a PR for it if it makes sense to you

Thanks for bringing this up. We are going to remove ./x soon/next week, which causes many cross-platform problems and so on. We would switch to npm scripts + zx to have consistent experiences for any platform.

Super 👌
Thanks

Sync up:
The Rspack team has met many problems with the current workflows.
After some discussions, the team had to decide to use zx and npm scripts to unity current scripts(runner).

Closed by

https://github.com/web-infra-dev/rspack/pull/2754
https://github.com/web-infra-dev/rspack/pull/2840
https://github.com/web-infra-dev/rspack/pull/2756


Enable NRF51822

/morph build

/morph build

/morph test

/morph build

/morph test

/morph test

/morph test

/morph test

Result: SUCCESS
Build number : 49
Build artifacts/logs :http://mbed-os-logs.s3-website-us-west-1.amazonaws.com/?prefix=logs/7/49

/morph test

/morph test

Result: SUCCESS
Build number : 58
Build artifacts/logs :http://mbed-os-logs.s3-website-eu-west-1.amazonaws.com/?prefix=builds/7/58

/morph test

Result: SUCCESS
Build number : 59
Build artifacts/logs :http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/7/59

Build : PENDING
Build number : 4
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/7/

Build : SUCCESS
Build number : 3
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/7/
Triggering tests
/test mbed-os-fork-ci

/morph test

Build : SUCCESS
Build number : 431
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/7/
Triggering tests
/morph test
/morph uvisor-test

/morph test

Build : SUCCESS
Build number : 431
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/7/
Triggering tests
/morph test
/morph uvisor-test

/morph test

Build : SUCCESS
Build number : 431
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/7/
Triggering tests
/morph test
/morph uvisor-test

/morph test

Build : SUCCESS
Build number : 431
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/7/
Triggering tests
/morph test
/morph uvisor-test

/morph test

Build : SUCCESS
Build number : 431
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/7/
Triggering tests
/morph test
/morph uvisor-test


Implement firebase google login #2

Closing due to not the proper way of PR on the specific issue 🤦♂


Expected
command works well
Environment Information

OS: ubuntu
Vim version: latest(neovim)

Provide a minimal .vimrc with less than 50 lines (Required!)
" Your minimal .vimrc
set runtimepath^=~/path/to/dein.nvim/
call dein#begin(path)
call dein#add('Shougo/vimfiler.vim',{'lazy' : 1 , 'on_cmd' : 'VimFiler'})
    noremap <silent> <F3> :VimFiler<CR>
call dein#end()

The reproduce ways from Vim starting (Required!)

star vim
type  twice
baz

Screen shot (if possible)
Upload the log messages by :redir and :message

Fixed by call dein#update() ,I think it is due to I change the plugin to lazy,but do not delet it from ~/cache/.dein/

@wsdjeg This seems to work for me just temporally. I'm a bit confused about using depends, cause it seems not to work, but if I call call dein#recache_runtimepath() manually it works for that session. But I guess this is a fault of my configuration. Be sure I will get it one day.


Fix handler if message with document

When user sent message with attached file, handler check only text field. But when file attached, text field replaced by caption.

Thank @ArthurPatriot! We are releasing this patch right now 🚀


Rename this repo to mapbox-gl-draw

Draw prefixed just with gl is too generic and doesn't really make sense.
cc @kelvinabrokwa

@tristen I can dig it


added business day functionality

Per feature request #568, I added a business day functionality (BDay) that allows user to add and subtract business days from dates.
Closes: #568

Codecov Report

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

@@          Coverage Diff          @@
##           master   #577   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          13     13
  Lines        3399   3465   +66
  Branches      238    250   +12
=====================================
+ Hits         3399   3465   +66

Impacted Files
Coverage Δ

tests/arrow_tests.py
100% <100%> (ø)
:arrow_up:

arrow/arrow.py
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


vscode-extensons.github.github-vscode-theme: 1.1.5 -> 3.0.0

Motivation for this change
Bumping the Github theme extension to the latest version:
https://github.com/primer/github-vscode-theme/releases/tag/v3.0.0
Things done

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

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

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

Result of nixpkgs-review run on x86_64-linux 1

1 package built:

vscode-extensions.github.github-vscode-theme

Result of nixpkgs-review pr 119342 at 6280bc5c run on x86_64-linux 1

1 package built successfully:

vscode-extensions.github.github-vscode-theme

3 suggestions:

warning: missing-phase-hooks
configurePhase should probably contain runHook preConfigure and runHook postConfigure.
Near pkgs/misc/vscode-extensions/vscode-utils.nix:21:12:
   |
21 |     inherit configurePhase buildPhase dontPatchELF dontStrip;
   |            ^

warning: missing-phase-hooks
buildPhase should probably contain runHook preBuild and runHook postBuild.
Near pkgs/misc/vscode-extensions/vscode-utils.nix:21:12:
   |
21 |     inherit configurePhase buildPhase dontPatchELF dontStrip;
   |            ^

warning: build-tools-in-build-inputs
unzip is a build tool so it likely goes to nativeBuildInputs, not buildInputs.
Near pkgs/misc/vscode-extensions/vscode-utils.nix:25:5:
   |
25 |     buildInputs = [ unzip ] ++ buildInputs;
   |     ^

Thanks for the fixes Sandro, and for the merge :+1:


IWW Issue #53, May 31st 👓 2021

This pull request is for gathering links for the May 31st issue of the Immersive Web Weekly newsletter for the W3C Immersive Web Community Group.
If you have a link to a news article, event, artwork, or project that is directly related to the immersive web then we welcome your help!
To submit a link comment below using this template:
title: Example title of link
url: https://example.com/
author: Alice Smith
content: A short description of what is at the link and why it's related to the immersive web

Please keep in mind that comments here and all submitted links are public!
We keep each issue pretty short so we won't immediately use every submission but we keep track of them all and they may appear in a later issue.
Deadline
IWW goes out each Tuesday morning around 10am Pacific time.
Trevor will edit each issue on the Monday before publication so submissions after that will roll over for use in future issues.
If you need editorial support then email @TrevorFSmith<EMAIL_ADDRESS>

title: Blockbench
url: https://blockbench.net/


Disable SELFDESTRUCT for feature scroll

Description

Add feature scroll to eth-types, and update both bus-mapping and zkevm-circuits scroll features to depend on it.

Fix OpcodeId conversion functions (both from u8 and FromStr to OpcodeId) to convert SELFDESTRUCT to OpcodeId::INVALID(0xff) when scroll feature is enabled.

Delete selfdestruct gadget for scroll feature in zkevm-circuits.

Add a test case invalid_opcode_selfdestruct_for_scroll.

Issue Link
Related issue https://github.com/scroll-tech/zkevm-circuits/issues/448

oh i realized we need also use if feature = scroll to update self destruct related codes inside circuit part / witness/step.rs.   If feature = scroll, the DummyGadget itself should exist.

It appears I still have almost everything to learn about this crypto coding. Or maybe I should just stick to trading.


Highlighting in multiple choice menus is in black

This is a problem, because the text is also in black...
I tried two styles, which both had the same issue, but it could be caused by something other than ozone-wayland?

On X11, the highlight in multiple choice menus is blue.

This could be due to some hardcoded internal style choices here: https://github.com/01org/ozone-wayland/blob/master/ui/webui/ozone_webui.cc, we choose black for fg, bg etc. Need to add proper support like with x11 variant.

Here is a patch: https://github.com/01org/ozone-wayland/pull/408

@joone, @kalyankondapally: Is this fixed now?

Yes, should be.


How to validation the model?

Dear author, I test your model on subset of fer2013. But I have a question. Since you used fer+ label in your work, how can I validation the model? I use origin label of fer2013, it seems not good. Thanks!

Dear Angel113110,
Thank you for contacting me.
The model uploaded to this repository was trained on AffectNet. Therefore, in order to achieve high accuracy on FER2013, you must retrain each convolutional branch as explained in our paper (https://arxiv.org/abs/2001.06338).
The training procedure is not complicated. You can use main_fer_plus.py as a template. Note that you should remove one neuron from the last layer of ESR-9 since FER has one less category than FER+, as explained later.
There are a few concerns regarding FER2013. I suggest reading the FER+ paper (https://arxiv.org/abs/1608.01041) by the Microsoft research group to check the problems with the original labels and the differences between FER2013 and FER2013+. For instance, FER+ added the contempt category to the dataset. Another problem is the noisy labels in FER as illustrated in the following Figure (FER top and FER+ bottom) from FER+'s repository (https://github.com/microsoft/FERPlus).

Best,
Henrique Siqueira
P.S. I could upload the trained model on FER+ for valuation but the University is currently closed due to COVID-19. Thus, I do not have access to the computer where the model was trained.


Eh customize

@ehdieunguyen Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

@ehdieunguyen Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.


Scream stream mixer+router, python receiver

Hey, I wanted to share some things I've created that use Scream.
The first is ScreamRouter, this is a multi-source multi-sink system for controlling where your audio goes, as well as equalization and volume. It uses ffmpeg for mixing and equalization. It sends audio back out as either normal Scream streams or as an HTTP MP3 stream. Unix-like only.
https://github.com/netham45/screamrouter
The second is a basic Python Scream receiver. It's largely untested so far but functional for stereo.
https://github.com/netham45/pyscreamreader

https://github.com/netham45/screamsender
This takes PCM stream in over stdin and puts a Scream header on it

https://github.com/netham45/esp32-audiokit-screamreader/
This takes a 16-bit 48kHz stream and plays it out of an esp32 a1s audiokit.

https://github.com/netham45/esp32-scream-receiver
esp32/esp32s toslink/usb audio host
https://github.com/netham45/windows-scream-receiver/
Windows receiver that does multichannel/remixing channels
https://github.com/netham45/windows-scream-sender
Usermode Scream sender for Windows

https://github.com/netham45/esp32s-usb-scream-sender
esp32s3 usb sound card to send scream


Phantom Process died

I have met a problem:
Unhandled rejection HeadlessError: Phantom Process died
    at ClientRequest.<anonymous> (/Users/zhuyingda/nodejs/veneno/node_modules/node-phantom-simple/node-phantom-simple.js:655:12)
    at emitOne (events.js:77:13)
    at ClientRequest.emit (events.js:169:7)
    at Socket.socketOnEnd (_http_client.js:288:9)
    at emitNone (events.js:72:20)
    at Socket.emit (events.js:166:7)
    at endReadableNT (_stream_readable.js:905:12)
    at doNTCallback2 (node.js:441:9)
    at process._tickCallback (node.js:355:17)

I just run this code:
var Horseman = require('node-horseman');
var horseman = new Horseman();
horseman
    .userAgent("Mozilla/5.2 (Windows NT 6.1; WOW64; rv:27.0) Gecko/20100101 Firefox/27.0")
    .on('resourceRequested', function (requestData, networkRequest) {
        if(!/[png|jpg|js|css]$/.test(requestData.url)){
            console.log(requestData.url);
        }
    })
    .open('http://www.zhuyingda.com')
    .log() // prints out the number of results
    .close();

I am sure that my network is fine and I can connect this website in my browser.
If I open charles or other vpn program, the problem would be fixed.  I wanna know why?

I don't quite follow. Are you say that if you run that code while VPNed it works, but if you run that same code while not VPNed it gives the above error?

yeah, I have this problem

+1 to this error on Windows 7 using example

var Horseman = require('node-horseman');
var horseman = new Horseman();

horseman
  .open('http://www.google.com')
  .type('input[name="q"]', 'github')
  .click("button:contains('Google Search')")
  .waitForNextPage()
  .count("li.g")
  .then(function(numLinks){
	console.log("Number of links: " +numLinks);
	horseman.close();
  });

@zhuyingda  The solution mentioned here worked for me: https://github.com/johntitus/node-horseman/issues/70
var Horseman = require('node-horseman');

var phantomjs = require('phantomjs');

var horseman = new Horseman({phantomPath: phantomjs.path});

horseman
  .open('http://www.google.com')
  .type('input[name="q"]', 'github')
  .click("button:contains('Google Search')")
  .waitForNextPage()
  .count("li.g")
  .then(function(numLinks){
	console.log("Number of links: " +numLinks);
	horseman.close();
  });

Yeah @0x1mason, horseman does not always find PhantomJS when it is installed by the phantomjs npm module, as mentioned in #101.

Any solution?
Unhandled rejection HeadlessError: Phantom Process died
    at ClientRequest.<anonymous> (/srv/node_modules/node-horseman/node_modules/node-phantom-simple/node-phantom-simple.js:659:12)
    at ClientRequest.emit (events.js:107:17)
    at Socket.socketErrorListener (_http_client.js:271:9)
    at Socket.emit (events.js:107:17)
    at net.js:459:14
    at process._tickDomainCallback (node.js:381:11)
From previous event:
    at null.<anonymous> (/srv/node_modules/node-horseman/lib/actions.js:51:10)
From previous event:
    at exports.open (/srv/node_modules/node-horseman/lib/actions.js:50:20)
    at null.<anonymous> (/srv/node_modules/node-horseman/lib/index.js:166:22)
    at processImmediate [as _immediateCallback] (timers.js:367:17)
From previous event:
    at Promise.HorsemanPromise.(anonymous function) [as open] (/srv/node_modules/node-horseman/lib/index.js:164:15)
    at Object.exports.data.getBank (/srv/monitoringData/csgoup.js:15:5)
    at /srv/monitoring.js:27:8
    at /srv/node_modules/async/lib/async.js:181:20
    at Object.async.forEachOf.async.eachOf (/srv/node_modules/async/lib/async.js:233:13)
    at Object.async.forEach.async.each (/srv/node_modules/async/lib/async.js:209:22)
    at startMonitoring (/srv/monitoring.js:26:8)
    at null._onTimeout (/srv/monitoring.js:36:4)
    at Timer.listOnTimeout (timers.js:119:15)

@Yashko can you provide an example that causes this error?

this code run every ~10 seconds. first 4-5 hours before working okay, but then this error. is there way to catch this so i can reload script?
horseman
			.userAgent("Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.75 Safari/537.36")
			.open(this.url)
			.on('consoleMessage', function( msg ){
				horseman
					.waitForSelector(selector)
					.text(selector)
					.then(function(text) {
						var bank = bankFormat(text);
						callback(bank);
					});
			})

Can't you just add  a .catch to the chain to handle the rejection @Yashko?

sorry, i cant find how to do that.
horseman
			.userAgent("Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.75 Safari/537.36")
			.open(this.url)
			.catch(function(e) {
				console.log("horseman error: "+e);
			})

like this?

Yes like that.

So after trying all the fixes listed above and testing several horseman functions I've been able to resolve this issue by removing all calls to horseman.close() from my code. Not sure what the implications of doing this would be if my app was running for a long time (memory leaks, etc).
Hopefully this helps shed some light on what's happening here.

It sounds like you were calling .close too early @ultratoast. Unfortunately the Phantom Process died message can be cause by many things (including misuse or potential bugs).

Yeah I had a feeling that might be the case, but it wasn't clear given the documentation. Do I not call horseman.close() after completing all actions via horseman? For example in my sequence where i fetch some data via AJAX:
horseman   .userAgent(agent)   .open('https://twitter.com/login?redirect=something')   .value(login DOM stuff)   .value(login DOM stuff)   .click(submit DOM stuff)   .waitForNextPage()   .evaluate(function(endpoint){     function getData() {       $.ajax({          url: endpoint       }).done(function(data){          window.alert(data)       })     }     return getData()   },endpoint)   .on('alert',function(data) {       return data   })   .then(function(data){     //do stuff with json   }) .catch(function(e){   console.log('horseman error: '+e)  }) .close()

It's kind of hard to tell since the formatting of your code is broken, but you can't return getData() inside of evaluate. getData is async, and isn't returning until after you've already closed horseman.
Instead of .evalute, use .do()
https://github.com/johntitus/node-horseman#dofn

The trouble is I need to execute that async call from within the phantomjs session. Do() is not giving me access to ajax functions - would I need then to load it (or some other request library) manually?

I see now.
@awlayton looks like we need to implement evaluateAsync. However it looks like it returns immediately, so we'd need some kind of wrapper around it, which would be a pain...
http://phantomjs.org/api/webpage/method/evaluate-async.html

I actually got my code working, my issue was that I needed to create a new instance of Horseman inside my function, and then close it at the end.
If anyone is looking for a quick fix for async calls, the following worked for us (apologies for my formatting skillls):
function pageScraper(){
let horseman = new Horseman()
horseman
.userAgent(agent)
.open(url)
//Do some DOM stuff
.waitForNextPage()
.evaluate(function(endpoint){
function getData(){
$.ajax({
url: endpoint,
async: false
}).done(function(data){
var json = JSON.stringify(data) || 'No Data';
$('').val(json).appendTo('body');
})
}
return getData()
},endpoint)
.waitForSelector('#json')
.value('#json')
.then(function(data){
// do stuff with the data,
//I have some async fs stuff happening here, at the very end i call this.close()
})
.catch(function(e){
console.log("horseman error: "+e)
this.close()
})
}

Yeah @ultratoast and @johntitus the .close was used correctly, but nothing was waiting for the async started in the .evaluate. That lead to the .close being "too early".
As for .evaluateAsync, the returning immediately makes it not that useful. I have actually already enhanced horseman's .evaluate in v3 to handle async (either callback or a Promise). See the Readme in v3 for details and examples.

I am fine with adding .evaluateAsync to horseman if you think we should @johntitus. I could also switch my async waiting stuff to be a part of that and make .evaluate only sync again. I don't have a terribly strong opinion either way.

Just took at look at .evaluate in v3 and I think what you've already done is the right way to go.

If the issue is still present in v3, you can reopen this @zhuyingda.

There's some sort of race condition w/ node-phantom-simple on Windows. I've found found the following pattern to be very robust:
var phantomjs = require('phantomjs-prebuilt'),
      Horseman = require('node-horseman'),
      Promise = require('bluebird');

var MAX_RETRIES = 15;

var startHorseman = function (i) {
   i = i || 0;
   var e = null;

   return Promise.try(function () {
      console.log('starting');
      return new Horseman({
         phantomPath: phantomjs.path
      });
   })

   .catch(function (err) {
      e = err;
   })

   .then(function (h) {
      return Promise.delay(2000).then(function () {
         if (!e && h) {
             console.log('returning');
             return Promise.resolve(h);
         }

         if (i < MAX_RETRIES) {
            console.log('retrying');
            e = null;
            return startHorseman(++i);
         }

         return Promise.reject(new Error('Failed to start PhantomJS.'));
      });
   })
}

var horseman = startHorseman();

// do stuff

horseman
.close()
.catch(function(e) {
   console.warn("Error closing PhantomJS: " + e);
   console.warn(e.stack);
})

Could be cleaner, but you get the gist.

What are you claiming is wrong @0x1mason? Are you getting an error?
When I run your code I get an error from horseman.close(), but that is because your horseman variable is a Promise and not a Horseman instance. Everything else does what I would expect.

There appears to be a race condition that produces the headless errors. I
posted my snippet if anyone else has an issue since it resolved the issue
for me.
On Apr 21, 2016 11:14 AM, "Alex Layton"<EMAIL_ADDRESS>wrote:

What are you claiming is wrong @0x1mason https://github.com/0x1mason?
Are you getting an error?
When I run your code I get an error from horseman.close(), but that is
because your horseman variable is a Promise and not a Horseman instance.
Everything else does what I would expect.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/johntitus/node-horseman/issues/111#issuecomment-212966075

Which is to say, nothing's wrong really :) sorry if I was unclear.
On Apr 21, 2016 11:14 AM, "Alex Layton"<EMAIL_ADDRESS>wrote:

What are you claiming is wrong @0x1mason https://github.com/0x1mason?
Are you getting an error?
When I run your code I get an error from horseman.close(), but that is
because your horseman variable is a Promise and not a Horseman instance.
Everything else does what I would expect.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/johntitus/node-horseman/issues/111#issuecomment-212966075

I was having the exact problem since 11:00h. It is 17:00h now my time.
It turns out @ultratoast was right and saved my day. I just removed all calls to close() and it suddenly worked. What I'm doing now is that I'm sharing a single Horseman instance and closing it at the end.


How to extend Dynamics 365 Finance trial

Would it be possible to extend Dynamics 365 Finance trial?

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

ID: 3be02eb7-47ec-11ee-6170-8e35f653eb32
Version Independent ID: d493e3d3-a003-f681-9cb1-7f80aea9be37
Content: Before you buy - Finance & Operations | Dynamics 365
Content Source: articles/fin-ops-core/fin-ops/get-started/before-you-buy.md
Service: dynamics-365-cross-app
Product: ****
Technology: ****
GitHub Login: @sericks007
Microsoft Alias: sericks

Bug 759629 has been logged to address this issue.

@twheeloc, can you take a look at this one, please?  Thanks!

@rojedai, thanks for contacting us. Unfortunately, we're unable to handle Support requests for the product here. To contact Support, consider one of the options described here: Support contact options. In particular, you might want to go to the Dynamics 365 community page to get help with your questions from the Dynamics community.


Start streaming API  failing in secure mode

🐞 Bug Report
Affected Services [REQUIRED]

 The issue is located in: Device usb service
Is this a regression?

 No
Description and Minimal Reproduction [REQUIRED]
USB Start streaming API tried to start streaming and then stops immediately in secure mode. Issue observed on Logitech C270 camera. Issue is not reproducible in non-secure mode.
Repro steps:

Deploy the edgex stack and usb service in secure mode with latest code from main branch
Verify basic rest-api like getting camera info and camera streaming status works correctly on connected USB camera.
Execute start streaming rest-api with valid input &output settings (see attached screenshot)
Execute stream status api to verify streaming status.

Expected behavior:
Start streaming starts video streaming and continue streaming until user stops or disconnects camera.
Streaming status api shows 'is streaming' set to true.
Actuak behavior:
Streaming starts for moment and stops immediately. Observed green light coming and going after executing start streaming api.
Streaming status api shows 'is streaming' set to false.
🔥 Exception or Error

Find attached logs
start_streaming_failing_usb_secure_mode.txt

🌍  Your Environment
Deployment Environment:
EdgeX Version [REQUIRED]:
3.0/latest main
Anything else relevant?

This is due to https://github.com/edgexfoundry/edgex-go/issues/4565

Fixed via https://github.com/edgexfoundry/edgex-compose/pull/378

Validation  looks good in secure mode.


tests: efinix: mux16 case in mux.ys fails due to wrong number of LUT4 on macOS

Environment:

macOS Sierra (10.12.6)
clang (8.1.0)
iverilog (7f95abc)
Yosys (7dece795)

Yosys built using official instructions from Readme.
Test run on macOS:
cd tests/arch/efinix
bash run_test.sh

Error log:
Running mux.ys..
ERROR: Assertion failed: selection contains 11 elements instead of the asserted 12: t:EFX_LUT4
Selection contains:
mux16/$abc$653$auto$blifparse.cc:498:parse_blif$654
mux16/$abc$653$auto$blifparse.cc:498:parse_blif$655
mux16/$abc$653$auto$blifparse.cc:498:parse_blif$656
mux16/$abc$653$auto$blifparse.cc:498:parse_blif$657
mux16/$abc$653$auto$blifparse.cc:498:parse_blif$658
mux16/$abc$653$auto$blifparse.cc:498:parse_blif$659
mux16/$abc$653$auto$blifparse.cc:498:parse_blif$660
mux16/$abc$653$auto$blifparse.cc:498:parse_blif$661
mux16/$abc$653$auto$blifparse.cc:498:parse_blif$662
mux16/$abc$653$auto$blifparse.cc:498:parse_blif$663
mux16/$abc$653$auto$blifparse.cc:498:parse_blif$664
make: *** [run-mux.ys] Error 1

I also ran the test on Linux and the error did not occur.
In attached blif files you can see that indeed there is a difference in number of LUTs.
blif_files.zip

Thank you for reporting this issue. Was able to reproduce it on macOS machine.

Just in case it gets lost, there was some discussion in https://github.com/YosysHQ/yosys/pull/1559#issuecomment-565581875 on the root cause:

After much debugging with @mmicko it turns out the destruction order of STL containers in macOS is different to gcc/clang/VS: apple/foundationdb#1862
Thus containers with IdString's in are destructed in a different order on macOS, and thus get recycled in a different order. And when other containers sort on the IdString index, we then get inconsistent behaviour.
~Is there any good reason why we should be recycling 32b indices in the first place?~
EDIT: I think the reason is that they are used to index into a std::vector...
https://github.com/YosysHQ/yosys/blob/9ab1feeaf11adb6b675ac4034e246cb137d07db9/kernel/rtlil.h#L82
Alternatives include sorting the recycle list (at some cost, and even then recycling only happens at a checkpoint() which is only called at the end of every pass):
https://github.com/YosysHQ/yosys/blob/9ab1feeaf11adb6b675ac4034e246cb137d07db9/kernel/rtlil.h#L80


Linkbucks not working

Linkbucks not working :(

This is a known issue. LinkBucks has some very challenging obfuscation techniques.


Apps Script Quickstart Google Sheet is not shared publicly

Expected Behavior
On this URL, on Step 1, a sample spreadsheet is linked, but the spreadsheet is not publicly accessible. https://developers.google.com/apps-script/quickstart/forms
Sample URL: https://docs.google.com/spreadsheet/ccc?key=1HgtMSoatp1M6pQwwwQqHgZX7jZRldDbSX8VIJ468d4c&newcopy=true
Description:
Actual Behavior
The sample spreadsheet is publicly accessible. No access request is required.
Steps to Reproduce the Problem

Navigate to https://developers.google.com/apps-script/quickstart/forms
Click "Apps Script Quickstart: Managing responses for Google Forms"
Receive an error that request needed for access

This is a 'copy link'. You can get the source file by deleting the word copy from the end of url https://docs.google.com/spreadsheets/d/1HgtMSoatp1M6pQwwwQqHgZX7jZRldDbSX8VIJ468d4c.
For main behavior you need to click Make a copy button

Looks like it's an org-wide security setting.


Don't work localization file in Dnn.TaskScheduler

When I change the language of the site to Persian, in the Dnn.TaskScheduler, the localization file is TaskScheduler.FA-IR.resx is not invoked.
Also, Persian date is not displayed.

Affected version

[x] 9.4.2-rc
[x] 9.4.1

Do we have anyone with knowledge about Persian calendar that can help here?


Azure Application Gateway Quick Start: missing creation instructions of "myBackendSubnet"

In "Azure Application Gateway Quick Start" https://learn.microsoft.com/en-us/azure/application-gateway/quick-create-portal are not present the creation instructions of "myBackendSubnet": this subnet suddenly appears in a subsequent step. The missing instructions can be taken from the following document: https://learn.microsoft.com/en-us/azure/application-gateway/create-ssl-portal, the missing instructions should be put after the following creation of "myAGSubnet":
=
Name: Enter myVNet for the name of the virtual network.
Subnet name (Application Gateway subnet): The Subnets grid will show a subnet named default. Change the name of this subnet to myAGSubnet.
The application gateway subnet can contain only application gateways. No other resources are allowed. The default IP address range provided is <IP_ADDRESS>/24.
and the missing instructions to add should be:
=
Subnet name (backend server subnet): In the second row of the Subnets grid, enter myBackendSubnet in the Subnet name column.
Address range (backend server subnet): In the second row of the Subnets Grid, enter an address range that doesn't overlap with the address range of myAGSubnet. For example, if the address range of myAGSubnet is <IP_ADDRESS>/24, enter <IP_ADDRESS>/24 for the address range of myBackendSubnet.
Thank you.

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

ID: 1b1e0765-a7aa-6e76-3aca-751dc8a531dc
Version Independent ID: e95861b3-cfd3-2b75-95e8-1c0176ba79f2
Content: Quickstart: Direct web traffic using the portal - Azure Application Gateway
Content Source: articles/application-gateway/quick-create-portal.md
Service: application-gateway
GitHub Login: @greg-lindsay
Microsoft Alias: greglin

@FabioPaganoAPSystem
Thank you for your feedback! We will review and update as appropriate.

@FabioPaganoAPSystem
Thank you for the feedback, I have made the suggested change and the PR will be merged soon. The change should reflect in next 24 hours. Thank you!


Injecting types defined in parent folders (and their children)

I got a problem when the definition of a type which I want to inject is in a parent folder (or one of the parent's sub folders).
I am importing my service like
import { ConfigurationService } from '../core/configuration-service'
But neither @inject nor @autoinject will work. I always get a badkeyerror. I tracked it down to a call in aurelia-dependency-injection to _aureliaMetadata.metadata.getOwn("design:paramtypes", target) || _emptyParameters which returns an array with an undefined entry for this case.
When using classes from the current folder or a subfolder of the current folder it works, e.g.:
import { AnotherService } from './another-service'
or
import { PartyService } from './party/party-service'
I am using RC1 with TypeScript 1.8.10 targetting ES6, working from skeleton with systemjs/jspm.
Am I refering my types wrongly, is this a bug with metadata or with DI?

I have tried to adopt all import statements to paths relative to the src folder, but that does not help either.

This isn't an Aurelia problem. If you are gettng that error, it's because the import itself is incorrect.

Let's say I have these components in my aurelia app:
app.ts
core/configuration-service.ts
users/user-service.ts
How can I import ConfigurationService inside UserService?
For the TypeScript compiler both of these are fine:
import { ConfigurationService } from 'core/configuration-service.ts';
import { ConfigurationService } from '../core/configuration-service.ts';

Also if I do such an import, I can create an instance with the new operator. It is just DI failing to provide it and only if the class is not in the same folder (or a subfolder of it).
So if I can do a new, how is the import wrong?

Show me the code for the class where you want the injection to happen.

Okay, this is brick-service.ts in subfolder bricks.
This works, not using DI:
import { autoinject, inject, LogManager } from 'aurelia-framework';
import { HttpClient } from 'aurelia-fetch-client';

import { BrickDef } from 'bricks/brick-def';
import { BrickGroup } from 'bricks/brick-group';
import { GateService } from 'core/gate-service';
import { ConfigurationService } from 'core/configuration-service';

export class BrickService {
    private log = LogManager.getLogger("loggerName");
    private client: HttpClient;
    private configurationService: ConfigurationService;
    private gateService: GateService;
    constructor() {
        this.configurationService = new ConfigurationService(); // TODO replace with DI
        this.gateService = new GateService(this.configurationService); // TODO replace with DI
        this.log.debug("Got objects:", this.configurationService, this.gateService);
        debugger;
    }
    public getAvailableBrickDefinitions(): BrickDef[] {
        return new BrickDef[0];
    }
    public getDefinitionById(id: string): BrickDef {
        return null;
    }
    public async initRemoteBricks(): Promise<boolean> {
        return true;
    }
}

Using DI for GateService and ConfigurationService, both in the sibling directory core, I get the badKeyError:
import { autoinject, inject, LogManager } from 'aurelia-framework';
import { HttpClient } from 'aurelia-fetch-client';

import { BrickDef } from 'bricks/brick-def';
import { BrickGroup } from 'bricks/brick-group';
import { GateService } from 'core/gate-service';
import { ConfigurationService } from 'core/configuration-service';

@autoinject
export class BrickService {

    private log = LogManager.getLogger("loggerName");
    private client: HttpClient;
    private configurationService: ConfigurationService;
    private gateService: GateService;

    constructor(configurationService: ConfigurationService, gateService: GateService) {
        this.configurationService = configurationService;
        this.gateService = gateService;
        this.log.debug("Got objects:", this.configurationService, this.gateService);
        debugger;
    }
    public getAvailableBrickDefinitions(): BrickDef[] {
        return new BrickDef[0];
    }
    public getDefinitionById(id: string): BrickDef {
        return null;
    }
    public async initRemoteBricks(): Promise<boolean> {
        return true;
    }
}

I have also tried to use @inject(ConfigurationService, GateService) instead of @autoinject.
It always throw an Error(badKeyError) in Container.get.
This does not happen when all classes/modules are in the same folder!

Do you have circular references?

The bad key error happens because the thing you are trying to inject is undefined. That means that the import isn't working correctly. (Nothing to do with Aurelia at that point.)

I can exchange that dependencies for a newly created TestService from the core folder which is empty and so has no dependencies. The same problem.
Yes, the thing I am trying to import is undefined but I have no idea at this point how to debug that. Importing from other modules in my own app should in fact be very simple.
Maybe I messed with the module loading or something, I will try to further investigate.

But which would be the correct syntax for the import in your opinion?
a) import { ConfigurationService } from 'core/configuration-service';
b) import { ConfigurationService } from '../core/configuration-service';

It depends on how your module loader is configured.
Can you zip up a simple version of your project that produces the issue so I can take a look?

Thanks for your support Rob!
While I was stripping all unnecessary things from my project to provide you a small sample - of course - I did also strip what was causing the issue.
Sorry that I bothered, sure thing I messed up the module loading.
This is how:
As you can see from a sample above I got some classes BrickGroup, BrickDef etc. which all have their very own file because I like the one class one file approach.
But that approach can mean lots of lines of import at the beginning of a file. So I basically created a brick-module.ts which does just this:
export * from 'bricks/brick-def';
export * from 'bricks/brick-group';
...

So I can import like this: import { BrickDef, BrickGroup } from 'bricks/brick-module';
And of course I was mixing that with importing that classes directly from their source files. Guess I will drop that and go with more import statements.
Shame on me :-(

Some of the transpilers have various issues with export * I think.

Your answer made me courious.
I retried changing my brick-module.ts not to use the star * but the class names. But that did not the trick.
Further I found out that not all places would have to omit brick-module.ts and go for the real modules to have it back to work. But I prefer to have it all consistent.
I guess even when imported from the same module, the BrickService from brick-service.ts and the one from brick-module.ts are not considered to be the same in all cases.

It sounds like a bug with the module loader where it's loading the same module twice somehow, resulting in two different instances of the same type? Are you using system.js?

That sounds fitting.
Yes it was system.js 0.19.6.
I just updated to 0.19.31 (jspm 0.16.39) to check but that would not solve the issue.
Guess I'll stick to not use that combine module file.


DataSAIL not available for Mac Apple Silicon M1 chip

I have difficulty in installing DataSAIL on my MacBook with Apple M1 chip (AArch64/osx-arm64 architecture).
Currently, have used a workaround by conda config --env --set subdir osx-64 and followed the instructions in the documentation as usual. The installation was a success, however, not sure if the translation would work correctly as it might not be optimized for the newer M1 architecture.
Requesting to please make it available for arm64
Thank you

Hey @tanyamalkani,
I modified the build-and-upload pipeline to provide osx-arm64 and win-64 builds of DataSAIL. Please check if this solves your issue and let me know.
Best, Roman


TailwindCSS doesn't load on production but in development it works

This problems happens with the following project: jheysaav/jheysonsaavedra.com. The projects is alive here.
TailwindCSS is configured as a the docs explain it and when I run deno task start it works fine like this:

But in the production mode when I run deno task preview or when I deploy it to Deno Deploy it seen like this:

The Tailwind css file doesn't work.
This is my tailwind.config.ts:
import { type Config } from "tailwindcss";
import colors from "tailwindcss/colors.js";

export default {
  content: [
    "{routes,islands,components}/**/*.{ts,tsx}",
  ],
  darkMode: "class",
  theme: {
    fontFamily: {
      sans: ["Inter Variable", "Inter", "sans-serif"],
    },
    colors: {
      gray: colors.zinc,
      primary: colors.blue,
      secondary: colors.emerald,
    },
  },
} satisfies Config;

The routes/_app.tsx file looks like this:
import { type PageProps } from "$fresh/server.ts";
import Header from "../components/Header.tsx";

export default function App({ Component, url }: PageProps) {
  return (
    <html lang="en">
      <head>
        <meta charset="utf-8" />
        <meta name="viewport" content="width=device-width, initial-scale=1.0" />
        <title>Jheyson Saavedra</title>
        <link rel="stylesheet" href="/styles/tailwind.css" />
        <link rel="stylesheet" href="/styles/inter.css" />
      </head>
      <body className="w-scren h-screen flex flex-col bg-gray-50 dark:bg-gray-900 text-gray-900 dark:text-gray-50">
        <Header url={url} />
        <main>
          <Component />
        </main>
      </body>
    </html>
  );
}

Finally the static/styles/tailwind.css file looks as this:
@tailwind base;
@tailwind components;
@tailwind utilities;

The tailwindcss plugin requires Ahead of time builds to be set up, see the requirements section in https://fresh.deno.dev/docs/examples/migrating-to-tailwind . This involves two steps:

Set deployment mode to GitHub Actions in Deno Deploy (your's is likely set to automatic which won't work)
Add the deploy.yml file from https://fresh.deno.dev/docs/concepts/ahead-of-time-builds and update the project name to match yours. The project name can be found in Deno Deploy under Settings > Project Name

I'm planning to add a specific error page to Fresh when it detects that the tailwindcss styles are not compiled and show a nice error page. It seems to be something that many users run into, so it's definitely on us to improve the DX.

The tailwindcss plugin requires Ahead of time builds to be set up, see the requirements section in https://fresh.deno.dev/docs/examples/migrating-to-tailwind . This involves two steps:

Set deployment mode to GitHub Actions in Deno Deploy (your's is likely set to automatic which won't work)

Add the deploy.yml file from https://fresh.deno.dev/docs/concepts/ahead-of-time-builds and update the project name to match yours. The project name can be found in Deno Deploy under Settings > Project Name

I'm planning to add a specific error page to Fresh when it detects that the tailwindcss styles are not compiled and show a nice error page. It seems to be something that many users run into, so it's definitely on us to improve the DX.
Related issues:

https://github.com/denoland/fresh/issues/2188

https://github.com/denoland/fresh/issues/2126

This solution works for me. @marvinhagemeister thank you.


multiple services in one container only creates https redirect for first service

Do you want to request a feature or report a bug?
Bug
Did you try using a 1.7.x configuration for the version 2.0?

[ ] Yes
[X] No

What did you do?
I'm trying to setup a docker container (ubiquiti unifi controller). that is exposing two https portals, one on 8443 for administration, and one on 8843 for a hotspot captive portal.
Both exposed ports are creating a distinct frontend host, unifi.xyz.dk for the admin part, and hotspot.xyz.dk for the hotspot part. Both is exposed as https frontends with ssl from lets encrypt
The unifi.xyz.dk get a redirect backend created but I am not able to create one for the hotspot.xyz.dk

What did you expect to see?
I expect to be able to redirect from
http://unifi.xyz.dk to https://unifi.xyz.dk as well as http://hotspot.xyz.dk to https://hotspot.xyz.dk
What did you see instead?
I am only able to get redirected from http://unifi.xyz.dk, if I go to http://hotspot.xyz.dk, nothing happens (If I go to https://hotspot.xyz.dk manually, i get the right portal shown)
Output of traefik version: (What version of Traefik are you using?)
1.7.10
docker traefik:v1.7
(paste your output here)

What is your environment & configuration (arguments, toml, provider, platform, ...)?
      --docker
      --docker.swarmmode
      --docker.watch
      --docker.exposedbydefault=false
      --entrypoints='Name:http Address::80'
      --entrypoints='Name:https Address::443 TLS'
      --consul
      --consul.endpoint="consul-leader:8500"
      --acme
      --acme.email=${EMAIL}
      --acme.storage="traefik/acme/account"
      --acme.entryPoint=https
      --acme.httpChallenge.entryPoint=http
      --acme.onhostrule=true
      --acme.acmelogging=true
      --logLevel=INFO
      --accessLog
      --api
      --logLevel="DEBUG"
      --insecureSkipVerify=true

in my docker-compose file for the unifi container, I have set the following labels
      labels:
        - traefik.docker.network=traefik-public
        - traefik.enable=true
        - traefik.redirectorservice.frontend.entryPoints=http
        - traefik.redirectorservice.frontend.redirect.entryPoint=https
        - traefik.frontend.whiteList.sourceRange=<IP_ADDRESS>/16
        - traefik.protocol=https
        - traefik.frontend.rule=Host:unifi.xyz.dk
        - traefik.port=8443
        - traefik.frontend.entryPoints=https
        - traefik.hotspot.port=8843
        - traefik.hotspot.frontend.entryPoints=https
        - traefik.hotspot.frontend.rule=Host:hotspot.xyz.dk

I have tried to create a second redirector service as below but it just replicates the one for unifi.xyz.dk
      - traefik.redirectorservice2.frontend.entryPoints=http
      - traefik.redirectorservice2.frontend.redirect.entryPoint=https

As seen from the status page, I only get one redirector service

Hi! I'm Træfiker :robot: the bot in charge of communication regulation.
Thanks for your interest in Traefik!
We dedicate the issue tracker to bug reports and feature requests only. My advanced AI tells me this one is neither of them.
I encourage your to seek community support: join our Slack workspace and reach out to us on the #support channel.
Another option is to use Stack Overflow and tag your question traefik.
You can of course double check Traefik's documentation :sweat_smile:


Lack of line number/file name when error occurs stalls development

Note: If your issue/bug is regarding the AWS Amplify Console service, please log it in the
official AWS Amplify Console forum

Describe the bug
Others have requested amplify to be more 'verbose' and the requests get closed so here's an example.
? Do you want to update code for your updated GraphQL API Yes
? Do you want to generate GraphQL statements (queries, mutations and subscription) based on your schema types? This will overwrite your current graphql queries, mutations and subscriptions Yes

Updating resources in the cloud. This may take a few minutes...Error updating cloudformation stack
× An error occurred when pushing the resources to the cloud

Invalid input for parameter key AuthRoleName. Need to specify either usePreviousValue as true or a value for the parameter
To Reproduce

amplify auth had to be manually removed (couldn't deploy or remove due to yet another issue, related here but manually removing the entries was my only workaround)
Auth doesn't show under amplify status any more but obviously in one of my other items Auth role lingers

Expected behavior
"awsconfiguration.json line 56: Invalid input for parameter key.." thus letting me know what item is sending an AuthRoleName parameter
Desktop (please complete the following information):

OS: Win10
Browser: Chome
Version 1.5 (amplify)

Additional context
The lack of what amplify is doing wastes hours of research time usually followed with deleting everything then redeploying which is a terrible resolution. Please add a way to see what amplify is doing

@BarberEngineering
Thanks for the feedbacks, we will discuss among the team.

@BarberEngineering Could you please show your terminal logs? Which version of the CLI are you using?

Didn't save it and I removed everything and started new since I was told where the issue was. Wasted a day blind hunting then gave up. Was newest cli - 1.6.3
"Another example -  Updating resources in the cloud. This may take a few minutes...Error updating cloudformation stack" - every time we hit this it pretty much means hang it up, delete the resource and redeploy. Example output below. As a user, what is this telling me to do next? Ask it nicer? There's no '-force' and no actual indication of where / what it choked on so it's putting on the blindfold birdbox style. It's no big deal when you're just trying stuff out but if this was anywhere near prod, deleting the resource and starting over isn't really an option when you have real data.
UPDATE_ROLLBACK_COMPLETE stackname AWS::CloudFormation::Stack Wed Apr 24 2019 09:38:55 GMT-0500 (Central Daylight Time)
DELETE_COMPLETE          authcognito                        AWS::CloudFormation::Stack Wed Apr 24 2019 09:38:54 GMT-0500 (Central Daylight Time)
UPDATE_IN_PROGRESS       analytics         AWS::CloudFormation::Stack Wed Apr 24 2019 09:38:54 GMT-0500 (Central Daylight Time)
UPDATE_IN_PROGRESS       storages3                  AWS::CloudFormation::Stack Wed Apr 24 2019 09:38:54 GMT-0500 (Central Daylight Time)
UPDATE_IN_PROGRESS       authcognito                    AWS::CloudFormation::Stack Wed Apr 24 2019 09:38:54 GMT-0500 (Central Daylight Time)
⠙ Updating resources in the cloud. This may take a few minutes...Error updating cloudformation stack
⠹ Updating resources in the cloud. This may take a few minutes...
Following resources failed
✖ An error occurred when pushing the resources to the cloud
Resource is not in the state stackUpdateComplete

@BarberEngineering Could you please show your terminal logs? Which version of the CLI are you using?

@BarberEngineering We enhanced our cloud formation logging capabilities to point you to the exact resource/template if which you're having an issue with. Please take a look at the latest version of the CLI and let me know if you have more suggestions.


Company link not working

Hello there,
I see you have listed various ML companies in Nepal. But most of the links of companies are not working. Can you please fix them?
Thanks

@NirmalSilwal Thanks for flagging this. I've fixed the links.

Thanks


[nrf fromlist] [zephyr] Use native locking primitives

Switch from Zephyr POSIX layer to Zephyr native locking primitives to reduce the memory overhead.

There are other failures in upmerge PR CI. Also the sdk-nrf west.yml manifest file has been updated with new sdk-connectedhomeip SHA, hence please rebase this PR and include additional fixes as necessary.


[Python] Update 3.9.12 to 3.9.13

https://docs.python.org/release/3.9.13/whatsnew/changelog.html#python-3-9-13-final

@jefftriplett Thank you for your first contribution 👍 💯 🥇 🎉 We will be glad to see your following contributions


Convert project to Typescript

This will allow people to use this project in Typescript projects

Thanks for the PR, but we're going to pass on this one. Adding a build step for such a small module doesn't have any added value. You can always use it in TypeScript with import * as parseMs from 'parse-ms';. If you want type definitions, feel free to add them to DefinitelyTyped and I will 👍 it.


Security vulnerability due to outdated google-auth-library dependency

Running npm run audit results in a high-severity vulnerability
High            Prototype Pollution in node-forge

  Package         node-forge

  Patched in      >= 0.10.0

  Dependency of   @assistant/conversation

  Path            @assistant/conversation > google-auth-library > gtoken >
                  google-p12-pem > node-forge

  More info       https://npmjs.com/advisories/1561

The core issue appears to be the usage of an obsoleted version of the "google-auth-library": "^5.10.1" dependency which prevents us from updating the node-forge upstream dependency.

Thanks for identifying this.

Please let me know how can I help here and at which point you could take a look into this further. Our CI is strict about high-severity vulnerabilities, so I could take a swing at migrating to the new library version as well. There are some non-specified breaking changes awaiting in v6 ref, but maybe they won't be a problem.
Let me know how you'd like to proceed here.

My plan for this library is to try updating the auth-library to v6 and run tests/sample. I don't believe there'd be any breakages, or if so they'd be minimal.

Thanks @Fleker, appreciate it! If you could give me a rough estimate of when you could take a look it'd help us plan on our side :-)

I hope to have an update before the week's end.

Appreciate the fast turnaround here, thanks!


Wrong number of autocorrections

When running rubocop -a --only=Layout/LineLength, it displays a total of 12 offenses, of which 7 were autocorrected. In fact, none of those offenses were corrected.
app/models/user.rb:77:151: C: [Corrected] Layout/LineLength: Line is too long. [151/150]
    last_push_token = user_tokens.where.not(push_token: [nil, '']).where.not(updated_at: nil).where.not(last_sign_in: nil).order('updated_at ASC').last

Here, for example, an offense was supposedly corrected, although nothing in this line was changed. And, sure enough, next time I run the same command, the offense shows up again.
I am not sure what is causing the problem as it seems to occur randomly on different line lengths (150-190 characters in my case).

Expected behavior
Either not to show that the offense was corrected, or correct it once and for all.
Steps to reproduce the problem
In rubocop.yml, specify
Layout/LineLength:
  Max: 150

Then run the autocorrection on the line above.
RuboCop version
1.5.2 (using Parser <IP_ADDRESS>, rubocop-ast 1.3.0, running on ruby 2.6.1 x86_64-darwin19)
  - rubocop-faker 1.1.0
  - rubocop-performance 1.9.1
  - rubocop-rails 2.8.1
  - rubocop-rake 0.5.1
  - rubocop-rspec 2.0.1

This is a continuation of #8978 and #9073. LineLength is a special case for autocorrect because it can only split lines at certain places. Your example should actually autocorrect, but it looks like my fix from #8978 (from before AutoCorrect was enabled by default) is preventing the autocorrect from actually running. I have a fix coming.


Reduce overhead of upgrades for users with custom stylesheets/JS

I have custom JS/CSS in use on my gitea instance and when I upgrade I have to edit head.tmpl and footer.tmpl to add in my changes again (otherwise I might have out of date templates). This will allow me to put all of my changes in header_extras.tmpl/footer_extras.tmpl and not worry about upgrading.
Open to suggestions regarding the names of the additional templates, or their locations.

Codecov Report

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

@@            Coverage Diff             @@
##           master    #3051      +/-   ##
==========================================
- Coverage   33.38%   33.34%   -0.05%
==========================================
  Files         270      270
  Lines       39566    39566
==========================================
- Hits        13211    13195      -16
- Misses      24466    24484      +18
+ Partials     1889     1887       -2

Impacted Files
Coverage Δ

models/repo_indexer.go
45.54% <0%> (-6.44%)
:arrow_down:

modules/indexer/repo.go
60.86% <0%> (-2.61%)
:arrow_down:

Continue to review full report at Codecov.

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

@sapk thanks for the feedback. I've changed the directory for the extras template files, and added in some documentation on when to use them.

LGTM

Would custom be a better directory name than extras?

@ethantkoenig Thanks for feedback. As custom is already a top level dir, when we tell people to go to the custom folder it might create confusion to have multiple dirs with the same name. (See use of custom on this page: https://docs.gitea.io/en-us/customizing-gitea/ )

@techknowlogick Could we explicitly tell them to go to templates/custom, so they don't get confused?

@ethantkoenig yes, but then for the other custom directory we have to explicitly say not the templates/custom directory. For example we have instructions for adding the robots.txt, and serving public files to put all of those in custom or custom/public. There is also a user on discord that is currently confused about just even the one custom directory.
However, this is as much commitment to the idea of that folder name as I have, and so in light of the above if you still want me to change the directory name I will.

I personally prefer custom over extras, for two reasons:

I think it more clearly describes the intent of the directory (customized template changes)
For consistency with the existing custom directory; every directory named custom is for some sort of custom change.

Ok. Sounds good. Im out right now, but will change it when I get home.
--
Matti
On Sat, Dec 2, 2017, at 02:32 PM, Ethan Koenig wrote:

I personally prefer custom over extras, for two reasons:

I think it more clearly describes the intent of the directory
(customized template changes)
For consistency with the existing custom directory; every
directory named custom is for some sort of custom change.> — You are receiving this because you were mentioned. Reply to this
email directly, view it on GitHub[1], or mute the thread[2].>

Links:

https://github.com/go-gitea/gitea/pull/3051#issuecomment-348714493
https://github.com/notifications/unsubscribe-auth/AAKBZQcxjG4AK4lDtor0NG0oKLGNBz5Wks5s8aXlgaJpZM4QyhIL

@ethantkoenig I've updated it. Thanks again for the feedback.
cc: @lafriks

LGTM


Delete transitive_reduction_exact.rb

I did not intend to upstream this script, it is too slow and it is confusing to have two transitive reduction scripts.

Please merge from main and the CI checks will pass.
I have just fixed a mistaken blueprint declaration.


Fix error message when watch-client.js is not installed

Fix TypeError, remove unnecessary stack trace.
Change this:
*** Cannot watch: TypeError: Cannot read property 'expressions' of undefined
        at multimeter.api.memory.get.then.val (/home/simon/screeps/node_modules/screeps-multimeter/plugins/watch.js:40:72)
        at process._tickCallback (internal/process/next_tick.js:68:7)

To this:
*** Watch plugin disabled: watch-client.js is not installed or out of date.

To be honest, the watch plugin should be disabled by default to prevent this message completely. As a policy any plugin that requires additional setup should be opt-in only - it should not be in the default plugins list.

To be honest, the watch plugin should be disabled by default to prevent this message completely. As a policy any plugin that requires additional setup should be opt-in only - it should not be in the default plugins list.

I think this is a fair policy. I would emphasize that the watch plugin is (in my opinion) one of the biggest value-adds to multimeter (aside from just being a headless console), so, while disabling it by default might be the best choice, emphasizing it and making setup easy should probably be a goal as well.


update probot to v7

Breaking these changes out from #79.
I still can't quite figure out why this test is failing.

and added the DCO signoff on all the commits  :trollface:

Are you trying to credit yourself for my commit? That is messed up :trollface:

Are you trying to credit yourself for my commit?

Event worse: I'm trying to claim that I have the rights to submit your commit to this repository! 😁


[FEAT] Adding  Team/Contributors Page to the website

I would like to add a team's page to the website.
Add the developers and contributors section to the page with a list of all contributors and developers in it.
This would improve user engagement and experience.
Plz, assign me this task under gssoc'23.

It's not required.


Create an UI for it.

It'd be better for lay people in computers! just like only a binary installer to make all the tecnical stuff. Because this app is so interesting even with the lay people in computing.

Another thing is that you need to install many things mannualy:

Go lang
ImageMagick
Git
Primitive

https://primitive.lol/

But it is only for MAC OS and it is paid. If your intent is to "sell" the UI, sorry, only thing I think is: if it was multi-platform it'd be better.

https://ondras.github.io/primitive.js/

Now we only need a plugin for GIMP :)

I made a more simplified web version for making gifs: https://www.kapwing.com/motion

@justswim Nice!


Update smart answer outcome for intestacy

Requested at https://govuk.zendesk.com/agent/tickets/3935092

There'll need to be some change to the flow logic to send them to a question with the updated amount, somewhere here: https://github.com/alphagov/smart-answers/blob/master/lib/smart_answer_flows/inherits-someone-dies-without-will.rb#L42
Or you might be able to get away with changing how the estate_over_250000 question (and answer) is displayed if the region is england-and-wales

Thanks Michael!


PSoC64: Fix SMIF flash algorithm type for cy8c64xx_cmX_full_flash targets

PSoC64-1M kits are equipped with S25Hx512T memory, not S25FL128S

/morph test

/morph test


Removing FlowDock reference

FlowDock integration is not currently supported in .5 version of AM.
See https://github.com/prometheus/alertmanager/issues/236

Thanks!


app::ui: intro Label and apply many other fixes

Most features are self-explanatory, but here it is anyway. Label defines a simple non-editable text field. And the newly public remove method remove views from other views (such as Layouts).
Other fixes clean up the relation with the Java GC and multi-threads behavior.

+1


Make all pages resizable

As the title says:

Currently, the course lists handle resizing well and only run into a few cosmetic problems when you smush it so small that section names and times can't fit on the same line. No changes are really needed.
The home page should have resize events that detect when it has grown too small for as many columns as it has or large enough to accommodate more, and repopulate the page accordingly.
The schedule page will be problematic. I don't quite like the fixed-pixel scheme it currently has, since that prevents resizing and also forces a standard font size. If there's any way to make it dependent on ems only, that should be done and then resizing should be added (perhaps by shrinking the font, or something.)

Marking this under RPI Release, but with the knowledge that this is not a high priority. It could be pushed back to General Release.

The schedule page is a whole other issue, and I don't want to possibly break it as we approach the release. I am changing the scope of this issue to making the home page only be the resizable one; that is still a reasonable goal for this release. We'll have to talk about the schedule page after that.

I think this is as simple as adding a resize event listener to the window, and having it recalculate the number of columns in the new window size, and if that is different from the current (will have to save the current in nsUser) then reload the schedule page.

Home page is now resizable, but the solution is kludgy: it will reload the home page when it detects the number of available columns has changed. Improving this will require a lot of restructuring of the home page generation logic, and probably should wait till we have a frontend templating framework too. Since the feature is done and I consider it to be acceptable for the RPI release, I'll be closing this issue and opening a new one for the General Release to cover these enhancements.