Could not find trained model in model_dir: /var/folders/b8/3ywv8wg10hlbfzv5m0nzswj80000gn/T/tmplx_CY_

py2.7 got this error

and why this path '/var/folders/b8/3ywv8wg10hlbfzv5m0nzswj80000gn/T/tmplx_CY_' ?

sorry only python3

i try to run similarity.py in python3.5, tensorflow-gpu==1.14.0, but raise an exceptiontion. AttributeError: module 'tensorflow.contrib.data' has no attribute 'map_and_batch'. how to fix this bug?


fix(fund with ar): add web esm compatible arweave export PE-5849

:tada: This PR is included in version 1.5.0-alpha.2 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.5.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Changed Article and Summary section info to a hoverable

Describe the PR
Solved the Issue #363

[x] SSOC Participant

I asked to change the article and summary of books section from embedded webpages to a still image which on hover shows some information about the image with the link to the original page to look into.
Original Screenshot

Updated Screenshot

On HOVER:-

@MridulTi Brother on hovring the section just show the title of the section remove the summery and also  add Read More button on every section.  It's look good.

ead More b

So, let me make sure if this is what you mean, you mean to remove the summary on hover, and also do you want the Read More button on every hover or on Every Section, cause there is no link available that I can attach to Readmore for every section there?

@MridulTi Why there's a horizontal scrolling here?

__
  Summary: :hammer_and_wrench: This code needs a fix

@MridulTi Why there's a horizontal scrolling here?
__       Summary: 🛠 This code needs a fix

Its for smaller screens so that the screen doesn't look too clogged up which was the reason this issue was raised my me .

@MridulTi Instead of scrolling, you can shift some items down by using grid

@MridulTi Instead of scrolling, you can shift some items down by using grid

Ok, then I will Apply it right now.

@MridulTi Instead of scrolling, you can shift some items down by using grid
Does this look right?

I changed it so please view it through preview

@MridulTi Your changes are not reflected in the deploy preview. What shall I do?
__
  Summary: :question: I have a question  |  Tags: Not reusable

@MridulTi Your changes are not reflected in the deploy preview. What shall I do?
__        Summary: ❓ I have a question  |  Tags: Not reusable

What? But I can clearly see my changes in the deploy preview
Here is the video link I recorded just now showing that
https://drive.google.com/file/d/1CDnRTsraunaT9_6SSs65qzh-c0iOZ_W9/view?usp=sharing

@MridulTi I got it. Your screen size is bigger taht's why it's visible to you.

Pull the recent changes once again and make the section responsive for all screen size as the articles is disappearing at a certain screen size.
Kindly fix it.

I fixed it kindly check it.

@MridulTi Can you share a video for that as your changes are not reflected in the deploy preview?
__
  Summary: :question: I have a question  |  Tags: Not reusable

@MridulTi Can you share a video for that as your changes are not reflected in the deploy preview?
__       Summary: ❓ I have a question  |  Tags: Not reusable

Sure , Here is the link https://drive.google.com/file/d/154FSUa_aYystTZcbKhTrRl9_RcpqIE0M/view?usp=sharing

Merge conflicts


DPI setting not working correctly on Logitech G300s

Information

ratbagd version (ratbagd --version): 0.16
Distribution: Pop!_OS 21.04
Kernel version (ex. uname -srmo): Linux 5.13.0-7614-generic x86_64 GNU/Linux

Device info (if applicable):
$ ratbagctl Logi info
warbling-mara - Logitech G300s Optical Gaming Mouse
             Model: usb:046d:c246:0
 Number of Buttons: 9
    Number of Leds: 1
Number of Profiles: 3
Profile 0: (active)
  Name: n/a
  Report Rate: 500Hz
  Resolutions:
    0: 50dpi
    1: 400dpi (active) (default)
    2: 450dpi
    3: 700dpi
  Button: 0 is mapped to 'button 1'
  Button: 1 is mapped to 'button 2'
  Button: 2 is mapped to 'button 3'
  Button: 3 is mapped to macro '↕SCROLLLOCK'
  Button: 4 is mapped to 'button 5'
  Button: 5 is mapped to macro '↓LEFTCTRL ↕RESERVED ↑LEFTCTRL'
  Button: 6 is mapped to macro '↓LEFTALT ↕RESERVED ↑LEFTALT'
  Button: 7 is mapped to 'profile-cycle-up'
  Button: 8 is mapped to 'resolution-cycle-up'
  LED: 0, depth: rgb111, mode: on, color: 00ffff
Profile 1:
  Name: n/a
  Report Rate: 1000Hz
  Resolutions:
    0: 100dpi
    1: 200dpi (active) (default)
    2: 300dpi
    3: 500dpi
  Button: 0 is mapped to 'button 1'
  Button: 1 is mapped to 'button 2'
  Button: 2 is mapped to 'button 3'
  Button: 3 is mapped to 'button 4'
  Button: 4 is mapped to 'button 5'
  Button: 5 is mapped to 'resolution-down'
  Button: 6 is mapped to 'resolution-up'
  Button: 7 is mapped to 'profile-cycle-up'
  Button: 8 is mapped to 'resolution-alternate'
  LED: 0, depth: rgb111, mode: on, color: ffffff
Profile 2:
  Name: n/a
  Report Rate: 500Hz
  Resolutions:
    0: 100dpi
    1: 400dpi (active) (default)
    2: 300dpi
    3: 800dpi
  Button: 0 is mapped to 'button 1'
  Button: 1 is mapped to 'button 2'
  Button: 2 is mapped to 'button 3'
  Button: 3 is mapped to macro '↕SCROLLLOCK'
  Button: 4 is mapped to 'button 5'
  Button: 5 is mapped to macro '↓LEFTCTRL ↕C ↑LEFTCTRL'
  Button: 6 is mapped to macro '↓LEFTCTRL ↕V ↑LEFTCTRL'
  Button: 7 is mapped to 'profile-cycle-up'
  Button: 8 is mapped to 'resolution-cycle-up'
  LED: 0, depth: rgb111, mode: on, color: 00ffff

Describe the bug
I'm not able to set the DPI correctly. Some values are bugged (for example, 850 is very slow, but 900 isn't) and I'm not sure if any of them is correct. I set it to 400 DPI and booted up Minecraft with the same sensitivity I use on Windows (with raw input on) and it is WAY faster.
To Reproduce
Steps to reproduce the behavior:

Run ratbagctl Logi dpi set 850
Move the cursor around and notice that it's very slow
Run ratbagctl Logi dpi set 900
Move the cursor around and notice that it's faster than with 900 DPI set

Logs
Please start the daemon with verbosity and reproduce the issue.
First make sure it isn't running already.
$ ratbagd --verbose=raw
ratbag debug: New device: SIGMACHIP USB Keyboard
ratbag debug: Using data directory '/usr/share/libratbag'
ratbag debug: No data file found for 1c4f:0002
ratbag debug: New device: SIGMACHIP USB Keyboard
ratbag debug: Using data directory '/usr/share/libratbag'
ratbag debug: No data file found for 1c4f:0002
ratbag debug: New device: Logitech G300s Optical Gaming Mouse
ratbag debug: Using data directory '/usr/share/libratbag'
ratbag debug: device assigned driver logitech_g300
ratbag debug: hidraw info: bus 0x03 vendor 0x46d product 0xffffc246
ratbag debug: Logitech G300s Optical Gaming Mouse is device '/dev/hidraw0'.
ratbag debug: Parsing HID report descriptor
ratbag debug: Parsing HID report descriptor
ratbag debug: hidraw info: bus 0x03 vendor 0x46d product 0xffffc246
ratbag debug: Logitech G300s Optical Gaming Mouse is device '/dev/hidraw1'.
ratbag debug: Parsing HID report descriptor
ratbag debug: Parsing HID report descriptor
ratbag debug: - HID report ID 01
ratbag debug: - HID report ID 80
ratbag debug: - HID report ID f0
ratbag debug: - HID report ID f1
ratbag debug: - HID report ID f2
ratbag debug: - HID report ID f3
ratbag debug: - HID report ID f4
ratbag debug: - HID report ID f5
ratbag raw: feature get:   f3 06 03 01 88 09 0e 40 01 00 00 02 00 00 03 00 00 00 00 47 05 00 00 00 01 00 00 04 00 0d 00 00 0c 00 00
ratbag raw: feature get:   f4 07 00 02 84 06 0a 02 01 00 00 02 00 00 03 00 00 04 00 00 05 00 00 0b 00 00 0a 00 00 0d 00 00 0e 00 00
ratbag raw: feature get:   f5 06 03 02 88 06 10 44 01 00 00 02 00 00 03 00 00 00 00 47 05 00 00 00 01 06 00 01 19 0d 00 00 0c 00 00
ratbag raw: feature get:   f0 02 00 00
ratbag raw: 'Logitech G300s Optical Gaming Mouse' is in profile 0
ratbag debug: driver match found: Logitech G300
hidraw0: "Logitech G300s Optical Gaming Mouse", 3 profiles
ratbag debug: New device: Logitech G300s Optical Gaming Mouse
ratbag debug: Using data directory '/usr/share/libratbag'
ratbag debug: device assigned driver logitech_g300
ratbag debug: hidraw info: bus 0x03 vendor 0x46d product 0xffffc246
ratbag debug: Logitech G300s Optical Gaming Mouse is device '/dev/hidraw0'.
ratbag debug: Parsing HID report descriptor
ratbag debug: Parsing HID report descriptor
DBus server ready
ratbag debug: Profile 0 changed, rewriting
ratbag raw: feature set:   f0 42 00 00
ratbag raw: feature set:   f3 06 03 01 92 09 0e 40 01 00 00 02 00 00 03 00 00 00 00 47 05 00 00 00 01 00 00 04 00 0d 00 00 0c 00 00
ratbag debug: Profile 1 changed, rewriting
ratbag raw: feature set:   f4 07 00 02 84 06 0a 02 01 00 00 02 00 00 03 00 00 04 00 00 05 00 00 0b 00 00 0a 00 00 0d 00 00 0e 00 00
ratbag debug: Profile 2 changed, rewriting
ratbag raw: feature set:   f5 06 03 02 88 06 10 44 01 00 00 02 00 00 03 00 00 00 00 47 05 00 00 00 01 06 00 01 19 0d 00 00 0c 00 00
ratbag debug: Profile 0 changed, rewriting
ratbag raw: feature set:   f0 42 00 00
ratbag raw: feature set:   f3 06 03 01 91 09 0e 40 01 00 00 02 00 00 03 00 00 00 00 47 05 00 00 00 01 00 00 04 00 0d 00 00 0c 00 00
ratbag debug: Profile 0 changed, rewriting
ratbag raw: feature set:   f0 42 00 00
ratbag raw: feature set:   f3 06 03 01 88 09 0e 40 01 00 00 02 00 00 03 00 00 00 00 47 05 00 00 00 01 00 00 04 00 0d 00 00 0c 00 00

Additional context
The debug output is after I ran the following commands:
$ ratbagctl Logi dpi set 900
$ ratbagctl Logi dpi get
900dpi
$ ratbagctl Logi dpi set 850
$ ratbagctl Logi dpi get
850dpi
$ ratbagctl Logi dpi set 400

It looks like related piece of code was changed in #1035. Would it be possible for one of you to revert the change and check if it fixes the problem?
git revert --no-commit 20b573668e664bb251db3bb1d078255085cebf98
ratslap - utility for G300 mentioned in #1458 - seems to set DPI the way before #1035 was merged.

It looks like related piece of code was changed in #1035. Would it be possible for one of you to revert the change and check if it fixes the problem? git revert --no-commit 20b573668e664bb251db3bb1d078255085cebf98 ratslap - utility for G300 mentioned in #1458 - seems to set DPI the way before #1035 was merged.

thanks!
works fine now.


[Bug]: Online - Stage selection fails with multiple players on same LAN

Tweaks version
OutRun2006Tweaks-0.5a
Describe your issue here (please attach the OutRun2006Tweaks.log file with your report, you can drag+drop it into the text area)
This one is a little weird to describe, sorry if this is unclear.
I played in a 5-player lobby, with 3 remote players (one of whom was hosting), myself, and one player on my LAN. At the end of the first section, every single time, the other player on my LAN would be able to continue, but my client wouldn't load the next stage. It was as if the next route wasn't selected at all: the "Next Stage" text wouldn't appear, the red arrows blocking one path wouldn't appear, and eventually I'd run into an invisible wall in a blue void.

This still occurs even if a fixed course (e.g. Goal A 2SP) is selected, I guess it still has to go through the "selection" step anyway.

OutRun2006Tweaks.log


remove all potentially sensitive words form username generator db

Alinn opened one before i got a chance, still needs doing but use her issue


Catch our fork up with kepler's master branch

The primary Kepler team has added a bunch of features/bug fixes that we should probably incorporate into our version sooner rather than later.

done!


Sporadic failure of WaitUntilAnnotationFeatureTest during full build

The test sometimes fails for me with:
Failed tests:
  WaitUntilAnnotationFeatureTest.demonstrateWaitUntilVisible:35
Expecting:
 <498L>
to be greater than:
 <500L>

Tests run: 430, Failures: 1, Errors: 0, Skipped: 0

Looks like a race against the system clock. Not sure how to resolve it yet, I'll can have a look later.


Nuget package 3.1.13 fails to declare dependency

The 3.1.13 nuget package for Microsoft.Diagnostics.Tracing.TraceEvent fails to declare it has a dependency on Microsoft.Diagnostics.NETCore.Client
The dependency was added in:
https://github.com/microsoft/perfview/commit/c847ec9392312c6159434cd87312040170303a35
and shows up as a dependent dll when examining referenced dlls in nuget package explorer (along with any other tooling that walks referenced dlls to confirm all needed dlls are present):

I'm not sure it's needed at runtime, but the reference is there, suggesting it is needed.

Thanks for reporting this @cg110.  I had noticed this during code review, but only got part of the fix in.  I've posted #2071 to finish it up.  Unless you're using EventPipe streaming support, you should be fine, and won't see the new DLL get loaded.

Great thank you.


windows 10 and python 3.5 ImportError: DLL load failed

I've installed the precompiled wheel file from http://www.lfd.uci.edu/~gohlke/pythonlibs/#rtmidi-python.
rtmidi-python is in the pycharm module list.
I ve used rtmidi-python on win7 and python 3.4 without problem.
thanks for your help

after installing Visual C++ Redistributable for Visual Studio 2015 it's OK

I'm glad to hear that you got it working.


gulp setup-project doesn't work

I've got the following errors:
Are you sure you want to continue connecting (yes/no)? The authenticity of host 'github.com (<IP_ADDRESS>)' can't be established.
RSA key fingerprint is SHA256:nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8.
Are you sure you want to continue connecting (yes/no)?
[20:05:27] 'setup-project:clone-repos' errored after 3.76 s
[20:05:27] Error: Command failed: /bin/sh -c git clone 'git@github.com:syntaxhighlighter/brush-delphi.git'
Cloning into 'brush-delphi'...
Host key verification failed.
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
git clone 'git@github.com:syntaxhighlighter/brush-delphi.git'
at setup-project.js:35:29
at tryCatcher (/Users/ivans/RingCentral/syntaxhighlighter/node_modules/bluebird/js/release/util.js:16:23)
at Promise._settlePromiseFromHandler (/Users/ivans/RingCentral/syntaxhighlighter/node_modules/bluebird/js/release/promise.js:503:31)
at Promise._settlePromise (/Users/ivans/RingCentral/syntaxhighlighter/node_modules/bluebird/js/release/promise.js:560:18)
at Promise._settlePromise0 (/Users/ivans/RingCentral/syntaxhighlighter/node_modules/bluebird/js/release/promise.js:605:10)
at Promise._settlePromises (/Users/ivans/RingCentral/syntaxhighlighter/node_modules/bluebird/js/release/promise.js:680:18)
at Async._drainQueue (/Users/ivans/RingCentral/syntaxhighlighter/node_modules/bluebird/js/release/async.js:126:16)
at Async._drainQueues (/Users/ivans/RingCentral/syntaxhighlighter/node_modules/bluebird/js/release/async.js:136:10)
at Immediate.Async.drainQueues [as _onImmediate] (/Users/ivans/RingCentral/syntaxhighlighter/node_modules/bluebird/js/release/async.js:16:14)
at processImmediate [as _immediateCallback] (timers.js:383:17)
``

you need to add the Git protocol, but I fix it by this way:
change the key world "git@github.com:" into "https://github.com/" in my local repo, run the command next:
gulp setup-project
enjoy it !

Should I update the docs to reflect this?
On Sun, Mar 6, 2016, 12:51 AM 史荣琦<EMAIL_ADDRESS>wrote:

you need to add the Git protocol, but I fix it by this way:
change the key world "git@github.com:" into "https://github.com/" in my
local repo, run the command next:
gulp setup-project
enjoy it !
—
Reply to this email directly or view it on GitHub
https://github.com/syntaxhighlighter/syntaxhighlighter/issues/378#issuecomment-192837075
.

Having spent hours today with a similar problem, would be good if the docs were updated to include this!
Using SyntaxHighlighter v4.0.1 I found I had to modify setup-project.js.
The source lines are:
const loadRepos = () => loadReposFromCache().error(loadReposFromGitHub).then(R.map(R.pick(['ssh_url', 'name'])));
const cloneRepo = repo => { git(`clone '${repo.ssh_url}'`, REPOS_DIR); }

And my replacement lines are:
const loadRepos = () => loadReposFromCache().error(loadReposFromGitHub).then(R.map(R.pick(['clone_url', 'name'])));
const cloneRepo = repo => git(`clone ${repo.clone_url}`, REPOS_DIR);

Rather important to note the single inverted commas have to be removed round ${repo.clone_url}, otherwise the https protocol is not recognised.

Me too.
There is no reason to use ssh to clone, I think.
I hope that @appetere 's fix is accepted

@appetere good catch! Want to make a PR?


Docs/readme contribute node version

Changing node version from node@^16 to<EMAIL_ADDRESS>to specify that node@{17,18} is not compatible.
Also I could not commit nor push without --no verify, so I added another ### Tooling part in the second commit.

closed. wrong PR target.


Proposed data directory layout

Currently, we only support variant data derived from VCF, in either vcf.gz or wormtable format. We need to support other types of data as we move to support the full API. I suggest we use a designated file system layout for the data directory to discover the files and their relationships. An initial pass at this might be
dataDir/
     datasetId1/
           variants/
                 variantSetId1/
                       chrom1.vcf.gz
                       chrom2.vcf.gz
                 variantSetId2/
                       variants.wt
           reads/
                  [Some directory structure laying out BAM/SAM files]
           references/
                  [Some directory structure laying out references]
     dataSetId2/
           variants/
                  ....
           reads/
                  ....
           references

That is, within the data directory, each directory d corresponds to a Dataset with ID d. Within a given dataset, we have three directories, called variants, reads and references. Within the variants directory, we then have more directories, one for each VariantSet. Within a VariantSet directory, we have a bunch of files that define these variants in what ever formats we support.
For data within a given variant set, we could follow the existing convention used for the TabixBackend: we can split the variant set over as many files as we like, so long as we don't have data for the same chromosome in two files. I've deliberately mixed up wormtable and VCF format files in here. The input should detect the file type and make an instance of the appropriate handler based on the extension. If we don't support a given file type then we complain and quit. This would get rid of the currently very clumsy model of specifying wormtable or tabix as command line arguments to determine the type of backend to allocate.
We'd then just call the server using ga4gh_server dataDir for development and testing purposes. For deployment an absolute path to the required data directory in a config file would be all that is needed.
The idea is that we use the file system hierarchy to explicitly set out the structure of the data to be served. This keeps the number of configuration variables we need as we deal with more complex datasets down. The downside is that we do require a pretty complex file system hierarchy to specify the data to be served. One way we could alleviate this problem is by providing a tool to check the layout of the hierarchy and to raise errors if it's not well formed. This could also print some summaries about the data that's in there too, so that people can get an overview of what they're about to serve.
I've not filled out the reads and references section, as I don't understand this side of things all that well. Will this sort of decomposition make sense here too? Does this hierarchy capture the structure of the API, or is it too restrictive? Any feedback would be much appreciated!

We need to push ahead with the reads and references API, so I think we should use this approach for the moment unless someone has a better idea. We can always move over to something better later if it turns out to be a bad idea. Are there any objections?

+1 This looks immensely workable.
On Tue Jan 13 2015 at 8:57:47 AM Jerome Kelleher<EMAIL_ADDRESS>wrote:

We need to push ahead with the reads and references API, so I think we
should use this approach for the moment unless someone has a better idea.
We can always move over to something better later if it turns out to be a
bad idea. Are there any objections?
—
Reply to this email directly or view it on GitHub
https://github.com/ga4gh/server/issues/44#issuecomment-69747048.

Proposed better idea: @Naburimannu is implementing configuration with defaults. Let's set some default directories in our default config and allow users to override via a config file. Longer term we will need to set many options (ACLs, size limits, logging retention, etc), and should consider an interactive setup script.

Would you mind fleshing out your idea with an example of what the config file would look like @kerrydc? I'm struggling to imagine how this approach would scale to hundreds of files (which we definitely need to support to be useful), so it would be good to talk through a concrete example here.

Closing this issue, as this has been resolved. For the record, the resolution is to have independent directories for each data set, and within the data set we have the required variants and reads subdirectories.


Having installed graalvm, why are npm modules now being stored in its tree?

>npm install -g @google/clasp
C:\Users\bugma\scoop\apps\graalvm11\current\languages\js\bin\clasp -><EMAIL_ADDRESS>npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| ^6.0.0 but none is installed. You must install peer dependencies yourself.

+<EMAIL_ADDRESS>added 160 packages from 92 contributors in 43.767s

I don't recall asking for this behaviour.

FWIW, the answer is: GraalVM has a node implementation that ships with it.  Their node, npm, et al commands are part of the standard set of binaries exposed.  So ... this is the correct behaviour as far as a GraalVM install is concerned.
Scoop would have to do extra work to make that, uh, not happen.  Which might be the right choice, but I would personally have been surprised to find out that the GraalVM version of node was not put on the path by default.

Ok


Allow the usage of more types of Actors and possibly other Documents (e.g. Items)

Solution
Either:

Harder: add another check for the new allowed types and use seperate mapping fields:

OR

Easier: remove that check completely and the user must change the mapping if they want to switch from exporting characters to any of the other options.

https://github.com/arcanistzed/pdf-sheet/blob/3ec5d5072d54aa2aef5363dfdd15e3ba5b06db8e/scripts/pdfsheet.js#L136-L137

Just putting my vote on allowing export of NPC's (monsters) as well

I'm working on a large refactor and it will be included in that. In the meantime, this issue describes the very small change required for this.

NPC now working will also work on items in time.
At the moment items get exported, for 5e, in the extended mapping and PDF


Update query cost for attribute values

Note This is a 3.5 port of https://github.com/saleor/saleor/pull/11411

I want to merge this change because it updates the query cost map for selected attribute values (which weren't considered when calculating cost).

Impact

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

Pull Request Checklist

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

Task linked: CLOUD-2106 Incident 66: Update query cost map for incident query


Clustering Coefficient example

Hi!
I tried to create a clustering coefficient as an example using the API. I doubt this is the best way to do it, so I would be glad if somebody could review this.
Thanks!

So I started looking at this and I accidentally merged with the upstream. Oops, sorry.
I tried using reduceOnNeighbors to generate the list of possible edges between the neighbors of a node, but it doesn't seem possible, since it has to return a single value, so I can't use something like out.collect.
I'll redo the clustering coefficient example using the same structure as the current examples and then we can try using more of the flink-graph features.

Hi @balidani! You can first use reduceOnEdges to store the neighborhood of each vertex in a HashSet. This HashSet will be the value you will return, i.e. the vertex value.
Then, you can use reduceOnNeighbors to compute the common neighbors between vertices.
Let me know if you have any doubts :)


HTML Lang Attribute

By default the  tag is rendered having the lang attribute set to language and location for example "en-us" for US English.
We don't want to differentiate between en-us and en-en for example, or de-de and de-au so we cut the location off leaving the two letters of the language code in the rendered  tag. We are not big enough of a site to have individual pages for each location and language is enough.
I could submit this as a change if there is any interest in this and would be glad not having to make a custom build anymore.
What are your thoughts?  Should this somehow be enabled/disabled? What would be the best way? Maybe the HostSetting or PortalSetting table? Would that be a good place to add a new setting? For example LanguageCodeWithoutLocation Y/N with the default being 'N'.
Here is some more info about the lang attribute: https://www.w3schools.com/tags/att_lang.asp
Best regards & happy DNNing
Andy9999

I'd think a portal setting, maybe something like ExcludeRegionFromLanguageAttribute

That is a great name for the setting! Thank you.


Typo Problem

In dygraph branch, I think that the module name BisicBlock should be BasicBlock.
It would be better if the module name is consistent with the name in origin paper ( and other frameworks ) to make it easier to understand.

Thanks for your attention! The typo is fixed in #236

Great!

It seems that some typos are still not fixed.

All fixed in #237 , Thx!


fix: avoid throwing if caches is undeclared

Problem
Using getAccessToken with a runtime that does not support the global caches property throws a reference error in any runtime that does not support the CacheStorage api. This happens during the support check for the default cache, which refers to the caches directly without having verified the support yet.
Solution
Use globalThis.caches to verify the reference.

@unkhz thanks, Juhani. Do you think we can use self.caches (for which Cloudflare provides type definitions) instead of globalThis.caches?

I chose globalThis because it should be widely supported. Node 12.0.0+ and Deno 1.0+ supported (along with Bun 0.5.7, which I tested). It's also polyfilled in core-js for more ancient runtimes: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/globalThis#browser_compatibility.
Did a quick check and self seems to work nicely for Deno, Bun and Chrome, but throws reference error with Node.

Good catch! Just published these updates under v1.0.3.


CSS color pick for box shadow

This issue has occurred thrice not necessarily under box shadow. It always seems to revolve around color picking when defining properties for a single selector. This time, I was listing two drop shadows under the box-shadow element. When I select the second shadow color-picker and change the color, it changes the color on the first shadow. The issue has always been about trying to change color, either it rejects changing color or it changes an adjacent color.  And there's nothing I can do about it from then on, well, maybe delete the entire selector and try to create a new one.

Can you add a code sample (if this is relevant), or maybe a annimated gif that shows the issue?


Reset the phase of oscillators on every new note?

At least for square wave instruments this would probably be an improvement.
maybe just if there is a note-off and then a note-on.

Moved to TODO file


Update overview-identity-protection.md

Updated spelling of corelation to correlation.

@dave-mccollough : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Looks good. Thanks!


Yolo Output grid (1,13,13,30) instead of (-1,-1,-1,-1)

Hey @Syn-McJ,
I'm just looking for some advice regarding my model. I tried making my own yolov2-tiny model (on 1 class) to deploy on Unity. I am not an expert on YOLO models. The output grid shape is different than your description on the website, also it is different from the graph you have in your repository. I was wondering how you did the calculations based on the graph you had to be able to get results. I looked at the microsoft website to get more familiar with their procedures, however, calculations done in Unity is a bit different.
As of now, the result I am getting for confidence or results is NaN which is most likely due to miscalculations. My whole model is different, but it works when I use darknet detector source code with an image.
Do you have any idea or resources that can help me?

@Pouyan97,
If your output is (1,13,13,30) than it seems ok, YOLO output depends on the number of labels you have. You can check this post for some details on how it works. 1 class in your models means the last dimensions should be 5 x (5 + 1) which is 30.
(-1,-1,-1,-1) isn't a typical output shape, but some models show them which doesn't necessarily mean that they won't work, the real output shape will be different anyway.
I'm not an expert on YOLO myself, but I would recommend trying your model with python on some well-tested inference code first to make sure it's 100% correct. Also, I myself prefer to work with darkflow to train tiny-yolo2 tensorflow models.

@Syn-McJ ,
Thank you I realized the 30 being the filters I set myself right after posting the question :)). The links are very helpful.
I have tested my model's weight however translating it to ONNX might have caused some problems. I can try training with Darkflow for comparison. Thanks again.

@Pouyan97 Have you solved the problem with your model? Currently, I am trying to use a tiny yolo model trained for face detection, however I am not getting any results. Unity has also been giving two warnings: "adjusted_input8: Unknown type encountered while parsing layer adjusted_input8 of type Transpose. We replace by an identity layer." and "transpose_output: Unknown type encountered while parsing layer transpose_output of type Transpose. We replace by an identity layer.". I think these warnings might be the reasons for my current problems. Any thoughts, or by any chance have you encountered this kind of warnings?


$watch vs stop() callback run sequence

I try to convert this connected list to the multiselection list. When I select multiple items from right to left, it doesn't work at all,  not sure if I did wrong or there is bug.
Here's the demo.

That's interesting... It seems right... I will investigate it.

The issue seems to be that the $watch runs before the stop callback, where the multi-item-selection actually moves the models from one list to an other. Here is a working sample-pen.

Feel free to re-open in any case.

Hi, thank you very much for the quick fix. I have another question.  I add a button to find all the selected items from the left, then add to the right instead of drag and drop. How can I find all the selected items?
Here's the pen.

Here is a working codepen sample.
Alternatively, you can listen for the ui-sortable-selectionschanged event one the parent element.

Thank you!

Hi, your codepen sample works find in Chrome and Firefox, but in IE11 got SCRIPT1002: Syntax error for the line "var selectedItems = $('.availableReportsBox .ui-sortable-selected').toArray().map(x => $(x).scope().listItem);", looks like the IE doesn't like the "=>".

I don't even remember using it... But it obviously got in there anyway. I guess you can easily change the arrow function expression to a plain anonymous function yourself function(x){...} .

It works fine change to "var selectedItems = $('.availableReportsBox .ui-sortable-selected').toArray().map(function (x) { return $(x).scope().listItem });", thanks.


Refactor codebase to async/await

We're currently using promise chains everywhere In the code. Refactoring to Async/await would be helpful as it gives better insight in how the code is organized, it's a less verbose and indented way to write code.
This epic is meant to track the work.

We've decided to do a max of 10 commands per PR.

[x] #3430
[ ] Refactor to async/await, commands ... to ...

Added the needs discussion label to indicate that we need to decide how we want to split the refactoring work to allow multiple people to help out and speed up the refactoring process.

Hi @pnp/cli-for-microsoft-365-maintainers,
Time for some discussion, as @milanholemans PR is almost merged by @waldekmastykarz 😉.
We have like 560 commands. I was planning on splitting the work into 5 issues, each with a nice task list of 112 commands.

Big fan of splitting the work!

Hi @pnp/cli-for-microsoft-365-maintainers,
Time for some discussion, as @milanholemans PR is almost merged by @waldekmastykarz 😉.
We have like 560 commands. I was planning on splitting the work into 5 issues, each with a nice task list of 112 commands.

Shouldn't we divide the workload in command groups? Will be more clear if your task is just to refactor all aad, planner and pp commands for example in one go.
This would also be easier to describe in the release notes.
If you just split it by a fixed number of commands it is possible that for example you have to refactor all aad, planner and few pp commands. This might be a bit unclear and is harder to document in the release notes. "Refactored add, planner and some pp commands" looks a bit weird in the release notes imo 🙂

However the group spo will be a tough one to refactor in one go 🙂

That's why I did it like this. But let me check if I can make a more logical split.

Ok, I updated it. SPO is a bit big. What do you think about splitting it in three?

Ok, I updated it. SPO is a bit big. What do you think about splitting it in three?

The proposed chunks are looking good to me. I think we can definitely split spo in smaller chunks, else no one will volunteer for that one 😄

Refactoring some commands will be more work than others. My first thought was to split the work per command but that might make a mess of our issue list so perhaps we should look at slightly bigger chunks but definitely smaller than a whole workload. Also, don't underestimate the time needed to review each change and ensure there are no breaking changes in the commands behavior.

Ok, so you would say split it in smaller chunks than I did? like 10-20 commands each or something?
spo is a very big task, with a lot of huge commands. But some other workloads (based on the ms graph) are relatively simple.
How about we split it per subsection?

That all are good comments and for sure we may try to divide in smaller parts in order to share the workload 👍.
Just a small comment from my side is not to try to find the perfect balance and now check every comment to make perfectly equal chunks 😉.
I guess I have no problem in doing something smaller then others 😅. Only joking. can't wait to try to help out 😉

After some discussion: putting this issue on hold until v6 is shipped.

When we start working on it, let's split it up indeed in small chunks with a few commands each so that the workload is reasonable and people don't get stuck for weeks working on it.

v6 is shipped, are we going to proceed with this? If so, let's discuss the chunk size of the amount of commands per issue.

We shouldn't have chunk sizes bigger than 10 commands. Anything more will extend the refactoring work, leading to tons of merge conflicts, and a lot of work to merge these PRs.

Will we open this up for everybody? If so, it could be nice to have one chunk ready as an example. A bit like we did with adding the responses to all our command docs.

Do you mean an example PR how to refactor it? Because we have plenty of commands that use async/await already.

Do you mean an example PR how to refactor it? Because we have plenty of commands that use async/await already.

In that case, let's link one as a reference for everyone to use and which we'll use when reviewing PRs.

Hi,
I would be very interested with helping refactoring this. Could I get started on this? I'd suggest that we start with the smallerish command groups, and work up that way.

Hi @MathijsVerbeeck, it would be great if you could help with this. We need to update the specs though. We've determined to take 10 commands max in every PR.
If you want to start already, just create a new issue with a checklist of 10 commands, and work through them. Reference the issue here, I'll add it to the specs.

Perfect, thanks for the feedback @martinlingstuyl

@martinlingstuyl
I've just created the first issue + PR
#4933 for the issue,
#4934 for the PR
If you have any feedback regarding naming, ... shoot!

@martinlingstuyl
I've just created the first issue + PR
#4933 for the issue,
#4934 for the PR
If you have any feedback regarding naming, ... shoot!

Added it, thx!

Nice @MathijsVerbeeck!

I think we should add a complete list of commands with checkboxes here, and check the ones that are PR'ed, to keep track of covered commands.

I think we should add a complete list of commands with checkboxes here, and check the ones that are PR'ed, to keep track of covered commands.

Those are referenced in the other issue. Otherwise this one would become massive!

Yes, but we need one overview, I think it will become unclear otherwise which ones have not been picked up...

Yes, but we need one overview, I think it will become unclear otherwise which ones have not been picked up...

Hi @MathijsVerbeeck, looking at it, this actually looks quite neat. Let's keep it like this 👍

Can I help on this one?

Can I help on this one?

I don't see any reason why not 😄 We'd just need to align who picks up which set of commands I guess, so no more me just creating issues and instantly creating the PR's 😭
I'm currently busy with the m365 pa commands. If it might be handy for you, I could give you a brief summary of what you should certainly check for when reviewing the commands.

I'm currently busy with the m365 pa commands. If it would be handy for you, I could give you a brief summary of what you should certainly check for when reviewing the commands.

I can start with m365 pp if that is good for you? I propose we create the issue before we start doing the work, that case we don't overlap each other and we have a clear view on who is doing what, is that ok for you?

I can start with m365 pp if that is good for you? I propose we create the issue before we start doing the work, that case we don't overlap each other and we have a clear view on who is doing what, is that ok for you?

Perfect.

Strong work guys! Love to see it. 🚀

@nicodecleyre @MathijsVerbeeck thank you for your enthusiasm to finally tackle this issue! It's been here for some time. It will take quite some effort to get everything refactored and we're grateful that you want to help us with that. May I ask you for sure to test every command that you refactored? With such 'repetitive' tasks, it is easy for bugs to creep in. Therefore, if both the contributor and the maintainer run all commands, we'll reduce that risk to a minimum.
Thank you for all the work! 🙏

Great work all, it's finally time to close this epic! 🥳🥳🥳🥳🎈🎈🎉🎉
Special thanks to @MathijsVerbeeck and @nicodecleyre who took on the brunt of the work.


feat: smaller networks for tests

What?
Make test run faster by using tiny networks
Why?
Faster is better?

Looks like it's ~1 minute faster :racehorse:


Remote Code Execution vulnerabilities in dependencies

When running npm install on this project I get two sever vulnerabilities for Remote Code Execution in the "pug" and the "pug-code-gen" dependencies.
https://npmjs.com/advisories/1643
https://npmjs.com/advisories/1644
This issue is resolved by updating the packages to 3.0.1 according to the links.

@MiniDigger What do you think about this?


Thrown error does not provide data where the validation error has happened

In the current implementation we're throwing errors without returning any structured data to determine where the validation error has happened. That information is being returned via the error message, which is not always ideal.
Example: A user provided a HAR config with an invalid request url.
{
  "log": {
    "entries": [
      {
        "request": {
          "method": "POST",
          "url": true
        }
      }
    ]
  }
}

Such a HAR config would throw  InvalidArchiveError  with a message of Invalid request url (0): must be string and with a set property name  equal to InvalidRequestUrl.
This implementation has a couple of issues:

The error message provides too much detail when not used in a CLI. Currently error messages almost always provide the index where the validation error happened. This probably leads to more confusion than actually helping the user if we're displaying error messages outside of a CLI.
A possible solution would be to remove the index part of the error message when validating HAR configs and only augmenting them with the index when used in a CLI.
This means the error message of our example would become:

Programmatic/Browser usage: Invalid request url must be string
CLI usage: Invalid request url must be string. Occurred in an entry with an index of 0.

Errors do not provide any structured data to determine where the validation error happened. Knowing where the validation error has happened would add more flexbility to the user to determine what to do with a given error.
Currently the only additional information that we provide is a name property (like InvalidRequestUrl or InvalidRequestQuery).
I'm suggesting extending the error object with two additional properties:

type - specifies the type of validation error. Since we're validating different types of data (like request, headers, cookies, queryString, etc.) it would be beneficial to know the type of validation error.
index - specifies the index of validation error. Usually this property would be a number. In some cases it would be a tuple [number, number]. For example, when throwing validation errors for headers we would like to know the indexes of both the entries and headers arrays respectively. With the addition of typeproperty or checking for the name property the user will know what type to expect from index.

Let me know your thoughts on the given suggestions. Thanks!

TL;DR; Would be nice to add json path to the affected node. Perhaps we could make us of inheritance (since we are dealing with a node tree (parent/child).

So if InvalidRequestUrl is thrown, wouldn't one expect to see InvalidRequestUrl: must be string. Received  <typeof request.url>. or at least InvalidRequestUrl: must be string? (spelling out Invalid request url seems redundant, since that part of the error is implied by the name of the error).
JSON Path
I would suggest that we "pin point" the problem with json path (rather than indexes).
Eg. { ..., path: 'entries[4].request.headers[0].name'}
Error inheritance
When it comes to ValidationError.type, I don't know if it would be easier to just keep indicating type with the error constructor (name).
Let's say we are throwing a InvalidRequestQuery (in combination with a json path), what would the type be?
Sharing some thoughts... Since we have a tree structure, one could make use of the structure when creating error types.
That would give us granular errors that uses the tree structure for inheritance (as a bonus, names could probably be less verbose).
Perhaps stupid?
RequestError extends ValidationError
HeadersError extends RequestError

const error = new HeadersError('Ermagherd!')

error instanceof ValidationError // It's a validation error
error instanceof RequestError // It's a request validation error
error instanceof HeadersError // It's a request headers validation error

Thanks for your suggestions! ❤
I really like the JSON Path solution, definitely better than what I had in mind 😅
In terms of error inheritance I had the same thought and while I agree that it's probably more correct semantically I did not want to introduce a breaking change if I did not need to. It felt like error inheritance solution achieved the same goal just using a different API, so extending the original InvalidArchiveError with a type property seemed less intrusive.
If my thought process does not make any sense pls let me know 👍

I really like these ideas that you guys have put forward. I have some thoughts and questions.
Having both verbose and less verbose error message sounds great!

Would it make sense for the choice to get verbose messages or not to be explicitly set when compiling rather implicit depending on runtime? Alternatively packing both a "stracktrace" style error + a "non programmer readable" version with the error meta?

Regarding the error type/specific error classes, what purpose would this information serve and how would it be used? We type out those error messages by hand so they should be pretty useful alone, if we add JSONpath on top of that it seems to me like the error message + JSONpath will be more than enough to highlight/help to pinpoint where the error is?


How to have more than 1 verb

Hey,
I am currently coding on an API Documentation and wanted to know if anyone ever needed 2verbs, I need to document PUT and PATCH in 1Method
[HttpPut]
[HttpPatch]
[Route("{id}")]
[ContentTypeRoute("", "application/json")]
[ContentTypeRoute("", "text/json")]
[ResponseType(typeof(UsersResponse))]
public IHttpActionResult Update(string id, [FromBody] Models.DataModels.User user)
{
LOGGER.Debug("Processing PUT/PATCH request with user content...");
var serviceUser = PreparePutUser(GetUserFromServer(id), user);
UpdateUserOnServer(serviceUser);
return ProcessSuccessfulPutUser(UsersMapper.Map2Api(serviceUser));
}
Anyone ever had to deal with double verbs? Does anyone know how to  this?

I did a push request, I made it myself lets discuss there #215


[Clang importer] Consider attributes on the typedef name for an anonymous tag.

In C, one can provide a typedef name for an anonymous tag declaration in
one shot, e.g.,
typedef struct {
  double x, y
} Point;

In this case, there are effectively two declarations at the C level:
the typedef and the struct. The Clang importer was only taking
attributes from the anonymous struct (i.e., the tag) and not from the
typedef. However, any attributes put before the typedef should apply
as well... so consider those, too.
For now, only do this for swift_attr attributes, because we're
seeing this primarily with Sendable annotations. In the future, we
can look to generalizing it, but that could have source-breaking
consequences.
Fixes rdar://91632960.

@swift-ci please smoke test


Add go module support

This resolves #181
Initialized go modules from go deps. Modified the testRuntimeStackTrace test to compare slice of the package path instead of the raw string. as only the last 5 packages/directories are returned from frame.path.
Modified the Travis-CI job to have a job which sets GO111MODULE to on and overrides the before_install and install step to use go mod download instead of dep ensure. All other steps are kept the same. See https://travis-ci.com/bhavikkumar/aws-lambda-go/builds/111472734

Codecov Report

Merging #189 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master    #189   +/-   ##
======================================
  Coverage    77.2%   77.2%
======================================
  Files          18      18
  Lines         636     636
======================================
  Hits          491     491
  Misses        104     104
  Partials       41      41

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 43eb3b9...766afd0. Read the comment docs.

The first line of go.mod should be github.com/aws/aws-lambda-go, not github.com/bhavikkumar/aws-lambda-go.

Good spot. I have fixed the module name.


feat(metrics): new splunk metrics sender

Hi @azlam-abdulsalam,
This feature includes the new Metrics Sender for Splunk. I looked at many Splunk Frameworks in NPM and the choice fell on splunk-logger. This had the most flexibility so other devs could use it as well. When implementing the settings, I oriented myself to the other senders. As you can see, the new implementation only works with an update of the core version. Enjoy the review. Feedback is welcome via our Slack channel. ;-)
I left the documentation open for the time being because I couldn't find any reference to the environment variables.
Checklist
All items have to be completed before a PR is merged

[x] Adhere to Contribution Guidelines
[x] Updates to Decision Records considered?
[ ] Updates to documentation at DX@Scale Guide considered?
[x] Tested changes?
[x] Unit Tests new and existing passing locally?

Thanks @Rocko1204  for this contribution.  Do you also have sample splunk dashboards  and instructions that we can plugin in the template directory

Thanks @Rocko1204 for this contribution. Do you also have sample splunk dashboards and instructions that we can plugin in the template directory

Hi @azlam-abdulsalam  Thx for the approval. I have created the mr https://github.com/dxatscale/dxatscale-template/pull/32 with 2 dashboard examples and the new splunk readme.


[Question] add model url failed in android

❓ General Questions

Hi
thanks for this opportunity on making LLMs run locally on android.
My device is  : samsung s22 ultra
the default models that appear on app launch are able to download and run just fine
but when I add other model URLs it just fails. the ones I tried are :
https://huggingface.co/jetro30087/vicuna-Wizard-7B-Uncensored-android-q4f16_0
https://huggingface.co/acalatrava/mlc-chat-luna-ai-llama2-7b-chat-uncensored-q3f16_1/tree/main
https://huggingface.co/jetro30087/vicuna-Wizard-7B-Uncensored-android-q3f16_0
🤔 is there any specific url formatting that I should consider?

Maybe you can refer to adding model by url on iOS. Check the steps and refer to the sample url in it.
Following is the link:
https://mlc.ai/mlc-llm/docs/prebuilt_models.html

Every link I tried so far, all state that it's not supported, with the current latest apk
Even the single other model listed for android on https://mlc.ai/mlc-llm/docs/prebuilt_models.html , the very same link shown as a sample in the app itself
https://github.com/mlc-ai/mlc-llm/assets/4752645/0df113e0-fc75-469d-8f63-ab847b6022fd
It would be helpful if someone can provide an example link that actually works

We revamped our tutorials lately to include instructions on building a model for Android from Huggingface: https://llm.mlc.ai/docs/deploy/android.html#compile-pytorch-models-from-huggingface.
For now, we haven’t been focusing on officially expanding model coverage yet - it’s just not the right timing. but if you encounter any issues building models for Android on your end, please reach out and we are happy to help!

but if you encounter any issues building models for Android on your end, please reach out and we are happy to help!

I assume the guide isn't for building on android for android, I encountered so many issue that I just gave up and rm -r the repo, I might have better luck in a proot distro but I already rm it.
Not to mention the final step of building the apk which I didn't even see since I was only on step 1* of this guide which I misunderstood the android tab as building on android from a quick glance without reading the whole thing, and who knows how much more complicated that would be on android if it's even possible.
*https://llm.mlc.ai/docs/compilation/compile_models.html#install-mlc-llm-package

Screenrecorder-2023-09-28-11-25-14-664.mp4

Has the feature that allows to add custom models in the compiled app been removed? I can't seem to find it


Mobile menu button not working

The menu button at mobile sizes:

Does not trigger any behaviour.
Is missing CSS styles

@MattGreyDesign what would you suggest to improve the design? We could get rid of the burger menu completely if the icons are small enough.


Cannot access 'androidx.lifecycle.FullLifecycleObserver' which is a supertype of 'io.github.sceneview.ar.ArSceneView'

This is for arsceneview "io.github.sceneview:arsceneview:0.10.0"
Having troubles in Android Studio yielding this error when trying to access any member within ArSceneView class.
Cannot access 'androidx.lifecycle.FullLifecycleObserver' which is a supertype of 'io.github.sceneview.ar.ArSceneView'. Check your module classpath for missing or conflicting dependencies

My build.gradle dependencies:
dependencies {
    implementation "org.jetbrains.kotlin:kotlin-stdlib:1.8.22"
    implementation "androidx.core:core-ktx:1.10.1"
    implementation "io.github.sceneview:arsceneview:0.10.0"
    implementation "com.google.ar:core:1.37.0"
    implementation "androidx.appcompat:appcompat:1.6.1"
    implementation "androidx.multidex:multidex:2.0.1"
    implementation "com.google.firebase:firebase-appcheck-debug:17.0.1"
    implementation platform("com.google.firebase:firebase-bom:32.1.1")
}

Resolution: If you see this issue, upgrade your Android Studio version to Hedgehog or later


Address offline installation with prerelease option

[x] I have signed the Contributor License Agreement.
[x] This pull request is related to an issue.

Addresses issue #134 and adds the ability to specify PreRelease.
Microsoft Reviewers: Open in CodeFlow

@ryfu-msft Can you shine your magic eyes on this PR? It should be relatively small change and all tests have passed locally.

P.S. It might be helpful to have a store for the .vsix files, instead of relying on downloading. If you have any suggestions, I can add it as a file to the repository


Set BETA ribbon on top left

Task linked: QF-1799 Add a banner on QFC web pages to clearly indicate that is a beta


remove shrinkwrap which references unavailable version of ansi-styles

the shrinkwrap file here specifies a version of ansi-styles which is no longer available, as many people have noted on https://github.com/npm/npm/issues/17723
https://docs.npmjs.com/files/shrinkwrap.json says "it's strongly discouraged for library authors to publish this file," so I tried removing it entirely.

Coverage remained the same at 94.872% when pulling b2f264e332875a029ad189dad82edff30ec8ad88 on veeloinc:no-shrinkwrap into f282384419d353a8fffb323fb4ee8b78594a0064 on wmluke:master.


Run kubernetes cluster behind http proxy

I'm trying to run a Kubernetes cluster behind corporate proxy. I still have some problems, since for some reason vagrantfile-user-data is not invoked and my changes do not apply.

Proxy related configuration is applied only if HTTP proxy is defined at system level. Still there is an issue with no_proxy settings: seems that Vagrant embedded ruby just ignores no_proxy setting.

I have no way to test this so please tell me when it works for you.
I just don't understand why the drop-in looks so complex.

I've tested the change. Everything works just fine, both behind http/s proxy and without a proxy.
I've also modified code that updates/created .bash_profile: now it replaces env variables if exist and adds if not.
Need also to update it, to handle case where bash is not a default shell (I use zshell, for example).

OK, I just want to know why the changes to the .bash_profile file since I've tried this without proxy and so far it is working.

When you replace BASE_IP_ADDR with another address, you need to check if ENV variables already defined in .bash_profile, with any IP address; and replace it with new MASTER_IP_ADDR if needed or create a new ENV variable, if not exists.
I have to use a different BASE_IP_ADDR for Parallels to avoid conflict with VirtualBox virtual network adapter.

When you replace BASE_IP_ADDR with another address, you need to check if ENV variables already defined in .bash_profile, with any IP address; and replace it with new MASTER_IP_ADDR

Yes, I get this. I just don't understand why you added NO_PROXY env var stuff and related.

Adding no_proxy to current environment is required because of how Vagrantfile script is checking service readiness. This script sends HTTP GET requests to BASE_IP_ADDR+ to check is master and minions are ready. Thus, local wget app should not go though http proxy for these requests.

Thank you very much @alexei-led.


MIssing slideout.png in Android project

When running the Android project you will get an error Resource not found.
Added a slideout.png to folder\Hanselman.Forms\Hanselman.Android\Resources\drawable to resolve the isssue

I have added one, but I did not see an exception at all running it on my machine. What emulator or device where you using?

I used the Android Emulator in Visual Studio. If for example I remove the slideout.png from the project I get again the error, see screenshots

If you pull the latest it is in there. Thanks for the screenshots.

Thanks for the update
This example helped me a lot to create a first Xamarin app with MVVM, menu page and master detail


feat(digest): impl digest_to_curve

Why?
To make it easier to operate with a hash of public parameters, part of #85
What?
Adding the digest_to_curve method
How?
We add a method that simply multiplies the result of digest_to_f by CommitmentKey

close it for now as duplicate with #125 with slightly difference that it uses generator instead of commitment key.


Configure zero services and clients

Allow configuration of none entities in order to reduce static memory

Done in https://github.com/micro-ROS/rmw-microxrcedds/pull/46


Set up SCSS build

I would like this repository to use SCSS.
The way I would like this to act:

I work on this github project locally
I write in a .scss file
Every time the .scss changes (on save of the file), compile the css and add it to style.css which will act as the main style for the site.

Do we need a pre-processor for this? Could just write pure CSS.

@nickcolley My reasons for using SCSS are: bleh, it's just what I'm used to.
I didn't put a whole lot of thought into it! However, I do want to minify our CSS using a build script or what have you, so I will create a new issue for that. Thank you :)


Do you have any theory why bufio improves performance?  Just curious, apart from my curiosity, the change looks good to me :)

@cfergeau
bufio supports buffering (reads in bulks. I believe here default size is 4096)
So this will eventually reduces the number of raw calls and for few the data will be returned directly from buffer cache
Since we were doing multiple size based reads during stream protocol only here we will get a performance gain, in other case of non-stream this will degrade the performance


Parent directory completion blanks out

The problem
When using options like:
zstyle ':completion:*:*:*:*:*' menu select
zstyle ':completion:*' menu select

There is a bug which happens as of late. Completing parent directories seems to have a rendering error.
Reproduction available on:
https://asciinema.org/a/ZCAZsm1MNXkXpw4fWOLS7l7Vp
Relevant Zsh configuration
zinit light spaceship-prompt/spaceship-prompt

What is version of Spaceship are you using?
v4.15.0-1-gbe826cb
What is version of Zsh are you using?
5.9
What operation system are you running?
macOS 14.1.1
Do you use any Zsh framework or plugin manager?
None
Which terminal emulator do you use?
iTerm.app
Additional information
No response

I'm encountering the same issue as described. Have you managed to resolve it yet?


Consolidate release notes from all repos and publish it in konveyor/community

Currently, each repo when it gets released, they have changelog/release notes associated with it. Going forward we would like to find a way to consolidate this and publish it in community repo whenever we have an operator release.

We probably want something similar to this that we had for alpha.6:
Konveyor v0.3.0-alpha.6 has been released and available [here](https://operatorhub.io/operator/konveyor-operator/alpha/konveyor-operator.v0.3.0-alpha.6).

Changelog

Features

* match targets with version ranges correctly by @pranavgaikwad in https://github.com/konveyor/analyzer-lsp/pull/341

* Update LSP types to more recent version by @JonahSussman in https://github.com/konveyor/analyzer-lsp/pull/324

* Add a label to short-circuit selector by @pranavgaikwad in https://github.com/konveyor/analyzer-lsp/pull/347

* Identify interesting Jars to decomp and improve decomp performance by @pranavgaikwad in https://github.com/konveyor/analyzer-lsp/pull/352

*  handle version ranges by @pranavgaikwad in https://github.com/konveyor/windup-shim/pull/93

* Download ruleSets with versioned labels. by @jortel in https://github.com/konveyor/tackle2-addon-analyzer/pull/54

* Analysis archiving by @jortel in https://github.com/konveyor/tackle2-hub/pull/493

* Apply Questionnaire seeds by @mansam in https://github.com/konveyor/tackle2-hub/pull/496

* Allow creating assessments "as-is" by @mansam in https://github.com/konveyor/tackle2-hub/pull/501

* Add `assessed` field to Archetype REST resource by @mansam in https://github.com/konveyor/tackle2-hub/pull/500

* Surface assessment tags on Archetype resource by @mansam in https://github.com/konveyor/tackle2-hub/pull/502

* Reports - Current Landscape update risk handling by @sjd78 in https://github.com/konveyor/tackle2-ui/pull/1395

* Add useLocalTableControlsWithUrlParams hook and update archetypes table to use it by @mturley in https://github.com/konveyor/tackle2-ui/pull/1392

Bug Fixes

* Update the label value format  as per new format by @pranavgaikwad in https://github.com/konveyor/analyzer-lsp/pull/342

* Exclude virtual tags from writing/updating by @mansam in https://github.com/konveyor/tackle2-hub/pull/495

* Fix latest analysis report. by @jortel in https://github.com/konveyor/tackle2-hub/pull/504

* Only marshal assessment sections if not empty by @mansam in https://github.com/konveyor/tackle2-hub/pull/506

* PrepareForArchetype should use criteria and tags by @mansam in https://github.com/konveyor/tackle2-hub/pull/508

* Restore missing params object when fetching issue reports by @mturley in https://github.com/konveyor/tackle2-ui/pull/1393

* Fix sorting on application inventory tables, misc cleanup in these tables by @mturley in https://github.com/konveyor/tackle2-ui/pull/1396

* Fix inconsistent styles between app inventory tables, fix wrong drawer component being used on analysis table, remove stray character by @mturley in https://github.com/konveyor/tackle2-ui/pull/1397

* Fix broken rendering of migration waves table rows, properly pass isExpandable prop in useTableControlProps by @mturley in https://github.com/konveyor/tackle2-ui/pull/1398

* Assessment settings table columns empty by @ibolton336 in https://github.com/konveyor/tackle2-ui/pull/1391

* Add missing clear handler for app import by @ibolton336 in https://github.com/konveyor/tackle2-ui/pull/1400

* Save as Draft not working by @ibolton336 in https://github.com/konveyor/tackle2-ui/pull/1401

* fix(autocomplete): tags not generated for preselected options by @gitdallas in  https://github.com/konveyor/tackle2-ui/pull/1403

* Applications form: Fix contributors and tags field handling by @sjd78 in https://github.com/konveyor/tackle2-ui/pull/1408

* Business services: Fix create/edit when owner is included by @sjd78 in https://github.com/konveyor/tackle2-ui/pull/1418

* String value breaking schema validation for repo type by @ibolton336 in https://github.com/konveyor/tackle2-ui/pull/1415

* Fetch target images in auth envs by @ibolton336 in https://github.com/konveyor/tackle2-ui/pull/1420

* fix styling for ssoMenu by @gitdallas in https://github.com/konveyor/tackle2-ui/pull/1424

* Update the label for the Tag field on the Application Form by @sjd78 in https://github.com/konveyor/tackle2-ui/pull/1427

* Fix broken tag colors by moving LabelCustomColor from lib-ui and updating it for PF5 by @mturley in https://github.com/konveyor/tackle2-ui/pull/1431

* fix issue with select menu getting cut by edge of modal by @gitdallas in https://github.com/konveyor/tackle2-ui/pull/1428

* Fix broken analysis report download by @ibolton336 in https://github.com/konveyor/tackle2-ui/pull/1407

* Add tooltip for weight column by @ibolton336 in https://github.com/konveyor/tackle2-ui/pull/1433

* Shows client side loading state for jira tracker by @ibolton336 in https://github.com/konveyor/tackle2-ui/pull/1409

* Application drawer > reports: show analysis details for successful task by @sjd78 in https://github.com/konveyor/tackle2-ui/pull/1437

* Update archetype model, form and detail drawer to current hub spec by @sjd78 in https://github.com/konveyor/tackle2-ui/pull/1438

New Contributors

* @jwmatthews made their first contribution in https://github.com/konveyor/analyzer-lsp/pull/346

* @fabianvf made their first contribution in https://github.com/konveyor/tackle2-addon-analyzer/pull/49

Regards,

Konveyor Maintainers


Make compilation tests target wasm32-unknown-unknown

Originally pointed out here. Basically compilation_tests are using host target rather than wasm32-unknown-unknown which makes testing wasm-specific code generation impossible to test.
From my short investigation, it seems like there is no way to easily change this behavior as trybuild does not have an option to control target architecture.

Unfortunately, it does not seem like there is a way to achieve this with trybuild. And the maintainer of the repo insists on keeping the library simple, so configuring target triple likely won't be supported. I have also considered its alternatives:

macrotest - has the same issue, does not have an option of controlling target triple
compiletest_rs - does allow configuring target triple but comes at a great cost in usability. The issues are explained well here: https://github.com/dtolnay/trybuild/issues/13. Going back to compiletest-rs does not seem like a great choice long term.

So aside from maintaining our fork of trybuild, it seems like our best shot would be trying to raise this with macrotest maintainers and seeing if they would consider allowing target customization.

Might find some inspiration from here: https://github.com/rustwasm/wasm-bindgen

@willemneal I'll give it another crack, thanks!

@willemneal looked into it and unfortunately they use trybuild in conjunction with the host architecture since their code generation macros do not depend on the architecture...


Initial preprocessing of qmod JSON.

No testing done yet

is this ready to be merged or not yet?

I suppose it is. Review and quality test it as you wish


Better ingress detection/prompting

Say I use a quickstart image and the port number exposed is 80.  Later I redeploy a new image that needs port 3000 exposed... right now we do not prompt for the port # again and have to manually change the number through Edit target port....  There's probably a couple things we can do here to improve the experience.  We can always re-prompt for the port or re-prompt conditionally.  When a Dockerfile is detected we could also smart detect/suggest the port based on the Dockerfile if it is included as part of the build.
If we want to do only conditional re-prompting, these are some obvious candidates:

When updating from a quickstart image
When Dockerfile shows a different exposed port

This could also be considered as part of this work: https://github.com/microsoft/vscode-azurecontainerapps/issues/311
Adding or updating an image may still be considered "creating a revision" until you actually deploy it, in which case, it'd be tracked in the JSON envelope.

It would be nice if there was a standard way for us to tell what ports need to be exposed from an image. Not sure if that exists...

Maybe we can prompt the user for target port only if the image changes. If only the tag is updated, then don't prompt the user for the port.

@nturinski We should re-discuss this in the case of our new batch revision update format.  Even if we prompt for a new port, we may not want to update that port until the entire draft is deployed.  Is this a case for adding some of the configuration settings to the draft template? 🤔


[enhancement] improve the closing mechanism for NVMeSubsystem

Detailed in https://gbmc-review.googlesource.com/c/dbus-sensors/+/14999/comment/d88462cb_b06e6af6/

quoted from the comment in gerrit review:
The flushOperations() cannot guarantee all NVMeMI tasks has been drained.
E.g. we have a recursive task A created by async timer.
task A will push a NVMeMi function call to worker thread.
task A has been enqueued in the immediate_exec_que of the timer but haven't been executed because the current code (nvme->flushOperations()) in currently in the io_context.


Translatable fields are missing from API exports

Reported by @aaronschachter:
http://dev.dosomething.org:8888/api/v1/campaigns.json?mobile_app=true&term_ids=669,667,668,670
Related #4834.
cc @mikefantini @sheydari-ds

I believe Message Broker still uses the older content endpoint, which calls a different callback function than the campaigns endpoint does. Something to double check as well.

So the thing is that LANGUAGE_NONE language is used by default:
Call_for_action/tagline loaded here: https://github.com/DoSomething/phoenix/blob/76c82fb77b1accdf015642588b75916e88c13791/lib/modules/dosomething/dosomething_campaign/includes/Campaign.php#L528
Function dosomething_helpers_extract_field_data() is used to extract actual data. It has a language param, but it falls back to LANGUAGE_NONE by default.
There are a number of translatable fields, for which, the language param needs to be provided from now.

@aaronschachter I believe we need to extend API with mandatory $language param, like
http://dev.dosomething.org:8888/api/v1/campaigns.json?mobile_app=true&term_ids=669,667,668,670&langauge=en

@aaronschachter and I just had a chat and decided the following:

For now quickest and easies fix would be using en language as a new default for dosomething_helpers_extract_field_data() function. If the english value isn't there, fall back to LANGUAGE_NONE
Long term solution is API extension that makes it possible to render output in different languages, using ?language URL parameter

cc @weerd

I'm going to close this issue out, we only support en in the api, and this is intended for now.
We can re-visit if we prioritize other languages in external services


Generate wrong alerts when upgrading Prometheus from 2.33.5 to 2.50.0

What did you do?
I create a alert rule, but it generates alerts' project label is not less
(max_over_time(app:container:kube_pod_container_status_terminated_reason_error{namespace!~".*(test|dev).*",project="lees"}[5m] offset 5m)) > 0

What did you expect to see?
Generate the alerts with project=less
What did you see instead? Under which circumstances?
What i saw
The Prometheus ALERTS metrics:

The alert rule query result of the same time:

How to reproduce
it happens occasionally, haven't found the way to reproduce.
Other information
I have two Prometheus of v2.33.5 and v2.50.0, the v2.33.5 works as expected while the v2.50.0 is not.
System information
No response
Prometheus version
Prometheus 2.50.0

Prometheus configuration file
alert:容器实例异常退出-cdn1s9mrjlj070sa9c40
expr:(max_over_time(app:container:kube_pod_container_status_terminated_reason_error{namespace!~".*(test|dev).*",project="lees"}[5m] offset 5m)) > 0
labels:
   category: app
   severity: serious
   source: x

Alertmanager version
No response
Alertmanager configuration file
No response
Logs
No related logs

There is an inconsistency between your screenshot which says less and your posted config which says lees.
I suspect you have not posted the exact and complete config, which makes it impossible to troubleshoot.
Mildly interested to know why you would run 2.50.0 when there was a bugfix release 2.50.1 a few days later.


feat(deepinfra): LLM

So this is some wrapper on top of openai, why is it relative-imported?

Hi @ichernev, we've reused OpenAI's implementation since we're using same chat specification with OpenAI. It is relatively imported by OpenAI's LlamaIndex TypeScript implementation.


   I want to deploy static files in webview, but the js packaged with vite is of module type. Direct opening will prompt cross-domain and file protocol is not supported. Does vite support unpackaged module types?

Clear and concise description of the problem
I want to deploy static files in webview, but the js packaged with vite is of module type. Direct opening will prompt cross-domain and file protocol is not supported. Does vite support unpackaged module types?
Suggested solution
vite support unpackaged module types
Alternative
No response
Additional context
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

Which webview are you saying about? Android webview?
What do you mean by "unpackaged module types"? Do you mean non-module script?


wrong global state after restart

We had 3 managed miners that suddenly restarted (VM crash?). They load the global state from the db, but the layer_id is off by one; see screenshot below.
In addition, their layer_hash is also incorrect. Probably for the same reason.

@noamnelke , could it be because of this code, where layer hash is persisted only after all layers have been pushed to state?:
func (m *Mesh) pushLayersToState(oldPbase types.LayerID, newPbase types.LayerID) {
	for layerId := oldPbase; layerId < newPbase; layerId++ {
		l, err := m.GetLayer(layerId)
		if err != nil || l == nil {
			// TODO: propagate/handle error
			m.With().Error("failed to get layer", log.LayerId(layerId.Uint64()), log.Err(err))
			break
		}
		m.AccumulateRewards(l, m.config)
		m.PushTransactions(l)
		m.logStateRoot(layerId)
		m.setLayerHash(l)
		m.setLatestLayerInState(layerId)
	}
	m.persistLayerHash()
}

I don't think it would make a difference if the m.persistLayerHash() was at the end of the loop. If there are more layers to push to the state and the loop isn't done yet, then you may get more layers to be persisted, but not all of them (since you didn't complete the loop).
What we need here is to process layers in a transaction, so we either persiste the entire update or none of it (and then we'll process it right after recovery).

I believe this is thee cause for the bug, do you agree?

I haven't looked at the entire code flow, but iirc (and this code snippet supports that) there's no tight control of state transitions. I.e. if a node crashes during a state transition it may end up with an invalid state.
This is not a small fix like moving the m.persistLayerHash() one line up. It's a change that may require changing some of the flows in the state transition and atomically persisting more granular statuses for recovery (in each database we'll need to store up to what point that particular database was updated).
I'm not 100% sure about how this should work - designing an airtight solution requires digging in the code a bit to understand the limitations.


Release/1.0.0

This is the first stable release of the tracker and adds the tracker to the list of our maintained trackers!
The release brings updates to the API and introduces a Snowplow class for easier initialization and management of one or more trackers. A new tracker can now be initialized with a single line of code, e.g., auto tracker = Snowplow::create_tracker("ns", "https://collector.com", POST, "sp.db");.
Support for the cmake build system was also introduced. This enables the package to be imported into other cmake projects. The library can be still be installed without using cmake by copying source files from the include folder.
Other changes include support for storing HTTP cookies in collector requests, adopting the version 1.0.2 of the client_session schema for session context entities with eventIndex and firstEventTimestamp properties, new API docs, and integration tests.
Changelog

Add a Snowplow interface with the ability to initialize and manage multiple trackers (#57)
Add eventIndex and firstEventTimestamp properties to client sessions (#80)
Add support for storing cookies in HTTP clients (#78)
Add build using cmake (#65)
Add integration tests using Snowplow Micro (#57)
Publish API docs on Github Pages (#73)

Thanks for your pull request. Is this your first contribution to a Snowplow open source project? Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
:memo: Please visit https://docs.snowplowanalytics.com/docs/contributing/contributor-license-agreement/ to learn more and sign.
Once you've signed, please reply here (e.g. I signed it!) and we'll verify. Thanks.


Gas price and Gas limit textboxes' keyboard should not allow entering "." in configure transaction screen

ConfigureTransactionViewController
Probably should be .numberPad? (like Nonce in the same screen).

@hboon How do I get to this screen?

@eviltofu

Wallet tab
Tap Ethereum
Tap Receive
Tap address to copy
Back
Tap Send
Paste address
Done
Send
Edit (this is the screen to adjust gas fees and nonce)
Tap Custom

@eviltofu Why does this not show up in my inbox? Tagged myself for this to show.

@eviltofu Why does this not show up in my inbox? Tagged myself for this to show.

@eviltofu does it now? It should.

There are lower limits on gas price and gas limit. When I move the slider to the minimum level, I get gas price 1 and gas limit 21000. It is possible to type in 0 for both these fields. Do you want me to limit the values in both these fields to 1 and 21000 respectively? @hboon

Also the Gas Price box appears to change from red to black but only for a very narrow range (99-120) regardless of the Gas Limit. @hboon

Also keyboard keeps showing Done and no Next. Tapping Done moves the focus to the next textfield. When I tap on the textfield, the keyboard obscures the textfield. When focus shifts to next textfield, that textfield is not scrolled into view.

.

@eviltofu can you help create a new issue for https://github.com/AlphaWallet/alpha-wallet-ios/issues/3751#issuecomment-1024775364 and the comments following it? And separate issues if appropriate? Easier to track.


Added Kyphosis Disease Classification based on issue #26

Related Issue
Closes: #26
Describe the changes you've made
I have added a folder which contains three file describes about how to classify kyphosis disease.
Give a clear description what modifications you have made
Type of change
This project allow us to predict the presence or absence of Kyphosis based on the Kyphosis dataset using a Random Forest and Decision Tree Machine Learning Model.
Kyphosis is an abnormally excessive convex curvature of the spine. The kyphosis data frame has 82 rows and 4 columns representing data on children who have had corrective spinal surgery.
What sort of change have you made:

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Code style update (formatting, local variables)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Screenshots(optional)

Original
Updated

original screenshot
updated screenshot

I'm closing this now! Make a new PR!

Hey there !!!
I'm owing you an apology for not being able to respond further in the process of making a pr. I have made more than 4 pr's which got matured recently in hacktoberfest . But, due to this invalid PR which you labelled.. it is affecting in contributing to hacktoberfest.
I am unfortunately unaware of the fact that making spam pr's will affect my contribution as I'm a newbie in open source contribution. Please do kindly consider my mistake and i owe you to remove that label. I'm making a promise that i will create a new issue and surely i will work on it by making a valid pr now. I will seriously work on it right away.
Please do remove the label. I hope i will never do such types  of mistakes again.


Fix: create edit rows for already verified apps

If some rows already are verified we need to create their verified rows so that users can edit.

For rows where there's only verified. Status will default to unverified on save because it will trigger an insert since we only have a verified row.
We will add functionality for handling edit once verified in the submit for review PR this is just to prevent staging from having blank pages if the row is verified


Ironic pxe_ssh driver configuration happens too late

We are using qemu://session to manage the overcloud VMs, which requires a change to the Ironic pxe_ssh driver configuration[1]. However, by doing this in the undercloud-install.sh script, we break someone following the instructions to "Run openstack undercloud install, then follow upstream instructions."[2]
Instead, we should do this ironic configuration at the end of the libvirt role, so that the alternative instructions work again.
[1] https://github.com/redhat-openstack/tripleo-quickstart/blob/master/playbooks/roles/tripleo/undercloud/templates/undercloud-install.sh.j2#L10-L17
[2] https://www.redhat.com/archives/rdo-list/2016-March/msg00171.html

The fact that we are defaulting the libvirt_uri var in the libvirt role[1], but using it in the tripleo/undercloud role is further evidence we are doing it in the wrong place.
[1] https://github.com/redhat-openstack/tripleo-quickstart/blob/master/playbooks/roles/libvirt/defaults/main.yml

We need this value in both the libvirt role and in the undercloud configuration.  If we're planning on moving the tripleo/* roles out of tripleo-quickstart, this suggests that the libvirt/* roles are the right place for it...and we also need the same setting in tripleo/undercloud.
Does that make sense?

Actually, after moving the ironic config step in https://review.gerrithub.io/#/c/270892 we no longer use libvirt_uri outside of the libvirt roles.


Tests are not Windows friendly

I can see this is fixed in #1. See this issue as a tip for future code :)
Instead of checking path separators like == '/' a better approach is to use os.PathSeparator. Otherwise this check would fail on Windows.
https://github.com/charmbracelet/taskcli/blob/23d7ac29a6919eaaf563b7819ac5ae82fad97e6d/db_test.go#L206C2-L208C3

yep, this should be fixed now!
thanks @henrikac :)


Bug 1905095: bump github.com/containers/image

Bump github.com/containers/image from v5.5.2 to v5.10.5 to pick up https://github.com/containers/image/pull/1089 and https://github.com/containers/image/pull/1138, this pulls in an update from github.com/containers/storage from v1.24.5 to v1.24.8.
Fixes #219.

e2e-aws-build will fail until https://github.com/openshift/origin/pull/25949 merges

/hold
Until ruby tests are cleaned up

/retest

/hold  cancel


Supporting simultaneous update.

Specifies the Simultaneous Mode of update to initiate. All role instances will be updated at once.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: hyunsoolee-msft sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


fix: private files included in analysis

Description
Generated files get included in the sourcing process as relative-path files. This causes an InvalidPathResult exception.
WARNING: I have only tested this change on Windows, and not on Linux or OS-X.

Type of change
Please delete options that are not relevant.

[X] Bug fix (non-breaking change which fixes an issue)

Checklist:

[X] Ran dart analyze .
[X] I have performed a self-review of my own code
[X] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works

Have you confirmed that this fixes an issue? Also can you add change log for version 4.4.1?

@l7ssha I have confirmed this fixes this issue on my side, but I only tested this on Windows. I have no access to a MacOS machine, but I could try this out in Linux.

@l7ssha I have confirmed this fixes this issue on my side, but I only tested this on Windows. I have no access to a MacOS machine, but I could try this out in Linux.

yes, please confirm also on linux since majority of bots are gonna be run on linux anyway. Mac os gonna behave simirarly to linux so there is no need in checking that

@tomassasovsky I found the root issue (we weren't resolving the URI when we found a part element) and have pushed a commit that seems to fix it.
Would you mind testing to see if this resolves your issue?


auth+mdserver: add rekeying protocol methods

Most of this is to add a key comparison method used by the mdserver.
KBFS side: https://github.com/keybase/kbfs/pull/508

:+1:


Config refactor

Before opening your pull request, please make sure that you have:

[ ] signed Uber's Contributor License Agreement;
[ ] added tests to cover your changes;
[ ] run the test suite locally (make test); and finally,
[ ] run the linters locally (make lint).

Thanks for your contribution!

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

This removes the dependency on the environment variable to find the primary yaml config file. Instead, that's now passed via command line and has a default value in defines.go.
What was previously passed via the command line via the "-c" option was the targets config. That is now defined in the yaml config as standaloneTargetConfig. That file is used when the orchestrator mode is disabled via an added field in the yaml config file as well.


Config validation

We are adding more to the config setup. We currently have zero validation on formats and inputs which make the errors incredibly bad when making a mistake.
We should look at adding scheme validation.
Potentially we can use joi and document it.

I agree! This should also happen soon, so we do not have to add it later. Lets add this to the next milestone 0.3

One thing to also take into account here is the following: CRD support passing of an OpenAPI 3 schema to validate applied schemas (see https://kubernetes.io/blog/2019/06/20/crd-structural-schema/)
This means whatever we do here now (in the CLI stage of this project) should somehow feed into that, so we in the end do not have to write two validations per type.
There are essentially four options:

Write the validation as Joi and export that using a library to OpenAPI https://www.npmjs.com/package/joi-openapi
Write the validation as Openapi and export that using a library to Joi https://www.npmjs.com/package/openjoi
Write the validation as OpenApi and use that to validate https://www.npmjs.com/package/openapi-enforcer
Write the validation as Joi and then again write the CRD validation as OpenApi.

I personally think Joi is very easy to write and integrate right now. OpenAPI is more powerful, yes, but it also requires a substantial time investment to use it. I vote 1. We can with the CRD then decide to go with the converter or duplication

I also vote for option 1 as its the easiest and provides the most flexibility.
But my reasons are a little different, I believe we are so far away from a CRD implementation that I don't believe the two need to be binary identical.
For example in the k8s CRD scheme there will be loads of k8s specific configs used to create the replica's and pods/stateful sets which would be totally transparent/opaque to lib/cli implementations.
For example
replicaSet:
  replicaSetName: mongo-rs
  servers:
  - host: mongo-rs-0:27000
    uri: mongodb://localhost:27000
  - host: mongo-rs-1:27001
    uri: mongodb://localhost:27001
  - host: mongo-rs-2:27002
    uri: mongodb://localhost:27002

While this is 100% valid configuration for setting up the replica set it will in no way be enough to create the k8s infrastructure to make this possible. We will need to include things like resource constraints, hard drive type, size,  and lots of other options.
What think will happen is we will use the CRD spec to generate the hydra spec via some sort of mapping logic. For example, the hostname will be calculated based on the stateful set (not user-supplied)
Also once we have a config  validation setup we can possibly refactor that to use another tool (this should be mostly internal)


Community provided article on an example of how to use Grid Control in ASP.NET

Hi all, attached please find an article submitted by an Taiwan MVP a while back which was published on a local section of the MSDN library and had higher views that other articles, meaning customers were looking at it. It provides a practical example on using Grid Control and may supplement this content.
It has been reverse-machine-translated to provide you with a readable English version - if you think it has some merit and could find a place in the official documentation, please do let me know and we can work with the author to have it amended as necessary.
This also serves as a test, to see if it's efficient to use this process for such submissions/proposals (that's why I'm using the private repo instead of the public one)
thanks to let me know your thoughts
ZH-TW Practical Examples in How to Use Grid Control in ASP NET.zip

cc @danroth27 @rachelappel @scottaddie  any thoughts?

I'm in favor of including the article, perhaps in the following section:
https://docs.microsoft.com/aspnet/web-forms/overview/presenting-and-managing-data/model-binding/
Is there an accompanying sample app?

@scottaddie thanks so much for your comment. unfortunately, there is no sample app.

@terrysheng  unfortunately we don't have the resources to add it to our docs.

aspnetGridDemo.zip
@scottaddie and @Rick-Anderson
Thanks so much for your update. I have just checked with the Taiwan MVP, and he has actually a sample code for this, and I have attached it here.
However, I notice Rick's comment regarding the resource limit.
Please feel free to let me (I am the Regional PM from APEX International) know if you have resources to support the case or similar cases (community produced content) in the future. And I will do my best to support you!
Have a nice Thanksgiving!
Terry

This content would fit in very nicely in the TechNet wiki, which samples like this one would fit in perfectly:  https://social.technet.microsoft.com/wiki/tags/ASP-NET/default.aspx


State SSH fingerprint in documentation

It would be great to be able to verify the SSH fingerprint when connecting to the cluster (for the first time).
When a user connects for the first time, their system usually asks:
ED25519 key fingerprint is SHA256:DiFgOsIH1WEUEDn6lg0ImIg7ok5RE+i4R26uxUhXjQA.
This key is not known by any other names.
Are you sure you want to continue connecting (yes/no/[fingerprint])?

Maybe add a line in the docs stating the fingerprint?

Thanks for the suggestion.  I added at the very top:
https://github.com/centerforaisafety/cluster-docs/commit/217b1459c26beb4a9a15899dd04ca1bd03f581b4


Language name ‘Norwegian’ is incorrect

The drop-down box for choosing language uses the name ‘Norwegian’ for the ‘nn’ translation. This is incorrect/misleading. The name should be ‘Norwegian Nynorsk’.
Some background: Norway has two official languages, Norwegian Nynorsk and Norwegian Bokmål. There is no written language called just ‘Norwegian’. The current translation is for Norwegian Nynorsk (language code: nn). (There is currently no translations into Norwegian Bokmål (language code: nb), but this may be added in the future.)

Hi @huftis, thank you for your message. I can see that on 'old' opensuse page (https://www.opensuse.org/en/) there is Norwegian Bokmål language in drop-down box.
ping @cyntss @ddemaio I can create a PR with fix if you OK with that.

Yes perfect ! I am not familiar at all with the correct denomination of the language but what @huftis says makes sense.
@Evalle if you want to create the PR please do it. I can also do it if you dont have time :)

@cyntss fixed in https://github.com/cyntss/opensuse-landing-page/pull/31 :)