test issue for bridge test

opening comment of test 1

public reply 2

comment from github 1

issue closed in github closing comment 1

public reply after solved 2

re-opening comment 1

closing coment 2

closing coment 3

re-opening comment 3

closing comment 4

re-opening comment 4

re-opening comment 5

re-opening comment 6

re-opening comment 7


Task "clear" doesn't work for "npm" task

From #30058
I don't know whether this is supposed to work. I modified the build task from https://github.com/Microsoft/vscode-chrome-debug-core/blob/master/.vscode/tasks.json to clear the terminal before building, and to be a build task instead of watching. So it looks like this:
{
    "label": "my build task",
    "type": "npm",
    "script": "build",
    "problemMatcher": "$gulp-tsc",
    "presentation": {
        "echo": true,
        "reveal": "always",
        "focus": false,
        "panel": "shared",
        "showReuseMessage": true,
        "clear": true
    },
    "group": {
        "kind": "build",
        "isDefault": true
    }
}

I run task my build task
I run it a second time
It doesn't clear the terminal, the output from the first run is still visible

If I modify it to be a shell task then it does clear the terminal as I'd expect
{
    "label": "my shell build task",
    "type": "shell",
    "command": "npm run build",
    "problemMatcher": "$gulp-tsc",
    "presentation": {
        "echo": true,
        "reveal": "always",
        "focus": false,
        "panel": "shared",
        "showReuseMessage": true,
        "clear": true
    }
}

Thanks for filing! Duplicate of #62474


New npm release for react 15.0.1?

Realize it was released recently, but on the other hand hopefully it wouldn't require a big change.  Thanks!
git:Graph-experiment npm install --save react-d3-components                         |
├── UNMET PEER DEPENDENCY<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>└── UNMET PEER DEPENDENCY<EMAIL_ADDRESS>
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.

Thanks for the comment! I'll check if it works and make a new release.

Just fyi, I'm using it for the scatterplot and t seemed to work fine for 15.0.1

I released 0.6.3 and changed the required version to >= 0.14.0 which should fix your problem.
Would be great if you could confirm.

@OAGr can you confirm and close?


fsevents dependency prevents installation

Hi @basarat,
I just re-installed atom (on mac os) no other packages, and then tried to install atom-typescript.
I get this error:
Some installed packages could not be loaded because they contain native modules that were compiled for an earlier version of Atom

In more detail
In file included from ../fsevents.cc:6:
In file included from ../node_modules/nan/nan.h:74:
In file included from ../node_modules/nan/nan_new.h:181:
../node_modules/nan/nan_implementation_12_inl.h:172:66: error: too many arguments to function call, expected at most 2, have 4
  return v8::Signature::New(v8::Isolate::GetCurrent(), receiver, argc, argv);
         ~~~~~~~~~~~~~~~~~~                                      ^~~~~~~~~~
/Users/rjhala/.atom/.node-gyp/.node-gyp/0.30.6/deps/v8/include/v8.h:4515:3: note: 'New' declared here
  static Local<Signature> New(
  ^
1 error generated.
make: *** [Release/obj.target/fse/fsevents.o] Error 1
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/Applications/Atom.app/Contents/Resources/app/apm/node_modules/npm/node_modules/node-gyp/lib/build.js:269:23)
gyp ERR! stack     at ChildProcess.emit (events.js:98:17)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (child_process.js:810:12)
gyp ERR! System Darwin 14.5.0
gyp ERR! command "node" "/Applications/Atom.app/Contents/Resources/app/apm/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /Users/rjhala/.atom/packages/atom-typescript/node_modules/grunt-ts/node_modules/chokidar/node_modules/fsevents
gyp ERR! node -v v0.10.30
gyp ERR! node-gyp -v v2.0.2
gyp ERR! not ok

npm ERR! Darwin 14.5.0
npm ERR! argv "/Applications/Atom.app/Contents/Resources/app/apm/bin/node" "/Applications/Atom.app/Contents/Resources/app/apm/node_modules/npm/bin/npm-cli.js" "--globalconfig" "/Users/rjhala/.atom/.apm/.apmrc" "--userconfig" "/Users/rjhala/.atom/.apmrc" "rebuild" "--target=0.30.6" "--arch=x64"
npm ERR! node v0.10.40
npm ERR! npm  v2.13.3
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'node-gyp rebuild'.
npm ERR! This is most likely a problem with the fsevents package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR! You can get their info via:
npm ERR!     npm owner ls fsevents
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/rjhala/.atom/packages/atom-typescript/npm-debug.log

And here is the content of the  npm-debug.log:
https://gist.github.com/ranjitjhala/1259a624309004498adc
Please let me know if I can provide any other information.
Could it be that I have a "stale" fsevents on my machine?
Shall I wipe the npm database or some such?

I recently upgraded to Yosemite, I notice this:
https://github.com/strongloop/fsevents/issues/56

Could it be a related issue?

Going through the log : https://gist.github.com/ranjitjhala/1259a624309004498adc#file-atom-typescript-error-L5859-L5870 It seems that its falling over installing grunt-ts which depends on chokidar which depends on fsevents.
The concern is that we only have grunt-ts as a dev dependency (code here) ... and don't expect it to be installed on apm install atom-typescript.  Is apm install atom-typescript the command you ran?

Same error here, just after installing an Atom update, I got a warning about atom-typescript requiring a rebuild. A few seconds after clicking "rebuild" I get the same error.

Looking at the Atom update changelog for 1.0.12:
Atom now ships with Chrome 43 and io.js 2.3.1.

@msurdi / @ranjitjhala can you follow dev machine workflow : https://github.com/TypeStrong/atom-typescript/blob/master/CONTRIBUTING.md#setup-dev-machine to rule out something atom specific crashing the whole workflow. Basically I am curious about manual npm install results :rose:

@basarat Following the dev setup instructions works fine. To me, it seems that Atom is using its own node version when doing the "rebuild" and not the system wide node I have on my computer. But I don't really now anything about the internals of Atom, so I'm just guessing.

So, even after manual installation, Atom still complains about the plugin needing a rebuild, and fails again.

@basarat I can confirm what @msurdi says -- same thing happens on the dev workflow.
(In addition to the above) I tried installing from within atom -- i.e. by clicking on the install button and by doing apm install atom-typescript. In both cases the install succeeds until I open a .ts file, in which case
the little bug appears on the bottom right, clicking which leads to the above (and the screenshot on #584).

I have the same problem. It seems that with<EMAIL_ADDRESS>this problem can be resolved (https://github.com/webpack/webpack/issues/1435)

same here. Package stopped working after updating atom.

@Sprechen
Hm - still the same

npm ERR<EMAIL_ADDRESS>install: node-pre-gyp install --fallback-to-build

I resolved this issue by navigating to .atom/packages/atom-typescript
rm -rf node_modules
npm install
and then rebuilding in atom.

Hooray! I can confirm that @brandom 's method works for me too!

It did not work for me. Instead, I got it working by doing the following:
in .atom/packages/atom-typescript:
remove grunt-ts from devDependencies in package.json (note this will break stuff if you are trying to develop atom-typescript)
rm -rf node_modules
rebuild in atom.

:+1: I have to vote for @isuda ;) strange issue.

@isuda did rebuild also do npm install for you ?
I had to do npm install in the end... however :+1:

This is failing for me too, with:

atom typescript v6.0.10
atom 1.0.13
OSX Yosemite 10.10.5

But I also tried making edits that break my build, and atom-typescript doesn't indicate there's any problems, while tsc shows them. So atom-typescript is not working anymore.
I've tried each of the suggestions here, but none have worked.
It seems that there is some difference between the way the fsevents package is being built by atom and the way it is built from the command line. When I exited atom, and ran the following commands:
cd ~/.atom/packages/atom-typescript/node_modules/babel/node_modules/chokidar
npm uninstall fsevents
sed -i .tmp 's/"fsevents": "^0.3.8"/"fsevents": "^1.0.0"/g' package.json
npm install fsevents

the build during install produces this output that seems clean:
><EMAIL_ADDRESS>install /Users/peter/.atom/packages/atom-typescript/node_modules/babel/node_modules/chokidar/node_modules/fsevents
> node-pre-gyp install --fallback-to-build

[fsevents] Success: "/Users/peter/.atom/packages/atom-typescript/node_modules/babel/node_modules/chokidar/node_modules/fsevents/lib/binding/Release/node-v14-darwin-x64/fse.node" is installed via remote
<EMAIL_ADDRESS>node_modules/fsevents
└──<EMAIL_ADDRESS>
But when I restart atom, the red bug symbol is still there, and clicking it, then rebuild packages produces a similar error as before, but with these lines:
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR<EMAIL_ADDRESS>install: `node-pre-gyp install --fallback-to-build`
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'node-pre-gyp install --fallback-to-build'.

Note that it's complaining about the same node-pre-gyp install --fallback-to-build command that worked from the shell!

getting this too

@psnider did you remove grunt-ts from package.json and did you remove all node_modules ?
For me it was not caused by babel but by fsevents in grunt-ts ...

Got it!
@sebilasse And, yes, I had removed grunt-ts from the top level, and also had removed all of the node_modules.  Thanks.
I have node installed in /usr/local/bin, which is on my PATH.
However, I noticed in the log that node-gyp couldn't find node.
So I added echo "node-gyp: env=`env`" 1>&2 to /Applications/Atom.app/Contents/Resources/app/apm/node_modules/npm/bin/node-gyp-bin/node-gyp
and my PATH variable's settings didn't appear in those listed.
So I created a symlink to node from /usr/bin,
and rebuilt from the Incompatible Packages tab in atom.
Now atom-typescript works again.
For those interested, that PATH that was passed to node-gyp contained these locations:
/Applications/Atom.app/Contents/Resources/app/apm/node_modules/npm/bin/node-gyp-bin:
/Users/peter/.atom/packages/atom-typescript/node_modules/babel/node_modules/chokidar/node_modules/fsevents/node_modules/.bin:
/Users/peter/.atom/packages/atom-typescript/node_modules/babel/node_modules/chokidar/node_modules/.bin:
/Users/peter/.atom/packages/atom-typescript/node_modules/babel/node_modules/.bin:
/Users/peter/.atom/packages/atom-typescript/node_modules/.bin:
/usr/bin:
/bin:/usr/sbin:
/sbin

@psnider: I also got this error. Launching atom from the command line, and then clicking "rebuild" fixed this for me.

@isuda: Also for me launching atom from command line and then clicking "rebuild" has worked!

@isuda Thanks, that worked for me also! Very strange why though...

It appears that Macs don't read your shell's configuration file when
launching an application by clicking an icon, such as from your Application
Dock or from Finder.
When you do start it from your shell's command line, I believe the
environment variables are set.
I have to find a solution to this that I like...
On Fri, Sep 18, 2015 at 9:47 PM, Sergey Galchenko<EMAIL_ADDRESS>wrote:

@isuda https://github.com/isuda Thanks, that worked for me also! Very
strange why though...
—
Reply to this email directly or view it on GitHub
https://github.com/TypeStrong/atom-typescript/issues/583#issuecomment-141576493
.

I've just published 6.0.11 without grunt-ts as a quick workaround.
Will keep this issue till I document the dev setup in CONTRIBUTING or figure out an alternative workaround.
At least you guys will have this version to manually install on latest atom if I break something again by trying to reintroduce grunt-ts :rose: I'll make it a major version upgrade.

in my case the last build keep sending requests everytime I write some code! at the right of Typescript toolbar appears a Github spinning icon (???) and by clicking on it a notification pop up where I read messages such as:

getProjectFilesDetails
editText
errorsForFile
etc...

how to disable it? :\

@tryIO these are requests send to a background process that is actually doing the heavy lifting of code analysis.

getProjectFilesDetails

@tryIO Seems related to : https://github.com/TypeStrong/atom-typescript/issues/332 see workaround : https://github.com/TypeStrong/atom-typescript/issues/332#issuecomment-140287071

Since a lot of people experienced this. I am marking this as closed with 6.0.12 :rose: (also had to remove grunt dependency for windows users)

For what it's worth, it looks like there was a bug on Atom's end for rebuilding native modules (see https://github.com/atom/atom/issues/8837) that is resolved in 1.0.15


#130: Added default content length to progress bar

Closes #130

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
113 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.06%) to 59.633%

Files with Coverage Reduction
New Missed Lines
%

com/devonfw/tools/ide/io/FileAccessImpl.java
113
56.64%

Totals

Change from base Build<PHONE_NUMBER>:
0.06%

Covered Lines:
4398

Relevant Lines:
7080

💛  - Coveralls


Request: Extend VE Genetics support

To be more specific:

Allow animal hybridization as well. Currently support is only for animal/human hybrids, but what about "bearwolf" for example?
Add spectrums to hybridization. Currently if VE Genetics is enabled for genes, children will always be a hybrid. But maybe you can make it so that there is a spectrum between "vanilla" births and "hybrid" births so it's not an either/or.

Probably a side note but:
I took a look at the defs for the compatibility patch. I'm still new to modding, but currently it is hard coded for each individual breeding pair for what it should result in. Which is fine. But couldn't it be possible to first categorize animals based on their "core"? I.e. wolf, timber wolf, and warg could be fit into a master group called "canine" and then use "canine" to determine what resulting children will be for all three. Sort of like how rjw handles animal genatalia. Would be a lot easier for me to make a patch myself for modded creatures not supported such as Medieval Overhaul.

I will close this for now but I have not forgotten.
The thing is I believe this would be best as a separate mod.


Visual Studio plugin does not support C++ Unit Test

Expected Behavior

cpp-unit-test should participate to Visual Studio project creation.
Current Behavior

C++ component added by cpp-unit-test aren't available in Visual Studio.
Context

Steps to Reproduce (for bugs)

Your Environment

Build scan URL:

I am very interested in this.
Currently, this is how I keep both main and test Visual C++ projects in a single source directory.
I generate a foo.vcxproj and foo-test.vcxproj side by side.
I adjust the "Intermediate Directory" to obj\main\$(Platform)\$(Configuration) and obj\test\$(Platform)\$(Configuration) accordingly.
In foo.vcxproj, I "Exclude From Project" the entire src/test directory.
In foo-test.vcxproj, "Exclude From Project" the src/main/main.cpp file or some similar conflict.
This way, foo-test statically imports foo sources, which, if I understand correctly, is how cpp-unit-test works. I have also experimented with foo-test dynamically linking with foo, successfully.
With this approach, cpp-unit-test works out of the box with my Visual C++ projects.


Getting rid of InternalArticle XML schema

There are some serious problems with our approach of 2 XML schemas. Especially during conversion. I've realised that we've so far programmed against the following assumption: During conversion at all times both schemas TextureArticle and InternalArticle need to be valid in order to use schema reflection (things like schema.findFirstValidPos(parent, tagName))
I'm now struggling with importing / exporting the article record:

In TextureArticle we have standard-conform tagging with strict order e.g. for (((fpage, lpage?)?, page-range?) | elocation-id)?
In InternalArticle these elements are not allowed (as we have them inside pubMetaDb (article-record) for storing that information
In InternalArticle we have some custom things in place such as aff-group or custom table schema
The importing step means that the underlying XML tree will be valid in InternalArticle but invalid in TextureArticle
Now this is a problem because during export I want to use schema reflection to find the insertion positions for fpage,lpage where i need to rely on schema.findFirstValidPos. However, this is not possible before the xml becomes valid for TextureArticle (it's only valid after completion of all export transforms, but not in between when we need the schema information)

Proposed strategy:

we only define TextureArticle schema
for custom elements we use Substance models directly (e.g. for our custom table model and things like affiliations, references etc. as we do now)
we keep the XML valid JATS at all times (e.g. interally we drop the ref-list since we have our own representation)
I'd even go so far that on import to remove the body element from the XML because then we can use regular substance container nodes and custom models for fig + table etc. without violating the JATS schema (it's fine to keep them XML nodes for now to satisfy the implementation but then we'd be free to use flat substance models everywhere in the future)
If we keep a reference to the original body node we could continue using el.find('') in subtrees etc.

@oliver---- what do you think about that matter? Is there an incremental path towards reaching that design without breaking too much? I'd be crucial to have a plan for this soon, as with the more complex metadata we're blocked currently. and i don't want to base the code on static assumptions (like ensure we have one anchor element in article-meta which we can use to derive element positions).

First I agree with you that the more we deviate internally from JATS the more it does not make sense to try an inplace-DOM-transformation -- which I guess is causing more problems than we would like.
Beyond that, I guess it might still be difficult with a Two-DOM (or model-to-DOM) conversion strategy -- because the target DOM (=JATS DOM) would still need to be in a valid state all the time.
What we could try for export is, create a new minimal JATS DOM and generate into it. @michael would that help?

I'm not completely sure yet. Maybe we should really think of it as a big import + export step (= end of line JATS ;-))
If we did a "full export" of article meta for instance, and assuming we have everything in some internal model, then we could hard-code the order and it would probably read more naturally.
Where it gets problematic is doing incremental transitions on an existing DOM.
But that's the more radical design we may want to have eventually one day. I'm fine with keeping some things XML-ish in the internal model, but then we should deviate from the JATS, because there it gets complicated. Means, if we do something custom, we do it outside of the DOM in regular Substance nodes.
It worked quite well to map individual elements of the doc to regular substance nodes (e.g. references etc.) and remove the original and later on export bring it back. Where it gets hard is when we introduce custom DOM structures (e.g. aff-group) and do as you say in-place transformations.
Currently we have a mix.. which is hard to understand.

Just want to make clear, that I have the feeling that there are >two things mixed here.

Struggling with the target schema is one thing.
Having a non XML internal model is another, but this is IMO not connected to this particular problem.
So my advice would be to solve the problems one after another.
Having a non-inplace conversion is probably in-evitable, no matter if we use XML internally or not.
The problem is just that we need to rewrite the converters to generate rather transform.
Altogether I am not much in favor of doing this in a hurry. Particularly because we want to switch to Stencila ASAP.
Are there any workarounds? E.g. determining the insert position manually, not relying on schema driven insert?

Yes I just discovered workaround. It is using article-meta as is in InternalArticle. Then use InternalArticle schema inspection to find the insert pos.
Yes we should take time for this. But better do the switch before we add the complete feature sets, as we'll write converters multiple times.

FYI, we will not be able to provide a XML Editor for un-implemented features.

After some sleep I have the feeling that this issue in some parts goes into the wrong direction, or at least too far.
Having an XML, or at least a structured model is not generally a bad thing. E.g. there is a natural order in XML DOMs, which for instance helped us with the numbering of references. Before we had a manual implementation, which was pretty arbitrary, and also utterly incomplete.
Beyond that I like XML being interface that can be understood pretty well by others. In general it is nice to have a specific place where an element is stored, rather than a soup of things, relying on indexes.
I assume the essence of this issue is that the current internal XML schema is just annoying in some cases, which comes from the fact that it is derived from the JATS schema.
On the other hand, we found that for entities it is nicer to have flat plain records.
Maybe a mixture could be interesting then, i.e. a document model which is structured like XML but where leafs can be record elements, not being restricted to having attributes and child nodes only, and not meant for hierarchical data.
Altogether I am in favor of moving towards a more handy internal model, that is not in our way. But I would not like to give up the benefits of the current XML model.

Ok, we will not do this. Instead improve on the current approach and merge pubMetaDb and document (as discussed this morning).


Adding Flet language

Adding a language

[x] The code displays "Hello World" (tio.run may help for testing)
[x] I have no association with the language
[x] There are no copyright issues with this code
[x] The language has not been added prior to this pull request

Link to programming language:

where I need to provide the link? here in comment box or in the flet file ?


Fix issue 1467 - Source on Change Log doesn't work

This draft PR is an initial pass at code to hide the Source and Get PDF buttons from the NavBar on the /changelog page, as they do not function there.

I think I prefer @ericscheid 's approach of just having a check for shareId == undefined.

Can certainly do that; my initial thought process was that it might be useful to be able to enable/disable these things in the SharePage route. However that might also be using a sledgehammer to crack a single walnut.

I think I prefer @ericscheid 's approach of just having a check for shareId == undefined.

I don't know react, but this looks promising:
https://reactjs.org/docs/conditional-rendering.html#inline-if-with-logical--operator

This commit is clean, elegant, simple - and as an added bonus, it even works, too.


Move K8s object from AWS extension to core

Moving the K8s object from the AWS extension to the core schema.
As discussed here: https://opencybersecu-lz97379.slack.com/archives/C03C2QJRA73/p1664470650464869
Updated dictionary.json with the required attributes.

@magnologan is this PR still applicable? Or, we should close it?


logging health changes excludes useful info

Hi,
When a service goes unhealthy, fabio seems to log:
"Health changed to #753565"
It would be really handy to know which service it's referring to. When debugging crashing backends, this would be super handy.
Is that possible to add? :)
Thanks much!

When this happens then the routing table changes and fabio should log the delta. The state change can also occur when there is no change in health but a change in the output of the health check. If you have volatile data like a timestamp or an ip address in the output then you can get a change like that without a routing table change.
You can run consul monitor to check what is going on in your cluster.

Ooh, I think you're right. This is mostly happening when I see:
[INFO] agent: Synced check '2d2b8e084ac62d104f97b46a3eb1031e0de165da'
Thanks again :)
Loving fabio, by the way. It's working wonderfully.

BTW, I'm not sure fabio should be logging anything unless the cluster state change impacts a service with urlprefix- tag(s), but knowing that I can ignore this is helpful.

Although this isn't  a directly useful information for fabio it is for the operator as a secondary indicator for your cluster health. The usual problem - and you're not the first to ask - is to have either an unstable environment (which you should fix) or to have health check output with volatile data (your case) which puts stress on consul and the raft layer.
I'm glad you like fabio. Please keep asking if there is anything that isn't clear.

See https://github.com/fabiolb/fabio/issues/226 for example


[feature] Allow to pass config as a function

Use case:
useSWR(key, '/somewhere', globalConfig =>  {
  return {
    ...globalConfig,
    onError: (error, key) => {
      if (error.response?.status === 403) {
         // some special logic here
         return
      }
      return globalConfig.onError(error, key)
    }
  }
})

What do you think?

supplement more information here
config callbacks would be overridden when pass callbacks in 3rd argument options.
thus, if user directly execute global config callback inside the callback with same name in options, it will fall into recursion.
useSWR(key, fetcher, {
   // this will override the global config onError
   onError(err, key, config) {
      config.onError(err, key)
   }
})

user might need some way to access the original callbacks in global config or have some methods to intercept the callbacks. not sure if this would be a probable reason why @vojty want this approach.
Other Possible Solutions

give each callback with one more argument context to access the global config

useSWR(key, fetcher, {
   onError(err, key, config, context) {
      context.onError(err, key)
   }
})

expose context out to let user use it directly. pretty aggressive, might not be ideal

import {SWRConfigContext} from 'swr'

const globalConfig = useContext(SWRConfigContext)
useSWR(key, fetcher, {
   onError(err, key, config) {
      globalConfig.onError(err, key)
   }
})

I'm not sure if this will be a popular demand (I don't see many people requesting for this). As of now, if you really need to reuse the logic, I think you can copy the implementation in config.ts and do changes on top of it.

Recommend to use SWRConfig provider to configure global config, and you can override the specific config option per hook. Default config value is also exposed as SWRConfig.default in<EMAIL_ADDRESS>


Saving artifact to GCS fails: failed to put file: The request signature we calculated does not match the signature you provided

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?
Hello,
I tested the newly released v3.4.7 with some of my standard workflows and noticed, they all fail to upload artifacts to a GCS bucket. This in turn fails any workflow.
The workflow controller is configured like this:
 s3:
    bucket: test-xyz
    keyPrefix: staging
    endpoint: "storage.googleapis.com"
    insecure: false
    accessKeySecret:
      name: s3-secret
      key: accessKey
    secretKeySecret:
      name: s3-secret
      key: secretKey

Interestingly, the same works with v3.4.6. So maybe it is something similar to https://github.com/argoproj/argo-workflows/issues/1060 and related to the update of the cloud.google.com/go/storage dependency from v1.29.0 in v3.4.6 to v1.30.1 in v3.4.7?
Unfortunately, I'm not really familiar with the way the minio client is used as a wrapper to communicate with s3-compatible storage APIs. It would be great, if someone more knowledgable could take a look. Thanks :)
Version
v3.4.7
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.
apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata:
  generateName: artifact-passing-
spec:
  entrypoint: artifact-example
  templates:
  - name: artifact-example
    steps:
    - - name: generate-artifact
        template: whalesay
    - - name: consume-artifact
        template: print-message
        arguments:
          artifacts:
          - name: message
            from: "{{steps.generate-artifact.outputs.artifacts.hello-art}}"

  - name: whalesay
    container:
      image: docker/whalesay:latest
      command: [sh, -c]
      args: ["sleep 1; cowsay hello world | tee /tmp/hello_world.txt"]
    outputs:
      artifacts:
      - name: hello-art
        path: /tmp/hello_world.txt

  - name: print-message
    inputs:
      artifacts:
      - name: message
        path: /tmp/message
    container:
      image: alpine:latest
      command: [sh, -c]
      args: ["cat /tmp/message"]

Logs from the workflow controller
kubectl logs -n argo deploy/workflow-controller | grep ${workflow}

time="2023-04-12T10:50:34.744Z" level=info msg="Processing workflow" namespace=testruns-on-dev workflow=artifact-passing-4lnm8
time="2023-04-12T10:50:34.750Z" level=info msg="Updated phase  -> Running" namespace=testruns-on-dev workflow=artifact-passing-4lnm8
time="2023-04-12T10:50:34.751Z" level=info msg="Steps node artifact-passing-4lnm8 initialized Running" namespace=testruns-on-dev workflow=artifact-passing-4lnm8
time="2023-04-12T10:50:34.751Z" level=info msg="StepGroup node artifact-passing-4lnm8-3119329443 initialized Running" namespace=testruns-on-dev workflow=artifact-passing-4lnm8
time="2023-04-12T10:50:34.751Z" level=info msg="Pod node artifact-passing-4lnm8-2774092361 initialized Pending" namespace=testruns-on-dev workflow=artifact-passing-4lnm8
time="2023-04-12T10:50:34.810Z" level=info msg="Created pod: artifact-passing-4lnm8[0].generate-artifact (artifact-passing-4lnm8-2774092361)" namespace=testruns-on-dev workflow=artifact-passing-4lnm8
time="2023-04-12T10:50:34.810Z" level=info msg="Workflow step group node artifact-passing-4lnm8-3119329443 not yet completed" namespace=testruns-on-dev workflow=artifact-passing-4lnm8
time="2023-04-12T10:50:34.810Z" level=info msg="TaskSet Reconciliation" namespace=testruns-on-dev workflow=artifact-passing-4lnm8
time="2023-04-12T10:50:34.810Z" level=info msg=reconcileAgentPod namespace=testruns-on-dev workflow=artifact-passing-4lnm8
time="2023-04-12T10:50:34.821Z" level=info msg="Workflow update successful" namespace=testruns-on-dev phase=Running resourceVersion=76791116 workflow=artifact-passing-4lnm8
time="2023-04-12T10:50:44.812Z" level=info msg="Processing workflow" namespace=testruns-on-dev workflow=artifact-passing-4lnm8
time="2023-04-12T10:50:44.812Z" level=info msg="Task-result reconciliation" namespace=testruns-on-dev numObjs=0 workflow=artifact-passing-4lnm8
time="2023-04-12T10:50:44.812Z" level=info msg="node changed" namespace=testruns-on-dev new.message= new.phase=Running new.progress=0/1 nodeID=artifact-passing-4lnm8-2774092361 old.message= old.phase=Pending old.progress=0/1 workflow=artifact-passing-4lnm8
time="2023-04-12T10:50:44.812Z" level=info msg="Workflow step group node artifact-passing-4lnm8-3119329443 not yet completed" namespace=testruns-on-dev workflow=artifact-passing-4lnm8
time="2023-04-12T10:50:44.812Z" level=info msg="TaskSet Reconciliation" namespace=testruns-on-dev workflow=artifact-passing-4lnm8
time="2023-04-12T10:50:44.812Z" level=info msg=reconcileAgentPod namespace=testruns-on-dev workflow=artifact-passing-4lnm8
time="2023-04-12T10:50:44.817Z" level=info msg="cleaning up pod" action=terminateContainers key=testruns-on-dev/artifact-passing-4lnm8-2774092361/terminateContainers
time="2023-04-12T10:50:44.831Z" level=info msg="Workflow update successful" namespace=testruns-on-dev phase=Running resourceVersion=76791203 workflow=artifact-passing-4lnm8
time="2023-04-12T10:50:54.832Z" level=info msg="Processing workflow" namespace=testruns-on-dev workflow=artifact-passing-4lnm8
time="2023-04-12T10:50:54.832Z" level=info msg="Task-result reconciliation" namespace=testruns-on-dev numObjs=0 workflow=artifact-passing-4lnm8
time="2023-04-12T10:50:54.832Z" level=info msg="Pod failed: Error (exit code 1): failed to put file: The request signature we calculated does not match the signature you provided. Check your Google secret key and signing method." displayName=generate-artifact namespace=testruns-on-dev pod=artifact-passing-4lnm8-2774092361 templateName=whalesay workflow=artifact-passing-4lnm8
time="2023-04-12T10:50:54.832Z" level=info msg="node changed" namespace=testruns-on-dev new.message="Error (exit code 1): failed to put file: The request signature we calculated does not match the signature you provided. Check your Google secret key and signing method."  Capturing script output ignored"
time="2023-04-12T10:50:42.784Z" level=info msg="No output parameters"
time="2023-04-12T10:50:42.784Z" level=info msg="Saving output artifacts"
time="2023-04-12T10:50:42.784Z" level=info msg="Staging artifact: hello-art"
time="2023-04-12T10:50:42.784Z" level=info msg="Copying /tmp/hello_world.txt from container base image layer to /tmp/argo/outputs/artifacts/hello-art.tgz"
time="2023-04-12T10:50:42.785Z" level=info msg="/var/run/argo/outputs/artifacts/tmp/hello_world.txt.tgz -> /tmp/argo/outputs/artifacts/hello-art.tgz"
time="2023-04-12T10:50:42.785Z" level=info msg="S3 Save path: /tmp/argo/outputs/artifacts/hello-art.tgz, key: staging/artifact-passing-4lnm8/artifact-passing-4lnm8-2774092361/hello-art.tgz"
time="2023-04-12T10:50:42.785Z" level=info msg="Creating minio client using static credentials" endpoint=storage.googleapis.com
time="2023-04-12T10:50:42.878Z" level=info msg="Saving file to s3" bucket=test-xyz endpoint=storage.googleapis.com key=staging/artifact-passing-4lnm8/artifact-passing-4lnm8-2774092361/hello-art.tgz path=/tmp/argo/outputs/artifacts/hello-art.tgz
time="2023-04-12T10:50:42.919Z" level=warning msg="Non-transient error: The request signature we calculated does not match the signature you provided. Check your Google secret key and signing method."
time="2023-04-12T10:50:42.919Z" level=info msg="Save artifact" artifactName=hello-art duration=134.21099ms error="failed to put file: The request signature we calculated does not match the signature you provided. Check your Google secret key and signing method." key=staging/artifact-passing-4lnm8/artifact-passing-4lnm8-2774092361/hello-art.tgz
time="2023-04-12T10:50:42.919Z" level=error msg="executor error: failed to put file: The request signature we calculated does not match the signature you provided. Check your Google secret key and signing method."
time="2023-04-12T10:50:42.920Z" level=info msg="S3 Save path: /tmp/argo/outputs/logs/main.log, key: staging/artifact-passing-4lnm8/artifact-passing-4lnm8-2774092361/main.log"
time="2023-04-12T10:50:42.920Z" level=info msg="Creating minio client using static credentials" endpoint=storage.googleapis.com
time="2023-04-12T10:50:42.922Z" level=info msg="Saving file to s3" bucket=test-xyz endpoint=storage.googleapis.com key=staging/artifact-passing-4lnm8/artifact-passing-4lnm8-2774092361/main.log path=/tmp/argo/outputs/logs/main.log
time="2023-04-12T10:50:43.007Z" level=warning msg="Non-transient error: The request signature we calculated does not match the signature you provided. Check your Google secret key and signing method."
time="2023-04-12T10:50:43.007Z" level=info msg="Save artifact" artifactName=main-logs duration=87.71257ms error="failed to put file: The request signature we calculated does not match the signature you provided. Check your Google secret key and signing method." key=staging/artifact-passing-4lnm8/artifact-passing-4lnm8-2774092361/main.log
time="2023-04-12T10:50:43.007Z" level=error msg="executor error: failed to put file: The request signature we calculated does not match the signature you provided. Check your Google secret key and signing method."
time="2023-04-12T10:50:43.053Z" level=info msg="Create workflowtaskresults 403"
time="2023-04-12T10:50:43.072Z" level=info msg="Patch pods 200"
time="2023-04-12T10:50:43.078Z" level=info msg="Alloc=10442 TotalAlloc=20569 Sys=28781 NumGC=5 Goroutines=12"
time="2023-04-12T10:50:43.078Z" level=fatal msg="failed to put file: The request signature we calculated does not match the signature you provided. Check your Google secret key and signing method."

We're seeing the exact same problem after upgrade to 3.4.7

Why not using GCS artifact directly? https://github.com/argoproj/argo-workflows/blob/master/examples/input-artifact-gcs.yaml

I am not sure how this issue is related to the upgrade of cloud.google.com/go/storage.

I am not sure how this issue is related to the upgrade of cloud.google.com/go/storage.

It was a rather uneducated guess based on the changes / dependency updates introduced with v3.4.7.

Why not using GCS artifact directly? https://github.com/argoproj/argo-workflows/blob/master/examples/input-artifact-gcs.yaml

I have another CRD which gets converted to a workflow in turn. To be a bit more flexible in choosing the storage backend, I used the s3-compatible credentials format in my setup so far. I would need to check, if I can move to a provider specific format.
Still, I would argue it is a regression :)

Seeing the same going from 3.4.5 to 3.4.7 in our pipeline.

I believe I am seeing it with a fresh non-production install as well but using S3 as a storage bucket

Even patch updates can result is regressions. Are there any bugs against the Google library that match this issue?

I just revisited the issue and I haven't been able to reproduce the behavior with v3.4.10 🎉 🪄  At least for me, it solves the issue as I can go to the latest/greatest patch version of the v3.4 release branch.

Thanks for confirming!


Set privileged = false by default when launcher is enabled

I came across this today during an installation with a customer and I realized that we don't disable privileged automatically when launcher.enabled. It would be a nice convenience if we did

cc @atheriel since you've been poking at a lot of permissions related stuff


Switching between collections shortcuts

Hi,
I have feature request
NOW
to open collection, I need:

press ctrl + shift + y
scroll collections using mouse
right click on chosen collection
press "Open all (10)"
or press "Open all (10) in new window"

EXPECTED BEHAVIOR
It would be nice if I can do it this way:

press ctrl + shift + y
scroll collections using arrow keys
press enter on chosen collection to "Open all (10)"
press ctrl + enter to "Open all (10) in new window"

This is a very nice feature request, and I could see myself using this too. But, unfortunately, this repository is for DevTools. DevTools is a developer feature built into Edge which has nothing to do with the browser UI, including collections.
Can you please send your feedback again by using the browser's feedback mechanism? Here's how:

Click Settings and more (the ... button in the top-right corner of the browser).
Click Help and feedback.
Click Send feedback.

Thank you for your understanding.

Ok.  I've got it. Thanks for advice!


Bug: SQLAlchemy 1 plugin mutates app state destructively

Description
When using the SQLAlchemy 1 plugin, repeatedly running through the application lifecycle (as done when testing an application not provided by a factory function), causes a KeyError on the second pass.
This is caused be the plugin's on_shutdown handler deleting the engine_app_state_key from the application's state on application shutdown, but only adding it on application init.
This can be solved by setting up the application state within on_startup.
URL to code causing the issue
No response
MCVE
from starlite.contrib.sqlalchemy_1.config import SQLAlchemyConfig
from starlite.contrib.sqlalchemy_1.plugin import SQLAlchemyPlugin
from starlite import Starlite
from starlite.testing import TestClient

app = Starlite(
    plugins=[
        SQLAlchemyPlugin(
            config=SQLAlchemyConfig(
                connection_string="sqlite+pysqlite:///:memory:",
                use_async_engine=False,
            )
        )
    ]
)

with TestClient(app) as client:
    pass

with TestClient(app) as client:
    pass

Steps to reproduce
No response
Screenshots
"![SCREENSHOT_DESCRIPTION](SCREENSHOT_LINK.png)"

Logs
No response
Starlite Version
This affects both 1.51 and the main branch.
Platform

[ ] Linux
[ ] Mac
[ ] Windows
[ ] Other (Please specify in the description above)

Can confirm.
We have this patch in starlite-pg-redis-docker:
@pytest.fixture(scope="session", autouse=True)
def _patch_sqlalchemy_plugin() -> "abc.Iterator":
    monkeypatch = pytest.MonkeyPatch()
    monkeypatch.setattr(
        sqlalchemy_plugin.SQLAlchemyConfig,  # type:ignore[attr-defined]
        "on_shutdown",
        MagicMock(),
    )
    yield
    monkeypatch.undo()

Adding an on_startup handler feels like the correct way to handle. Good idea!


Add now built in function

This pull request adds a stateless function now() that could be used in conjunction with the recently merged function unixNano() to compare fields containing time encoded in nanoseconds with the current time.
Relevant feature request: Add stateless function now() to get the current local time
Required for all non-trivial PRs

[X] Rebased/mergable
[X] Tests pass
[X] CHANGELOG.md updated
[X] Sign CLA (if not already signed)

(pull request beginner here, please let me know if I've made a mistake in the process, thanks)

Hi! In case you don't have time to have a look at my recent changes on my PR, I:

fixed the signature for the function now()
added an integration test
made the function now() rely on a package-local variable (timeNowFunction). I needed to do so in order to have deterministic tests by stubbing now(). If you prefer another approach or feel like it doesn't fit well enough in Kapacitor's source code and code style, just let me know, I'm open to other ideas.

Also, I know that my test is failing right now and I'm working on it, however I have an issue with not being able to run the integration tests properly on my machine. If I do
./test.sh
I end up with lots of tests failing (besides of the one I wrote) with lots of messages of this form:
Get http://[::]:36319/kapacitor/v1/tasks/TestStream_....: dial tcp [::]:36319: connect: cannot assign requested address

I guess it comes from my personal machine and system configuration, and I know here is not the proper place to ask this, but if you have any clue of what could cause this problem, I'd be pleased to know.

@mbresson if you're using go 1.9+, I'd recommend just running go test ./.... If you're using a version less than that you'll need to specify the packages you'd like to test explicitly go test . ./alert (...).

Hi!
Thanks for the tip, it worked. I have fixed the test. Can you have a look and tell me if you are satisfied with my PR? Otherwise I can rework it, add more tests or fix whatever is not right.

@mbresson just curious if you've made any more progress on this issue. If the InfluxDBOut stuff is still causing issues, maybe we should just make it so that now returns an integer. This will un-complicate the InfluxDB issues that may come up.

Hi, I have made some progress but I'm still not there yet. Nonetheless I prefer not to make now() return an integer and keep working on it, because having now() returning a time.Time is more interesting, especially if it can be used with other functions taking a time in parameter. I'll keep you updated.

@mbresson Sounds good. Just a heads up, we're getting ready to start the 1.4 release process and I'd love to see this PR make it in there!

And I prefer not to make now() return an integer and keep working on it, because having now() returning a time.Time is more interesting, especially if it can be used with other functions taking a time in parameter.

I definitely agree that having a time.Time value would be more useful, but I think that change might be more involved. In fact I think it might involve a change with InfluxDB, I could be wrong though, maybe just before it's written to InfluxDB convert it to an int? Just kind of thinking out loud.

I should have time to push my updates by tomorrow evening or the day before tomorrow, just didn't have time to do it these last days.
No need to change anything in InfluxDB, but there is a choice to make: before writing it to InfluxDB, should we convert it to an int (Unix timestamp), or to a string representation of the time ? (such as ISO8601)
Tell me what you prefer.

Hi, finally, here are my updates:

In order to be able to evaluate time.Time values, in tick/ast/node.go, I added a TimeNode type, and I also added the file tick/stateful/eval_time_node.go for the same reasons.
In edge/messages's ToRow methods, I convert time.Time values to unix timestamps in nanoseconds (int64). I do the same in influxdb/client.go's Bytes method. I do it so that we can convert the time.Time values we get when now() is evaluated to integral values. Otherwise, they are automatically converted to string, ISO8601 representation of dates, which is not what we want.
I have changed my test TestStream_EvalNow because it was impossible to have it pass if I made it output now(), since the expected value could never be exactly the same, nanoseconds-wise, as the value produced. Instead I altered the test to get the current year() and compare it, but I think it makes the test much less useful since initially it was intended to check what would happen if now() was fed to httpOut. I'm not very satisfied for one more reason, it is that if that test happens to run at the very end of a year, it may fail because the expected value for year may be the next year. That's the problem with testing non-deterministic time values :P.
I have completed the test TestStream_EvalNowInfluxDBOut, and it checks that the time.Time value resulting from lambda: now() is indeed sent as a unix nanoseconds timestamp, encoded as an int64.

I'm not sure my explanations are clear because to be blunt, my understanding of Kapacitor's source code is incomplete, so I'd appreciate if you could double-check the new code that I brought in. Maybe some more tests could be added, if you feel like it's needed, I can work on it another day.
Thanks

It seems that the CI checks have failed. I didn't have any error when running the tests on my machine, and I cannot access the CI logs (the loader keep spinning forever). I'll check again tomorrow.

@mbresson  looks like its just a flakey test. I'm rerunning the build.

Hi, thanks for your feedback! I made the changes you suggested, I think your code suggestions are clearer and more concise.
About the TimeNode, you are right, it is not needed, as other things that I have removed in my latest commit. I added these because I misunderstood some parts of the code in kapacitor. My fault. :)
I'll be without internet until beginning of next week, so I hurried a little bit for my latest commit. I'm looking forward to your feedback.

@mbresson looks good! After a rebase and squash into a single commit I think this should be good to merge.

Sorry, I've failed my squash & rebase because now it appears that I'm the (co-)author of commits that are not mine. (f1f9bb0, 8933719, aa33d98, e48f9f0, 81576da, 156349f, 871d796, 77c91f9, ffcb25a, 0dd1d3e, 3a4d43f, 860b95c).
I'm not good at git, do you know how to squash & rebase and retain the original author information?
Either way I'll try and clean up my mess when I'm back next week.

@mbresson The process should be something like
git rebase -i master
that will take you a screen that looks like this
  1 pick d25510d0 Add example of all nodes in load tasks style dir
  2
  3 # Rebase 6e45b39d..d25510d0 onto 6e45b39d (1 command)
  4 #
  5 # Commands:
  6 # p, pick = use commit
  7 # r, reword = use commit, but edit the commit message
  8 # e, edit = use commit, but stop for amending
  9 # s, squash = use commit, but meld into previous commit
 10 # f, fixup = like "squash", but discard this commit's log message
 11 # x, exec = run command (the rest of the line) using shell
 12 # d, drop = remove commit
 13 #
 14 # These lines can be re-ordered; they are executed from top to bottom.
 15 #
 16 # If you remove a line here THAT COMMIT WILL BE LOST.
 17 #
 18 # However, if you remove everything, the rebase will be aborted.
 19 #
 20 # Note that empty commits are commented out

Change all of the pick commits to squash except for the very first one and change that one to reword. Then quit and reword the commit appropriately.

I actually did git rebase -i HEAD~10 and squashed all my commits into f1f9bb0ecdd9ff6f653b88e18b9cc9de886dd64f and left other people's commits intact.
But I don't understand why, on Github, it looks like I'm the committer of all commits, not only mine:

Anyway, I'll fix that when I'm back.

Hi! I'm finished at last. I see the checks have failed but it seems to come from another test than mine:
=== RUN   TestServer_RecordReplayStreamWithPost
--- FAIL: TestServer_RecordReplayStreamWithPost (1.19s)
	server_test.go:3528: failed to finish recording

Maybe it's an issue with the CI system again?

Hi, is everything ok with my pull request? Please let me know if some rework or enhancement is needed.

@mbresson sorry about the delay in my response. After a bit of internal discussion, we think that allowing time.Times to be passed around as fields is a bit more of a substantial change. There are a number of places where we make assumptions that the fields will be an int, float, string, or bool.
We think the now function is still a great addition, the only change from whats here will be
stream
    |from()
        .measurement('cpu')
    |eval(lambda: now())
        .as('now')

should result in
ts=2017-10-27T12:02:35.313-04:00 lvl=error msg="error evaluating expression" service=kapacitor task_master=main task=now node=log4 err="expression returned unexpected type time"

But
stream
    |from()
        .measurement('cpu')
    |where(lambda: "time" > now())

and
stream
    |from()
        .measurement('cpu')
    |eval(lambda: unixNano(now()))
        .as('now')

are perfectly fine.
My apologies the last second changes. I wasn't thinking clearly when I suggested that we allow times be passed around like values. I'll go through and note the changes necessary to get us to the state suggested above.

No problem, I understand. I have just made the relevant changes.


"Junos CLI Automation" sends junos command to child VMs(e.g. vFPC)

"Junos CLI Automation" sends junos command to child VMs(e.g. vFPC).
It consumes much time to wait timeout. It's feels bad. Please change to skip non-junos VMs.
https://qiita-image-store.s3.amazonaws.com/0/104974/996be18d-10f5-89f6-a3b9-99d23c03c8e6.png

I have looked code and I guess that the root cause is b'junos_vpfe' contains "junos" and current code thinks it is Junos VM as code.
https://github.com/Juniper/wistar/blob/5c0f58171075362dc7c315f15071f4f0d4021308/ajax/views.py#L1157

Thanks for the report. Fix applied in commit: https://github.com/Juniper/wistar/commit/83d527423447eceef5ce39764b596f39da6c4e11
Wistar will now determine if an instance is a 'child' instance and use that to no longer attempt direct access for things like Cli automation or boot up status.

Thank you for the fix!


[BUG REPORT] Misspelling of elixir

The bug
I found a misspelling of elixir
Steps to reproduce
when I use https://skillicons.dev/icons?i=elixr, it should be elixir
https://skillicons.dev/icons?i=elixir =>
https://skillicons.dev/icons?i=elixr =>
Any extra info
Here are some screenshots from the elixir official website:

@mogeko The issue has been resolved, you may close this issue now :3


Fix: Today Page Not Updating #126

The issue was that the DOM elements were being updated every second, but the data they displayed was not changing because it was only being set on page load or reload. To resolve this, I modified the code so that the today variable, which holds the current date and time, is refreshed every second within the setInterval function. This ensures that the data is current when it’s used to update the DOM elements. Additionally, I consolidated the getAndSetDomElements and setDomElements functions into a single setDomElements function to streamline the code. Now, this unified function is called within the setInterval method, which not only simplifies the code but also guarantees that both the data and the DOM elements are updated in sync every second.

Looks good. Slight revision can you use arrow functions instead to keep all the functions consistent.

Can you use arrow functions for updateDate and setDomElements.

Yes sir, I'm on it

Fixes #126

Looks good. Go for merge


fix(charts): reference registry-proxy on <IP_ADDRESS>

On some providers, "localhost" is not set up on the host network. explicitly calling the loopback
address fixes this.
See deis/workflow#678

Codecov Report

:exclamation: No coverage uploaded for pull request head (localhost-to-127@634bfe9).

Continue to review full report at Codecov.

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


Cloudlink Suite

🔴  not ready to pull 🔴
just not a draft for so mike can review
Roadmap
todo:
Done:

Home server side auth (1 commit untested)
CloudDisk Home Server
Server CA connection (untested due to using github.dev and phone being dead again)

not planned fetures

Client Side SDK`s
cloudcoin

Servers use the WSS:// protocol string.

Servers should use the WSS:// protocol string.

ye, local testin tho so i dont have wss

Servers should use the WSS:// protocol string.

this is home server btw
what im asking is, how shoud other servers connect to home (clients alr connect via websockets)

Servers use the same protocol, they just need to run a client alongside the server and conditionally transfer messages

Currently the client logs into the home server, logs in and gets a token to
login to the non home server btw (the non home server then asks the home
server what user is associated with this token  not implemented)
On Fri, Dec 9, 2022, 8:34 AM MikeDev101 @.***> wrote:

Servers should use the WSS:// protocol string.
this is home server btw
what im asking is, how shoud other servers connect to home (clients alr
connect via websockets)
Servers use the same protocol, they just need to run a client alongside
the server and conditionally transfer messages
—
Reply to this email directly, view it on GitHub
https://github.com/MikeDev101/cloudlink/pull/91#issuecomment-1344382290,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQHW4PZOMSWWIFWEOQK4GJTWMM7OXANCNFSM6AAAAAASYPLIPE
.
You are receiving this because you authored the thread.Message ID:
@.***>

Oh, and did you see the test server I have public on replit? (#92)

currently untested due to using github.dev

Can’t you just make a code space?

I prefer to not use code spaces, as they cost money where I can just spin
up a repl on my phone (it was dead yesterday)
I also have replit hacker for free
On Fri, Dec 9, 2022, 10:02 AM Asherlr @.***> wrote:

currently untested due to using github.dev
Can’t you just make a code space?
—
Reply to this email directly, view it on GitHub
https://github.com/MikeDev101/cloudlink/pull/91#issuecomment-1344480875,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQHW4P2QJP326E5AYFPAM3DWMNJ2PANCNFSM6AAAAAASYPLIPE
.
You are receiving this because you authored the thread.Message ID:
@.***>

I prefer to not use code spaces, as they cost money where I can just spin up a repl on my phone (it was dead yesterday) I also have replit hacker for free
…

how did you get free replit hacker? (without cycles, replit is pretty much.net fiddle)

code. Spaces are literally free. Go to your repository, click code, click code spaces, then click the plus icon at the top of the box.

I have never paid for anything from github in my entire life

Yes, I know that the urls are extremely weird

GitHub education lmao
On Fri, Dec 9, 2022, 10:08 AM Asherlr @.***> wrote:

I prefer to not use code spaces, as they cost money where I can just spin
up a repl on my phone (it was dead yesterday) I also have replit hacker for
free
… <#m_-2883500397940527114_>

how did you get free replit hacker? (without cycles, replit is pretty
much.net fiddle)
2.
code. Spaces are literally free. Go to your repository, click code,
click code spaces, then click the plus icon at the top of the box.
I have never paid for anything from github in my entire life
—
Reply to this email directly, view it on GitHub
https://github.com/MikeDev101/cloudlink/pull/91#issuecomment-1344487374,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQHW4PZMMXLV6JLJELXSAZDWMNKONANCNFSM6AAAAAASYPLIPE
.
You are receiving this because you authored the thread.Message ID:
@.***>

I don’t have github education.

If your in highschool or college you can apply for it

Ok and? All I’m saying is that you don’t need a subscription for codespaces, it’s free.

Ok and? All I’m saying is that you don’t need a subscription for codespaces, it’s free.

Up to a certain point, then you need to pay

wait really

wait really

Ye

Ok and? All I’m saying is that you don’t need a subscription for codespaces, it’s free.

Up to a certain point, then you need to pay

Just don’t code for a total 120 hours (see https://github.com/settings/billing/plans )

ready for review, but not for pulling

I'm actually going to test this now

This is basically ready to pull, but the SDK does not work bc of some bugs within cloudlink.

edited above for discord

Test suite must be created to verify functionality. Will not merge if there is buggy/missing functions.

Test suite must be created to verify functionality. Will not merge if there is buggy/missing functions.

Cloudlink itself has bugs that make the server suit impossible to create

example: statuscode does not get called. nor does the connection callback

example: statuscode does not get called. nor does the connection callback

Will look into this issue.

also, a pain to init the client, as i dont use parent, and dont have it


Add OpenAPI spec for quarkus app so it registers as API within backstage

We want the Quarkus app to register as an API in the Backstage console after it's created.

Closed with PR: https://github.com/janus-idp/software-templates/pull/105


Quantum Opaque Types (in Resources)

The spec defines both Opaque types (which are Classic) and QPaque (which are linear, i.e. non-classic). So, we should have some syntax in the YAML (and, following #186, we'll need to add some support in the Rust Hugr codebase) for both linear and classic type definitions (including parameterized).
It seems reasonable that any type that instantiates a TypeDef with linear type arguments (e.g., MyList<Qubit>) must be linear. But new TypeDef's can also be linear (i.e., fail to be copyable) regardless of any type arguments; for example MyNewQubit, Qudit or the polymorphic definition Quxit<Int> (which gives rise to types Quxit<3> and Quxit<8>).

Outdated, covered by TypeDefBound etc.


Add Default Histogram Aggregation in prometheus schema

Adds support for providing default_histogram_aggregation via a config file for Prometheus Metric Exporter.
Support for configuring Default Histogram Aggregation for Prometheus exporter is added in this PR: https://github.com/open-telemetry/opentelemetry-java/pull/6541.

We have a policy to only add schema surface area for configuration options which are defined in the spec. I'm supportive of this change and opened open-telemetry/opentelemetry-specification#4124 to add the corresponding option in the spec, which would unblock this.

Thanks a lot @jack-berg!

This is superseded by #107, which solves the problem more generally and for all metric exporters. Closing this PR.


Is it possible to restrict TLS 1.2 or its later?

Is there any way to allow only TLS 1.2 (or its later version) via configuration?

yes, by the command line:
--min-tls-version=1.2

or environment variable:
DRACHTIO_MIN_TLS_VERSION=1.2

or in config file:
<sip>
   <tls>
      <min-tls-version>1.2</min-tls-version>
   </tls>
</sip>


Added convenience functions for window::icon::Icon

See #1170
Since the image dependency was already an (optional) dependency of iced, why not provide these convenience functions that save a few lines of code in applications that need an icon

Thank you for the PR!
Could you make it so that your convenience function is only available if the iced image feature is enabled?
The image crate is quite large, and iced tries to give users the option for simplicity, but tries to be as light as it can be by default. This is the reason that image isn't already included by default.

Well, I had already gated this behind an image_rs feature I had just added, for the very reasons you described.
I've changed this PR so that this optional feature is now tied to the already-existing image feature.
I'm afraid I cannot remove the image_rs feature and keep only the image feature, since image is both the name of a crate and a feature. To do so, we would need:

either to rename the image feature so that it does not clash with the crate name
wait for https://github.com/rust-lang/cargo/issues/5565 to be ever stabilized
some other solution I would not be aware of?

Also, I'm not sure how docs.rs generates its doc. Will these functions be shown in https://docs.rs/iced/latest/iced/?
There is already a
[package.metadata.docs.rs]
rustdoc-args = ["--cfg", "docsrs"]
features = ["image", "svg", "canvas"]

...but I'm not sure how this will render the functions that are gated behind the image_rs feature instead of the image feature

I did not manage to build the doc locally though the docs.rs project to test the image_rs-gated functions are visible, but since this feature is implied by the image one, it should be fine.
I think this MR is ready to be merged. What's your opinion on this?
Thanks

I'm finally having a green CI on this PR.
Is this PR OK for you? Or do you need anything else from me before merging it?
Thanks


Test CircleCI GH Checks

Use CircleCI workflows in order to integrate with the GitHub Checks API. As an
added bonus, execute v1 and v2 jobs in parallel.
https://circleci.com/blog/see-the-status-of-your-circleci-workflows-in-github/
a7f0bf0

This change is

Getting CircleCI to use the GitHub Checks required using workflows.
Consolidating duplicate job commands required using CircleCI 2.1.
Outside of this repo, we needed an admin of the LiveRamp GH org to grant CircleCI permissions.


Add Avro Schema Registry Message Decoder

This should be a separate plugin - pinot-confluent-avro. I am guessing pinot-kafka module should work with confluent kafka as well.

Codecov Report

Merging #4973 into master will increase coverage by 20.98%.
The diff coverage is n/a.

@@              Coverage Diff              @@
##             master    #4973       +/-   ##
=============================================
+ Coverage     36.35%   57.33%   +20.98%
- Complexity        0       12       +12
=============================================
  Files          1174     1174
  Lines         62244    62244
  Branches       9148     9148
=============================================
+ Hits          22627    35689    +13062
+ Misses        37596    23883    -13713
- Partials       2021     2672      +651

Impacted Files
Coverage Δ
Complexity Δ

.../impl/dictionary/LongOffHeapMutableDictionary.java
52.68% <0%> (-10.76%)
0% <0%> (ø)

...e/impl/dictionary/LongOnHeapMutableDictionary.java
52.43% <0%> (-9.76%)
0% <0%> (ø)

...r/filter/predicate/PredicateEvaluatorProvider.java
52.17% <0%> (-4.35%)
0% <0%> (ø)

...ces/PinotSegmentUploadDownloadRestletResource.java
61.34% <0%> (+0.61%)
0% <0%> (ø)
:arrow_down:

...e/io/writer/impl/MutableOffHeapByteArrayStore.java
85.71% <0%> (+1.09%)
0% <0%> (ø)
:arrow_down:

...g/apache/pinot/common/request/InstanceRequest.java
28.83% <0%> (+1.14%)
0% <0%> (ø)
:arrow_down:

...impl/dictionary/DoubleOnHeapMutableDictionary.java
37.8% <0%> (+1.21%)
0% <0%> (ø)
:arrow_down:

...org/apache/pinot/common/metrics/MetricsHelper.java
48.75% <0%> (+1.25%)
0% <0%> (ø)
:arrow_down:

...rg/apache/pinot/common/request/FilterQueryMap.java
40.79% <0%> (+1.49%)
0% <0%> (ø)
:arrow_down:

...e/pinot/core/query/request/ServerQueryRequest.java
89.39% <0%> (+1.51%)
0% <0%> (ø)
:arrow_down:

... and 582 more

Continue to review full report at Codecov.

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

Redid the dependencies, let me know when you have a chance to review, thanks!

Redid the dependencies, let me know when you have a chance to review, thanks!

Can you update the PR description.

This looks good. @elonazoulay can add some description


Tkc dc

Revive TKC DC and IP

Merge scripts to notebooks
Break a part forward and inversion notebooks for both DC and IP.
Only works simpeg/dcip/spectralIP branch

Thanks for this Seogi! There are a couple issues I have come across in TKC_DC_fwd (I fixed a couple plt.show() statements to prevent duplicate plots with ipywidgets), but there are some more involved ones I could use your help with:

I am fairly sure that using
fig, ax = plt.subplots(1, 2)

is more stable than using add subplot. Would you mind replacing those?
(P.S. I am using matplotlib 4.3.23)

thanks @lheagy I did not change using fig, ax = plt.subplots(1, 2),
but made some modifications due to plt.show() issue, and
it seems working for my end at the moment.


Remove duplicate const

Removes the ERROR_INSUFFICIENT_BUFFER const that's shadowing an equivalent import from winapi. This just makes the crate compile on rustc 1.13.0.
cc: @Aaronepower

Derp. GitHub lead me to open this on the wrong repo 😆


[BUG]: [ERR] DL Track[Reason Why] failed.Can't get the streamUrl, type is application/dash+xml

Which tool
tidal dl Enter Choice:https://tidal.com/browse/track/370665178?u
[ERR] DL Track[Reason Why] failed.Can't get the streamUrl, type is application/dash+xml
Version
2<IP_ADDRESS>
Platform
Windows
Describe the bug
Enter Choice:https://tidal.com/browse/track/370665178?u
[ERR] DL Track[Reason Why] failed.Can't get the streamUrl, type is application/dash+xml
Relevant log output
No response
Add screenshots

Hi, I'm having the same problem, it seems that this error only occurs with albums that are listed as MAX quality 24 bits 192 KHZ.
[ERR] DL Track[Grease (From “Grease”)] failed.Can't get the streamUrl, type is application/dash+xml

Just use less quality like "Hi-Fi" and you are done.

Thanks Djsantours this was the same for me now I am on Hi-Fi.  Be nice to have the MAX quality as well one day

Indeed, there is no possibility of downloading in HR 24bit, nor is it possible to download ATMOS which has replaced MQA, when will it be possible to download in 24bit and in Atmos?


Depnedency Constraints

Can you guys update the dependencies, because in my case version solving is getting failed again and again

I'm facing the same issue.
It's because giphy_get still depends on http 0.13.3
giphy_get >=2.0.1 depends on http ^0.13.3 and project_name depends on http ^1.1.0, giphy_get >=2.0.1 is forbidden.

Any updates?

done!


Update eds-icons with latest changes

new filter_alt icon
updates to info_circle & list icon

resolves #588

@vnys We have no new lines at end of file on any of our svg og json files from figma-broker. Fixing this results in over 630 file changes, so saving it for a seperate fix here #599 😅


Can't join my server

When i try to join my server this error occurs:
TypeError: p[0] is undefined. Please reload the page
I am hosting Prismarine-web-client on my pc and I left the proxy section blank

Can you please add a log from console?


ReferenceError: toasterHub is not defined

I already install the package through composer. I also performed the following steps:

But still things not working for me. Can I have little assistance?

Hi, how are you building your scripts?

I'm afraid I can't do anything unless I'm provided a clue or repro. 😕

I resolved the problem. I hope this helps to my friends who are stuck in this problem.

We need to include app.js in our layout. I am using vite, so I am including like this:

Also don't forget to run npm run build 😅


Clipping mask with custom shape

Hi, can clipping mask be made with custom shape? If yes, how? Thanks.

Can it draw a Difference Chart?
http://bl.ocks.org/mbostock/3894205


Add section on scoped proofs

Attempts to resolve #103, open to feedback on alternative ways to describe this functionality

Multiple approvals, purely editorial, merging


Couple "error on ambiguity" with a fuzzer to generate ambiguous inputs.

Because of how GLL control-flow maps all the way down to machine code, it should be possible for a program-trace-aware fuzzer to hit enough codepaths to cause an ambiguity through its crafted input.
(suggested by @nikomatsakis)

Alternatively, we could try to transform the grammar to reveal ambiguities more easily - e.g. turn A | B | C into (A & B) | (B & C) | (A & C) and aggressively optimize it.
That sort of grammar might not need the SPPF, making it more efficient, if it "succeeds if ambiguous" (not "iff" because that's harder/impossible to obtain in general).

For future reference: @nikomatsakis's idea seems similar to what what I had in mind in https://github.com/AltSysrq/proptest/issues/61 save for the exhaustiveness (as PBT tools like proptest and Haskell's QuickCheck usually randomize tests).


New version: DeterminedAI.CLI version 0.33.0

Pull request has been created with komac v2.2.1 :rocket:
Microsoft Reviewers: Open in CodeFlow

/azp run

/azp run


How do you install this into KeyCloak?

I am having trouble finding out how to install this in KeyCloak. Am I missing something from the doumentation?

If you are using a default keycloak setup, you just need to copy the .ear file to the folder  <keycloak_dir>/standalone/deployments

If you are using a default keycloak setup, you just need to copy the .ear file to the folder <keycloak_dir>/standalone/deployments

Great, thanks for the quick reply. Where is this .ear file? I see the ear-module has a pom.xml file in it?

Did you build the project with maven? If so, you will find a .ear file in the ear-module/target folder.

Hm, where should I run the build command from? The deployments folder?

@aspiazza , this repository is an open source java maven project meant to
be compiled  and then deployed in keycloak. The way you write your
questions makes me think that you are unaware of what is maven or how to
build a java project.  If this is the case, there is no problem, you can
still benefit from this federation provider, but I think it is better you
look for some help on your organization before.
After building it with maven, like I described in the README file, and then
deploying it to the corresponding folder, the one I have previously
indicated, you should see an option to select the singular-db-user-provider
on the web interface of keycloak.
This is not a default pre-configured solution, keep in mind that even after
everything is deployed, you still have to write your SQL queries
accordingly so that the provider can look up your users and check passwords
against the database.
Feel free to ask any other questions, I will try to help somehow.
Best regards,
On Thu, 2 Sept 2021 at 10:03, aspiazza @.***> wrote:

Hm, where should I run the build command from? The deployments folder?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/opensingular/singular-keycloak-database-federation/issues/3#issuecomment-911656843,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAER4LYXPHSYN3HSVN3ZD3DT75YY5ANCNFSM5DEZD5TA
.
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.


Load bash_profile.bak

Current bash-it template does not load its backed up .bash_profile.bak file.

Why would you want to do this? What do you have in your backup file that you need to load?

I have virtualenvwrapper (python), boot2docker, anaconda stuffs that create env variables and modify paths. After I ran install.sh from Bash-it, the whole .bash_profile was replaced with Bash-it template, and the above tools were not functioning properly.
In my opinion, Bash-it shouldn't simply replace the whole bash_profile file and let things break when installing. It should do the job it did prior to the installation, and add new features that Bash-it provides.
What do you think?

Bash-it has plugins for most of the above (virtualenvwrapper, boot2docker, etc.), you might want to enable some of them.
If you want to add custom settings, you can add a file to the custom folder, e.g. mystuff.bash - it will be loaded by Bash-it to include your custom settings.


Rename Index.qmd to index.qmd

You can use https://delft-rcafe.github.io/home/ if you lower the letter I. This aligns with the standards.

@J535D165 sorry for the slow response, since we have distributed the link as Index.html I had to create a redirect so we wouldn't break all the links. Can you update the branch to resolve the conflict?


F90 module list generation

What changes does this PR introduce?
Bug in f90mkdepend tool.
What is the current behaviour?
modreflist keeps a carriage return character if modules are loaded with a line break. This affects any code that has USE <modulename> type integration
Example module loading scenario for blabla_do_something.F90:
#include "BLABLA_OPTIONS.h"
...
    USE blablareadin,   only: read_some_stuff, blabla_var
    USE blablaphysics
...

f90mkdepend produces the following warning to error output:
WARNING: f90mkdepend: no source file found for module blablaphysics

and f90mkdepend.log (in vim) produces:
blabla_do_something.F90 => blablareadin
blablaphysics^M

This creates missing dependencies for blabla_do_something.f90, which leads to compilation errors.
What is the new behaviour
Updated f90mkdepend tool accounts for carriage returns when creating modreflist. Now ^M is removed from module name blablaphysics
Does this PR introduce a breaking change?
Not that I know of
Other information:
Tested using a package in development written in F90, with the current mitgcm code checkpoint, and on the verification problem tutorial_global_oce_latlon
Suggested addition to tag-index

sample f90 package
sample file: line 14 produces a WARNING from f90mkdepend
  USE iHopMod
sample f90mkdepend output
f90mkdepend.err.txt
f90mkdepend.log
Checked on:
Linux with gfortran
Linux with ifort
Linux with ifort+mpi

Thanks @IvanaEscobar
@jahn if you have a minute, could you take a look at the problem and solution here, want to make sure you are on board. Thanks

Thanks, Ivana, for pointing these out.
We generally try not to have carriage returns in source files, so the first error doesn't occur.
For compiled modules, the convention in MITgcm is that a module mymodule has to be defined in a source file of one of the following names:
mymodule.F90
mymodule.F
mymodule_mod.F90
mymodule_mod.F

If the module is precompiled, dependency resolution is not an issue and the warning can be ignored.

@jahn
Line 14 of the sample file doesn't have a carriage return included. So it is unclear when a carriage return is introduced. Maybe an artifact of using awk parsing?
The sample f90 package contains the module specified in a source file written in the style you pointed out. Specifically as ihopmod.F90 (link to file).
I don't change the inner workings of genmake2 which links the sample file to each of the modules it specifies as shown in Makefiles in the comment above (Makefile_ifort.txt)
If it's easier for me to demo the bug for you, I can illustrate the compilation warnings via Zoom?

I cloned your repository and removed all carriage returns from the files and f90mkdepend works fine.  I used sed -i 's/\r//g' *in the ihop directory but you could also use dos2unix.

I was able to reproduce no warnings with your fix to the package.
Vim wasn't displaying carriage returns for FORTRAN type files. So the bug is fixed by clearing return carriages from the source files.

@jahn I was wondering what happens if you do not have write permissions to fix a file using sed
This happens in our Linux cluster with the netcdf header file. There are instances in that header file where they use multi-line comments that happened to produce lines that start with the word use
/* comment starts .....
use this feature ....
more comment ....
and done */

with the current f90mkdepend, this comment will trigger a warning.
WARNING: f90mkdepend: for netcdf.h no source file found for this
Overall, it's harmless but was curious on potential solutions

@IvanaEscobar See if changing lines 17-19 as the following would get rid of the warning
if grep -i '^ *use ' $filename | grep -iv '^ *use this' $filename > /dev/null; then
   # extract module name in lower case
   modreflist=$(grep -i '^ *use ' $filename | grep -iv '^ *use this' | awk '{print tolower($2)}' | sed 's/,.*$//')


error Couldn't find match for "pull/6/head" for command-exists on npm install

On npm install -g generator-kittn I get:
npm ERR! code 1 npm ERR! Command failed: /usr/bin/git checkout pull/6/head npm ERR! error: pathspec 'pull/6/head' did not match any file(s) known to git. npm ERR! npm ERR!      /Users/m.rabelero.campos/.npm/_logs/2017-06-08T12_46_17_856Z-debug.log
The error log shows this error message:
35 silly fetchPackageMetaData error for command-exists@github:mathisonian/command-exists#pull/6/head Command failed: /usr/bin/git checkout pull/6/head 35 silly fetchPackageMetaData error: pathspec 'pull/6/head' did not match any file(s) known to git. 36 verbose stack Error: Command failed: /usr/bin/git checkout pull/6/head 36 verbose stack error: pathspec 'pull/6/head' did not match any file(s) known to git. 36 verbose stack 36 verbose stack     at ChildProcess.exithandler (child_process.js:252:12) 36 verbose stack     at emitTwo (events.js:125:13) 36 verbose stack     at ChildProcess.emit (events.js:213:7) 36 verbose stack     at maybeClose (internal/child_process.js:887:16) 36 verbose stack     at Socket.stream.socket.on (internal/child_process.js:340:11) 36 verbose stack     at emitOne (events.js:115:13) 36 verbose stack     at Socket.emit (events.js:210:7) 36 verbose stack     at Pipe._handle.close [as _onclose] (net.js:546:12) 37 verbose cwd /Users/m.rabelero.campos/Sites 38 verbose Darwin 15.6.0 39 verbose argv "/usr/local/Cellar/node/8.0.0_1/bin/node" "/usr/local/bin/npm" "install" "-g" "generator-kittn" 40 verbose node v8.0.0 41 verbose npm  v5.0.3 42 error code 1 43 error Command failed: /usr/bin/git checkout pull/6/head 43 error error: pathspec 'pull/6/head' did not match any file(s) known to git. 44 verbose exit [ 1, true ]
On yarn add generator-kittn I get:
yarn add v0.24.6 info No lockfile found. [1/4] 🔍  Resolving packages... error Couldn't find match for "pull/6/head" in "laggingreflex-sync,master,10/head,11/head,2/head,3/head,4/head,5/head,6/head,8/head,v0.1.0,v1.0.0,v1.0.1,v1.0.2,v1.1.0,v1.2.0,v1.2.1,v1.2.2" for "https://github.com/mathisonian/command-exists.git". info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.

Will be fixed with next release!
Already fixed in develop-branch.

https://github.com/kittn/generator-kittn/commit/cdeb5269f9af8fa5aa2df56766d3b4b14a4d9a9c


Implementation of the SfButton Control in MAUI Toolkit

Description
The Button control is a fundamental UI element that allows users to trigger actions or commands with a click or tap. This control is versatile and can be customized with text, icons, and various visual styles. It plays a crucial role in user interaction by initiating navigation, submitting forms, and performing other tasks.
Key Features
Text and Icon Customization
Ability to set text content and incorporate icons for better visual representation.
Styles and Themes
Supports various customizable styles such as flat, circular, outlined, or icon buttons.
Command Binding
Built-in support for binding commands to enable seamless integration with MVVM architecture.
Event Handling
Provided click event handling for flexible user interactions.
Enabled/Disabled State
Ability to toggle between enabled and disabled states, providing visual feedback when a button is inactive.
Animation and Visual Feedback
Includes animations such as ripple effects to indicate user interaction.
Accessibility Support
Ensures compatibility with screen readers, improving the experience for users with disabilities.
Customizable Shapes and Sizes
Supports customization of button shapes (e.g., rounded, rectangular) and sizes to fit various use cases.
Issues Fixed
Fixes #30
Output screenshots
https://github.com/user-attachments/assets/1231382a-ede6-48bf-aeea-4e11a77987af
https://github.com/user-attachments/assets/c1a638ee-6704-4dfa-90c5-f0eeffb96239

/azp run

/azp run


The tooltip of Country Map is not readable

Screenshot
The tooltip is OK on World Map :

The tooltip follows the position of mouse

and background color is used. The value is readeable
It is not the same for Country Map

Best regards

Yes, I was just noticing this a couple days ago... I'm not sure when it regressed, but I believe the name should be located at the centroid of the region you're hovering on. I'm not sure how far back this happened, but a git bisect would likely turn up the problem, if anyone doesn't see it immediately in the code.
The position and the legibility are somewhat separate issues... I'm more worried about the position, but both are valid. Should we split these into two issues? Do you have interest in tackling either?
@michael-s-molina just merged a new tooltip renderer that we'd like to start standardizing on... perhaps this is a good chance to spiff things up a little bit while we're at it?

Thank you for your feedback, I personally see no point in splitting the subject into 2 because for me it forms a whole.
I understand that corrections can be effective on one subject or another.
If you would like me to troubleshoot to make this easier to fix, I can do that.
Sincerely

If you would like me to troubleshoot to make this easier to fix, I can do that.

That would be amazing! Many of us are stretched for time, so any help we can get goes a long, long way. A PR would be the dream, but more diagnostics sure help!


Adds first version of ROCm install script.

The proposed script download in parallel all RPM packages from the latest ROCm distribution, excluding the variants containing RPATH's, and extract them. The binaries are then moved to the final installation path.

not sure where this goes, but if you're making this into a module, it's worth considering that hyperdrive et. al. need to have the environment variables HIP_PATH set such that $HIP_PATH/include/hip/hip_runtime_api.h exists in order to work.

Closing this one as it seems not to produce correct installations for some ROCm packages. David takes care of installing software anyway.


Inazkue patch  basque language

Basque language translation

I see language codes for eu or eu_ES
Not for any eu_EU
Is that correct?

Hi inazkue,
We are updating Stirling-PDF's license to MPL 2.0 (Mozilla Public License Version 2.0) to continue fostering our open-source commitment while introducing more flexible usage of the project.
What We Need From You:
In order to transition to the MPL 2.0 license, we need the explicit consent of all our contributors.

If you're comfortable relicensing your contributions for this specific PR under MPL 2.0, please respond with:
I, inazkue, grant permission to relicense my contributions from this PR to Stirling-PDF under the Mozilla Public License 2.0.
If you'd prefer to give blanket permission for all of your contributions to Stirling-PDF (be it through pull requests, commits, or any other form of contribution) rather than on a PR-by-PR basis, please respond with:
I, inazkue, grant permission to relicense all my contributions to Stirling-PDF under the Mozilla Public License 2.0.

What does this do and why?
As your old code was contributed under a different license it legally cannot move to a new license without your permission, and since we dont want to lose your code we wanted to reach out. Remember this project is remaining open-source!.
Deadline:
If we dont receive a response, or if you decline, unfortunately, we will have to remove your contributions from Stirling-PDF before the license change, which is scheduled  in coming months.
Thank You!
Your contributions are invaluable, and we hope to continue having them in Stirling-PDF under the new license. Feel free to ask if you have any questions or concerns about this change.
Best,
Frooodle
Stirling-PDF Maintainer

Hi inazkue,
We are updating Stirling-PDF's license to MPL 2.0 (Mozilla Public License Version 2.0) to continue fostering our open-source commitment while introducing more flexible usage of the project.
What We Need From You:
In order to transition to the MPL 2.0 license, we need the explicit consent of all our contributors.

If you're comfortable relicensing your contributions for this specific PR under MPL 2.0, please respond with:
I, inazkue, grant permission to relicense my contributions from this PR to Stirling-PDF under the Mozilla Public License 2.0.
If you'd prefer to give blanket permission for all of your contributions to Stirling-PDF (be it through pull requests, commits, or any other form of contribution) rather than on a PR-by-PR basis, please respond with:
I, inazkue, grant permission to relicense all my contributions to Stirling-PDF under the Mozilla Public License 2.0.

What does this do and why?
As your old code was contributed under a different license it legally cannot move to a new license without your permission, and since we dont want to lose your code we wanted to reach out. Remember this project is remaining open-source!.
Deadline:
If we dont receive a response, or if you decline, unfortunately, we will have to remove your contributions from Stirling-PDF before the license change, which is scheduled  in coming months.
Thank You!
Your contributions are invaluable, and we hope to continue having them in Stirling-PDF under the new license. Feel free to ask if you have any questions or concerns about this change.
Best,
Frooodle
Stirling-PDF Maintainer

I, inazkue, grant permission to relicense all my contributions to
Stirling-PDF under the Mozilla Public License 2.0.
El dom, 8 oct 2023 a las 21:11, Anthony Stirling @.***>)
escribió:

Hi inazkue,
We are updating Stirling-PDF's license to MPL 2.0 (Mozilla Public License
Version 2.0) to continue fostering our open-source commitment while
introducing more flexible usage of the project.
What We Need From You:
In order to transition to the MPL 2.0 license, we need the explicit
consent of all our contributors.

If you're comfortable relicensing your contributions for this
specific PR under MPL 2.0, please respond with:
I, inazkue, grant permission to relicense my contributions from this
PR to Stirling-PDF under the Mozilla Public License 2.0.
If you'd prefer to give blanket permission for all of your
contributions to Stirling-PDF (be it through pull requests, commits, or any
other form of contribution) rather than on a PR-by-PR basis, please respond
with:
I, inazkue, grant permission to relicense all my contributions to
Stirling-PDF under the Mozilla Public License 2.0.

What does this do and why?
As your old code was contributed under a different license it legally
cannot move to a new license without your permission, and since we dont
want to lose your code we wanted to reach out. Remember this project is
remaining open-source!.
Deadline:
If we dont receive a response, or if you decline, unfortunately, we will
have to remove your contributions from Stirling-PDF before the license
change, which is scheduled in coming months.
Thank You!
Your contributions are invaluable, and we hope to continue having them in
Stirling-PDF under the new license. Feel free to ask if you have any
questions or concerns about this change.
Best,
Frooodle
Stirling-PDF Maintainer
—
Reply to this email directly, view it on GitHub
https://github.com/Frooodle/Stirling-PDF/pull/244#issuecomment-1752135919,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAH4CPRTATTPQK6RV56UXN3X6L3HTAVCNFSM6AAAAAAZLXA3KOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJSGEZTKOJRHE
.
You are receiving this because you authored the thread.Message ID:
@.***>


ARROW-8203: [C#] Use the latest SourceLink

This fixes "dotnet pack". See JIRA issue for full error message.

@eerhardt I'll merge this for green CI but you can add any comments to this change.


feat: nonfungibles devnet runtime + pop-api

Codecov Report
Attention: Patch coverage is 96.06299% with 10 lines in your changes missing coverage. Please review.

Please upload report for BASE (chungquantin/feat-nonfungibles@83e8122). Learn more about missing BASE report.

Files with missing lines
Patch %
Lines

pallets/api/src/nonfungibles/mod.rs
82.85%
2 Missing and 4 partials :warning:

runtime/devnet/src/config/api/mod.rs
96.26%
4 Missing :warning:

@@                        Coverage Diff                        @@
##             chungquantin/feat-nonfungibles     #350   +/-   ##
=================================================================
  Coverage                                  ?   69.87%
=================================================================
  Files                                     ?       72
  Lines                                     ?    12937
  Branches                                  ?    12937
=================================================================
  Hits                                      ?     9040
  Misses                                    ?     3624
  Partials                                  ?      273

Files with missing lines
Coverage Δ

pallets/api/src/fungibles/mod.rs
92.59% <ø> (ø)

pallets/api/src/fungibles/tests.rs
99.73% <100.00%> (ø)

pallets/api/src/nonfungibles/tests.rs
100.00% <100.00%> (ø)

pallets/api/src/nonfungibles/types.rs
0.00% <ø> (ø)

pallets/nfts/src/benchmarking.rs
85.79% <ø> (ø)

pallets/nfts/src/types.rs
67.11% <ø> (ø)

runtime/devnet/src/config/api/versioning.rs
90.90% <100.00%> (ø)

runtime/devnet/src/lib.rs
5.53% <ø> (ø)

runtime/devnet/src/config/api/mod.rs
91.61% <96.26%> (ø)

pallets/api/src/nonfungibles/mod.rs
59.74% <82.85%> (ø)


using prev/next methods with external buttons

Hi :)
I'm using external buttons for prev and next buttons like this:
$('#my-prev-button').click(function() {     $('#calendar').fullCalendar('prev'); });
$('#my-next-button').click(function() {     $('#calendar').fullCalendar('next'); });
I expect these buttons to navigate one month up or down,  but when I click on it, multiple clicks are thrown, resulting in moving two months (sometimes more) away instead of one.
To make work this code I placed it inside the viewRender function, which I'm suspecting is the cause of this behaviour. However, I tried to fire these events from the controller and I get same behaviour.
Any help would be much appreciated, thanks!

finally moved that button initialization to the directive source, is woking fine.


Expressions: New simple functions

Extracted from #646.
We should implement some new simple functions in the expression language. All of these implementations should be fairly easy, but if any of these presents problems during the implementation phase, new issues should be created for them specifically.
List of functions we need:

[x] round

Rounds a number to an integer, or optionally a decimal with a configurable amount of decimal points

[x] text

Should look up a value from a text resource, or from a language key. Additional arguments should be considered parameters to the text resource, if any are provided. Returns string or null

[x] strLength / stringLength / numCharacters

Function taking a sting as an argument and returns the number for characters in the string (note: the number of characters is not the same as the number for bytes)

[x] language

Function with no parameters, returns the currently selected language (i.e. nb, en, etc).

[x] contains

String-checking function to check if the second parameter (a string) is inside the first parameter (also a string)

[x] notContains

Synonym for ["not", ["contains", ...]]

[x] endsWith

String-checking function to check if the first parameter ends with the string in the second parameter

[x] startsWith

Same as the above, but for the beginning of the text

[x] commaContains

Special function for checking if a value is included in a comma-separated list of strings.
Can also be represented as a shortcut to ["or", ["equals", string, input], ["startsWith", string, ["concat", input, ","]], ["endsWith", string, ["concat", ",", input]], ["contains", string, ["concat", ",", input, ","]]]

[ ] displayValue Created a separate issue

Looks up a component nearby, and presents its display value (which should work for number-formatted Input fields). See comment here: https://github.com/Altinn/app-frontend-react/issues/1105#issuecomment-1536240868

[x] upperCase

Takes a string, turns it into UPPERCASE

[x] lowerCase

Takes a string, turns it into lowercase

List of functions that require list support in the expression language:

[ ] sum

Should take any amount of numbers as input, and also lists of numbers. All these numbers should be summed, and the resulting number should be returned. null and non-numeric values should be considered to be 0 (i.e. no effect on the sum).

[ ] average

Same as above, but should produce the average of all the numbers summed. null and non-numeric values should be considered entries when calculating the average, as we should make a filtering function for those cases where invalid values should not be considered instead.

[ ] in

Shortcut function similar to equals, but compares the first argument against multiple others to check if the first argument matches either one of them. Should support lists of items as parameters, and should then check inside the lists as well.

[ ] notIn

Synonym for ["not", ["in", ....]]

I decided not to implement displayValue within this issue, due to https://github.com/Altinn/app-frontend-react/issues/1208,

Is this the expected behavior? That startsWith, endsWith, and contains always return true for an empty string

Is this the expected behavior? That startsWith, endsWith, and contains always return true for an empty string

Everything seems to work, tested in dev-tools.

Hmm, that looks wired.. I think we should fix this. If I remember correctly this functions is implemented using the JavaScript startsWith etc.

@bjosttveit I think it's expected behaviour, because all strings both starts and ends with nothing. It does not make sense to do that, but I still think it should work. If you do a ["startsWith", "myString", ["dataModel", "something"]] and that lookup in the data model returns an empty string, you'd get true back - but you could guard against that by checking for an empty string as well. However, if the data model path does not exist, a null will be returned, and after #1217 that should always return false.
So, TL;DR: All strings starts/ends with an empty string, but no string starts/ends with a null. I think that's the appropriate compromise, as long as we document it.


Modify NavBar

Description
Revamp Your Website: Stylish Navbar Menu for Contributing to an Open-Source Project for a Sleek and Modern Design #1291
Fixes #(#1291)
Screenshots

Checklist

[x] Tests have been added or updated to cover the changes
[x] Documentation has been updated to reflect the changes
[x] Code follows the established coding style guidelines
[x] All tests are passing

Hi @SurajPratap10
I recently updated the navbar menu for your project to make it more attractive and user-friendly. Enhance readability, improve navigation, and give your site a visually appealing touch that stands out with these simple yet impactful design updates. I've attached screenshots of the changes that contribute to this enhancement to improve the overall design.
Effect: When hovering over a navbar menu option, the background color changes, the text color also changes, and an underline appears, as shown in the screenshot.
I'm looking forward to hearing feedback from you!
Best regards,
Issue #1291
@khurshed07
https://github.com/khurshed07

Hi @rajveeerr
Please review and merge PR

Sorry I can just review code, only @SurajPratap10 can merge the code

Hi @SurajPratap10
Please review and merge PR


Verishop

global.py not require, just remove it.

Also the last commit does not have the verishop.py. have deleted it?

global.py not require, just remove it.

OK

Also the last commit does not have the verishop.py. have deleted it?

No,I will solve this problem


Add GarbageCollector for successful Sign job

In case Sign job has finished successfully, operator should delete it.
Upstream-Commit: 94747dc4e475b7c5b36cbc0c524f30ecae99aecf
Fixes: https://github.com/rh-ecosystem-edge/kernel-module-management/issues/372

/lgtm

/cherry-pick release-1.0

/cherry-pick release-1.0


Build examples

How can we build the usage examples?
I'm trying to build the examples doing the following steps:
cd examples
mkdir build
cd build
cmake ..
make all

Getting the following error:
$ make all
[  4%] Building C object CMakeFiles/features.dir/common.c.o
[  9%] Building C object CMakeFiles/features.dir/features.c.o
[ 14%] Linking C executable features
/usr/bin/ld: CMakeFiles/features.dir/common.c.o: undefined reference to symbol 'gattlib_adapter_scan_disable'
/usr/bin/ld: /usr/local/lib/libgattlib.so: error adding symbols: DSO missing from command line
collect2: error: ld returned 1 exit status
make[2]: *** [CMakeFiles/features.dir/build.make:113: features] Error 1
make[1]: *** [CMakeFiles/Makefile2:93: CMakeFiles/features.dir/all] Error 2
make: *** [Makefile:136: all] Error 2

Do I need to execute another steps or am I missing something?

Giving up using this library