Error: Social Media Icons Overlapping and Hidden Behind Profile Card in Mobile View

Describe the Error
The social media icons are getting hidden behind the readmes and other UI elements when viewed on smaller screens or in mobile view.
Expected behavior
The social media icons should be fully visible and positioned correctly to the right of the profile card without overlapping or getting obscured by other elements
Additional context
The issue might be related to improper z-index stacking or the use of a flex/grid container that causes the icons to overlap.
Screenshot attached to illustrate the problem (see attached image for reference).

Please Assign it to me
I will fix this

Please Assign it to me

you can assign this to me
https://github.com/user-attachments/assets/0dfb287d-91a4-4b8f-827d-6fb6365289df


Cache limit

The drone cache used all of my disk. Perhaps there should be some limiting to maximum size of the entire cache?

I'd like to create a drone-cleanup utility similar to docker-custodian but that is optimzed for build servers. This would include cache management, removing untagged images, etc

Any idea when this is going to push? Can't the build automatically do cleanup? I.E. when a build is triggered, as the last step, purge cache older than 48 hours?

Hi @bradrydzewski, are there plans to release a drone-cleanup utility soon? My drone cache is currently using ~60GB disk space.
In the meantime, how can I clean up the cache manually (or with cron) to make sure the build server doesn't run out of disk space entirely?

Addendum: I could let cron delete all cache.*.tar files older than e.g. 48 hours from /var/lib/drone/cache/. Would that work, or is that too naive and will it break future builds depending on these older cache files?

Addendum: I could let cron delete all cache.*.tar files older than e.g. 48 hours from /var/lib/drone/cache/. Would that work, or is that too naive and will it break future builds depending on these older cache files?

That should work as drone just rebuilds a cache if it's missing. In worst case you will have a longer build time because of the cache rebuild.

Great, thanks. I'll look into that and share the cron script here once I have something working.

We just do something like sudo find /var/lib/drone/cache -atime +7 -delete which will delete any drone cache file that hasn't been accessed in the last wee, if that helps.

Yeah, that's exactly what I'm adding to our CI server now, too. Thanks for sharing :smiley:

Here is what I just implemented in crontab:
# Every Sunday at 3:00am, delete Drone cache not accessed within the last 5 days
0 3 * * 7 find /var/lib/drone/cache -atime +5 - delete

the cache plugins can now purge history thanks to https://github.com/drone/drone-cache-lib/pull/1 from @jmccann


New project based in your code

Hi man,
first of all thanks for your work, I forked your project and update it for general purpose card games prototyping. My idea is to help game designers to build card decks fast and easy, as most of them uses Magic Card format, I think the modifications I have done could be really useful. If you are agree I'd like to make the code public under the name of LightWeightCardPrototiping. Obviously I'll add the recognition and original repo in the readme file.
Cheers,
Fernando

Fantastic! Glad it can be of use.

Andrew Tiller
(615) 306-2616
Sent from mobile

On Fri, Oct 22, 2021, 6:34 AM fmolinagomez @.***> wrote:

Hi man,
first of all thanks for your work, I forked your project and update it for
general purpose card games prototyping. My idea is to help game designers
to build card decks fast and easy, as most of them uses Magic Card format,
I think the modifications I have done could be really useful. If you are
agree I'd like to make the code public under the name of
LightWeightCardPrototiping. Obviously I'll add the recognition and original
repo in the readme file.
Cheers,
Fernando
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/tilleraj/LightWeightMTGProxy/issues/7, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFLLBNU4FUZDFKUAYYFLQLUIFD45ANCNFSM5GQK7J4Q
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


feat: optimize dry for cpu

Optimized version with a few more params (could expose as engine args).
Tested to build stably on 0.6.4.post1 (0.6.5 has crashing issues). Could use help in double checking accuracy & exposing params for different setups. Speedup is significant, close to without using DRY.
See https://chatgpt.com/share/676a05a7-2c20-800f-95b7-c2c5ee33d48d for more context

I'll review this tonight, but maybe instead of engine args, we could use env vars for the extra params?


Allow for selecting and excluding telescopes in the arrayConfig

Add new entries to the arrayConfigFile: selectTelescopes and excludeTelescopes with lists of telescope names.

This issue is not clear to me. Could someone with more insight clarify what is meant where with arrayConfigFile and the application is here?
If not, let's close.

This issue suggests to add the functionality of selecting a sub array from the full list of telescopes in the hyperarray. I don't know if this is the best way to do it (or if this functionality is needed) though. If someone thinks it is needed functionality, we can keep it open (and modify the title/explanation). Otherwise, I suggest we close it indeed.

This might be quite useful for the construction/monitoring arrays, as we have investigated with Julia in the summer school. However, this is not a priority now for any of us I think. By the way, I created a tag for this kind of issues: "Archive". Instead of completely closing it, we archive it for later. What do you think?

For what we did with Julia we do not need to simulate subarrays but rather select them in the analysis. Therefore, the functionality discussed here is not relevant for that.
The idea of archiving issues is not bad, but I think this issue does not need to be archived, so I suggest to close it. Is that OK @VictorBarbosaMartins?

Sure @orelgueta . thanks for the feedback. Lets close it.


Navigator component uses rebound for animations

I'm finding they often stutter in my app. Animations done with the Animated module don't tend to. Any plans to port Navigator over to use Animated?

This would definitely be awesome!

I believe this is underway but not sure of the time schedule. Maybe slated for 0.12 or 0.13? cc @ericvicenti @hedgerwang

This is indeed in progress -- going to close the issue as it's known and underway :)

@brentvatne any idea when it's gonna make it into master?

Personally no, @hedgerwang and @ericvicenti are the people who might have some idea of that :)
That said, this won't completely fix the issue of stuttering - another comment that goes into more detail here: https://github.com/facebook/react-native/issues/2490#issuecomment-136249185


Also stop compute containers alongside services

Some tripleo containers are not managed with systemd services, and need to be stopped.
Stop nova_virtlogd tripleo container on compute hosts to let decontainerized libvirt/virtlogd functioning during adoption process.
JIRA OSPRH-5315

FYI @mrkisaolamb i think this is related to what you're presently working on.

should go to https://github.com/openstack-k8s-operators/edpm-ansible/pull/580


Allow us to use custom props in styled-component

I'm migrating MUI version 4 to 5.
I'm not used to use styled-component before since it was not default in MUI.
But as far as I know, styled-component can pass custom props like this.
const MyButton = styled(Button)`
...
${props => props.isActive && css`
    color: black;
  `}
`;
<MyButton isActive={...} />

The isActive prop is very common use case when we want to conditionally apply some styles.
I've tried to passing custom props to styled component, but is didn't worked.
It seems that custom props blurred by predefined props(or vice versa)
// isActive not working!!
const MyButton = styled(Button)(({ theme, isActive }) => ({
  color: (isActive) => isActive ? theme.palette.primary.main : '#ccc'
}));

const MyComponent = () => {
 const session = ...;
  return <MyButton isActive={session ? true : false} />
}

Currently, migration document suggest to do like this.
const classes = {
  isActive: "isActive",
};

const MyButton = styled(Button)(({ theme }) => ({
  color: '#ccc',
  [`&.${classes.isActive}`]: {
    color: theme.palette.primary.main,
  },
}));

const MyComponent = () => {
 const session = ...;
  return <MyButton isActive={session ? classes.isActive : undefined} />
}

But in my opinion, this solution is a bit verbose, and no intuitive, and inconsistent.
Why not just allow us to pass custom props to the component as we are already familiar with to use.

[ x] I have searched the issues of this repository and believe that this is not a duplicate.

I found shouldForwardProp.
I didn't noticed this exist before.


Add support for blkio read/write iops device

Signed-off-by: Ma Shimiao<EMAIL_ADDRESS>

@Mashimiao need rebase
LGTM

does this depend on the other PR's? https://github.com/docker/docker/issues/14466 and https://github.com/docker/docker/issues/13959?
(looks like this needs a rebase :cry:)

@Mashimiao Would you mind to answer @thaJeztah question?

I think this can go ahead now :)

@Mashimiao whoa, sorry, need rebase again.

This PR is similar to #14460, I want to rebase and fix this after #14460 merged

@LK4D4  @runcom  @thaJeztah   PR rebased and fixed. I think it failed with unrelated case.

Thanks @Mashimiao, test failure will be fixed in https://github.com/docker/docker/pull/18458

https://github.com/docker/docker/pull/18458 was merged, so if you rebase, the tests should be green again

Thanks @thaJeztah   rebased.

@Mashimiao sorry, looks like this needs a rebase again :cry: could be because of https://github.com/docker/docker/pull/18472 being merged, I hope it isn't bad. Feel free to blame @calavera :smiling_imp:

@thaJeztah  That's OK. rebased again.

ping @runcom @cpuguy83 PTAL for the latest code changes, let's see if we can get this in docs review now :-)

(Thanks @Mashimiao!)

ping @cpuguy83 @LK4D4 @jfrazelle PR was update, PTAL, let's see if we can move this forward \o/

LGTM

LGTM

ping @thaJeztah @moxiegirl

Docs LGTM. Unfortunately, this PR will need to be rebased before merging.
@thaJeztah can you take a look?

@calavera  thanks, rebased.

Thanks @Mashimiao two nits. Also can you add the new options to the API changelog, for example:
`POST /containers/create` allows you to set a read/write rate
limit for a device (in bytes per second or IO per second).

(We forgot to add "BlkioThrottleReadBpsDevice" and "BlkioThrottleWriteBpsDevice" to the change log in https://github.com/docker/docker/pull/14466)

@thaJeztah  added to api Changes

jenkins failed with unrelated case

Thanks @Mashimiao, happy to see this ready to merge!!
LGTM
Documentation is basically the same as for blkioBps, so it should be good to go. Moving to "merge"
I restarted janky and experimental, but the failing tests are not related, probably a time issue;
--- FAIL: TestFormat (0.00s)
	formatter_test.go:152: Expected
		CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES
		containerID1        ubuntu              ""                  45 years ago                                                foobar_baz
		containerID2        ubuntu              ""                  45 years ago                                                foobar_bar
		, got
		CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES
		containerID1        ubuntu              ""                  46 years ago                                                foobar_baz
		containerID2        ubuntu              ""                  46 years ago                                                foobar_bar
FAIL

seems like failure comes from #18820

@runcom yes I just found that one, to check if an issue was already created for it.

@Mashimiao can you rebase? Tests should be fixed after that (by https://github.com/docker/docker/pull/18820)

It's green! \o/ :tada:


kubectl describe ingress not working (1.15.0 against 1.12.7 server)

$ k get ingress some-app
NAME          HOSTS                       ADDRESS   PORTS     AGE
some-app   some-app.domain.com            80, 443   4m58s

$ k describe ingress some-app
Error from server (NotFound): the server could not find the requested resource

Client Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.0", GitCommit:"e8462b5b5dc2584fdcd18e6bcfe9f1e4d970a529", GitTreeState:"clean", BuildDate:"2019-06-19T16:40:16Z", GoVersion:"go1.12.5", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"12+", GitVersion:"v1.12.7-gke.25", GitCommit:"d4c79083ab6dea5d26ef4ed8d50b145268349bc3", GitTreeState:"clean", BuildDate:"2019-06-22T16:10:31Z", GoVersion:"go1.10.8b4", Compiler:"gc", Platform:"linux/amd64"}

It works if I downgrade kubectl to 1.12.7

https://github.com/kubernetes/kubernetes/pull/74057 seems to be related.
kube-apiserver logs indicate that get uses the extensions/v1beta1 api, and describe uses the networking.k8s.io/v1beta1 api:
I0709 01:37:46.569519       1 wrap.go:47] GET /apis/networking.k8s.io/v1beta1/namespaces/some-namespace/ingresses/some-app: (576.366µs) 404 [kubectl/v1.15.0 (linux/amd64) kubernetes/e8462b5 <IP_ADDRESS>:51960]

This is the yaml output of the resource (using the deprecated ingress):
$ k get ingress some-app -o yaml
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  annotations:
    kubernetes.io/ingress.class: nginx
  creationTimestamp: "2019-07-09T01:32:45Z"
  generation: 1
  labels:
    heritage: isopod
  name: some-app
  namespace: some-namespace
  resourceVersion: "148136283"
  selfLink: /apis/extensions/v1beta1/namespaces/some-namespace/ingresses/some-app
  uid: 73a301b6-a1e9-11e9-87fe-42010ad40009
spec:
  rules:
  - host: some-app.domain.com
    http:
      paths:
      - backend:
          serviceName: some-app
          servicePort: 8200
        path: /
  tls:
  - hosts:
    - some-app.domain.com
status:
  loadBalancer:
    ingress:
    - {}

Same problem! Version 1.12.7 works fine.

I also encountered this problem running client 1.15.0 against a 1.13.7-gke.8 server:
Client Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.0", GitCommit:"e8462b5b5dc2584fdcd18e6bcfe9f1e4d970a529", GitTreeState:"clean", BuildDate:"2019-06-20T04:49:16Z", GoVersion:"go1.12.6", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"13+", GitVersion:"v1.13.7-gke.8", GitCommit:"7d3d6f113e933ed1b44b78dff4baf649258415e5", GitTreeState:"clean", BuildDate:"2019-06-19T16:37:16Z", GoVersion:"go1.11.5b4", Compiler:"gc", Platform:"linux/amd64"}

Downgrading to client 1.14.3 solved it:
brew install https://raw.githubusercontent.com/Homebrew/homebrew-core/fcb6cce3bdd37db3c53c2fcbdf9a47671a592c96/Formula/kubernetes-cli.rb

Please note that Kubernetes version skew policy is to provide a kubectl that is guaranteed to work against an API Server that is +/- 1 version. So for the initial scenario of a 1.12 API Server, kubectl version 1.11, 1.12, and 1.13 are guaranteed to work. Closing this issue.
/close

@seans3 perhaps a version compatibility warning would be useful to avoid time spent troubleshooting this..

@seans3: Closing this issue.

Hi,
I'm getting "Error from server (NotFound): the server could not find the requested resource" while running describe ingress command . Client and server versions is v1.15.0 ,v1.13.6
Please help me.

Hi,
I'm getting "Error from server (NotFound): the server could not find the requested resource" while running describe ingress command . Client and server versions is v1.15.0 ,v1.13.6
Please help me.

@Prakashreddy134 Try matching your kubectl version to your server version.

@demisx, how would you best handle multiple Kubernetes clusters on different versions if you have to match kubectl client to the server version?

@demisx   I think you should reopen this.    Users are likely going to have the most recent kubectl version and maintaining old version is not a viable solution.

@BenjaminSchiborr Perhaps, via different docker containers?
@ebn-rec I can't reopen this issue, since I am neither the author, not a member of this project with sufficient rights to do so. I just ran into this issue myself today and matching kubectl version to the server version fixed the problem.

We have clusters on GKE in the last stable version v1.13.7-gke.19.
Our workstation are on Ubuntu 18.04.3 LTS, we use the repo "deb http://packages.cloud.google.com/apt cloud-sdk-bionic main" for gcloud and kubectl.
Kubectl is in v1.15.3.
Could you re-open this issue please ?

Why not display a warning, if the client and server versions don't match?

Will leave it here for those who might struggle :

Verify client & server versions of kubectl by
kubectl version
Check the skew policy and select appropriate client binary for download
https://kubernetes.io/docs/tasks/tools/install-kubectl/
Download the binary with curl for example > chmod > move
Like here : https://kubernetes.io/docs/tasks/tools/install-kubectl/

I have the same problem. Below the output of kubectl version:
[root@nxdh-cloud] app # kubectl version
Client Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.3", GitCommit:"2d3c76f9091b6bec110a5e63777c332469e0cba2", GitTreeState:"clean", BuildDate:"2019-08-19T11:13:54Z", GoVersion:"go1.12.9", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"12+", GitVersion:"v1.12.10-eks-825e5d", GitCommit:"825e5de08cb05714f9b224cd6c47d9514df1d1a7", GitTreeState:"clean", BuildDate:"2019-08-18T03:58:32Z", GoVersion:"go1.12.9", Compiler:"gc", Platform:"linux/amd64"}

Why the issue is closed ?

I have the same problem. Below the output of kubectl version:
[root@nxdh-cloud] app # kubectl version
Client Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.3", GitCommit:"2d3c76f9091b6bec110a5e63777c332469e0cba2", GitTreeState:"clean", BuildDate:"2019-08-19T11:13:54Z", GoVersion:"go1.12.9", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"12+", GitVersion:"v1.12.10-eks-825e5d", GitCommit:"825e5de08cb05714f9b224cd6c47d9514df1d1a7", GitTreeState:"clean", BuildDate:"2019-08-18T03:58:32Z", GoVersion:"go1.12.9", Compiler:"gc", Platform:"linux/amd64"}

Why the issue is closed ?

Issue is closed , because there is no bug.
This suppose to work like this and compatible client<>server versions are mentioned in skew policy
In your case Client v1.15.3 -> Server v1.12.10-eks-825e5d
Basically, this is out of compatibility. What you can do in order to fix the issue is to downgrade the client to v1.13.10 for example. This should work

Hi,
is there a way to install via apt-get an old version of kubectl ?
I've tried to install the 1.13.7, but it doesn't work:
apt-get install kubectl=1.13.7-00
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances
Lecture des informations d'état... Fait
E: La version « 1.13.7-00 » de « kubectl » n'a pu être trouvée

apt-cache policy kubectl
kubectl:
  Installé : 1.15.3-00
  Candidat : 1.15.3-00
 Table de version :
 *** 1.15.3-00 500
        500 http://packages.cloud.google.com/apt cloud-sdk-bionic/main amd64 Packages
        100 /var/lib/dpkg/status

Do you know how to contact a person in charge of packages.cloud.google.com/apt  ?
It could be very interesting that they maintain multiple version.

Hi,
is there a way to install via apt-get an old version of kubectl ?
I've tried to install the 1.13.7, but it doesn't work:
apt-get install kubectl=1.13.7-00
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances
Lecture des informations d'état... Fait
E: La version « 1.13.7-00 » de « kubectl » n'a pu être trouvée

apt-cache policy kubectl
kubectl:
  Installé : 1.15.3-00
  Candidat : 1.15.3-00
 Table de version :
 *** 1.15.3-00 500
        500 http://packages.cloud.google.com/apt cloud-sdk-bionic/main amd64 Packages
        100 /var/lib/dpkg/status

Do you know how to contact a person in charge of packages.cloud.google.com/apt ?
It could be very interesting that they maintain multiple version.

Just give it a try in a way mentioned in official repo :
https://kubernetes.io/docs/tasks/tools/install-kubectl/
For example:
curl -LO  https://storage.googleapis.com/kubernetes-release/release/**v1.13.10**/bin/linux/amd64/kubectl


code: standardizing filetype outputs from the crosswalk function

Figure out the ideal file type to feed into HTML for the website
More detail to come

this is gonna go in a separate step/helper function


auth0-cli doesn't adhere to the BROWSER environment variable

when running BROWSER=chromium auth0 login, the signin prompt should open in the specified browser on supported OSes (mac+linux)

Hi @trondhindenes, thanks for raising this. For the use case of opening the login URL in a non-default browser, we'd prefer to go with the solution of adding an option to print the login URL instead of opening a browser.


No sound in some videos

Please follow the guide below

You will be asked some questions and requested to provide some information, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your issue (like that [x])
Use Preview tab to see how your issue will actually look like

WARNING
All invalid issues will be rejected!!

Before going further

If your problem is a bug with youtube-dl or a request for new site support please report it here

Make sure you are using the latest youtube-dl-gui version (Click the Settings icon and then About to view the current version)

Make sure you are using the latest youtube-dl version (Click the Settings icon and then Update to update to the latest youtube-dl version)

Make sure you searched the bugtracker for similar issues including closed ones

Make sure to read the FAQs file

[ ] I think my problem is NOT with youtube-dl
[x] I've verified and i assure that I'm running youtube-dl-gui 0.4
[x] I assure that i am using the latest version of youtube-dl
[x] Searched bugtracker
[x] I've read the FAQs file

What is the purpose of your issue?

[x] Bug report
[ ] Feature request (request for a new functionality)
[ ] Question
[ ] Other

Please remove any sections between (---) if they are not related to your issue

Bug report
If the problem occurs when downloading a URL please provide the full verbose output as follows:

Restart youtube-dl-gui
Go to Options > Extra tab
Enable Debug youtube-dl
Go to Options > Advanced tab and Clear your log content
Try to download the URL
Copy the whole log content and insert it between the ``` part below

[08/07/17 04:04:43] [debug] System config: []
[08/07/17 04:04:43] [debug] User config: []
[08/07/17 04:04:43] [debug] Custom config: []
[08/07/17 04:04:43] [debug] Command-line args: ['--newline', '-i', '-k', '-o', '(my drive here :P)%(title)s.%(ext)s', '-v', '--ignore-config', '--hls-prefer-native', 'https://www.youtube.com/watch?v=xxx :<']
[08/07/17 04:04:43] [debug] Encodings: locale cp1250, fs mbcs, out cp1250, pref cp1250
[08/07/17 04:04:43] [debug] youtube-dl version 2017.08.06
[08/07/17 04:04:43] [debug] Python version 3.4.4 - Windows-10-10.0.15063
[08/07/17 04:04:43] [debug] exe versions: ffmpeg 3.3.2, ffprobe 3.3.2
[08/07/17 04:04:43] [debug] Proxy map: {}
[08/07/17 04:04:43] WARNING: Requested formats are incompatible for merge and will be merged into mkv.
[08/07/17 04:04:52] [debug] System config: []
[08/07/17 04:04:52] [debug] User config: []
[08/07/17 04:04:52] [debug] Custom config: []
[08/07/17 04:04:52] [debug] Command-line args: ['--newline', '-i', '-k', '-o', '(my drive here :P)%(title)s.%(ext)s', '-v', '--ignore-config', '--hls-prefer-native', 'https://www.youtube.com/watch?v=xxx']
[08/07/17 04:04:52] [debug] Encodings: locale cp1250, fs mbcs, out cp1250, pref cp1250
[08/07/17 04:04:52] [debug] youtube-dl version 2017.08.06
[08/07/17 04:04:52] [debug] Python version 3.4.4 - Windows-10-10.0.15063
[08/07/17 04:04:52] [debug] exe versions: ffmpeg 3.3.2, ffprobe 3.3.2
[08/07/17 04:04:52] [debug] Proxy map: {}
[08/07/17 04:04:52] WARNING: Requested formats are incompatible for merge and will be merged into mkv.
[08/07/17 04:05:25] [debug] System config: []
[08/07/17 04:05:25] [debug] User config: []
[08/07/17 04:05:25] [debug] Custom config: []
[08/07/17 04:05:25] [debug] Command-line args: ['--newline', '-i', '-k', '-o', '(my drive here :P)%(title)s.%(ext)s', '-v', '--ignore-config', '--hls-prefer-native', 'https://www.youtube.com/watch?v=xxx']
[08/07/17 04:05:25] [debug] Encodings: locale cp1250, fs mbcs, out cp1250, pref cp1250
[08/07/17 04:05:25] [debug] youtube-dl version 2017.08.06
[08/07/17 04:05:25] [debug] Python version 3.4.4 - Windows-10-10.0.15063
[08/07/17 04:05:25] [debug] exe versions: ffmpeg 3.3.2, ffprobe 3.3.2
[08/07/17 04:05:25] [debug] Proxy map: {}
[08/07/17 04:05:25] WARNING: unable to download video info webpage: HTTP Error 502: Bad Gateway
[08/07/17 04:05:25] WARNING: Requested formats are incompatible for merge and will be merged into mkv.

What operating system do you use ? Windows 10 x64
List of actions to perform to reproduce the problem:

..Re-install
..Re-download
..

What is the expected behaviour ?
What happens instead ?

I don't have sound in some videos and when this is happend i have this in logs [08/07/17 03:53:06] WARNING: Requested formats are incompatible for merge and will be merged into mkv.
Everything is default options.

Looks similar to https://github.com/MrS0m30n3/youtube-dl-gui/issues/223
@CrAvErS do you still have that problem?
The MKV warning should not prevent from having a working audio+video file.

Update your ffmpeg version
Update your media player or use a different one
If you don't want to update just download a different format (e.g. mp4)
Read https://github.com/rg3/youtube-dl/issues/8908 for more informations


Disable Scale Mode Uniform by default.

Disable Scale Mode Uniform by default.
This will add more clarity to graph when we see the curve. If it is enables by default, 2nd and 3rd Graphs looks like a straight line.

@avinasshcm I also feel the same. In coming days, recovery and death is going to be nowhere close to new cases. It makes sense to have uniform turned off.
@jeremyphilemon @JunaidBabu Please review.

I think this is debatable. Ideally, all three curves should be shown on the same graph so that in future we can see recoveries reaching towards the total cases.
Having Uniform scaling on, is closer to that reality. @jeremyphilemon thoughts?

With your close to reality recommendation, people cannot see proper variation in the graph. Please see the attached one.
Scale it not the thing which users see, what makes usability better is what is the variation in number compared to yesterday or day before or week before.

Please refer https://www.worldometers.info/coronavirus/country/india/
They have graphs without uniform scaling.
They have comparison graphs as below which makes more sense for such data. We can also implement that. May be Recovered vs Death in same graph

This is quite simple to implement and more useful for user.

Same thing holds good for this graph too.
Recovered and Deceased is flat.

Once the recovery numbers pick up, won't it be nice to see it peaking :)

Fine, if you want to stick to your so called Close to reality feature. leave it.

If you dont have mindset to understand what graph is, its waste arguing with you.

@avinasshcm thanks for your feedback, I have to back @sudevschiz decision on this, not just on his intention to have it represent something "close to reality", but to have proper design in showing the graphs in the first place.
When you first see the graphs without uniform scaling turned on, there is a significant possibility of misinterpreting the graphs that the deaths are in par with the numbers of confirmed cases. Since both the graphs, without having checked what the y-axis are, look alike.
Your idea of "understanding the graph" is falling short behind not understanding that users may not see the Y-axis as non-uniform on first sight.
Hence, the button. Go ahead and click it for clarity. We wouldn't want to confuse users into thinking that the graphs for death are in scale in with the graphs for confirmed/recovered :)

I agree with @jeremyphilemon that there is a chance of misinterpretation.

Firstly, thanks for your explanation.
Secondly, soon Worldometer is going to implement statewise patient data, and once it comes in, no body will be damn interested in your page. no matter what improvements you give it on your page.

Good Luck guys

To tell you about End user experience, no body will give a damn about what number you display in y-axis scale. the only information they expect is compared to yesterday or day before, what is the change today. whether it is more than yesterday or less than yesterday.

@avinasshcm aww :)


Remove BigBird ONNX support

As per title, refer to the comments in the PR and to https://github.com/huggingface/optimum/issues/754#issuecomment-1429830467 .

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


Add html pages for new bundle

For each solution, copy the index.html page to index-new.html and reference the bundle that has the latest aurelia libraries.  update the sample list to be able to launch either version.

this has been completed.


Feature request: Retire old charts

It would be nice to have a flag that allows to keep only the last x versions of a chart.

@aleerizw I agree! Thanks for opening.

@jdolitsky Thanks for the quick reply! I will take a stab at implementing this.


Russian / plural forms support

Hi,
Our iOS app uses FormatterKit and we're in the process of localizing it to Russian. As you may know, pluralization rules in Russian go beyond the simple distinction between one and many – there's a form that should apply to 'few' (~ 2, 3). We're getting the messages translated right now and this is a point of contention with our translators.
Could you add support for multiple plural forms and, more broadly, for Russian in FormatterKit?
For the record, we're also getting FormatterKit messages translated in several other languages, including Japanese and Chinese. Ultimately, we'd like to channel those translations (currently in our fork) back to your project but I'm assuming engineering work is needed to actually make the formatters use these.

This issue is definitely not resolved. TTTTimeIntervalFormatter doesn't work for Russian language (and maybe others similar) and this is not a localization problem :(


Prevent text selection in editor when dragging splitPane divider.

Hoping this fixes #1632, preventing the selection of text in the editor when the split pane divider is moved.
Also, I noted that someone else has commented out a unFocus method that I think had the same goal.  I uncommented it and tried it, and was still able to get a selection.  I commented it out again and left it in this branch for now, but I can remove it with another commit before this gets merged (if it does).

Ok, I can't seem to replicate the error either so I assume this is good enough. I'll merge it.


[WIP] Fix anchor scrolling issue

Signed-off-by: isamrish<EMAIL_ADDRESS>

closing this PR because it is already fixed in https://github.com/openebs/website/pull/261


Remove template and data add/view commands

add commands are useless, we can just use the edit commands and open the whole directory in an editor and add/edit/remove whatever.

Let's just outright remove the data command, we can do config edit to open the whole config directory in our editor.

Hell, let's remove the template command too.


Add Harmony backend

Can you give some more information? What is Harmony?

Can you give some more information? What is Harmony?

Harmony is a new-ish chat protocol being developed at https://github.com/harmony-development

opening a new one


Example not updated for 1.2.0 Data node

Problem description
The example code https://github.com/nlpsandbox/nlpsandbox-client/blob/main/examples/push_dataset.py has not been updated to support the 1.2.0 data node textPhysicalAddressAnnotations is still referenced. instead of TextLocationAnnotation

@thomasyu888 Also, what about making the example code using the "sdk" client?

@tschaffter The example code does use the nlpsandbox client.


Return values

I'm running this from an automation python script which always gets the same return value (0) whether the submission passed or failed, this could be as a result of running it through the JVM? does the program return the success of the submission?

Hum I didn't setup any return code relative to the submission status. I
just print the result in stdin. But that makes senses, I will update it
today.
Le vendredi 29 avril 2016, vetlzerdoron<EMAIL_ADDRESS>a écrit :

I'm running this from an automation python script which always gets the
same return value (0) whether the submission passed or failed, this could
be as a result of running it through the JVM? does the program return the
success of the submission?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/Faylixe/googlecodejam-cli/issues/7

--

Félix Voituret
Research and development engineer
iSmart, SmartLab, Kware
www.ismart.fr http://www.ismart.fr
Phone : +33 6 48 95 75 46, Fax : +33 4 42 24 45 78

Push a new release v1.3.2, Error code -1 has been set for failed execution.

Merci beaucoup, fonctionne très bien


Avoid casting a tsvector column to text and back again.

When you have a tsvector column but want to search against both it and other text columns (without having to deal with triggers) the :tsvector_column option is no use as it causes everything in :against to be ignored. Also since a column's type is available I don't see why the need to specify something as a tsvector column. This change allows you to simply pass column names to :against, and if any of those are tsvectors then they will be used directly, otherwise they will be converted to tsvectors as before.

My data set is over 900 records and as well as the document I search 4 additional small text fields, also there is an postgres gin index being used. On a query that matched just 4 results the time improved from 40ms to 3ms. And on a query that matched 397 results the time improved from over 3000ms to 60ms.

I think this essentially solves the problem that the :tsvector_column option tries to solve, but automatically. It takes the columns in :against and if they are a tsvector it does not cast them (to text, and back to tsvector). I think the only slight difference is that with this commit the column will still be coalesced with "".
Here's what the relevant part of an example query looks like:
setweight(to_tsvector('english', coalesce("documents"."title"::text, '')), 'A') || setweight(to_tsvector('english', coalesce("documents"."author"::text, '')), 'B') || setweight(coalesce("documents"."content_tsv", ''), 'C')

Thanks for reading, if this is something you'll consider merging here are a couple of followup questions.
If you agree that this renders the :tsvector_column option obsolete is it worth removing that feature as part of this PR?
Do the changes here apply to either trigram or dmetaphone searching? I don't use those but would look at improving them too if the changes are relevant.

This was #247, but I needed it to point to a new branch on my fork.

+1'ing this pull request, also it would be nice to make it work in associated_against columns too.


Added ASCII fast path in std.utf.byUTF

@9il @DmitryOlshansky

please benchmarks with combination with previous one PR

Just tested it, still slower and with no noticeable difference in speed.
Hmm, I'm looking at the profile output and I don't see what could be causing the 8x slower speeds.

maybe inlining bug?

I don't think so, but I am a novice at assembly. I found LDC's out put of the function, but I don't see it a call for it anywhere, so I guess it was inlined at every call point

Ok, I think I've figured it out. byUTF spends time decoding dchars when toUTF8 correctly skips that step with dstrings.
Will post numbers soon.

Well, that did make the UTF string faster, but I forgot that the ascii string isn't using that code path, so no change :/

Regardless of the other PR, these are two good optimizations that IMO should be pulled.

Fixed test errors

Current coverage is 88.68% (diff: 100%)

Merging #4642 into master will increase coverage by <.01%

@@             master      #4642   diff @@
==========================================
  Files           121        121
  Lines         73827      73833     +6
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits          65471      65477     +6
  Misses         8356       8356
  Partials          0          0

Powered by Codecov. Last update 6db08d3...46594d6

Ping

Ping @9il

please benchmarks with combination with previous one PR

How about starting to include such benchmarks in a special benchmark folder?
This would make it easier for future improvements & also help to prevent regressions.
I believe @burner is envisioning sth. similar with #2995, but we could still start to collect the benchmark script as (a) it comes "for free" (they are already written) and (b) might help to move forward with a future "full-blown" benchmark suite as then already have real scripts and know what functions / features are lacking.
Btw [runtime has already gone a similar way.
(pinging @qznc here as he has written an nice blog post about benchmarking Phobos)

Ping @9il @klickverbot
I think these two optimizations are good to go regardless of the other PR.

@andralex Thanks!


add more detailed error messages for invalid #[wasm_bindgen] invocations

Allows this code:
#[wasm_bindgen(readonly)]
pub fn a() {}

#[wasm_bindgen(js_name)]
pub fn b() {}

#[wasm_bindgen(a = b)]
pub fn c() {}

#[wasm_bindgen(js_name = 1)]
pub fn d() {}

#[wasm_bindgen(version = "1", version = "2")]
extern {}

To produce this:
error: attribute is not available in this context
  --> src/lib.rs:15:16
   |
15 | #[wasm_bindgen(readonly)]
   |                ^^^^^^^^
   |
   = help: attribute "readonly" is not allowed before exported function

error: attribute "js_name" requires a value
  --> src/lib.rs:18:16
   |
18 | #[wasm_bindgen(js_name)]
   |                ^^^^^^^

error: unrecognized attribute "a"
  --> src/lib.rs:21:16
   |
21 | #[wasm_bindgen(a = b)]
   |                ^

error: failed to parse value for attribute "js_name"
  --> src/lib.rs:24:26
   |
24 | #[wasm_bindgen(js_name = 1)]
   |                          ^
   |
   = help: expected ident

error: duplicate attribute "version"
  --> src/lib.rs:27:31
   |
27 | #[wasm_bindgen(version = "1", version = "2")]
   |                               ^^^^^^^^^^^^^

error: aborting due to 5 previous errors

I added #[cfg(feature = "spans")] before each error message, but I'm not sure if that is enough to make it work with the stable compiler. Would it be better to create a type that imitates the unstable Diagnostic type but that can be used without the span API?

True! Ideally though I think we'd have a method that doesn't involve adding #[cfg] on all APIs but instead is what you're thinking, imitating the diagnostic apis but can be used without spans.
That also allows us to decouple the spans feature from this feature, which I think are pretty separable.

I'm going to close this because I don't want to work on it and it might be a better idea to wait until this API is finalized anyway.


[backport] Windows: Skip failing cuDNN tests

Backport of #4893

[automatic post] Jenkins, test this please.

Jenkins CI test (for commit 2965f7008e0b9c7cf653f2d8851830070e87d45d, target branch v8) succeeded!


Colors inverted for all themes

Whenever I use any of the themes, the colors are completely inverted from what is shown in the example photos. Top is what I'm getting and the bottom is the expected.

https://github.com/khanhas/spicetify-cli/issues/217


Git docs

Fixes the docs portion of https://github.com/pachyderm/pachyderm/issues/1261

@dwhitena is this ready for review / merge? If so you should generally assign it to someone and ping them for a review. I just took a look at this one and it all LGTM so you can go ahead and merge once CI is pasing.

@jdoliner Thanks.  Good to know.  I will assign someone from now on.  It should be ready to merge.  CI was passing, I think I just need to re-run it.


Add configurable static file path

Closing, as https://github.com/contolini/dash/pull/6 negates the need for these changes

j/k


Point GitHub workflow Node version to .nvmrc

Current dependencies on/for this PR:

master

PR #237   👈

This comment was auto-generated by Graphite.


⚠ GitLab Server has degraded performance

In 8d1300a, GitLab Server (https://gitlab01.its-telekom.eu) experienced degraded performance:

HTTP code: 200
Response time: 6310 ms

Resolved: GitLab Server performance has improved in 0ce73fa.


DWARF information in Go ELF exe causes problems for Auto-Analysis

Describe the bug
After Auto-Analyzing an x86_64 ELF Go executable (the Hello World program from https://gobyexample.com/hello-world), several error messages are displayed (see the 'Additional Context' section below)
To Reproduce
Steps to reproduce the behavior:

Follow the steps on https://gobyexample.com/hello-world to compile the hello-world executable
Import into Ghidra and auto-analyze with default options

Expected behavior
I'm not sure... IDA also has problems parsing some of the DWARF header information in compiled Go executables, and from talking with their support team, Go doesn't seem to strictly follow the DWARF specification.  I can provide a more specific, detailed example of this from another executable if you'd like.
Regardless, the 'MemoryAccessException' sounds kinda like a NULL-pointer exception, so I figured I'd report this as a bug just in case.  It'd be awesome to have Ghidra handle parsing the unusual DWARF information from Go binaries, but that is more of a feature request.  :)
Screenshots
N/A
Environment (please complete the following information):

OS: Ubuntu 18.04 x86_64

Additional context
Skipping DWARF import because a precondition was not met:
Found cross-compilation unit references between DIE records, but 'preload' is not turned on
Manually re-run the DWARF analyzer after adjusting the options or start it via Dwarf_ExtractorScript
Error analyzing GCC DebugFrame exception tables
ghidra.program.model.mem.MemoryAccessException: Unable to read bytes at OTHER:00000000
Demangle Symbol> Unable to demangle symbol at 00401000; name: sync/atomic.(*Value).Store.  Message: Name is null or empty!
Demangle Symbol> Unable to demangle symbol at 00404700; name: runtime.(*waitq).dequeue.  Message: Name is null or empty!
Demangle Symbol> Unable to demangle symbol at 00404870; name: runtime.(*cpuProfile).add.  Message: Name is null or empty!
Demangle Symbol> Unable to demangle symbol at 004049a0; name: runtime.(*cpuProfile).addNonGo.  Message: Name is null or empty!
...
Demangle Symbol> Unable to demangle symbol at 004788d0; name: reflect.(*ptrType).FieldByIndex.  Message: Name is null or empty!
Demangle Symbol> Unable to demangle symbol at 00478910; name: reflect.(*ptrType).FieldByName.  Message: Name is null or empty!

There were too many messages to display.
77 messages have been truncated.

Are you using go 1.12 to produce the binaries?
In the release notes of go 1.12:

There have been many improvements to the DWARF debug information produced by the compiler, including improvements to argument printing and variable location information.

@odiferousmint I was using 1.10.4, but building with go 1.12 causes similar issues

Ouch. No luck then, sorry. :/

I tried reproducing this but couldn't.  I used go 1.12.7 on Ubuntu to produce an ELF, and tried importing/analyzing with default options in Ghidra 9.0, 9.0.4, and current master.

@ryanmkurtz I verified that I still get these messages after autoanalysis in Ghidra 9.0.4, but my machine has go 1.10.4, so maybe that's what is causing the differences.  My hello-world binary is attached.
hello-world.tar.gz

Looks like the exception is actually due to a problem in the GccExceptionAnalyzer.

@recvfrom What happens if you turn on the preloading (the very last option for DWARF auto-analysis) like the error says you should?

@recvfrom
I just tried a hello-world type Go program with Ghidra, and did not get any errors. Regarding the "Unable to demangle symbol errors", the Demangler option for auto-analysis has two sub-options, the latter is something like "Only demangle known mangled symbols". Checking that sub-option should prevent those errors.
(I used Go 1.13.8.)
Also note that there is a Ghidra extension for Go: https://github.com/felberj/gotools, possibly it also can somewhat improve Go analysis.

Closing this due to inactivity for now; it can be reopened if needed.
FWIW, I tried this using the current Ghidra master and Go 1.15 and was able to import/analyze with no errors (default settings).


Regenerate gapic clients, add IoT and Web Security Scanner clients

Also remove beta packages for dlp, as they are removed from googleapis. IoT packages were moved from cloudiot to just iot.

@garrettjonesgoogle PTAL

@garrettjonesgoogle PTAL


DrawString isn't working

DrawString does not draw anything for me, do i have to load a font? Does it have a default font? I tried loading a font but it didn't help. All i'm doing is a basic ctx.DrawString("some string", 16, 16)

Are you setting the color first? Did you try the text examples from the examples directory?

@fogleman the text example worked (commented the font part), not sure what was i doing different, i think it was the color, also what font is gg using by default? and how can you change the text size to be bigger?

@fogleman are you alive? I still need help on how to change font size, I'm going to work on my project again soon and really need this.

Nevermind


Rename Projection matrix to columns

Same as #60627 but for Projection.
This breaks compatibility with third-party modules, but this is otherwise not exposed.
Alternative to one of the shadowed variable renames in #66808.

Thanks!


[$500] Settings - Using deep link, admin can request money to user workspace chat even though its not allowed

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Open the app
Open settings->workspaces->any workspace-> members->invite any member
Open the new chat created between workspace and user added in step 2
Click plus and observe that request money is not present as we are admin
In the URL, replace '/r/' with '/request/new/' and observe that it allows to open request money page
Complete the process and observe that app raises a request

Expected Result:
App should display 'Hmm its not here' page for request money by deep link by admin in workspace chat as request money option is not available for admin
Actual Result:
App allows to request money by deep link by admin in workspace chat even though request money option is not available for admin
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[x] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: v1.3.61-3
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/115492554/bd1189fd-151c-429a-b57b-d976626d65d9
https://github.com/Expensify/App/assets/115492554/c19de3ee-768d-4c47-be61-c2971efc939a
Expensify/Expensify Issue URL:
Issue reported by: @Dhanashree-Sawant
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1692943365255729
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01fea0f36079525f3d
Upwork Job ID:<PHONE_NUMBER>503803392
Last Price Increase: 2023-09-04

Proposal
Please re-state the issue
The request money deep link has no checks to ensure that the action is allowed or not.
What is the root cause of this issue?
The request money page MoneyRequestSelectorPage has no logic to check if the requesting action is allowed for the particular report.
What changes should be made in order to fix this?
We already have a method called ReportUtils.getMoneyRequestOptions() which returns the valid money request options for a particular report that we are using in the + button in the composer to display valid options.
https://github.com/Expensify/App/blob/c16995257c738761206ea07645e863ee717ecbc0/src/libs/ReportUtils.js#L2977-L2996
We should use this function in MoneyRequestSelectorPage as well. Since, we are already using FullScreenNotFoundView in the page already:
https://github.com/Expensify/App/blob/c16995257c738761206ea07645e863ee717ecbc0/src/pages/iou/MoneyRequestSelectorPage.js#L90

We need to check if the passed iouType is allowed for the current report. Therefore, we should modify the condition to the following:

const isInvalid = !IOUUtils.isValidMoneyRequestType(iouType) || (props.report && !_.includes(ReportUtils.getMoneyRequestOptions(props.report, reportParticipantIDs, props.betas), iouType));
...
<FullPageNotFoundView shouldShow={isInvalid}>

We also need to pass the reportParticipantIDs so we can add that to the body of the component as a memo:

const reportParticipantIDs = useMemo(
    () => _.without(lodashGet(props.report, 'participantAccountIDs', []), props.currentUserPersonalDetails.accountID),
    [props.currentUserPersonalDetails.accountID, props.report],
);

To get the relevant parameters for getMoneyRequestOptions(), we can modify the HOCs and add some properties to the withOnyx HOC as well as add the withCurrentUserPersonalDetails HOC, like this:

export default compose(
    withCurrentUserPersonalDetails,
    withOnyx({
        selectedTab: {
            key: `${ONYXKEYS.SELECTED_TAB}_${CONST.TAB.RECEIPT_TAB_ID}`,
        },
        report: {
            key: ({route}) => `${ONYXKEYS.COLLECTION.REPORT}${route.params.reportID}`,
        },
        betas: {
            key: ONYXKEYS.BETAS,
        }
    })
)(MoneyRequestSelectorPage);

@ntdiary I think a combination of backend and frontend are required. This is how we handled the issue of accessing things like workspace settings for non-admins. Like in this issue: https://github.com/Expensify/App/issues/22013

if there are other normal flows that would cause a user to hit this issue?

I appreciate it's not a normal flow but given the world of finance, these are the sort of back doors you want to shore up, so let's fix it. If it is on the back end as well, I'll assign the internal label.

Hey @pecanoro - similar to this issue here, we believe that this requires a fix on both the back end and front end - so not sure if you want to take care of both or just the back end?

Can someone summarize what I need to block on the back-end? Blocking admins from making money requests on workspace chats?

@ntdiary In that case, we can subscribe to the ONYXKEYS.SESSION in the withOnyx HOC and access accountID like this: props.session.accountID
Infact, this is how we are getting the accountID in the currentUserPersonalDetails HOC

Asked internally because I am not sure what's the current behavior

Ok, figured this out, I am going to move to weekly so I can take care of this bug during the week but it's not extremely urgent. Once we have the back-end fix, we can implement the front-end ones.

Actually moving to weekly

Ok, figured this out, I am going to move to weekly so I can take care of this bug during the week but it's not extremely urgent. Once we have the back-end fix, we can implement the front-end ones.

@pecanoro why not do them in parallel? Because I don't this the front end PR will interfere with the backend one in any way...

@pecanoro - what's happening here?

@ntdiary Would like to hear your thoughts as to if we can proceed with frontend and backend simultaneously

Basically if we proceed with both there is a high chance that I will forget to fix it in the back-end since I currently have a high amount of workload. But sure, let's try both at the same time, though I don't think I can handle this until next week.

@ntdiary Was there any approved proposal?

Oh, sounds like we're holding this issue then?

@ntdiary I am not sure if that thread ended up agreeing on a path forward. Am I missing something?

Where did we end up here @ntdiary?

(Sorry, Im out in the depths of Indonesia and wifi is verrrry slow)

If they ask why, just say that there have not been sufficient funds over the last three months, and they have had negative days in balance. We cannot give more specifics than that, as we don't want to give away our risk protection mechanism!

Coming from here: https://github.com/Expensify/App/issues/29367#issuecomment-1759919616 we also want to prevent send money in group chat or other flows except global create and DM 1:1.

@ntdiary I think Tim closed the discussion here with a good proposal to move forward, do you think we could apply to this problem as well?

Ahh got it, I will put in on hold as well/

Issue not reproducible during KI retests. (First week)

I see that requesting money seems to be available now for admins both ways (using the + and the link), so should it actually be allowed? I am confused about what's the desired behavior. @sophiepintoraetz Can you maybe bring it up in Slack? It seems admins can request money just fine like anyone else.

Yes, I am going to close this issue out - Admins will be able to request money as a part of the invoicing/bill pay flow we are building.


move-or-copy-files 0.0.1

New Pull Request Checklist
Please mark the points which you did / accept.

[x] I read the Step Development Guideline
[x] I have a test for my Step, which can be run with bitrise run test (in the step's repository)
[x] I did run bitrise run audit-this-step (in the step's repository - note, if you don't have this workflow in your bitrise.yml, you can copy it from the step template.)
[x] I read and accept the Abandoned Step policy

Hi @Dave005 and thanks for the Step! ;)
The step's code seems 👍  but please fix the things I listed above. Important: please do NOT remove the existing tag/version, simply do the changes and create a new version of the step (e.g. 0.0.2) and then submit that version in a new PR
If you have any questions just let us know!


GitHub Pages

Is your feature request related to a problem?
Introduce GitHub pages to this repo
Describe the solution to the problem
No response
Describe the uses cases for the feature
No response
Additional details
No response

closed by #8


How to pass custom/new information to current peers?

For example, I want to inform current peers of a new infohash for an updated file. Is there a way to send extra data to the peers currently connected?

There's no way of currently doing that in WebTorrent, but could be done with protocol extensions I suppose.

I found this conversation which talks about sending messages using a protocol extension: https://github.com/feross/webtorrent/issues/368 Time to do some homework on extensions


Compilation options of a multi-output model: multiple losses & loss weighting

As described in the Keras handbook -Deep Learning with Pyhton-, for a multi-output model we need to specify different loss functions for different heads of the network. But because gradient descent requires you to minimize a scalar, you must combine these losses into a single value in order to train the model.
Very imbalanced loss contributions will cause the model representations to be optimized preferentially for the task with the largest individual loss, at the expense of the other tasks. To remedy this, you can assign different levels of importance to the loss values in their contribution to the final loss. This is useful in particular if the losses’ values use different scales.
Can anyone help with the following:
I've got a five-output model as described in #10120.
The outputs of the model are the following:

emotion (multiclass, multilabel classification)
valence (regression)
arousal (regression)
dominance (regression)
age (multiclass classification)

I am using the following :
    losses_list = {'EMOTIONS': 'binary_crossentropy',
                   'VALENCE': 'mse',
                   'AROUSAL': 'mse',
                   'DOMINANCE': 'mse',
                   'AGE': 'categorical_crossentropy'}

    losses_weights = {'EMOTIONS': 1.0,
                      'VALENCE': 0.025,
                      'AROUSAL': 0.025,
                      'DOMINANCE': 0.025,
                      'AGE': 0.45}

    metrics ={'EMOTIONS': 'crossentropy',
              'VALENCE': 'mse',
              'AROUSAL': 'mse',
              'DOMINANCE': 'mse',
              'AGE': 'categorical_accuracy'}

Can anyone comment on this ?
Are those the right loss functions? Are those the right weights and are those metrics properly set?

7900/60000 [==>...........................] - ETA: 44s - loss: 1.6085 - classification_loss: 1.3906 - autoencoder_loss: 0.4358 - classification_acc: 0.5711 - autoencoder_mean_squared_error: 0.1194

Many thanks for that @brge17.
Can you please elaborate on
loss_weights={'classification': 1.0, 'autoencoder': 0.5}

and how you've chosen those weights (floats) ?
Also why  do you use 2 metrics for the autoencoder?
metrics={'classification': 'accuracy', 'autoencoder': ['binary_crossentropy', 'mse']}

It's a toy problem, the loss weights are meaningless but show you how to use them.
Same with the metrics, just showing you how to use them.

hello,
i want to train a model to predict heatmap (mean square error loss) and binary segmentation (binary cross entropy loss).
i tried to train model using multi branch (2 branch duplicates for 2 output). but the the final output will favour for only one type of output.
For example when i train using model.fit with equal loss weights, the output is good for heatmap, but binary mask output is wrong and gives pixels 1 for the regions similar to heatmaps.
And when i train using gradtape loop, the output is good for segmentation mask, but heatmaps are wrong and looks like masks.
how can i solve this, please give me your suggestion.
thank you

@soans1994 Any updates on this issue? I am too facing the same issue

@g-jindal2001
apparently we cannot train model for 2 entirely different tasks like heatmaps and binary mask since the weights cannot learn 2 different tasks.
In my case , i used 2 outputs at the end of the model by using 2 final dense layers like below. this is wrong since all weights are shared for these 2 outputs. and cannot learn both. Note at the end both output and output2 takes x (same branch data)
from tensorflow.keras.layers import Input, concatenate, Dense, Flatten, BatchNormalization, Dropout, ReLU, Conv2D, Reshape, MaxPooling2D, Conv2DTranspose
from tensorflow.keras.models import Model, Sequential
from tensorflow.keras.applications.vgg16 import VGG16, preprocess_input
import tensorflow as tf
from tensorflow.keras.regularizers import l2

input_shape = (256,256,3)
Nkeypoints = 15

def model(input_shape):
    H = input_shape[0]
    W = input_shape[1]
    def downsample_block(x, block_num, n_filters, pooling_on=True):

        x = Conv2D(n_filters, kernel_size=(3, 3), strides=1, padding='same', activation='relu',
                   name="Block" + str(block_num) + "_Conv1")(x)
        x = Conv2D(n_filters, kernel_size=(3, 3), strides=1, padding='same', activation='relu',
                   name="Block" + str(block_num) + "_Conv2")(x)
        skip = x

        if pooling_on is True:
            x = MaxPooling2D(pool_size=(2, 2), strides=2, padding='valid', name="Block" + str(block_num) + "_Pool1")(x)

        return x, skip

    def upsample_block(x, skip, block_num, n_filters):

        x = Conv2DTranspose(n_filters, kernel_size=(2, 2), strides=2, padding='valid', activation='relu',
                            name="Block" + str(block_num) + "_ConvT1")(x)
        x = concatenate([x, skip], axis=-1, name="Block" + str(block_num) + "_Concat1")
        x = Conv2D(n_filters, kernel_size=(3, 3), strides=1, padding='same', activation='relu',
                   name="Block" + str(block_num) + "_Conv1")(x)
        x = Conv2D(n_filters, kernel_size=(3, 3), strides=1, padding='same', activation='relu',
                   name="Block" + str(block_num) + "_Conv2")(x)

        return x

    input = Input(input_shape, name="Input")

    # downsampling
    x, skip1 = downsample_block(input, 1, 64)
    x, skip2 = downsample_block(x, 2, 128)
    x, skip3 = downsample_block(x, 3, 256)
    x, skip4 = downsample_block(x, 4, 512)
    x, _ = downsample_block(x, 5, 1024, pooling_on=False)

    # upsampling
    x = upsample_block(x, skip4, 6, 512)
    x = upsample_block(x, skip3, 7, 256)
    x = upsample_block(x, skip2, 8, 128)
    x = upsample_block(x, skip1, 9, 64)

    output = Conv2D(17, kernel_size=(1, 1), strides=1, padding='valid', activation='linear', name="output")(x)#heatmap
    output2 = Conv2D(1, kernel_size=(1, 1), strides=1, padding='valid', activation='sigmoid', name="output2")(x)  # binary mask
    model = Model(inputs=input, outputs=[output, output2], name="Output")
    model.summary()
    return model
if __name__=="__main__":
    model(input_shape)

So, we have to build 2 branches same as first one. 2 branches weights to learn 2 different task and finally concatenate outputs.
note at the end output and output2 takes x and xx resepectivly.
from tensorflow.keras.layers import Input, concatenate, Dense, Flatten, BatchNormalization, Dropout, ReLU, Conv2D, Reshape, MaxPooling2D, Conv2DTranspose
from tensorflow.keras.models import Model, Sequential
from tensorflow.keras.applications.vgg16 import VGG16, preprocess_input
import tensorflow as tf
from tensorflow.keras.regularizers import l2

input_shape = (256,256,3)
Nkeypoints = 15

def model(input_shape):
    H = input_shape[0]
    W = input_shape[1]
    def downsample_block(x, block_num, n_filters, pooling_on=True):

        x = Conv2D(n_filters, kernel_size=(3, 3), strides=1, padding='same', activation='relu',
                   name="Block" + str(block_num) + "_Conv1")(x)
        x = Conv2D(n_filters, kernel_size=(3, 3), strides=1, padding='same', activation='relu',
                   name="Block" + str(block_num) + "_Conv2")(x)
        skip = x

        if pooling_on is True:
            x = MaxPooling2D(pool_size=(2, 2), strides=2, padding='valid', name="Block" + str(block_num) + "_Pool1")(x)

        return x, skip

    def upsample_block(x, skip, block_num, n_filters):

        x = Conv2DTranspose(n_filters, kernel_size=(2, 2), strides=2, padding='valid', activation='relu',
                            name="Block" + str(block_num) + "_ConvT1")(x)
        x = concatenate([x, skip], axis=-1, name="Block" + str(block_num) + "_Concat1")
        x = Conv2D(n_filters, kernel_size=(3, 3), strides=1, padding='same', activation='relu',
                   name="Block" + str(block_num) + "_Conv1")(x)
        x = Conv2D(n_filters, kernel_size=(3, 3), strides=1, padding='same', activation='relu',
                   name="Block" + str(block_num) + "_Conv2")(x)

        return x

    def downsample_block2(x, block_num, n_filters, pooling_on=True):

        x = Conv2D(n_filters, kernel_size=(3, 3), strides=1, padding='same', activation='relu',
                   name="Block2" + str(block_num) + "_Conv1")(x)
        x = Conv2D(n_filters, kernel_size=(3, 3), strides=1, padding='same', activation='relu',
                   name="Block2" + str(block_num) + "_Conv2")(x)
        skip = x

        if pooling_on is True:
            x = MaxPooling2D(pool_size=(2, 2), strides=2, padding='valid', name="Block2" + str(block_num) + "_Pool1")(x)

        return x, skip

    def upsample_block2(x, skip, block_num, n_filters):

        x = Conv2DTranspose(n_filters, kernel_size=(2, 2), strides=2, padding='valid', activation='relu',
                            name="Block2" + str(block_num) + "_ConvT1")(x)
        x = concatenate([x, skip], axis=-1, name="Block2" + str(block_num) + "_Concat1")
        x = Conv2D(n_filters, kernel_size=(3, 3), strides=1, padding='same', activation='relu',
                   name="Block2" + str(block_num) + "_Conv1")(x)
        x = Conv2D(n_filters, kernel_size=(3, 3), strides=1, padding='same', activation='relu',
                   name="Block2" + str(block_num) + "_Conv2")(x)

        return x

    input = Input(input_shape, name="Input")

    # downsampling
    x, skip1 = downsample_block(input, 1, 64)
    x, skip2 = downsample_block(x, 2, 128)
    x, skip3 = downsample_block(x, 3, 256)
    x, skip4 = downsample_block(x, 4, 512)
    x, _ = downsample_block(x, 5, 1024, pooling_on=False)

    # upsampling
    x = upsample_block(x, skip4, 6, 512)
    x = upsample_block(x, skip3, 7, 256)
    x = upsample_block(x, skip2, 8, 128)
    x = upsample_block(x, skip1, 9, 64)
######################################################
    # downsampling seg
    xx, sskip1 = downsample_block2(input, 1, 64)
    xx, sskip2 = downsample_block2(xx, 2, 128)
    xx, sskip3 = downsample_block2(xx, 3, 256)
    xx, sskip4 = downsample_block2(xx, 4, 512)
    xx, _ = downsample_block2(xx, 5, 1024, pooling_on=False)

    # upsampling seg
    xx = upsample_block2(xx, sskip4, 6, 512)
    xx = upsample_block2(xx, sskip3, 7, 256)
    xx = upsample_block2(xx, sskip2, 8, 128)
    xx = upsample_block2(xx, sskip1, 9, 64)

    output = Conv2D(17, kernel_size=(1, 1), strides=1, padding='valid', activation='linear', name="output")(x)#heatmap
    output2 = Conv2D(1, kernel_size=(1, 1), strides=1, padding='valid', activation='sigmoid', name="output2")(xx)  # mask
    model = Model(inputs=input, outputs=[output, output2], name="Output")
    model.summary()
    return model
if __name__=="__main__":
    model(input_shape)


Fixes chrono vulnerability caused by time dependency

Pre-review checklist

[ ] I have split my patch into logically separate commits.
[ ] All commit messages clearly explain what they change and why.
[ ] I added relevant tests for new features and bug fixes.
[ ] All commits compile, pass static checks and pass test.
[ ] PR description sums up the changes and reasons why they should be introduced.
[ ] I have provided docstrings for the public items that I want to introduce.
[ ] I have adjusted the documentation in ./docs/source/.
[ ] I added appropriate Fixes: annotations to PR description.

Thanks for your contribution!
nit: 'Fixes #722 ' is missing from the commit message.


Reintroduced old fixed bug: Changes to workflow semaphore seems not to trigger reload semaphore state in workflow-controller?

Pre-requisites

[X] I have double-checked my configuration
[X] I can confirm the issues exists when I tested with :latest
[ ] I'd like to contribute the fix myself (see contributing guide)

What happened/what you expected to happen?
Three years ago we reported issue #4327 which also were fixed in release v2.12.0.
Later we were running v3.0.1 which is the latest version we know this was working as we expected and later we upgraded to v3.4.3 which is the version we found out that this issue is reintroduced. So we don't know for sure which Argo versions this issue is reintroduced.
We have tried latest version v3.5.1 and the issue is still present.
We wonder if this is due to a mistake or a conscious decision to go back to old implementation of the workflow resync period?
Version
v3.5.1
Paste a small workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflows that uses private images.
➜ kubectl apply -f - <<EOF
apiVersion: v1
kind: ConfigMap
metadata:
  name: testsystem-sync
data:
  darksow: "0"
EOF

kubectl apply -f - <<EOF
apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata:
  name: counter
spec:
  entrypoint: counter
  synchronization:
    semaphore:
      configMapKeyRef:
        name: testsystem-sync
        key: darksow
  templates:
  - name: counter
    container:
      image: alpine
      command: ["/bin/sh"]
      args: ["-c", "n=0; while [ $n -lt 60 ]; do echo $n; sleep 1; n=$((n+1));done" ]
      resources:
        limits:
          memory: 32Mi
          cpu: 100m
EOF

Logs from the workflow controller
kubectl logs deployments/argo-argo-workflows-workflow-controller | grep counter
time="2023-11-13T14:35:08.702Z" level=info msg="Processing workflow" namespace=default workflow=counter
time="2023-11-13T14:35:08.719Z" level=info msg="default/ConfigMap/testsystem-sync/darksow acquired by default/counter. Lock availability: 0/1" semaphore=default/ConfigMap/testsystem-sync/darksow
time="2023-11-13T14:35:08.719Z" level=info msg="Updated phase  -> Running" namespace=default workflow=counter
time="2023-11-13T14:35:08.720Z" level=warning msg="Node was nil, will be initialized as type Skipped" namespace=default workflow=counter
time="2023-11-13T14:35:08.720Z" level=info msg="was unable to obtain node for , letting display name to be nodeName" namespace=default workflow=counter
time="2023-11-13T14:35:08.720Z" level=info msg="Pod node counter initialized Pending" namespace=default workflow=counter
time="2023-11-13T14:35:08.746Z" level=info msg="Created pod: counter (counter)" namespace=default workflow=counter
time="2023-11-13T14:35:08.746Z" level=info msg="TaskSet Reconciliation" namespace=default workflow=counter
time="2023-11-13T14:35:08.747Z" level=info msg=reconcileAgentPod namespace=default workflow=counter
time="2023-11-13T14:35:08.762Z" level=info msg="Workflow update successful" namespace=default phase=Running resourceVersion=1042 workflow=counter
time="2023-11-13T14:35:18.746Z" level=info msg="Processing workflow" namespace=default workflow=counter
time="2023-11-13T14:35:18.754Z" level=info msg="Task-result reconciliation" namespace=default numObjs=0 workflow=counter
time="2023-11-13T14:35:18.754Z" level=info msg="node changed" namespace=default new.message=PodInitializing new.phase=Pending new.progress=0/1 nodeID=counter old.message= old.phase=Pending old.progress=0/1 workflow=counter
time="2023-11-13T14:35:18.755Z" level=info msg="TaskSet Reconciliation" namespace=default workflow=counter
time="2023-11-13T14:35:18.755Z" level=info msg=reconcileAgentPod namespace=default workflow=counter
time="2023-11-13T14:35:18.771Z" level=info msg="Workflow update successful" namespace=default phase=Running resourceVersion=1059 workflow=counter
time="2023-11-13T14:35:33.179Z" level=info msg="Processing workflow" namespace=default workflow=counter
time="2023-11-13T14:35:33.250Z" level=info msg="Task-result reconciliation" namespace=default numObjs=0 workflow=counter
time="2023-11-13T14:35:33.250Z" level=info msg="node changed" namespace=default new.message= new.phase=Succeeded new.progress=0/1 nodeID=counter old.message=PodInitializing old.phase=Pending old.progress=0/1 workflow=counter
time="2023-11-13T14:35:33.251Z" level=info msg="TaskSet Reconciliation" namespace=default workflow=counter
time="2023-11-13T14:35:33.251Z" level=info msg=reconcileAgentPod namespace=default workflow=counter
time="2023-11-13T14:35:33.251Z" level=info msg="Updated phase Running -> Succeeded" namespace=default workflow=counter
time="2023-11-13T14:35:33.251Z" level=info msg="Marking workflow completed" namespace=default workflow=counter
time="2023-11-13T14:35:33.252Z" level=info msg="Lock has been released by default/counter. Available locks: 1" semaphore=default/ConfigMap/testsystem-sync/darksow
time="2023-11-13T14:35:33.252Z" level=info msg="default/counter released a lock from default/ConfigMap/testsystem-sync/darksow"
time="2023-11-13T14:35:33.252Z" level=info msg="Released all acquired locks" key=counter namespace=default workflow=counter
time="2023-11-13T14:35:33.257Z" level=info msg="cleaning up pod" action=deletePod key=default/counter-1340600742-agent/deletePod
time="2023-11-13T14:35:33.265Z" level=info msg="Workflow update successful" namespace=default phase=Succeeded resourceVersion=1074 workflow=counter
time="2023-11-13T14:35:33.286Z" level=info msg="cleaning up pod" action=labelPodCompleted key=default/counter/labelPodCompleted
time="2023-11-14T05:05:21.374Z" level=info msg="Processing workflow" namespace=default workflow=counter
time="2023-11-14T05:05:21.378Z" level=info msg="default/ConfigMap/testsystem-sync/darksow acquired by default/counter. Lock availability: 0/1" semaphore=default/ConfigMap/testsystem-sync/darksow
time="2023-11-14T05:05:21.378Z" level=info msg="Updated phase  -> Running" namespace=default workflow=counter
time="2023-11-14T05:05:21.378Z" level=warning msg="Node was nil, will be initialized as type Skipped" namespace=default workflow=counter
time="2023-11-14T05:05:21.379Z" level=info msg="was unable to obtain node for , letting display name to be nodeName" namespace=default workflow=counter
time="2023-11-14T05:05:21.379Z" level=info msg="Pod node counter initialized Pending" namespace=default workflow=counter
time="2023-11-14T05:05:21.388Z" level=info msg="Created pod: counter (counter)" namespace=default workflow=counter
time="2023-11-14T05:05:21.388Z" level=info msg="TaskSet Reconciliation" namespace=default workflow=counter
time="2023-11-14T05:05:21.388Z" level=info msg=reconcileAgentPod namespace=default workflow=counter
time="2023-11-14T05:05:21.397Z" level=info msg="Workflow update successful" namespace=default phase=Running resourceVersion=1529 workflow=counter
time="2023-11-14T05:05:31.392Z" level=info msg="Processing workflow" namespace=default workflow=counter
time="2023-11-14T05:05:31.399Z" level=info msg="Task-result reconciliation" namespace=default numObjs=0 workflow=counter
time="2023-11-14T05:05:31.404Z" level=info msg="node changed" namespace=default new.message= new.phase=Running new.progress=0/1 nodeID=counter old.message= old.phase=Pending old.progress=0/1 workflow=counter
time="2023-11-14T05:05:31.405Z" level=info msg="TaskSet Reconciliation" namespace=default workflow=counter
time="2023-11-14T05:05:31.405Z" level=info msg=reconcileAgentPod namespace=default workflow=counter
time="2023-11-14T05:05:31.409Z" level=info msg="cleaning up pod" action=terminateContainers key=default/counter/terminateContainers
time="2023-11-14T05:05:31.422Z" level=info msg="Workflow update successful" namespace=default phase=Running resourceVersion=1552 workflow=counter
time="2023-11-14T05:05:41.852Z" level=info msg="Processing workflow" namespace=default workflow=counter
time="2023-11-14T05:05:41.856Z" level=info msg="Task-result reconciliation" namespace=default numObjs=0 workflow=counter
time="2023-11-14T05:05:41.856Z" level=info msg="node changed" namespace=default new.message= new.phase=Succeeded new.progress=0/1 nodeID=counter old.message= old.phase=Running old.progress=0/1 workflow=counter
time="2023-11-14T05:05:41.856Z" level=info msg="TaskSet Reconciliation" namespace=default workflow=counter
time="2023-11-14T05:05:41.856Z" level=info msg=reconcileAgentPod namespace=default workflow=counter
time="2023-11-14T05:05:41.856Z" level=info msg="Updated phase Running -> Succeeded" namespace=default workflow=counter
time="2023-11-14T05:05:41.856Z" level=info msg="Marking workflow completed" namespace=default workflow=counter
time="2023-11-14T05:05:41.856Z" level=info msg="Lock has been released by default/counter. Available locks: 1" semaphore=default/ConfigMap/testsystem-sync/darksow
time="2023-11-14T05:05:41.856Z" level=info msg="default/counter released a lock from default/ConfigMap/testsystem-sync/darksow"
time="2023-11-14T05:05:41.856Z" level=info msg="Released all acquired locks" key=counter namespace=default workflow=counter
time="2023-11-14T05:05:41.861Z" level=info msg="Workflow update successful" namespace=default phase=Succeeded resourceVersion=1561 workflow=counter
time="2023-11-14T05:05:41.862Z" level=info msg="cleaning up pod" action=deletePod key=default/counter-1340600742-agent/deletePod
time="2023-11-14T05:05:41.872Z" level=info msg="cleaning up pod" action=labelPodCompleted key=default/counter/labelPodCompleted
time="2023-11-14T05:06:01.409Z" level=info msg="cleaning up pod" action=killContainers key=default/counter/killContainers
time="2023-11-14T05:07:11.188Z" level=info msg="Processing workflow" namespace=default workflow=counter
time="2023-11-14T05:07:11.192Z" level=warning msg="Workflow processing has been postponed due to concurrency limit" namespace=default workflow=counter
time="2023-11-14T05:07:11.192Z" level=info msg="Updated phase  -> Pending" namespace=default workflow=counter
time="2023-11-14T05:07:11.192Z" level=info msg="Updated message  -> Waiting for default/ConfigMap/testsystem-sync/darksow lock. Lock status: 0/0" namespace=default workflow=counter
time="2023-11-14T05:07:11.197Z" level=info msg="Workflow update successful" namespace=default phase=Pending resourceVersion=1615 workflow=counter
time="2023-11-14T05:27:11.189Z" level=info msg="Processing workflow" namespace=default workflow=counter
time="2023-11-14T05:27:11.196Z" level=warning msg="Workflow processing has been postponed due to concurrency limit" namespace=default workflow=counter
time="2023-11-14T05:27:11.212Z" level=info msg="Workflow update successful" namespace=default phase=Pending resourceVersion=1615 workflow=counter
time="2023-11-14T05:47:11.190Z" level=info msg="Processing workflow" namespace=default workflow=counter
time="2023-11-14T05:47:11.198Z" level=warning msg="Workflow processing has been postponed due to concurrency limit" namespace=default workflow=counter
time="2023-11-14T05:47:11.213Z" level=info msg="Workflow update successful" namespace=default phase=Pending resourceVersion=1615 workflow=counter
time="2023-11-14T06:07:11.192Z" level=info msg="Processing workflow" namespace=default workflow=counter
time="2023-11-14T06:07:11.199Z" level=info msg="default/ConfigMap/testsystem-sync/darksow acquired by default/counter. Lock availability: 0/1" semaphore=default/ConfigMap/testsystem-sync/darksow
time="2023-11-14T06:07:11.199Z" level=info msg="Task-result reconciliation" namespace=default numObjs=0 workflow=counter
time="2023-11-14T06:07:11.199Z" level=info msg="Updated phase Pending -> Running" namespace=default workflow=counter
time="2023-11-14T06:07:11.199Z" level=info msg="Updated message Waiting for default/ConfigMap/testsystem-sync/darksow lock. Lock status: 0/0 -> " namespace=default workflow=counter
time="2023-11-14T06:07:11.199Z" level=warning msg="Node was nil, will be initialized as type Skipped" namespace=default workflow=counter
time="2023-11-14T06:07:11.268Z" level=info msg="was unable to obtain node for , letting display name to be nodeName" namespace=default workflow=counter
time="2023-11-14T06:07:11.269Z" level=info msg="Pod node counter initialized Pending" namespace=default workflow=counter
time="2023-11-14T06:07:11.292Z" level=info msg="Created pod: counter (counter)" namespace=default workflow=counter
time="2023-11-14T06:07:11.292Z" level=info msg="TaskSet Reconciliation" namespace=default workflow=counter
time="2023-11-14T06:07:11.292Z" level=info msg=reconcileAgentPod namespace=default workflow=counter
time="2023-11-14T06:07:11.300Z" level=info msg="Workflow update successful" namespace=default phase=Running resourceVersion=3552 workflow=counter
time="2023-11-14T06:07:21.296Z" level=info msg="Processing workflow" namespace=default workflow=counter
time="2023-11-14T06:07:21.379Z" level=info msg="Task-result reconciliation" namespace=default numObjs=0 workflow=counter
time="2023-11-14T06:07:21.379Z" level=info msg="node changed" namespace=default new.message= new.phase=Succeeded new.progress=0/1 nodeID=counter old.message= old.phase=Pending old.progress=0/1 workflow=counter
time="2023-11-14T06:07:21.379Z" level=info msg="TaskSet Reconciliation" namespace=default workflow=counter
time="2023-11-14T06:07:21.379Z" level=info msg=reconcileAgentPod namespace=default workflow=counter
time="2023-11-14T06:07:21.379Z" level=info msg="Updated phase Running -> Succeeded" namespace=default workflow=counter
time="2023-11-14T06:07:21.380Z" level=info msg="Marking workflow completed" namespace=default workflow=counter
time="2023-11-14T06:07:21.380Z" level=info msg="Lock has been released by default/counter. Available locks: 1" semaphore=default/ConfigMap/testsystem-sync/darksow
time="2023-11-14T06:07:21.380Z" level=info msg="default/counter released a lock from default/ConfigMap/testsystem-sync/darksow"
time="2023-11-14T06:07:21.380Z" level=info msg="Released all acquired locks" key=counter namespace=default workflow=counter
time="2023-11-14T06:07:21.385Z" level=info msg="cleaning up pod" action=deletePod key=default/counter-1340600742-agent/deletePod
time="2023-11-14T06:07:21.389Z" level=info msg="Workflow update successful" namespace=default phase=Succeeded resourceVersion=3575 workflow=counter
time="2023-11-14T06:07:21.401Z" level=info msg="cleaning up pod" action=labelPodCompleted key=default/counter/labelPodCompleted

Logs from in your workflow's wait container
kubectl logs -c wait -l workflows.argoproj.io/workflow=counter,workflow.argoproj.io/phase!=Succeeded
time="2023-11-14T06:07:13.320Z" level=info msg="Starting Workflow Executor" version=v3.5.1
time="2023-11-14T06:07:13.325Z" level=info msg="Using executor retry strategy" Duration=1s Factor=1.6 Jitter=0.5 Steps=5
time="2023-11-14T06:07:13.325Z" level=info msg="Executor initialized" deadline="0001-01-01 00:00:00 +0000 UTC" includeScriptOutput=false namespace=default podName=counter template="{\"name\":\"counter\",\"inputs\":{},\"outputs\":{},\"metadata\":{},\"container\":{\"name\":\"\",\"image\":\"alpine\",\"command\":[\"/bin/sh\"],\"args\":[\"-c\",\"n=0; while [  -lt 60 ]; do echo ; sleep 1; n=1;done\"],\"resources\":{\"limits\":{\"cpu\":\"100m\",\"memory\":\"32Mi\"}}}}" version="&Version{Version:v3.5.1,BuildDate:2023-11-03T18:37:58Z,GitCommit:877c5523066e17687856fe3484c9b2d398e986f5,GitTag:v3.5.1,GitTreeState:clean,GoVersion:go1.21.3,Compiler:gc,Platform:linux/amd64,}"
time="2023-11-14T06:07:13.326Z" level=info msg="Starting deadline monitor"
time="2023-11-14T06:07:18.328Z" level=info msg="Main container completed" error="<nil>"
time="2023-11-14T06:07:18.328Z" level=info msg="No Script output reference in workflow. Capturing script output ignored"
time="2023-11-14T06:07:18.328Z" level=info msg="No output parameters"
time="2023-11-14T06:07:18.328Z" level=info msg="No output artifacts"
time="2023-11-14T06:07:18.328Z" level=info msg="Alloc=7106 TotalAlloc=12866 Sys=24165 NumGC=4 Goroutines=7"
time="2023-11-14T06:07:18.328Z" level=info msg="Deadline monitor stopped"

So the logic does still exist. #11855 (and #11799 before it) are/were improving it as well, but have yet to be approved/merged/released.
It's possible a bug was introduced somewhere in the update code from #4421.
It may be a different issue though; the original PR only watches for changes to the managed namespace (unlike what the comment above that line says). Are your Workflow and ConfigMap in an Argo managed namespace? Or is it in a single namespace? Or in a cluster-wide install? Your workflow-controller-configmap could be useful to see

For the first run for this example we did a cluster wide installation in the default namespace using the following command
helm install argo --set server.authMode=server argo/argo-workflows

and created the workflow in the same default namespace.
After your input we installed Argo in managed namespace mode with the following helm command (after first creating namespace argo and fke-job)
helm -n argo install argo --set server.authMode=server --set "controller.workflowNamespaces[0]=fke-job" --set singleNamespace=false --set controller.extraArgs\[0\]=--namespaced --set controller.extraArgs\[1\]="--managed-namespace=fke-job" argo/argo-workflows

We could actually not notice any difference, we first restored semaphore value to "1" and the job was not started until after 20 minutes.
The workflow-controller-configmap is quite empty and here it is:
k -n argo describe configmaps argo-argo-workflows-workflow-controller-configmap
Name:         argo-argo-workflows-workflow-controller-configmap
Namespace:    argo
Labels:       app.kubernetes.io/component=workflow-controller
              app.kubernetes.io/instance=argo
              app.kubernetes.io/managed-by=Helm
              app.kubernetes.io/name=argo-workflows-cm
              app.kubernetes.io/part-of=argo-workflows
              helm.sh/chart=argo-workflows-0.39.0
Annotations:  meta.helm.sh/release-name: argo
              meta.helm.sh/release-namespace: argo

Data
====
config:
----
nodeEvents:
  enabled: true

BinaryData
====

Events:  <none>

And this is the deployment specification of Argo controller
k -n argo describe deployments.apps argo-argo-workflows-workflow-controller
Name:                   argo-argo-workflows-workflow-controller
Namespace:              argo
CreationTimestamp:      Thu, 16 Nov 2023 10:56:12 +0100
Labels:                 app.kubernetes.io/component=workflow-controller
                        app.kubernetes.io/instance=argo
                        app.kubernetes.io/managed-by=Helm
                        app.kubernetes.io/name=argo-workflows-workflow-controller
                        app.kubernetes.io/part-of=argo-workflows
                        app.kubernetes.io/version=v3.5.1
                        helm.sh/chart=argo-workflows-0.39.0
Annotations:            deployment.kubernetes.io/revision: 1
                        meta.helm.sh/release-name: argo
                        meta.helm.sh/release-namespace: argo
Selector:               app.kubernetes.io/instance=argo,app.kubernetes.io/name=argo-workflows-workflow-controller
Replicas:               1 desired | 1 updated | 1 total | 1 available | 0 unavailable
StrategyType:           RollingUpdate
MinReadySeconds:        0
RollingUpdateStrategy:  25% max unavailable, 25% max surge
Pod Template:
  Labels:           app.kubernetes.io/component=workflow-controller
                    app.kubernetes.io/instance=argo
                    app.kubernetes.io/managed-by=Helm
                    app.kubernetes.io/name=argo-workflows-workflow-controller
                    app.kubernetes.io/part-of=argo-workflows
                    app.kubernetes.io/version=v3.5.1
                    helm.sh/chart=argo-workflows-0.39.0
  Service Account:  argo-argo-workflows-workflow-controller
  Containers:
   controller:
    Image:       quay.io/argoproj/workflow-controller:v3.5.1
    Ports:       9090/TCP, 6060/TCP
    Host Ports:  0/TCP, 0/TCP
    Command:
      workflow-controller
    Args:
      --configmap
      argo-argo-workflows-workflow-controller-configmap
      --executor-image
      quay.io/argoproj/argoexec:v3.5.1
      --loglevel
      info
      --gloglevel
      0
      --log-format
      text
      --namespaced
      --managed-namespace=fke-job
    Liveness:  http-get http://:6060/healthz delay=90s timeout=30s period=60s #success=1 #failure=3
    Environment:
      ARGO_NAMESPACE:             (v1:metadata.namespace)
      LEADER_ELECTION_IDENTITY:   (v1:metadata.name)
    Mounts:                      <none>
  Volumes:                       <none>
Conditions:
  Type           Status  Reason
  ----           ------  ------
  Available      True    MinimumReplicasAvailable
  Progressing    True    NewReplicaSetAvailable
OldReplicaSets:  <none>
NewReplicaSet:   argo-argo-workflows-workflow-controller-69f7fbdd48 (1/1 replicas created)
Events:
  Type    Reason             Age   From                   Message
  ----    ------             ----  ----                   -------
  Normal  ScalingReplicaSet  22m   deployment-controller  Scaled up replica set argo-argo-workflows-workflow-controller-69f7fbdd48 to 1

When this was working for us using Argo workflow v3.0.1 we were using the argo cluster wide install yaml manifest files. After that we were starting to use Helm chart instead for installing Argo workflows v3.4.3. After that we can not get it to work anymore.
First we thought we had installed it incorrectly since we were using cluster wide install even with helm, but in this example we changed to managed namespace install as we described above, but still no success.

We could actually not notice any difference, we first restored semaphore value to "1" and the job was not started until after 20 minutes.

To clarify, you put the Workflow and the semaphore ConfigMap into the fke-job namespace?
If so, then that would suggest the old fix broke again. Whereas if the Workflow and semaphore were in a different namespace, then that may be due to the other issue I mentioned above.

but in this example we changed to managed namespace install as we described above, but still no success.

The simplest reproduction would actually be in single namespace mode, where you run Workflows in the same namespace as your Argo install.

The workflow-controller-configmap is quite empty and here it is:

The only thing I see here that may be off is that the ConfigMaps's namespace field isn't specified. But I believe the flag is the main one that is used... I'll need to double-check the code

Yes semaphore ConfigMap and the workflow are in the fke-job namespace.

I first edit the ConfigMap, set semaphore value to 0
Create the workflow which are put in pending state since semaphore is 0
Edit ConfigMap, restore semaphore value back to 1

But workflow wont start until around 20 min later.
I also did single namespace install with:
helm -n argo install argo --set server.authMode=server --set singleNamespace=true argo/argo-workflows

but the issue are there as well.

I think it relates to https://github.com/argoproj/argo-workflows/pull/6639
I'm trying to fix it


Should data_for_path only allow returning hashes?

Starting to look at 4.1 compat for middleman-data_source, and I think I found a case of a contract that's a bit too constrained (see this failing build, w/ CONTRACTS=false everything is peachy).
The contract in question is for data_for_path, it's expecting a return of Hash or nil, although I think array, string, integer would all be valid possibilities. (really any "data" type, not sure what a good list of that would be).
Local data that as far as I can tell is always coming from method_missing doesn't have that same constraint.

Hmm, all that data is from front matter so it's always a Hash. Are you side-loading arrays from somewhere. I can see making this more permissive, but I'd like to know what the 3rd party extensions are doing

Yeah, adding data callbacks for things -- but I would think it'd be possible to get other types as well with local data (at least arrays). If you had a file in data like:
# data/foo.yaml
- one
- two
- three

Then data.foo, would return ['one', 'two', 'three']

Cool, then sure, get me a PR to loosen the Contract and I'm cool with that.


nrf52840 and ENC28J60 Interfacing Issues

Hi guys,
I realized the issue I opened earlier #61190 had been closed before I got a resolution to the problem. I am still having the same error in building even after having tried to follow the instructions in the responses i got.
Could you please give me some pointers as to where I may be getting lost?

The issue was closed because it is not a bug, this is user error. I will move it to a discussion


Analyze FOC timing of AMCBLDC and AMC2C

          Let me try to recap what I got from a F2F alignment with @sgiraz.

There's pretty much NO difference between using STD or CMSIS ops on AMCBLDC and AMC2C.
On the AMCBLDC, the FOC is taking up $8$ $\mu s$ and NOT $17$ $\mu s$. The difference is represented by the ADC operations.
FOC takes up $14$ $\mu s$ on AMC2C, longer than on AMCBLDC.

Point 1 completes this issue ✅ We go with STD. See #75.
Follow-up question on Point 2: "Why does ADC last that long compared to FOC? Is there any margin for improvement?"
Follow-up question on Point 3: "Why is AMC2C slower than AMCBLDC?" We know this is an ongoing study and we're probably at the right point to contact ST.

cc @Nicogene @sgiraz @marcoaccame @maggia80 @mfussi66
Originally posted by @pattacini in https://github.com/robotology/icub-firmware-models/issues/67#issuecomment-1921377510

This task has to be done after harmonizing Ts_FOC between the 2 boards.

In poi 2 I want to remark that the 8.3 us are taken to execute the AMC_BLDC_step_FOC() function when the control mode is IDLE.
When the control mode is set to CURRENT instead, it takes 10.7 us, see the scope plot below:

I Apologize for the mistake/confusion!
By the way, the EventViewer shows that the whole DMA interrupt takes about 15 us:

Measuring with the scope:
.... ⚠ in progress [image here] ⚠

➡ AMC2C (66.6 KHz)
When the control mode is set to CURRENT instead, the AMC_BLDC_step_FOC() function takes $20$ $\mu s$, see the scope plot below:

The the whole onCurrents_FOC_innerloop function takes $25.45$ $\mu s$:

The whole DMA takes $26.86$ $\mu s$:

cc @pattacini @marcoaccame @maggia80 @Nicogene

To summarize we have

AMC2C (66.6 KHz)
AMCBLDC

AMC_BLDC_step_FOC() function
$20$ $\mu s$
$10.7$ $\mu s$

onCurrents_FOC_innerloop function
$25.45$ $\mu s$
$13.1$ $\mu s$

the whole DMA
$26.86$ $\mu s$
$14.34$ $\mu s$

"Why is AMC2C slower than AMCBLDC?" We know this is an ongoing study and we're probably at the right point to contact ST.

A ~ 2x factor seems a lot, maybe it is the case of contacting ST

The analysis of @sgiraz pointed out an important timing issue on amc2c, and this will be further investigate contacting ST, after that we hopefully know how to align the performance of the two boards.
Closing.

Interesting timing for a comparison:

Source: https://www.mathworks.com/campaigns/offers/next/field-oriented-control-techniques-white-paper.html

[!note]
We're not that bad, after all!

cc @marcoaccame @sgiraz @mfussi66 @Nicogene @maggia80


Adds Travis CI integration, resolves #13

For #13.
Let's see if we can simply let Travis CI build and then run our docker image and container, respectively.
Travis env vars from https://docs.travis-ci.com/user/environment-variables/
Only Linux workers for now; we could add macOS later if we really want to.

Yeap works on Travis CI

Successfully tagged moabitcoin/ig65m-pytorch-f1f2d2211d3d6bbb149c31d2fe0599d26491ba89:latest

Here is the build log for this pull request
https://travis-ci.org/moabitcoin/ig65m-pytorch/builds/593026330
Adding Travis CI badge to readme then I think we're good here for a start.