Language settings

Hi, is there an option to change language or is it a feature that cannot be changed? Thanks!

No. Enable Chrome translation if you want

On Jan 7, 2021, at 16:51, geneva<EMAIL_ADDRESS>wrote:
Hi, is there an option to change language or is it a feature that cannot be changed? Thanks!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/111116/webosu/issues/64, or unsubscribe https://github.com/notifications/unsubscribe-auth/AET5RLDL4GEPQLIA5EV4CXDSYVY27ANCNFSM4VYVNHZQ.

No. Enable Chrome translation if you want

On Jan 7, 2021, at 16:51, geneva<EMAIL_ADDRESS>wrote:
Hi, is there an option to change language or is it a feature that cannot be changed? Thanks!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/111116/webosu/issues/64, or unsubscribe https://github.com/notifications/unsubscribe-auth/AET5RLDL4GEPQLIA5EV4CXDSYVY27ANCNFSM4VYVNHZQ.


font size

VSCode Version:1.4.0
OS Version:Microsoft Windows [Version 6.1.7600]

how to change the font size of intellisense list in vs code the font is too small to read

@RolandBrake Go to File > Preferences >User settings. Two new editor tabs should open, one being "Default Settings" the other being "settings.json". You can't edit the Default Settings so you override it by putting your edited settings in settings.json. The default font size is set to 14, so in settings.json you would put "editor.fontSize": 16 chance 16 to your desired font size.

@BinaryResolved  the editor.fontSize  property work just for the editor font not for intellisense list any other suggestions?

#2465


header(CONTENT_TYPE) overridden by further call to json()

I've got a similar issue than #1615 of something being silently overwritten. In my case, that's the Content-Type header which is silently being replaced by the json() method. If you go like .header(CONTENT_TYPE, "foo").json(&body), at the end you get a request with a content-type of application/json.
Although it doesn't concern the body() method used twice like in #1615, it's still something quite hard to figure out. I was aiming at changing the doc a bit to have this point explicitly written in the json() method documentation, but maybe someone can think of something more relevant?
edit: doing .json(&body).header(CONTENT_TYPE, "foo") works as expected

It's probably logical for the json() method to only set the content-type header if not already set... I wonder if people expect the opposite.
It'd be interesting to check what similar libraries from other languages do.

I am experiencing this issue now  where i intend to change the content-type  but it got override.  Although when i added the header after setting the body,  the content-type becomes duplicated  but still the one set by  .json is used.

edit: doing .json(&body).header(CONTENT_TYPE, "foo") works as expected

If it does, it's only by accident. Inspecting the request will reveal that it contains two content-type headers, in this order:

content-type: application/json
content-type: foo

Reqwest - correctly - sends both; this is legal as HTTP headers may have multiple values, though this header is not expected to have more than one. If your server is interpreting the result as content-type: foo, that's reasonable, but not all implementations do that: Hashicorp Vault, for example, will use the first value rather than the last one, and that's reasonable as well. (Guess how I discovered this issue.)
The builder does not have a way to remove or replace headers, which would address this pretty cleanly. Something like
let response = client.post(url)
    .json(&body)
    .set_header("content-type", "application/x-my-app+json") // replace existing content-type header instead of appending
    .send()
    .await?;

would have pretty decent ergonomics in my view, though obviously the difference between .header and .set_header is a potential hazard. If breaking changes are on the table, I'd prefer .header set the header, replacing existing values, and .add_header added to it, appended after existing values.

Just had a similar issue:
        let req: reqwest::RequestBuilder = self.http.post(self.url.as_str())
            .json(&query)
            .header("Content-Type", "application/json")
            .header(AUTH_HEADER, self.auth_token.as_str());

The above snippet sets the content-type twice resulting in ["application/json","application/json"] which some GCPs ingress kindly changed to application/json,application/json silently breaking things.
I'd love to see this behavior changed to be more obvious or consistent with the RFC to only allow one Content-Type.
Adding a note in the docs for RequestBuilder::json() would also be nice.


Enable proxy mode for fuzzing software running in other domains

This pull request adds a proxy library to support the "proxy mode" that allows a target program to act as a proxy for fuzzing software in other domains (e.g., the operating system kernel).  It also fixed a bug in afl-staticinstr.c which fails to send a "P" command that is expected from afl-fuzz.exe.

Not sure why, but I did have submitted a Google CLA agreement with my email and Github account listed.  Let me know if I miss any step.


limiting a burst of outgoing packets

See https://github.com/cloudflare/quiche/pull/684

This was actually kind of done with this:
https://github.com/netty/netty-incubator-codec-quic/pull/228


Bulk Import Insomnia

Currently, you can only import one Insomnia collection at a time. I tried throwing a full Insomnia export at it, but Bruno only took the first one.

Duplicate of #157


[Need] PR template

Is your feature request related to a problem? Please describe.
PR template
Describe the solution you'd like
I want to add a PR template

I would like to work on this issue, Please add labels and kindly assign it to me

Go ahead ! @Mustafiz04  can you assign him?

Please Add gssoc21 label to this Issue and PR


quad-rand patch

Build error on the current master branch:
Updating git repository `https://github.com/not-fl3/quad-rand`
error: failed to get `quad-rand` as a dependency of package `zemeroth v0.7.0-snapshot (/home/.../zemeroth)`

Caused by:
  failed to load source for dependency `quad-rand`

Caused by:
  Unable to update https://github.com/not-fl3/quad-rand#b1aabd4c

Caused by:
  revspec 'b1aabd4c5033a19bba79583ada17418c2cf45674' not found; class=Reference (4); code=NotFound (-3)

So I have updated Cargo.toml and core/utils.rs to use quad_rand from crate.

Cargo.toml
quad-rand = { version = "0.1.1", features = ["rand"] }

src/core/utils.rs
use quad_rand::compat::QuadRand;


zulipbot test issue

Read our guide on bug reports here
Actual Behaviour
Explain what is currently happening.
Expected Behaviour
Explain what you expected (unnecessary if it's obviouxly broken, e.g. a crash).
Would you like to work on the issue?
Let us know if this issue should be assigned to you.

@zulipbot claim-issue

@zulipbot claim-issue

@zulipbot claim-issue


Proposal: Change checked exceptions to runtime exceptions

Most methods of com.offbytwo.jenkins.JenkinsServer throws an checked exception (java.io.IOException). This makes the API harder to use - especially with lambdas.
From the caller's side I can't do anything about it. I suggest defining a specific RuntimeException that contains the real cause. In this way, the caller can decide whether to handle the exception or not.

Sounds like a good idea...


Crashed when run Coda daemon kimziv#2691

Coda daemon is booting up; built with commit "3e9b1748183e653a7891adea1fef07c8e1a7dfcd" on branch "feature/bump-genesis-timestamp"
I just running the code daemon, then crashed, and attach the crash report /root/.coda-config/coda_crash_report_2020-09-04_23-24-34.262026.tar.gz
coda_crash_report_2020-09-04_23-24-34.262026.tar.gz
My Discodrd ID: kimziv#2691

@kimziv this error Failure "no seed or initial peer flags passed" is caused because there is no current active network to connect to. You will need to wait until the launch of 3.3 to connect to a public testnet or alternatively use the sandbox node  to run a private network. See the #announcements channel in Discord for more.

Closing this issue as it is stale for a long time.


Connect to vnet step 1

Description

References

#0000

Codecov Report

Merging #364 (5b218cb) into main (49d18a9) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #364   +/-   ##
=======================================
  Coverage   67.70%   67.70%
=======================================
  Files           9        9
  Lines         192      192
  Branches       19       19
=======================================
  Hits          130      130
  Misses         57       57
  Partials        5        5

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


test(client): update tracing tests for MongoDB to match real queries

Refs: https://github.com/prisma/prisma-engines/pull/5014

Merged in https://github.com/prisma/prisma/pull/25399.


Fix DialTimeout for direct call of Dial

See issue #689

I change the dial function, setting the timeout for dialing based on dialTimeout() instead of writeTimeout().

Update the direct public functions DialTimeout(..) and DialTimeoutWithTLS(..), passing the dialTimeout to the client, because these functions creates a client on the fly to operate the Dial.

Codecov Report

Merging #691 into master will increase coverage by 0.03%.
The diff coverage is 33.33%.

@@            Coverage Diff             @@
##           master     #691      +/-   ##
==========================================
+ Coverage   58.17%   58.21%   +0.03%
==========================================
  Files          37       37
  Lines       10116    10116
==========================================
+ Hits         5885     5889       +4
+ Misses       3174     3169       -5
- Partials     1057     1058       +1

Impacted Files
Coverage Δ

client.go
58.94% <33.33%> (+1.32%)
:arrow_up:

Continue to review full report at Codecov.

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


Wide tables should scroll horizontally within the page

Wrap the main table in <div style="overflow-x: auto">

I tried this out and it did cause one problem with plugins: datasette-cluster-map still injected itself inside the scrolling area, when instead we would want that map to stay outside of the div with the table in it.

So maybe this is blocked on #987 and adding a new hook in the HTML which plugins like datasette-cluster-map can attach their content to.

This may require updates to the column action menu JavaScript too, since it was not built with scrolling sideways in mind.

Easiest fix for the column action menu positioning - hide them when the user scrolls the containing div:
document.querySelector('.table-wrapper').addEventListener(
  'scroll', () => document.querySelector('.dropdown-menu').style.display = 'none'
);

This isn't blocked on #987 - it just means that datasette-cluster-map will need to learn to look for .table-wrapper first and fall back on the table.

Demo:

This is now live here: https://global-power-plants.datasettes.com/global-power-plants/global-power-plants

Hello Simon,
I have a similar problem with horizontal scrollbar display with Datasette version 0.51 and superior for a table with more than 30 rows. With Datasette 0.50, the horizontal scrollbar is displayed, if I upgrade Datasette to 0.51 and superior, the horizontal scrollbar disappears.
Datasette 0.50: horizontal scrollbar

Datasette 0.51 and superior: no horizontal scrollbar

Thanks,


[libigl] Fix dynamic build and enable header-only mode

This is an attempt at getting rid of libigl huge static .lib file and getting the header-library mode. I could make it work on my machine (Windows VS2019 Clang 10) with the current set of modifications. Not necessarily optimal nor "clean", but hopefully a good start to resolve the issue.
Let me know if anything is missing or feel free to take over from here.

What does your PR fix? Fixes #14371

Which triplets are supported/not supported? Have you updated the CI baseline?
Dynamic library version works on windows but not the static, and other platform untested. I don't know what is the CI baseline.

Does your PR follow the maintainer guide?
I think so.

Alright so, despite compiling successfully, the baseline x64-windows-static is not actually usable. It leads to /failifmismatch: mismatch detected for '_ITERATOR_DEBUG_LEVEL'. Current changes also successfully pass the CI and leads to same problem.
However my question is, should vcpkg_check_linkage(ONLY_DYNAMIC_LIBRARY) be imposed and ci.baseline.txt updated to libigl:x64-windows-static=fail or stick to "if it compiles it is fine"
Otherwise, I am out of idea to make the static build actually be usable. Since it does not alter the original behavior (on x64-windows) the PR should be ok, but could be simplified if dynamic only is decided (I most probably added too many if(LIBIGL_USE_STATIC_LIBRARY) initially hoping to solve the static build issue).
Let me know your opinion on the subject

The CI x86_windows instance is hogging.
For convenience, I made the gist with the test files here (requires building igl from head for fixes on writeDAE): https://gist.github.com/FabienPean/9c1a6c5eea6b304d0e1241024e0387b1

/azp run

Thanks @FabienPean :)


im getting this error help

'Display' does not contain a definition for 'activeEditorGameViewTarget'

Hello,
Which version of Unity are you using?

The issue should be fixed with the latest release: https://github.com/alelievr/HDRP-UI-Camera-Stacking/tree/1.1.2


perf: remove useless fields in CellData

Labor work. Re-calc the length is tough work, a huh? :)  Rebase please @handsome0hell


Clean up documentation

What is the new or updated feature that you are suggesting?
In some of the documentation markdown files, there is markdown that is not getting rendered properly. For example, in the hooks documentation, :::tip and :::info are not getting rendered properly.
Why should this feature be included?
It is important to maintain technical documentation and make sure it is as clear, understandable, and readable as possible for the users.
What docs changes are needed to explain this?
This change is a doc change only. I can work on it if this gets approved as a valid issue!

That's the source code of the docs. The real docs are over at https://react-redux.js.org/api/hooks

That's the source code of the docs. The real docs are over at https://react-redux.js.org/api/hooks

Thank you! Makes sense and closed the issue.

Appreciate you trying to notify us!
(btw, out of curiosity: how did you end up browsing those Markdown files to start with, rather than looking at the published docs site? Just wondering if there's something we can do to make the link to the docs site more obvious)

@markerikson The Higher-Order Components React documentation links to the connect documentation here, which should be updated to point to the docs site instead.
I didn't realize the connect.md was for the docusaurus site, assumed that was coming from another markdown repository and not within the main codebase itself

Huh, yeah, had no idea the React docs linked there!
That's presumably been there for a looooong time :)  Once upon a time, the React-Redux docs were just "the Markdown files in the repo". But we set up an actual published docs site in... 2018? 2019?
I know the new React beta docs are almost ready to become the real docs site, and that the beta docs don't talk about Higher Order Components. But we ought to file a PR against the existing React docs repo to go update that link anyway.

@markerikson if you can help by pointing me in the direction of where the React docs live, i would love to make the change!

@samilieberman Sure, I can even do a quick search and point you to the exact file :)
It'd be here:
https://github.com/reactjs/reactjs.org/blob/b0ccb47f33e52315b0ec65edb9a49dc4910dd99c/content/docs/higher-order-components.md?plain=1#L17
Appreciate you helping out with that!
(Also: not sure if you actually have any intent to learn Redux atm or were just browsing the React docs, but: we Redux maintainers hang out in the #redux channel in the Reactiflux Discord ( https://www.reactiflux.com ) and are happy to answer questions, and Reactiflux in general is a great place to chat and get help with React.)

@markerikson Thank you! I will make the change shortly.
and thank you for sharing! That sounds awesome, I will definitely take a look.

@markerikson here is the PR for reference. I am just waiting on approvals


Add functionality to invert a matrix.

We can add this functionality as a util under a "linalg" file, like numpy does.
See: https://docs.scipy.org/doc/numpy-1.13.0/reference/generated/numpy.linalg.inv.html

Solved my issue for a 2 x 2 matrix and extended my first deeplearnjs class :>
     class myNDArrayMathGPU extends deeplearn.NDArrayMathGPU {        inverse2DSquare(b)  {                  var myInverseMultiplier  = 1 / ( (b.getValues()[0] * b.getValues()[3]) - (b.getValues()[1] * b.getValues()[2]) )           var myMatrixConverted = deeplearn.Array2D.new([2, 2], [b.getValues()[3]*myInverseMultiplier, b.getValues()[1]*-1*myInverseMultiplier, b.getValues()[2]*-1*myInverseMultiplier, b.getValues()[0]*myInverseMultiplier])           return myMatrixConverted       }    }
Demo at https://hpssjellis.github.io/deeplearnjs-javascript-examples/a03-matrix-math.html
A demo of a pure javascript solution for any sized matrix here
Converting that to typescript is out of my comfort zone.

where should this file be added?

I don't know, how do you propose to find an inverse by matrix multiplication. I am well versed with matrix maths. what I think is for 2*2 it can be easily calculated and for the rest we can use gauss jordan  method. Should be easy to implement.


Fix to get grunt tsdocs work again

This PR changes (delete as applicable)

TypeScript Defs

Describe the changes below:

Fixed module name for phaser-ce
Fixed AStar plugin definition to get grunt tsdocs work again, which currently breaks with an error

Fixes: #29

Thank you! With this I can release 2.7.4 next week.


exporter-node chart: Set rollingUpdate release strategy

This helps ensure that when we make a change it actually gets deployed.
bump the chart version to indicate this change; bump the appVersion to
reflect the version of node-exporter being deployed.

It looks like @gianrubio has already done this change on the version that's in helm/stable https://github.com/helm/charts/commit/26d94b15c8dfa0ebeec4d02de299821fcd81fdb9#diff-8121193f2f4ccd175a78005dd7cdd99d

Sorry for the inconvenience, but the prometheus-operator and kube-prometheus helm charts are currently being migrated to the upstream stable helm charts. Because of this we are currently not accepting any pull requests. We apologize for the inconvenience, but this is necessary for the migration to actually happen. We announced this here: https://github.com/coreos/prometheus-operator/tree/master/helm#warning
You can view the progress and help here and here.
Thank you for your understanding! :slightly_smiling_face:


first commit

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes # (issue no.)
#334
Type of change
Started with the development of template

[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Explain the Testing instructions
Test Configuration:

Operating system: none for now
Version: none for now
Text-editors used: none for now

PR is empty


Add Mathematical expression

Is your feature request related to a problem? Please describe.
I wanna add Mathematical expression to the README file as GitHub supports Maths in Markdown.
Describe the solution you'd like
Adding Math expression syntax to improve the cheatsheet
Describe alternatives you've considered
None
Additional context
Code:
When $a \ne 0$, there are two solutions to $(ax^2 + bx + c = 0)$ and they are
$$ x = {-b \pm \sqrt{b^2-4ac} \over 2a} $$

Output:
When  $a \ne 0$, there are two solutions to $(ax^2 + bx + c = 0)$ and they are
$$ x = {-b \pm \sqrt{b^2-4ac} \over 2a} $$

Hey @Susmita-Dey I see some are added already: https://github.com/atapas/markdown-cheatsheet#mathematical-expressions
Do we want to add more?

@atapas I just wanna add the above code.


Add hint system

Not everything Lintje can detect should be an error.
I can add an hint system to show messages with suggestions like in #23 for adding links to issues, which is not a hard requirement.

This will be added in the next version.


Unexpected logging

My project tests create servers and clients that communicate via grpc. When using grpc, starting with tag 1.65.0, test execution began to be accompanied by debugging messages from grpc being output to the console. Here is an example of these messages:
WARNING: All log messages before absl::InitializeLog() is called are written to STDERR
I0000 00:00:1721286355.339384  310786 config.cc:230] gRPC experiments enabled: call_status_override_on_cancellation, event_engine_dns, event_engine_listener, http2_stats_fix, monitoring_experiment, pick_first_new, trace_record_callops, work_serializer_clears_time_cache
I0000 00:00:1721286355.339806  310786 server_builder.cc:401] Callback server.
I0000 00:00:1721286355.358196  310786 server_builder.cc:401] Callback server.
I0000 00:00:1721286355.474098  310786 server_builder.cc:401] Callback server.
I0000 00:00:1721286355.588977  310786 server_builder.cc:401] Callback server.
I0000 00:00:1721286355.706689  310786 server_builder.cc:401] Callback server.
I0000 00:00:1721286355.826878  310786 server_builder.cc:401] Callback server.
I0000 00:00:1721286355.943314  310786 server_builder.cc:401] Callback server.
I0000 00:00:1721286356.059026  310786 server_builder.cc:401] Callback server.
I0000 00:00:1721286356.174688  310786 server_builder.cc:401] Callback server.
I0000 00:00:1721286356.290079  310786 server_builder.cc:401] Callback server.
I0000 00:00:1721286356.405874  310786 server_builder.cc:401] Callback server.
I0000 00:00:1721286356.623427  310786 server_builder.cc:401] Callback server.
I0000 00:00:1721286356.940707  310786 server_builder.cc:401] Callback server.
I0000 00:00:1721286356.964498  310786 server_builder.cc:401] Callback server.
I0000 00:00:1721286356.987785  310786 server_builder.cc:401] Callback server.
I0000 00:00:1721286357.012006  310786 server_builder.cc:401] Callback server.
I0000 00:00:1721286357.230540  310786 server_builder.cc:401] Callback server.
I0000 00:00:1721286357.447788  310786 server_builder.cc:401] Callback server.
I0000 00:00:1721286357.665315  310786 server_builder.cc:401] Callback server.
I0000 00:00:1721286357.884892  310786 server_builder.cc:401] Callback server.
I0000 00:00:1721286358.007671  310786 server_builder.cc:401] Callback server.
I0000 00:00:1721286358.134681  310786 server_builder.cc:401] Callback server.
I0000 00:00:1721286358.357640  310786 server_builder.cc:401] Callback server.
I0000 00:00:1721286358.577162  310786 server_builder.cc:401] Callback server.
I0000 00:00:1721286358.712529  310786 server_builder.cc:401] Callback server.
I0000 00:00:1721286358.836620  310786 server_builder.cc:401] Callback server.
I0000 00:00:1721286359.059110  310786 server_builder.cc:401] Callback server.
I0000 00:00:1721286360.368937  310786 server_builder.cc:401] Callback server.
I0000 00:00:1721286360.495818  310786 server_builder.cc:401] Callback server.
I0000 00:00:1721286360.512977  310786 server_builder.cc:401] Callback server.
I0000 00:00:1721286360.722194  311443 subchannel.cc:806] subchannel 0x7fdc44008620 {address=ipv6:%5B::1%5D:59811, args={grpc.client_channel_factory=0x3547810, grpc.default_authority=localhost:59811, grpc.internal.channel_credentials=0x356d330, grpc.internal.client_channel_call_destination=0x155e818, grpc.internal.event_engine=0x7fdc44003780, grpc.internal.security_connector=0x7fdc44002ba0, grpc.internal.subchannel_pool=0x3577c40, grpc.primary_user_agent=grpc-c++/1.65.1, grpc.resource_quota=0x353cf00, grpc.server_uri=dns:///localhost:59811}}: connect failed (UNKNOWN:Failed to connect to remote host: connect: Connection refused (111) {created_time:"2024-07-18T07:06:00.722090798+00:00"}), backing off for 1000 ms
I0000 00:00:1721286360.722551  311443 subchannel.cc:806] subchannel 0x7fdc44007ff0 {address=ipv4:<IP_ADDRESS>:59811, args={grpc.client_channel_factory=0x3547810, grpc.default_authority=localhost:59811, grpc.internal.channel_credentials=0x356d330, grpc.internal.client_channel_call_destination=0x155e818, grpc.internal.event_engine=0x7fdc44003220, grpc.internal.security_connector=0x7fdc44007b00, grpc.internal.subchannel_pool=0x3577c40, grpc.primary_user_agent=grpc-c++/1.65.1, grpc.resource_quota=0x353cf00, grpc.server_uri=dns:///localhost:59811}}: connect failed (UNKNOWN:Failed to connect to remote host: connect: Connection refused (111) {created_time:"2024-07-18T07:06:00.722455899+00:00"}), backing off for 999 ms
I0000 00:00:1721286360.919797  310786 server_builder.cc:401] Callback server.
I0000 00:00:1721286362.127611  310786 server_builder.cc:401] Callback server.
I0000 00:00:1721286362.637087  310786 server_builder.cc:401] Callback server.
I0000 00:00:1721286363.147797  310786 server_builder.cc:401] Callback server.
I0000 00:00:1721286364.655489  310786 server_builder.cc:401] Callback server.
I0000 00:00:1721286364.863363  310786 server_builder.cc:401] Callback server.
I0000 00:00:1721286365.169967  310786 server_builder.cc:401] Callback server.
I0000 00:00:1721286366.579307  310786 server_builder.cc:401] Callback server.

If you compile tests with grpc version lower than 1.65.0, then these messages do not appear.
I note that messages are output regardless of the presence or absence of the GRPC_TRACE or environment variables
GRPC_VERBOSITY, as well as regardless of the build mode (Debug, Release, RelWithDebInfo).

Sorry for the trouble. These are being cleaned up in PRs like https://github.com/grpc/grpc/pull/37253, and a clean release will be made available soon.


refactor providers to be loaded via hooks instead of direct imports

consider using http://gossip.readthedocs.io/en/latest/

Is this what causes the schema validation for all providers (not only the used) during notifiers import?

@gs202 well, the providers are init on import and schema is validated on init, so yes.
Issue will be handled differently.


signing auto-generated SBOM using cosign

With new ko release, it creates and pushes an SBOM file by default. ^1 We can also pass a new flag called --sbom-sign <true|false> to sign before publishing it. In the SBOM push stage, we can execute cosign's SignCmd if aforesaid flag is set true.
Still not sure what kind of flags should be needed since we might use keyless mode, PKI, etc. options.
@developer-guy

+1, but we should depend on cosign SDK packages instead of it's CLI commands. We would also need to figure out what flags from cosign we want to bring over and what to do when they conflict (e.g., -a annotates signatures, but also might annotate images; should it also annotate signatures on SBOMs?)

/remove-lifecycle stale
For depending on the cosign SDK concern, let me link the related issue: https://github.com/sigstore/cosign/issues/1462

@imjasonh Is there any update on this? Happy to try and help with the process of making this possible.

we can work in a collaboration @ChaosInTheCRD, WDYT?

This is likely currently blocked on refactoring/rewriting the sigstore Go client to trim its dependencies and simplify the interface.
This is closely related to (and likely blocked on) #357, since as soon as we can easily sign the image we produce, we can also sign the SBOMs we produce. See that issue for discussions and open questions about how this should work, what CLI surface it should have, and open questions currently blocking.

@imjasonh noted, and figured this could well be the case.
@developer-guy that sounds like a great idea to me! only problem is that I am planning on being on holiday from tomorrow until 20th, so won't be possible to do so until then. If the offer is still open when I get back, that sounds good to me.

kindly ping @dentrax

Is there a good way to do this right now by invoking cosign after ko?
I was thinking about doing something like:
img=$(ko build)
cosign sign ${img}
cosign sign --attachment sbom ${img}

But I think the --attachment sbom call is unsafe because the sha256-xxxx.sbom tag could be modified and we could unwittingly end up signing something that ko didn't actually produce.

I would be interested in this feature as well!

With the maturing of https://github.com/sigstore/sigstore-go, does it make sense to revisit this issue to add SBOM signing using the lower-dependency sigstore-go library?

In particular, https://github.com/sigstore/sigstore-go/pull/30 may provide some hints on constructing these signatures using sigstore-go.

@evankanderson I would be interested in doing some work on this. maybe there is scope for us to pair?

Yes, I just wanted to check that this would fit the project goals before getting started.


Proof of Concept: Checksum field in dependencies

Given the move a federated buildpack dependencies it seems like it might be prudent for us to allow for different checksum algorithms to be used so that we can better adapt to checksums given by upstream providers. I have put together a quick POC to gauge the interest as well as prove out the possibility of the approach. I would love feedback on this!

Could we do the same thing for SourceSHA256?

@ryanmoran I can try it out and see what happens.


Support python3.

Compatible with python3 and python2.
Restructure the directory to support install via python setup.py install.
Support recovery before fresh login.

接口/运行方法 变了，文档尚需作相应修改

OK，我再改下

@liuwons updated.


can not start 64bit Applications

Links to 64bit Applications do not start the Application from within a fence.

Experiencing the same

Somehow it uses the 32bit program files path.
Even tho the shortcut i dragged into the fence links to "C:\Program Files\Google\Chrome\Application\chrome.exe"

By the way. Simply rebuilding with x64 as a target architecture makes it work.

@herrrossi69
This one is built for x64
https://filetransfer.io/data-package/CvapH4vV#link

After the change by GordnCZ in #45, x64 is now the default. Can you try the with the latest build from main if the problem is now fixed?

i am not very familiar with git. how to get the build from "main"?


Create RN-USRockets.netkan

You shouldn't need x_netkan_epoch -- that's for existing mods whose authors drastically alter their versioning scheme/break their version order

Passes local + Jenkins. Merging with my thanks.


EKS- Upgrade notification is not seen in imported cluster

What kind of request is this (question/bug/enhancement/feature request):
Bug
Steps to reproduce (least amount of steps as possible):
From EKS console, create an EKS cluster with k8s version 1.15
When cluster comes into active state, upgrade the cluster in the console to k8s 1.16
Do not upgrade the node group
When cluster comes into active state, import it into rancher
Result:
The cluster is active without an upgrade notification:

A notification is expected, informing the user a k8s upgrade is available for the node group:

Other details that may be helpful:
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): master-head version df9345c
Installation option (single install/HA): HA

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported): Imported

The bug fix is verified with Rancher server rancher\rancher:master-head version ec04f78
Steps:
From EKS console, create an EKS cluster with k8s version 1.15
When cluster comes into active state, upgrade the cluster in the console to k8s 1.16
Do not upgrade the node group
When cluster comes into active state, import it into rancher
Results:
The upgrade notification is seen on cluster import


delete old pointer

https://github.com/bmathieugit/steward/blob/31a43953d614bf5949ee099063d1031bc00eeb42/src/stew.hpp#L843

memory leak


Aggregates in select list result in model field type interface{}

db: Postgres
consider:
select
   sum(it.vatpence) as vatpence
from ...

where vatpence is an integer SQLC generates a row model with interface{} as the field type.  Workaround is to cast to int64 in client code.
thx
M

where vatpence is an integer SQLC generates a row model with interface{} as the field type. Workaround is to cast to int64 in client code.

Did you modify the generated sqlc code substituting the interface with an int or did you manually cast the interface to an int?
At the best of my knowledge I did it this way where intCast is the receiving end of the new int and interfaceVar is the interface returned by the sqlc query.:
	intCast, ok := interfaceVar.(int)
	if !ok {
            ....
	}

Any feedback on this approach? I'm not sure its the best, nor the only way to do it.

@kyleconroy Do we have a list of query types that are not fully supported? It might be nice to have a note in the readme and examples of handling some of the current edge cases.

We don't have such a list. There's a list of supported functions in pg_catalog.go, but's it's not complete. We'll need to generate that list from a fresh install of PostgreSQL.

This now works! I'm not sure when it got fixed, but v1.9.0 will generate the correct code, as shown here.


Add blurb in docs about Android NDK

cc @zapu and @cjb, who also ran into this error.

Obsoleted by https://github.com/keybase/client/pull/15850 (per @chrisnojima's suggestion)


vmconnect broken in master

I can't seem to get connections to Hyper-V instances working since a few commits.
Here's how I'm trying to connect: xfreerdp /v:VM_HOST /u:USER /p:PW /cert-ignore /vmconnect:INSTANCE_ID.
The output I get:
[17:12:21:011] [39992:1922523904] [DEBUG][com.freerdp.client.common.cmdline] - windows: 0/1 posix: -1000/0 compat: -1000/0
[17:12:21:030] [39992:47570944] [ERROR][com.freerdp.client.x11] - Property 296 does not exist
[17:12:21:031] [39992:47570944] [DEBUG][com.freerdp.core.nego] - Enabling security layer negotiation: FALSE
[17:12:21:031] [39992:47570944] [DEBUG][com.freerdp.core.nego] - Enabling restricted admin mode: FALSE
[17:12:21:031] [39992:47570944] [DEBUG][com.freerdp.core.nego] - Enabling RDP security: TRUE
[17:12:21:031] [39992:47570944] [DEBUG][com.freerdp.core.nego] - Enabling TLS security: TRUE
[17:12:21:031] [39992:47570944] [DEBUG][com.freerdp.core.nego] - Enabling NLA security: TRUE
[17:12:21:031] [39992:47570944] [DEBUG][com.freerdp.core.nego] - Enabling NLA extended security: FALSE
[17:12:21:031] [39992:47570944] [DEBUG][com.freerdp.core.nego] - Security Layer Negotiation is disabled
[17:12:21:031] [39992:47570944] [DEBUG][com.freerdp.core.nego] - Sending preconnection PDU
[17:12:21:032] [39992:47570944] [DEBUG][com.freerdp.core.nego] - state: NEGO_STATE_NLA
[17:12:21:039] [39992:47570944] [DEBUG][com.freerdp.core.nego] - Attempting NLA security
[17:12:21:040] [39992:47570944] [DEBUG][com.freerdp.core.nego] - nego_security_connect with PROTOCOL_NLA
[17:12:21:053] [39992:47570944] [DEBUG][com.freerdp.core.nla] - User: USERHERE Domain: (nil) Password: PASSHERE
[17:12:21:053] [39992:47570944] [DEBUG][com.winpr.sspi] - InitSecurityInterfaceExA
[17:12:21:053] [39992:47570944] [DEBUG][com.winpr.sspi] - QuerySecurityPackageInfoA: SEC_E_OK (0x0000)
[17:12:21:053] [39992:47570944] [DEBUG][com.winpr.sspi] - AcquireCredentialsHandleA: SEC_E_OK (0x0000)
[17:12:21:053] [39992:47570944] [DEBUG][com.winpr.sspi] - InitializeSecurityContextA: SEC_I_CONTINUE_NEEDED (0x90312)
[17:12:21:053] [39992:47570944] [DEBUG][com.freerdp.core.nla] - Sending Authentication Token
[17:12:21:053] [39992:47570944] [DEBUG][com.freerdp.core.nla] - 0000 4e 54 4c 4d 53 53 50 00 01 00 00 00 b7 82 08 e2 NTLMSSP.........
[17:12:21:053] [39992:47570944] [DEBUG][com.freerdp.core.nla] - 0010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
[17:12:21:090] [39992:47570944] [DEBUG][com.freerdp.core.nla] - 0020 06 01 b1 1d 00 00 00 0f                         ........
[17:12:21:090] [39992:47570944] [DEBUG][com.freerdp.core.nego] - RequestedProtocols: 3
[17:12:21:091] [39992:47570944] [ERROR][com.freerdp.core.nego] - Protocol Security Negotiation Failure
[17:12:21:091] [39992:47570944] [ERROR][com.freerdp.core] - freerdp_set_last_error 0x2000C
[17:12:21:091] [39992:47570944] [ERROR][com.freerdp.core.connection] - Error: protocol security negotiation or connection failure
[17:12:21:091] [39992:47570944] [ERROR][com.freerdp.client.x11] - Authentication only, exit status 1
[17:12:21:092] [39992:1922523904] [DEBUG][com.winpr.sspi] - DeleteSecurityContext: SEC_E_OK (0x0000)

Adding /sec:rdp/tls or nla into the mix doesn't change anything.

Just had a little git bisect session, this is the result: 9c7b7ab56165cf72ff002ab2e0dccfcedb96e3ce is the first bad commit

Just ran the same test using latest master, here's the output:
[15:49:56:022] [2734:72976300] [DEBUG][com.freerdp.client.common.cmdline] - windows: 0/1 posix: -1000/0 compat: -1000/0
[15:49:56:046] [2734:02eb9000] [ERROR][com.freerdp.client.x11] - Property 296 does not exist
[15:49:56:046] [2734:02eb9000] [DEBUG][com.freerdp.core.nego] - Enabling security layer negotiation: FALSE
[15:49:56:046] [2734:02eb9000] [DEBUG][com.freerdp.core.nego] - Enabling restricted admin mode: FALSE
[15:49:56:046] [2734:02eb9000] [DEBUG][com.freerdp.core.nego] - Enabling RDP security: TRUE
[15:49:56:046] [2734:02eb9000] [DEBUG][com.freerdp.core.nego] - Enabling TLS security: TRUE
[15:49:56:046] [2734:02eb9000] [DEBUG][com.freerdp.core.nego] - Enabling NLA security: TRUE
[15:49:56:046] [2734:02eb9000] [DEBUG][com.freerdp.core.nego] - Enabling NLA extended security: FALSE
[15:49:56:046] [2734:02eb9000] [DEBUG][com.freerdp.core.nego] - Security Layer Negotiation is disabled
[15:49:56:046] [2734:02eb9000] [DEBUG][com.freerdp.core.nego] - Sending preconnection PDU
[15:49:56:047] [2734:02eb9000] [DEBUG][com.freerdp.core.nego] - state: NEGO_STATE_NLA
[15:49:56:047] [2734:02eb9000] [DEBUG][com.freerdp.core.nego] - Attempting NLA security
[15:49:56:079] [2734:02eb9000] [DEBUG][com.freerdp.core.nego] - nego_security_connect with PROTOCOL_NLA
[15:49:56:080] [2734:02eb9000] [ERROR][com.freerdp.core] - freerdp_set_last_error ERRCONNECT_TLS_CONNECT_FAILED [0x20008]
[15:49:56:080] [2734:02eb9000] [ERROR][com.freerdp.core.nego] - Protocol Security Negotiation Failure
[15:49:56:081] [2734:02eb9000] [ERROR][com.freerdp.core.connection] - Error: protocol security negotiation or connection failure
[15:49:56:081] [2734:02eb9000] [ERROR][com.freerdp.client.x11] - Authentication only, exit status 1

Same problem here with the latest master. Tested with Hyper-V Server 2012 R2

Can anyone shine some light as to what/when it can be built with working vmconnect feature?

Same problem here but with GW option. Without GW it is okay, but I kinda have to go through GW...

Any updates?

I've tested the latest build trying to connect to and it will not connect to any of the following:
Windows Hyper-V Server 2012 (Normal RDP using 3389, and /vmconnect using 2179)
Windows Server 2012 R2 (Normal RDP using 3389)

I've tracked the commit that broke this functionality down to 9c7b7ab56165cf72ff002ab2e0dccfcedb96e3ce.

@jmdevince That's the same commit that I found 9 months ago: https://github.com/FreeRDP/FreeRDP/issues/2421#issuecomment-85507468

Is there any workaround for this issue? Is there a way with current master to connect to Hyper-V with FreeRDP? Or is the only workaround to use snapshot before commit 9c7b7ab?

I have a fix here: https://github.com/FreeRDP/FreeRDP/pull/3329

I confirm this is fixed (tested with WS 2012 R2).

Connection to Hyper-V VM on Windows Server 2016 using /vmconnect ends with error described below. On the other hand it works correctly on Windows Server 2012 R2. Also RDP connection to the same Windows Server 2016 on port 3389 works well.
FreeRDP version: freerdp-nightly-2.0-0+0~20161229033923.270~1.git90877f5, freerdp-nightly-2.0-0+0~20170112033917.272~1.git9e636f2
Client OS: Fedora 25 (also tested on Windows using wfreerdp)
/opt/freerdp-nightly/bin/xfreerdp /u:Administrator /vmconnect:3b32e28e-2117-4d7c-866e-021fb94316d9 /v:os-hyperv01 /log-level:trace
...
[12:08:38:425] [23596:23597] [INFO][com.freerdp.core] - ERRINFO_RPC_INITIATED_DISCONNECT (0x00000001):The disconnection was initiated by an administrative tool on the server in another session.
[12:08:38:425] [23596:23597] [DEBUG][com.freerdp.core.rdp] - DisconnectProviderUltimatum: reason: 1

Event log on Windows shows successfull logon session creation, but it's destroyed immediately (logoff without any errors).

@lemonmojo @jmdevince can you also verify that this is solved?

I no longer have an environment to test this in. Sorry I can't help.
Sent from my iPhone

On Jan 16, 2017, at 3:57 AM, Bernhard Miklautz<EMAIL_ADDRESS>wrote:
@lemonmojo @jmdevince can you also verify that this is solved?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Connection to Hyper-V VM on Windows Server 2016 using /vmconnect ends with error described below.
/opt/freerdp-nightly/bin/xfreerdp /u:Administrator /vmconnect:3b32e28e-2117-4d7c-866e-021fb94316d9 /v:os-hyperv01 /log-level:trace
...
[12:08:38:425] [23596:23597] [INFO][com.freerdp.core] - ERRINFO_RPC_INITIATED_DISCONNECT (0x00000001):The disconnection was initiated by an administrative tool on the server in another session.
[12:08:38:425] [23596:23597] [DEBUG][com.freerdp.core.rdp] - DisconnectProviderUltimatum: reason: 1

Can be solved by adding user (even if you are an administrator user) to the Hyper-V Administrators group using lusrmgr.msc (Local Users and Groups Manager).

@mkisielewski Thank you for the follow up. Closing this as resolved now.


Add types to NPM package and create publish script

@azmenak I already created a github action to automatically publish to NPM when you create a release on Github.

I just published the first version: https://github.com/d1g1tinc/fairlight/releases/tag/v0.4.1
Which triggered this build: https://github.com/d1g1tinc/fairlight/runs/487957625?check_suite_focus=true

Also it should already be publishing the typescript types, which were generated by tsc using the declaration: true tsconfig option
That being said, this process can be improved by uploading build artifacts to the github release.


Build/Rebuild doesn't generate XML documentation if DLL is up to date

Refiling for @MV10 on roslyn-project-system
Can't recall whether VS has always worked this way, I've probably never tried this particular scenario, but it seems like a bug.
Version Used:
VS 2015 Community edition with .NET Core 1.0 release and Tools Preview 2
Steps to Reproduce:

Create a .NET Core class project
Build
Open project properties
Check the "XML documentation file" option
Rebuild

Expected Behavior:
XML documentation file will be generated in the framework bin folders.
Actual Behavior:
No docs are generated. I have to go into the bin folders and delete the DLL (or change the source) to force a rebuild before the XML file is created.

@mv10 This is a bug/limitation in what we call the "fast up-to-check" which for performance reasons bypasses msbuild to do a quick up-to-date check. We're tracking for the rewrite under this feature: https://github.com/dotnet/roslyn-project-system/issues/62.


fix(OpenVINO): parse input sizes of 1d tensors

fixes issue
#71

Thank you @SolomidHero for spotting and solving the bug!!


enforce jobs/ to match the spec name

See https://github.com/cloudfoundry-incubator/kubo-release/pull/132 - I think bosh create-release should have failed if the job spec name didn't match the jobs folder name. It is spontaneously confusing to the casual reader when job names in source repo don't match the names in the final releases/manifests.

Story created https://www.pivotaltracker.com/story/show/153460843


lsb_release useless on NixOS

We have the lsb-release package in nixpkgs, but if you run it on NixOS, you get:
LSB Version:	n/a
Distributor ID:	n/a
Description:	(none)
Release:	n/a
Codename:	n/a

It seems like we need a file in /etc/lsb_release for the tool to find. My inclination would be to make a NixOS module that just injects sensible values into that file and to include it unconditionally. Am I missing anything obvious there?
Edit: or we could patch it somehow to just read /etc/os-release, which seems like a better path forward, but less standard.

It's worth noting that having (maybe it needs to be a non-symlink though?) /etc/lsb_release makes grub-mkconfig of other distros try to add NixOS configurations to their grub configurations, which is probably not desirable: https://github.com/NixOS/nixpkgs/issues/7406#issuecomment-94392628

What do you think about this?
--- a/lsb_release
+++ b/lsb_release
@@ -43,7 +43,7 @@

 # Defines the data files
 INFO_ROOT="/etc"                              # directory of config files
-INFO_LSB_FILE="lsb-release"                   # where to get LSB version
+INFO_LSB_FILE="os-release"                    # where to get LSB version
 INFO_DISTRIB_SUFFIX="release"                 # <distrib>-<suffix>
 ALTERNATE_DISTRIB_FILE="/etc/debian_version"  # for Debian [based distrib]
 ALTERNATE_DISTRIB_NAME="Debian"               #     "
@@ -167,6 +167,10 @@
     then
         # should init at least LSB_VERSION
         . "$INFO_ROOT/$INFO_LSB_FILE"
+        DISTRIB_ID=$ID
+        DISTRIB_DESCRIPTION=$PRETTY_NAME
+        DISTRIB_RELEASE=$VERSION_ID
+        DISTRIB_CODENAME=$(echo $VERSION | cut -d\( -f2 | cut -d\) -f1)
     fi
     [ -z "$LSB_VERSION" ] && LSB_VERSION=$MSG_NA
 }

Only LSB_VERSION is missing. It's supposed to be something like
:core-4.1-amd64:core-4.1-noarch:cxx-4.1-amd64:cxx-4.1-noarch:desktop-4.1-amd64:desktop-4.1-noarch:languages-4.1-amd64:languages-4.1-noarch:printing-4.1-amd64:printing-4.1-noarch

I have no idea what its meaning is and I couldn't find more information about it.

On Ubuntu the path is /etc/lsb-release and it has a different content than /etc/os-release.
/etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.2 LTS"

/etc/os-release
NAME="Ubuntu"
VERSION="16.04.2 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.2 LTS"
VERSION_ID="16.04"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"
VERSION_CODENAME=xenial
UBUNTU_CODENAME=xenial

I installed the lsb-release package on NixOS 16.09 and created /etc/lsb-release, but still get:
LSB Version:	n/a

I also renamed /etc/lsb-release to /etc/lsb_release but still same output.
Should we also include this package by default that people can use it to see on what type of system they are?

I installed the lsb-release package on NixOS 16.09 and created /etc/lsb-release, but still get:

Seems like the version in nixpkgs (currently 1.4 from 2001-01-04 :D) is outdated and still from sourceforge.
I think the most recent version is 4.1 (repo-link) or 5.0 (news-link).
We should probably upgrade the tool first and then test it again.

Oh wow, just a tad out of date :)
On Tue, Feb 21, 2017 at 14:50 Michael Weiss<EMAIL_ADDRESS>wrote:

I installed the lsb-release package on NixOS 16.09 and created
/etc/lsb-release, but still get:
Seems like the version in nixpkgs (currently 1.4 from 2001-01-04 :D) is
outdated and still from sourceforge
https://sourceforge.net/projects/lsb/.
I think the most recent version is 4.1 (repo-link
http://bzr.linuxfoundation.org/loggerhead/lsb/) or 5.0 (news-link
https://wiki.linuxfoundation.org/lsb/start).
We should probably upgrade the tool first and then test it again.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/NixOS/nixpkgs/issues/22729#issuecomment-281459722,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAKP7d78Fs-3rnjz9yfMmR6Jj5gkve1ks5re0AYgaJpZM4L-uHL
.

Should we also include this package by default that people can use it to see on what type of system they are?

:+1: - Sounds like a good idea and AFAIK most (nearly all?) Linux distributions include it by default (Gentoo is the only exception I remember).

We could also simply write our own version as well.
Or we could rewrite nixos-version.sh accordingly to the specification (or at least try to make it as compatible as possibly) and use it for both lsb_release and nixos-version (just some thoughts :smile:).

We could also simply write our own version as well.

Why? There are more important things to do. Just replace with the most official version and get it to work.

if we want to use /etc/os-release instead

is there any advantage to not use the common path? some scripts may depend on that path or people just cat it

The LSB Download page is temporarily down, and will be made available shortly.

Time to have an IPFS mirror of all our sources. So wait if it comes up again the next days, maybe ask, or else use the 4.1 from bzw repo.
When lsb_release works we can propose deleting nixos-version and just refer to it in the issue template and manual.

Time to have an IPFS mirror of all our sources.

We mirror most sources already (but not on IPFS).

I asked when the LSB Download page will be up again.

the work is currently in process

So we can wait some days until it is available again.
Can we get consent on how to proceed until then?

Can we get consent on how to proceed until then?

We could try but then I'd recommend asking at #nixos, nix-dev or mentioning some devs. Also a quick reminder that branch-off is in 5 days (28. February).

We could also simply write our own version as well.

Why? There are more important things to do. Just replace with the most official version and get it to work.

There are "always" more important things to do... (and I would even volunteer to write that version if necessary).
The question is whether it would help or not.
https://gist.github.com/skx/1f9e5240856c5976193a - An example for a simple Bash implementation (only 135 lines of code).
The advantage of writing our own version would be that we could introduce an additional "--hash|--revision" option which would make if compatible with nixos-version. And since nixos-version already exists as a Bash script inside the nixpkgs repo we could simply rewrite/extend it accordingly.
Also that way we could ignore the actual LSB stuff (I'm not aware of a discussion whether we want to follow the actual specification or not).
But there are obviously disadvantages as well.

is there any advantage to not use the common path? some scripts may depend on that path or people just cat it

https://github.com/NixOS/nixpkgs/issues/22729#issuecomment-279415374

When lsb_release works we can propose deleting nixos-version and just refer to it in the issue template and manual.

Especially deleting nixos-version would require a post to nix-dev and a note in the release notes. This could potentially break a lot of custom scripts which is why I'd try to avoid that. And we would have to properly replace all references (manual, modules, tests, the issue template, ... - git grep nixos-version).
Anyway imho it's already a bit too late for 17.3 but could we add a milestone for 17.9?

Note that nix packages have to break LSB, by design, so I don't think we should claim any LSB version.

Note that nix packages have to break LSB, by design

@vcunat thanks for clarifying. it's not about beeing LSB compliant, just about having the lsb_release program so people that wants to know on what system they are get that information, in a convenient way. i think using the official script and throwing the information in a textfile would be the easiest option to achieve this. but maybe we should avoid any "lsb" in NixOS...

The advantage of writing our own version would be that we could introduce an additional "--hash|--revision" option which would make if compatible with nixos-version. And since nixos-version already exists as a Bash script inside the nixpkgs repo we could simply rewrite/extend it accordingly.

@primeos thats a point, so why not if you would like to do that.

Especially deleting nixos-version would require a post to nix-dev and a note in the release notes. This could potentially break a lot of custom scripts which is why I'd try to avoid that. And we would have to properly replace all references (manual, modules, tests, the issue template, ... - git grep nixos-version).

sure. when we have this issue done, we could propose marking nixos-version as deprecated in release notes etc and delete every reference. then delete the actual command in the next release (17.09)

I meant just the contents of that line, which we might best leave as it is:

LSB Version:	n/a

I didn't mean that it's whole useless or anything similar.

Isn't lsb_release more or less deprecated now that we have /etc/os-release? (Why bother with it?)

@bjornfor i have sometimes the case that i get a ssh login and have to move a website from a server to our server. i'm interested what os is running. i use cat /etc/issue what NixOS don't have or lsb_release -a what works at least on debian based systems. on NixOS i currently get no information with this methods.

@davidak: But what if you run "cat /etc/os-release"? That works on all(?) modern distros, right?

/etc/os-release does exist on all the ones I've tried, but I don't think anyone's explicitly deprecated lsb_release as a result, so tools and humans still use it a fair amount.

@bjornfor @copumpkin I agree that lsb_release is a legacy tool but like @copumpkin said tools and humans probably still use it a fair amount. Do you think we should include lsb_release by default or not? And if you have time for it I'd be interested what you think of #23175 (it basically extends the nixos-version Bash script so that we could use it for lsb_release as well).

I have no strong opinion.

whether we make lsb_release do something in NixOS, or not, but it should definitely work by default in an FHS env. Which it currently doesn't

I don't know use cases, but sounds OK for FHS envs.  /cc @abbradar.

My use case was to play around with the chromium source tree. The tools to do so (repo, gclient, hooks) are complicated, chromium-specific and prone to a high rate of change, thus good candidates to be worked within an FHS env.
lsb_release is one of the tools, that chromium expects to be functional


question about test

with the program , l can train my data, but l can't test my data, It has a RuntimeError: Coordinator stopped with threads still running: Thread-11 Thread-12...can you give me some suggestion about it

Hi, were you able to solve this?


"$ npm run build" in windows stays freeze

Hi I successfully installed the dependencies and was able to run the app. But when I run the "$ npm run build" to build the app for deployment cursor blinks and nothing happened. Is that process take lot of time? or any issue with windows environment.

It does take a bit of time, but there should be output. Do you see absolutely no output in the terminal, and what's your Windows version?

windows 7 professional. Yes no output in the terminal.

Seems the issue is related with the directory creation. I manually created the "build" folder and now it's fixed.

I've experienced similar issues before on Windows. In order to avoid these problems make sure that

the command line you use is run as administrator,
your project files are on C:\ (or the partition windows is installed on).

See if this works :-)

Good suggestions form @maxmantz. Something else to keep in mind is that on windows, npm can die silently if you run into max-path issues. Thus, you should use npm 3+ to avoid this issue as well.

Since this seems like an environment-specific problem to @ududsha's machine I'll close this issue for now.
The excellent pointers by @joevbruno and @maxmantz should point you in the right direction to fix this issue, thanks to you two!


Please update this page managed virtual network is now GA

Hello,
This page is referencing 'managed virtual network' in 'preview' state...However, this service now in GA state, see below link
https://azure.microsoft.com/en-us/updates/azure-machine-learning-general-availability-for-october/
-Kirit

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

ID: cf71dd3a-2b00-ffea-4d7d-e48a15da88c6
Version Independent ID: 41ff90f9-75ef-db2e-64ef-9e5c5f77f6b8
Content: Machine learning enterprise security - Cloud Adoption Framework
Content Source: docs/ready/azure-best-practices/ai-machine-learning-enterprise-security.md
Service: caf
Sub-service: caf-methodology-ready
GitHub Login: @jhirono
Microsoft Alias: jhirono

Thank you for your feedback.  I have made an update to the page, which will be reflected after the next build.


Tag helpers lose user's case for class attribute when merging a TagBuilder

E.g.
<input Class="single-line" asp-for="property" />

results in
<input class="single-line" type="text" ... />

Fix is a very simple change to TagHelperOutputExtensions.
Self-assigning because I fixed this while making other changes...

27e4822


Annotate widget file upload stretches image

Prevent image stretching (the image that is loaded, e.g. a photo). Not sure what the desired behavior should be, but either:
a. keep canvas the same default size but load image similar to CSS object-fit: cover, or
b. resize canvas to aspect ratio of image (this will be more difficult on mobile portrait/landscape I think)

https://github.com/szimek/signature_pad/pull/241


Support for outgoing intendation lines with Outliner plugin

Is your feature request related to a problem? Please describe.
Outliner is adding great value to Obsidian for outlining of ideas.
https://github.com/vslinko/obsidian-outliner Currently Outliner has around 108k downloads.
When using Outliner with Minimal the the settings  "Draw vertical indentation lines" to show indentation doesn't look great (screenshot below)

The way it should be looking

Describe the solution you'd like
Making changes  in the theme that allow CSS  indentation  from Outliner to work (it may be toggle-able) or creating support of this style vertical lines in minimal itself

This should be requested on the Outliner plugin as it appears this way with every theme.
You can use Indentation Guides plugin for correct relationship lines


Treat boxes as owned pointers

What Changed?
Pointers of type Box are no longer associated with UNKNOWN_REGION and thus not considered to be aliasing one another.
Why Does It Need To?
Fixes the overtaint associated with the aliasing behavior of box.
Checklist

[x] Make tcx an argument to is_direct
[x] Above description has been filled out so that upon quash merge we have a
good record of what changed.
[x] New functions, methods, types are documented. Old documentation is updated
if necessary
[ ] Documentation in Notion has been updated
[x] Tests for new behaviors are provided

[ ] New test suites (if any) ave been added to the CI tests (in
.github/workflows/rust.yml) either as compiler test or integration test.
Or justification for their omission from CI has been provided in this PR
description.

@willcrichton this is the changes I made to accommodate boxes. Sadly most of them aren't visible here, because they're in rustc_utils. But maybe you could take a look at the test cases in boxes.rs and see if you have any further ideas for things to check for.


⚠ GitLab Server has degraded performance

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

HTTP code: 200
Response time: 7037 ms

Resolved: GitLab Server performance has improved in eb7fdc9.


Autodetecting gulpfile.ts tasks

As it seems, VS Code does only detect gulpfile.js tasks but not gulpfile.ts tasks. Would be nice if it works with a .ts file as well.

Wouldn't you have to compile the gulpfile.ts to a gulpfile.js first anyway?

no, you just require ts-node (as far as I can tell, I am a beginner in typescript)

To verify:

new folder
install ts-node, typescript and gulp locally
create a gulpfile.ts

import * as gulp from 'gulp';

gulp.task('compile', () => {
	console.log('Hello World');
});

Run task should list the task from the gulpfile.ts

Need to move to next milestone. This is not fully working.


original_dst_integrtion tests failing locally for main branch

I built the main branch and ran the tests locally on my machine and out of all the tests, the following target is failing:
test/extensions/filters/listener/original_dst/original_dst_integration_test
Since it was merged into the main branch, I guess that this problem is due to my machine, but I couldn't understand what makes this test special. Will appreciate help on this. Attaching the test output:
[==========] Running 6 tests from 2 test suites.
[----------] Global test environment set-up.
[----------] 4 tests from Protocols/OriginalDstIntegrationTest
[ RUN      ] Protocols/OriginalDstIntegrationTest.OriginalDstHttpManyConnections/IPv4_HttpDownstream_HttpUpstreamHttpParserNghttp2NoDeferredProcessing
[2023-02-02 16:47:08.769][12][critical][assert] [test/integration/http_integration.cc:533] assert failure: 0. Details: Timed out waiting for new connection.
[2023-02-02 16:47:08.769][12][critical][backtrace] [./source/server/backtrace.h:104] Caught Aborted, suspect faulting address 0x3e80000000c
[2023-02-02 16:47:08.769][12][critical][backtrace] [./source/server/backtrace.h:91] Backtrace (use tools/stack_decode.py to get line numbers):
[2023-02-02 16:47:08.769][12][critical][backtrace] [./source/server/backtrace.h:92] Envoy version: 0/1.26.0-dev/test/DEBUG/BoringSSL
[2023-02-02 16:47:08.837][12][critical][backtrace] [./source/server/backtrace.h:96] #0: Envoy::SignalAction::sigHandler() [0x4b9f968]
[2023-02-02 16:47:08.838][12][critical][backtrace] [./source/server/backtrace.h:98] #1: [0x7fd55be5a520]

It looks like this test relies on having many loopback addresses: <IP_ADDRESS>-<IP_ADDRESS>. Is there anything on your system that would disallow using those loopback addresses?

No, and this test has passed some time ago, it started recently after pulling latest commits.

Hi @ohadvano I am seeing the same issue, were you able to figure out what was wrong?

@ohadvano I created another issue, but then found a build option that worked for me https://github.com/envoyproxy/envoy/issues/25585


Include privacy info for Cocoapods

Recently SnapKit introduced support for Privacy manifest but only for SPM. This PR introduces the support for Cocoapods based projects by adding using resource_bundles in the podspec.
While using resources can lead to collisions for resources with the same name, using resource_bundles is safe because it is the bundle that gets copied to the main app target, not the contents of the bundle themselves.
More details on the solution using resource_bundles can be found in this great comment in the Google promises repository, which is working on the same fix:
https://github.com/google/promises/pull/226#discussion_r1447871477

@dcacenabes
I'm wondering if it shouldn't be
'SnapKit' => ['Sources/PrivacyInfo.xcprivacy'] instead of 'SnapKit_Privacy' => ['Sources/PrivacyInfo.xcprivacy'].
Looking at other libraries, it seems that resources are set using the library name... I might be wrong, but I think it's worth checking.

I'm holding out on this until there is a bit more official response from the Cocoapods teams, though I'm not sure there will be because the project seems to be mostly in stable and maintenance mode (which is totally fair!).
I'm not sure that this method of including it covers all use cases of Cocoapods but I'm willing to merge it if nothing further emerges from their end by the first weekish in Feb.

I'm holding out on this until there is a bit more official response from the Cocoapods teams, though I'm not sure there will be because the project seems to be mostly in stable and maintenance mode (which is totally fair!).
I'm not sure that this method of including it covers all use cases of Cocoapods but I'm willing to merge it if nothing further emerges from their end by the first weekish in Feb.

Apple enforces Privacy Manifest, but doesn't seem to share the curiosity clearly in applying it 😭
It would be nice to have a lot of information..😢

@dcacenabes
I'm wondering if it shouldn't be 'SnapKit' => ['Sources/PrivacyInfo.xcprivacy'] instead of 'SnapKit_Privacy' => ['Sources/PrivacyInfo.xcprivacy'].
Looking at other libraries, it seems that resources are set using the library name... I might be wrong, but I think it's worth checking.

Hey @wlxo0401 .
You can define whatever you want as a bundle name. I was following this approach of adding the _Privacy to the bundle for 2 reasons mainly:

After bumping to Xcode 15 we started having issues with bundles that had the same name as the module when loading assets in test targets. Changing the name to something different than the module name fixed it.
Google is also taking this approach to adding _Privacy to the bundle name: https://github.com/google/promises/pull/226/files#diff-dd80f678cfd0518f567236e913b53c5ff56dffff5eb81891d04f6c440d1d7d21R27

Unless the maintainer of this library has a strong opinion against the current naming I would like to keep it as is.

I'm holding out on this until there is a bit more official response from the Cocoapods teams, though I'm not sure there will be because the project seems to be mostly in stable and maintenance mode (which is totally fair!).
I'm not sure that this method of including it covers all use cases of Cocoapods but I'm willing to merge it if nothing further emerges from their end by the first weekish in Feb.

Thanks a lot for your reply @robertjpayne ! We will keep an eye here to any comms from Cocoapods or Apple regarding this matter.

Hi @robertjpayne !
It is almost mid-February already and there are no news from Cocoapods. Would it be possible to merge this already so that we can start adopting the latest version of the library? Thanks in advance!

@dcacenabes thanks :) Will publish to trunk tonight hopefully

@wlxo0401 @dcacenabes also I agree _Privacy on the bundle suffix. Too many things may make for weird collisions leaving it the same as the library itself. Also it's basically hidden and irrelevant to developer or end users.

Thanks @robertjpayne !
Looking forward to it getting released to start shipping this in our newest build :D !


Update package.json to make dependencies more flexible

Current dependencies and peer dependencies specs makes lib not usable together with monotrepo / nx as require exact versions of dependencies - which trigger conflicts.
With this change, adding ^ to versions, minor updates (that by semver do not break backward compatibility) are still alowed

Hi @dlvoy , this is merged and I will release a new version on npm soon.


Area Select crash

EA 138516
Factory Skyline  0.1.3
When choosing an area to select, and I release the mouse button the game crashes

Do you have the crash log or saving file or how it happens? I try several times in 138516, but can't get a crash.

Is the log saved in a particular place? Let me know and I can send it to you.
Kind regards,
Oscar Capote
Sent with ProtonMail Secure Email.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Thursday, December 3rd, 2020 at 10:09 PM, cepheidqq<EMAIL_ADDRESS>wrote:

Do you have the crash log or saving file or how it happens? I try several times in 138516, but can't get a crash.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

It did not do it now. Could have been something else that caused it. I will continue testing.
Kind regards,
Oscar Capote
Sent with ProtonMail Secure Email.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Friday, December 4th, 2020 at 12:04 AM, Oscar Capote<EMAIL_ADDRESS>wrote:

Is the log saved in a particular place? Let me know and I can send it to you.
Kind regards,
Oscar Capote
Sent with ProtonMail Secure Email.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Thursday, December 3rd, 2020 at 10:09 PM, cepheidqq<EMAIL_ADDRESS>wrote:

Do you have the crash log or saving file or how it happens? I try several times in 138516, but can't get a crash.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Hi i got the same Problem.
with normal Game Version CL177909.320 and Experimental CL184566.647.
Ive installed Mod Version 0.2.0 but in the game it views me 0.1.3 and i get an strange white box if select an area see here in screenshot.


Fix get bool env Issue #102

Contains fix for https://github.com/pryorda/vmware_exporter/issues/102

Codecov Report

Merging #103 into master will increase coverage by 0.1%.
The diff coverage is 100%.

@@            Coverage Diff            @@
##           master     #103     +/-   ##
=========================================
+ Coverage   91.64%   91.75%   +0.1%
=========================================
  Files           4        4
  Lines         455      461      +6
=========================================
+ Hits          417      423      +6
  Misses         38       38

Impacted Files
Coverage Δ

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

Continue to review full report at Codecov.

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

*@pryorda *- .lower() makes sense. Makes it a little bit more user friendly
IMO. I will make the modification.
On Fri, May 10, 2019 at 9:19 AM Daniel Pryor<EMAIL_ADDRESS>wrote:

@pryorda commented on this pull request.
This looks good to me let me know your thoughts on .lower()?
In vmware_exporter/helpers.py
https://github.com/pryorda/vmware_exporter/pull/103#discussion_r282950595
:

@@ -4,7 +4,13 @@

def get_bool_env(key, default=None):

return bool(os.environ.get(key, default))

value = os.environ.get(key, default)
if isinstance(value, str):

   if value == 'False':

Should we add .lower() to this to make sure that we account case
variations?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/pryorda/vmware_exporter/pull/103#pullrequestreview-236194022,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAFVZHJG2LODYJ7NUGD374TPUWN7VANCNFSM4HLXAQAQ
.

Closing in favor of #108


Install and set-up Kubernetes cluster using kubenow

This has been implemented using the steps at
https://github.com/airavata-courses/airavata-nextcoud/wiki/Assignment-4#steps-to-deploy-the-kubernetes-on-the-kubenow


Better options for spot instances

Environment:
all
Bug description and how to reproduce:
FEATURE request
Additional context:
Would be great to have an option (or even make that default behavior)  to switch to on demand if spot compute nodes fulfillment fails.

compute fleet with a mix of on-demand/spot might be a solve..

Hi, sneimir.

compute fleet with a mix of on-demand/spot might be a solve

I believe that a feature that will be part of the next release will provide this functionality.
As for the current version, you should be able to update a running cluster's config file's cluster_type value from spot to ondemand and then use pcluster update to apply the changes.
Here's what the update process looks like when I try it:
➜  pcluster update spot-to-ondemand
Validating configuration file ...
Retrieving configuration from CloudFormation for cluster spot-to-ondemand...
Found Configuration Changes:

#    parameter          old value    new value
---  -----------------  -----------  -----------
     [cluster default]
01   cluster_type       spot         ondemand

Validating configuration update...
Congratulations! The new configuration can be safely applied to your cluster.
Do you want to proceed with the update? - Y/N: Y
Updating: spot-to-ondemand
Calling update_stack
Status: parallelcluster-spot-to-ondemand - UPDATE_IN_PROGRESS

If you wanted to automate this, you could do so by periodically parsing the output from the shell command aws autoscaling describe-scaling-activities --auto-scaling-group-name ${ASG_NAME} --region ${CLUSTER_REGION} and, if for a certain period of time the output shows that the spot price is too low or there's too little spot capacity, you could then run pcluster update accordingly.

Starting from version 2.9.0, ParallelCluster introduced support for multiple queues and multiple instance types with Slurm scheduler: https://docs.aws.amazon.com/parallelcluster/latest/ug/queue-mode.html.
With this new feature you could configure an ondemand and a spot queue within the same cluster and build some custom automation in order to select the queue based on nodes availability. For the moment we do not plan to allow a single queue to contain both spot and ondemand capacity.


Is there any way i can attach label with a polygon?

No, polygons and labels are independent. You can attach properties to both, though.

Thanks for your fast response.
Can you explain what all properties.
My problem statement is that,  after importing gds if I move any polygon, label attach to that polygon should move as well but not vice versa.
Also this attachment would help in various other things.

There is no element attachment in the GDSII format. Labels are placed independently of polygons. If you move a label, only the label moves. The same goes for polygons. If you need a structure that moves together, place both the polygon and the label in a cell and move the cell reference around.
Properties are dictionaries associated to GDSII elements. You can access them through the properties variable.

Ok thank you


Fixes #24

Hi Robbert,
Thanks for the fix, however I would like it if you make a pull request to the dev branch with only the files that have been adjusted for the specific fix (Grid.js and Grid.md).
The jest files are a very good idea, which I would like to add in the future but I don't want a dev dependency from a different component library. We are going to contact the other lightning-ui-component in order to separate the test-render feature into a new library.
With kind regards,
Jeffrey

Hi @jfboeve,
I changed the base of the PR to be dev. As you can see I didn't remove the devDependencies, as I do not really understand why you wouldn't want to include them.
If in the future the TestRenderer feature is isolated into a new library, we can alter the dependencies to reflect the new state, right? I don't think it should be a reason to exclude tests from this project now.
Also, since only devDependencies have been installed, it will not affect the bundle size for users that install this package.
Feel free to convince me otherwise ofcourse, but please reconsider as I think it's good practice to start adding tests into this project :-)


url_parser  bug in requirements.txt

all version of optimus using git+https://github.com/hi-primus/url_parser@master
but url_parser doesn't have a master branch.
this is a link to the file: https://github.com/hi-primus/optimus/blob/develop-21.8/requirements.txt
please fix to main.
pr: https://github.com/hi-primus/optimus/pull/1137/files
easy fix.

it's true.
if you can merge the PR.
good work @liRONCO11.

Thank you @liRONCO11 and @avishai-o


Couldn't generate guest token

Hey, how are you?
I've been off for a while, working on my final engineering project.
I'm having this issue on my EC2 instance:
2023-10-28 19:35:52,979 [ERROR] :: Couldn't generate a new session.
'guest_token'
Traceback (most recent call last):
  File "/home/ec2-user/.local/lib/python3.9/site-packages/tweeterpy/tweeterpy.py", line 152, in generate_session
    guest_token = make_request(
KeyError: 'guest_token'
Traceback (most recent call last):
  File "/usr/lib64/python3.9/runpy.py", line 197, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/usr/lib64/python3.9/runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "/home/ec2-user/flask_api/phishbuster-cron/src/api/api.py", line 19, in <module>
    twitter_collector = TwitterDataCollector()
  File "/home/ec2-user/flask_api/phishbuster-cron/src/lib_tweeterpy/scrap_tweeterpy.py", line 12, in __init__
    self.twitter = TweeterPy()
  File "/home/ec2-user/.local/lib/python3.9/site-packages/tweeterpy/tweeterpy.py", line 29, in __init__
    self.generate_session()
  File "/home/ec2-user/.local/lib/python3.9/site-packages/tweeterpy/tweeterpy.py", line 152, in generate_session
    guest_token = make_request(
KeyError: 'guest_token'

I really dunno why it is happening and running out of options tbh.
Could you help me @iSarabjitDhiman ?

Hey @fpmirabile
I am good thanks. Hope you are well.
Have you tried residential proxies? The script usually doesn't work on VPS without proxies. Also check if the script is running fine on your local machine. If it is, try using it with residential proxies on your EC2 instance.
If it still doesn't work, let me know.

I'm well thanks !
Yes you are right, after reading and trying to udnerstand I saw a 429 (Too many requests) there.
Do you have any suggestion for the proxy? I never used one, and I'd love to avoid this issue, since probably today or tomorrow I will be doing a demo and need the "scrapper" to work

I'm well thanks !
Yes you are right, after reading and trying to udnerstand I saw a 429 (Too many requests) there.
Do you have any suggestion for the proxy? I never used one, and I'd love to avoid this issue, since probably today or tomorrow I will be doing a demo and need the "scrapper" to work

You can use any of them. Just search for residential proxies. I have used brightdata and smartproxy before. These work pretty well. (I am not affiliated with any of these.) There are also services like oxylabs, soax etc.
Do your research before choosing any.
Feel free to close the issue as well.


[RPO] use loss from v3 of paper

fixes #1868

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

https://github.com/huggingface/trl/blob/29bd0046a9e85cc5c4ff80d15322737caa06adfb/docs/source/dpo_trainer.mdx?plain=1#L149
SFT loss on the chosen preferences together with a weighted DPO loss

to
DPO loss together with a weighted SFT loss on the chosen preferences


Removing the  tag from our documentation

Multiple customers have told us that the  tags were not working for them.  Upon removing them on these specific policies they were able to get the preferences to apply correctly.

@JohanFreelancer9 Copy editing is needed for this PR. Thanks.

@adeejoseph PR has been copyedited and is ready for final review, could you please check and merge? Thanks!


Resources Menu

Describe the bug
Add back Resources menu option
To Reproduce
Resources menu hidden per previous request.
Expected behavior
Be able to see Resources menu.

Change menu option to Helpful Links


Migrate algorithm-related tutorials from qiskit-tutorials to qiskit-algorithms.

Summary
This PR aims to resolve issue #14
The tutorials have been added and modified to be consistent with the new library qiskit-algorithms
To do:

[ ]  History-preserving move from qiskit-tutorials/algorithms to qiskit_algorithms/tutorials
[ ]  Update imports in code snippets from qiskit.algorithms to qiskit_algorithms
[ ]  Update API-reference links and other documentation links in the tutorial body
[ ]  Update any references to tutorials in code API docstrings - grover.py has a note that links to the textbook and the tutorial (I noticed this first and searched for others but that was the only place I saw that needed fixing)
[ ]  Update wording around Qiskit. For instance the title of the 1st tutorial is An Introduction to Algorithms in Qiskit and perhaps we need something more like An Introduction to Algorithms for Qiskit instead given the move etc. Text in the main body should be checked over too and reworded appropriately e.g. from same tutorial Qiskit provides a number of Algorithms...
[ ]  Update random_seed setting using algorithm_globals (an import change) - see A new algorithm_globals to replace use of qiskit.utils instance #33

Details and comments
File docs/tutorials/01_algorithms_introduction.ipynb

Updated the links in the markdown cells
Modified the title to  "[..] Algorithms for Qiskit rather than "in Qiskit"
Re-run the cells
Note the Noisy VQE tutorial link will returns 404 because the tutorial has not been deployed yet. When the new changes are merged then the link should be working.

File docs/tutorials/02_vqe_advanced_options.ipynb

Updated the links in the markdown cells
Migration from qiskit.opflow to primitives

File 03_vqe_simulation_with_noise.ipynb, 04_vqd.ipynb

Updated the links in the markdown cells
Migration from qiskit.algorithms to qiskit_algorithms

The history preserving move/copy would be the first thing done so when the files are in the new place they already have their commit history - e.g that history would be visible in your fork. Then any changes are done to the files afterwards so these new changes build. You can search for git history preserving copies for how this is done. I imagine this would be all tutorials except 09_IQPE which does not use anything from algorithms at all - if it needed to be copied to facilitate the history that would ok. As part of the next changes it can just get deleted.
We would likely have to do the move/copy in a separate PR since by default the merge here flattens commit history so we would need to do something special when merging (which can be done) to preserve that history.  It would be possible to add in the new changes at the same time but if that is done over a set of commits, because we want/need to comment/fix any new changes etc, they would all end up in the history which is not something we would likely want - for new changes normally all commits are flattened into a single commit (this is what history of tutorials is already). So arguably separating dealing with the history and then the new changes across a couple of PRs is more likely the better way to cater to this.

OK @woodsp-ibm  I will do some research on that, and make new branch to do the move/copy step. Thank you for the explanation.


corp: add decimal support

@ngaut @coocood @qiuyesuifeng  PTAL
After this pr, #535 should be resolved.

PTAL @morefreeze

LGTM

What's the upper limit of Decimal? Did you test for parsing string like "99999..." ('9' of 30 digits or more)?

Upper limit has not been added yet. There is a TODO for it.

LGTM

@ngaut @qiuyesuifeng PTAL


Graph does not load properly, when there is lazy loading component

Bug Report
Description

The graph does not load properly when there is a lazy loading component on the dom along with the carbon-graph.
Graphs affected

[ ]  Bar graph
[ ]  Bubble graph
[ ]  Gantt chart
[x]  Line graph
[ ]  Paired result
[ ]  Pie chart
[ ]  Scatter plot
[ ]  Timeline

Steps to Reproduce

Add a component and import it using React.lazy()

Additional Context / Screenshots

Expected Behavior

The graph should load properly.
Possible Solution

I had posted the same in teams channel. Here is the link.
@ Mentions

@mraplumb Unfortunately I could not reproduce in the codesandbox. I am not sure if it is fine to provide the internal github link. All the details are mentioned in the teams channel.
https://teams.microsoft.com/l/message/19:ae0d6e7035e041c7b3fa1a1b9ad27c2d@thread.skype/1617010416621?tenantId=fbc493a8-0d24-4454-a815-f4ca58e8c09d&groupId=45f47bfa-38a9-444d-8933-9c20266ae38c&parentMessageId=1617010416621&teamName=Terra&channelName=Carbon Graphs&createdTime=1617010416621

The issue is resolved once I wrapped the lazy loading component with React.Suspense.

Good to hear @SharathAlur.  Closing this as a non issue then.


update(plugins): bump sdk go to latest dev version

What type of PR is this?
/kind cleanup
Any specific area of the project related to this PR?
/area plugins
What this PR does / why we need it:
This PR bumps the plugin sdk go dependency to its latest dev version for all plugins bundled with Falco. The purpose is to have a dev version of Falco with plugins supporting the latest plugin API major version 3.0.0 and start testing the whole package.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jasondellaluce
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [jasondellaluce]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jasondellaluce, leogr
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [jasondellaluce,leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: 3e4b0a8ddcdd5603c10c82db1b37a0c0ff2cab7f


Use sorted courses list for download course

Changed the download course function to use the courses list of the Adapter since it is updated after sorting, alphabetically and according to favourite status.
Fixes #331

Just went through the commit history. I introduced this bug in 0e58e235de44f929da545a67464e2d7328095854 when migrating to Kotlin. Good job spotting and fixing it.
Ideally, we should just rewrite this entire fragment+adapter so that it's the fragment that modifies the list while the adapter simply accesses it. Or possibly have only one List representing the list of courses. Two different lists that are supposed to serve the same purpose but are out-of-sync with each other will cause subtle bugs like these.
@VaishnaviShri Go ahead and merge this in.


How to mount instance storage automatically

Environment:

AWS Region: ap-northeast-2
Instance Type(s): m5d.xlarge

Hi,
Our application generates a lot of temporary data, and we would like to take advantage of instance storage to store temporary data. So, I would like to learn how to mount instance storage automatically, so that Pods can use mount points for hostPath volumes. Currently we have to log on to each instance and mount instance storage manually, which is tedious and does not scale.
What I tried is to append the following script to the end of 'files/bootstrap.sh' and create a new AMI.
if [ "$(file -b -s /dev/nvme1n1)" == "data" ]; then
mkfs -t ext4 /dev/nvme1n1
mkdir -p /tmp/ephemeral1
mount /dev/nvme1n1 /tmp/ephemeral1
chown ec2-user:ec2-user /tmp/ephemeral1
fi
Then, I create an EKS cluster (using eksctl) with the new AMI and an EC2 instance type that comes with instance storage (e.g., m5d.xlarge which has /dev/nvme1n1). Still, /dev/nvme1n1 is not mounted automatically. (I can log on to the EC2 instance and mount it manually.)
I would appreciate any comment on this issue.
--- Sungwoo

@glapark did you find a solution to this? Can you share? Thank you.

I use preBootstrapCommands to mount instance storage. Here is an example of
YAML:
nodeGroups:

name: mr3-worker
preBootstrapCommands:

"mkfs -t ext4 /dev/nvme1n1"
"mkdir -p /ephemeral1"
"mount /dev/nvme1n1 /ephemeral1"
"chown ec2-user:ec2-user /ephemeral1"

--- gla
On Thu, Dec 12, 2019 at 8:04 AM John Win<EMAIL_ADDRESS>wrote:

@glapark https://github.com/glapark did you find a solution to this?
Can you share? Thank you.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/awslabs/amazon-eks-ami/issues/326?email_source=notifications&email_token=ABQHUWIHX4ZPJAKJSLLAQ5DQYFWY7A5CNFSM4ISW3IK2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGU4BHY#issuecomment-564773023,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABQHUWLC3I3YKTYMGXOVB4LQYFWY7ANCNFSM4ISW3IKQ
.

Thank you. That was very helpful.

@glapark
How did you provision the EC2 node, using nvme SSD disk such as m5d.xlarge?
I want to make a EKS cluster using c5d.2xlarge node, but on the AWS console there's no instance type supporting instance storage.
Did you use eksctl?
I am wondering how did you make m5d.xlarge type ec2 node.
Thank you.

Yes, I used eksctl. For details, please see:
https://mr3docs.datamonad.com/docs/quick/aws/run-eks-autoscaling/
-- gla
On Thu, Nov 5, 2020 at 11:45 AM 최준영<EMAIL_ADDRESS>wrote:

@glapark https://github.com/glapark
How did you provision the EC2 node, using nvme SSD disk such as m5d.xlarge
?
I want to make a EKS cluster using c5d.2xlarge node, but on the AWS
console there's no instance type supporting instance storage.
Did you use eksctl?
I am wondering how did you make m5d.xlarge type ec2 node.
Thank you.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/awslabs/amazon-eks-ami/issues/326#issuecomment-722101155,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABQHUWOFAOJWSMOD3GRRXBLSOIGU7ANCNFSM4ISW3IKQ
.


Improve Regex for LC0024 to support return value

I didn't know how to create a PR for a wiki therefore here is my suggestion:
Replace the current RegEx for Rule LC0024 with the following
((.*)procedure(.*)\((.*)\)(.*))([;]$)

The additional group (.*) inside the first capturing group provides support for return values:
internal procedure HtmlToText(HtmlText: Text): Text;
begin
end;
internal procedure HtmlToText(HtmlText: Text) PlainText: Text;
begin
end;

Awesome! 🙌
I've updated the wiki-page with your suggestion.
When the new version of the AZ AL Dev Tools/AL Code Outline will be release, there will even be a Code Action (https://github.com/anzwdev/al-code-outline/issues/506) available for this.
This because breaking the method on multiple lines will not be resolved with the regex (couldn't get it to work unfortunately.
    internal procedure HtmlToText(HtmlText: Text;
                                     Encoding: TextEncoding) PlainText: Text;
    begin
    end;


CSV download not working

After I click the "List All Files" button from the "Project Contents" page, this triggers the background job for generating the CSV file for download.  However when the job completes as reported in my dashboard, when I click on the "download" link, I get the following error:

It is also logged in Honeybadger here.
The shared file locations referenced here is configured and the CSV is being generated on the server (I logged in and checked).
Does something need to be adjusted in this method?

I see the problem, the code is looking under ./public instead of looking in the shared location /mnt/nfs/tigerdata/. Not sure why, though. I'll take a closer look.


Works in Chrome, Not in MS Explorer11

Works great in Google Chrome, but no worky in MS Exploder11.

@Homewatts, can you provide more information?

Is there an error message on the JS console? What is it?
Are you sure that is the line that is failing?
Can you split up that line to isolate the error? eg,if (Tablesort) {
    if (document.getElementById) {
        var table = document.getElementById("myTable");
        if (table) {
            new Tablesort(table);
        }
    }
}

Hi tripu,
I'm not getting an error message. It just does nothing in IE11.
Here is all of the pertinent code.

{$doctitle}

Serial
Start Wt
Max Wt
Min Wt
Max Delta
Capacity

		{foreach $results as $r}

{$r['serial']}
{$r['startwt']}
{$r['maxwt']}
{$r['minwt']}
{$r['maxdelta']}
{$r['capacity']}

		{/foreach}

(I edited your last comment just to fix Markdown formatting, @Homewatts.)
There are lots of things that could be going wrong; it's difficult to tell just by looking at this code.
Some ideas:

Are the JS files being loaded OK?
What is that .tablesorter() function?
Please debug the script I gave you using devtools, line by line, to see what conditions are met, thus what statements are executed or are not executed.
This seems to be a dynamic table, generated via JS. Try with a simpler table first (one with static data), and see if that works.

Hi there, just ran into this problem myself.  Can't be sure it's the same as OP but here's what I'm seeing.

That specific code looks like this (line 44 is the init() with character 11 being the space right after init):
    (a.prototype = {
      init(a, b) {
        let c,
          d,
          e,
          f,
          g = this;
        if (
          ((g.table = a),
          (g.thead = !1),
          (g.options = b),
          a.rows && a.rows.length > 0)
        )
          if (a.tHead && a.tHead.rows.length > 0) {
            for (e = 0; e < a.tHead.rows.length; e++)
              if (
                a.tHead.rows[e].getAttribute('data-sort-method') === 'thead'
              ) {
                c = a.tHead.rows[e];
                break;
              }
            c || (c = a.tHead.rows[a.tHead.rows.length - 1]), (g.thead = !0);
          } else c = a.rows[0];
        if (c) {
          const h = function() {
            g.current &&
              g.current !== this &&
              g.current.removeAttribute('aria-sort'),
              (g.current = this),
              g.sortTable(this);
          };
          for (e = 0; e < c.cells.length; e++)
            (f = c.cells[e]),
              f.setAttribute('role', 'columnheader'),
              f.getAttribute('data-sort-method') !== 'none' &&
                ((f.tabindex = 0),
                f.addEventListener('click', h, !1),
                f.getAttribute('data-sort-default') !== null && (d = f));
          d && ((g.current = d), g.sortTable(d));
        }
      },
      sortTable(a, g) {

So my guess is that it's thinking that's supposed to be a dictionary: init: function() or something...?

@tripu I reverted back to version 5.0.0 and the problem went away.

@tripu both those codepens worked for me in IE11 so I'm guessing it was something with my setup.  I was using PUG and hosting on Firebase Functions so I'm wondering if perhaps the file passed through my babel or something as part of my build process.  When I'm back in that area of the code I'll try to upgrade again and let you know if I see a problem.


fix(docs): Map @alpha tags to "Legacy" alerts in API documentation

In our repo, we are currently using the @alpha release tag to mean something different than "alpha". We currently map it to a concept we're calling "legacy". This PR updates the generated API docs to use "Legacy" terminology in various tables in the API docs, instead of "Alpha" to avoid any customer confusion.
In the future, we plan on reclaiming @alpha for its traditional meaning, and using a @legacy tag for the special concept. The configurations changed here will be need to changed again at that time.
Before

After

AB#8406

Pending #21524 being merged and published. At which time the dependency can be updated in this PR, and the new needed functionality can be leveraged.

🔗 Found some broken links! 💔

The link checker appears to be broken. We must not be building the API docs before running it. I'll investigate separately.


More details needed for smoke test

Hi all,
Thanks for searching the work. I'm using a single GPU box to smoke test the repo. But I don't think it's working despite the required changed in the instructions. Please let me know if I'm missing something.
Command:
bash ./base_experiment_scripts/search_backup_train.sh
All the output I got:
We don't use warmup lr when using NASModelMaker
Setting drop_connect_rate as 0. We don't use drop_connect when search
train steps :  10008
next eval point :  12510
We don't use warmup lr when using NASModelMaker
Setting drop_connect_rate as 0. We don't use drop_connect when search
train steps :  12510
next eval point :  12510
We don't care about latency when we train
train steps :  150120
next eval point :  50040
We don't care about latency when we train
train steps :  437850
next eval point :  6255

Changes made to base_experiment_scripts/search_backup_train.sh
export DATA_DIR= a local directory with train-xxxxxx-of-01024 TF records
export MODEL_NAME=mixconv_super_3_4_7_4_11.json
export TEST_SAVE_FOLDER= a local directory
export TPU_SETTINGS=""
export TARGET_LATENCY=1.40

Removed gsutil from all cp operations, such as
cp ${SEARCH_LOG_FILE} ${SEARCH_DIR}/${SEARCH_LOG_FILE}
Changes made to run/main.py
The use_tpu flag set to False
flags.DEFINE_bool(
    'use_tpu', default=False,
    help=('Use TPU to execute the model for training and evaluation. If'
          ' --use_tpu=false, will use whatever devices are available to'
          ' TensorFlow by default (e.g. CPU and GPU)'))

Hi @lcmeng ,
Thanks for the smoke test!!
Sorry for the lack of information.
When I use GPU, I try to use
export TPU_SETTINGS="--use_tpu=False --transpose_input=False --use_cache=False"

transpose_input=False : This FLAG is for optimizing input format when using TPU, not GPU.
use_cache=False : Not necessary, but this reduces memory consumption.

Also, please check the batch size.
Additional notes

check the MODEL_NAME. I made an env variable named MODEL_JSON, which appends '.json'. Maybe you are using path like mixconv_super_3_4_7_4_11.json.json ...
Did you change the Latency Folder name (constraint_lut_folder FLAG) correctly?

Again, thanks. I will add details to the README file.

Please open again when more information is needed.


Before index hook

What does this PR do?
It adds a before_index option to the extension, which accepts a proc that will be called with each record prior to indexing. This allows users to modify the data format of the records, prior to them being shipped off to Algolias
How should this be tested?

Read the tests, make sure they're sane, and run them
If you're so inclined, you can play around with the base fixture to actually run this on a middleman app

Notes
I did some tab-sizing fixes on this one, so there's a lot of lines changed that didn't actually change functionally. Sry.

FYI, gonna add rubocop and some contribution guidelines in my next PR. Sorry it's missing here.

👍