⚠ gorzdrav.org has degraded performance

In a55b86d, gorzdrav.org (https://gorzdrav.org) experienced degraded performance:

HTTP code: 200
Response time: 5553 ms

Resolved: gorzdrav.org performance has improved in 22cc872.


Override sorting type when using t.crud

Hi, first of all, thank you for maintaining this fork even when the original is deprecated.
This is not an issue rather a question, I'm upgrading prisma from 3.x to 5.1.0 and using t.crud is generating new types instead of the old ones which is a breaking change in our graphql schema.
If a model MyModel have a nullable field x, then if I do t.crud.mymodel({ ordering : { x: true } })
then, the generated input in my schema.graphql is input QueryMyModelOrderByInput { x: SortOrderInput }
previously, the generated type in<EMAIL_ADDRESS>using an older version of nexus-plugin-prisma will generate input QueryModelOrderByInput { x: SortOrderInput } which I know is fine since SortOrderInput is an improvement but, in my case, for my current existing graphql schema is a breaking change since it will affect the frontend (cached versions especifically).
Given this context, my question is: do you know how can I keep backwards compatibility by using like SortOrderInput | SortOrder when using this library? The workaround I realized is by manually overwriting the generated schema and/or creating another query like a v2.
Thanks in advance.

@bmaciass thx for the issue. Could you provide the full type info for SortOrderInput and SortOrder (respectively latest prisma vs. prisma@3.x)? (or a small repro so I can look).
Looking at this repo (between commits<PHONE_NUMBER>7f106b13f4514d72e54c34d334db36 and<PHONE_NUMBER>7f106b13f4514d72e54c34d334db36), I see the ./tests/__app/generated/schema.graphql generated file creating SortOrder in both cases, as:
enum SortOrder {
  asc
  desc
}

@morgothulhu sorry for the very late response, I think when upgrading to prisma v5 the Sort enums changed when the field being ordered accepts null. If a field does not accept null the sort enum remains the same.
In short, upgrading from prisma v3 to v5 and generating schema.graphql by running nexus breaks the schema; so I fixed this by manually creating the SortOrder enum - in this way, the enum won't be created at all and the schema won't break :sweat_smile:


Cannot read with AcadSharp dwg file created with AcadSharp

Describe the bug
Cannot read with AcadSharp a dwg file written with AcadSharp.
To Reproduce
I've created a dwg file with AcadSharp and then saved.
All the documents section (such as the Header) are as default.
When I try to load the file with DwgReader it throws the following exception:
ACadSharp.Exceptions.DwgNotSupportedException: 'Dwg version not recognised.
Write dwg code:
// new document
ACadSharp.CadDocument doc = new ACadSharp.CadDocument();
// write file
ACadSharp.IO.DwgWriter writer = new ACadSharp.IO.DwgWriter("Test.dwg", doc);
writer.Write();

Read dwg code:
ACadSharp.CadDocument loaded = ACadSharp.IO.DwgReader.Read("Test.dwg");

Full exception and stack trace:
ACadSharp.Exceptions.DwgNotSupportedException: 'Dwg version not recognised
at ACadSharp.IO.DWG.DwgFileHeader.CreateFileHeader(ACadVersion version) in C:\Users\stage1\source\repos\ACadSharp\ACadSharp\IO\DWG\FileHeaders\DwgFileHeader.cs:line 37
at ACadSharp.IO.DwgReader.readFileHeader() in C:\Users\stage1\source\repos\ACadSharp\ACadSharp\IO\DWG\DwgReader.cs:line 225
at ACadSharp.IO.DwgReader.Read() in C:\Users\stage1\source\repos\ACadSharp\ACadSharp\IO\DWG\DwgReader.cs:line 97
at ACadSharp.IO.DwgReader.Read(String filename, DwgReaderConfiguration configuration, NotificationEventHandler notification) in C:\Users\stage1\source\repos\ACadSharp\ACadSharp\IO\DWG\DwgReader.cs:line 83
at ACadSharp.IO.DwgReader.Read(String filename, NotificationEventHandler notification) in C:\Users\stage1\source\repos\ACadSharp\ACadSharp\IO\DWG\DwgReader.cs:line 66

Expected behavior
No exception
Screenshots
From CadUtils:

It return AcadVersion.Unknown

Hi @sv-ed,
There is a dedicated test for this feature ACadSharp.Tests.IO.DWG.DwgWriterTests and it seems to work find, if that fails for you it may be related to the Encoding of the file.
If you open the file using a text editor can you see the version there?

No, I cannot see it

How can I make sure to set the right encoding when saving the file?

This is strange... this part of the file is enforced in ASCII Encoding:
////0x00	6	“ACXXXX” version string
this._stream.Position = 0L;
this._stream.Write(Encoding.ASCII.GetBytes(this._document.Header.VersionString), 0, 6);

Which you should be able to read without any problem using a text editor.
Check the version of the header to be sure that the CadDocument.Header.Version is equal to AC1018.
Also if you could attach this corrupted file it would be great so I can take a look.

This is strange... this part of the file is enforced in ASCII Encoding:
////0x00	6	“ACXXXX” version string
this._stream.Position = 0L;
this._stream.Write(Encoding.ASCII.GetBytes(this._document.Header.VersionString), 0, 6);

Which you should be able to read without any problem using a text editor.
Check the version of the header to be sure that the CadDocument.Header.Version is equal to AC1018.
Also if you could attach this corrupted file it would be great so I can take a look.

Header.Version is set by default in CadHeader.cs as ACadVersion.AC1018 and it was not modified.
Here is a screenshot from Quick Watch at this line: ACadSharp.IO.DwgWriter writer = new ACadSharp.IO.DwgWriter("Test.dwg", doc);

Link to the Test.dwg file below.
Test.zip

It seems that a part of the file is not written:
Your file:

My file:

You can se that both files are almost equal at the line 00000100 but the first 100 bytes are missing in your file and filled with empty bytes, the writer does that to save a space for the metadata:
public DwgFileHeaderWriterAC18(Stream stream, CadDocument model) : base(stream, model)
{
	// File header info
	for (int i = 0; i < this._fileHeaderSize; i++)
	{
		this._stream.WriteByte(0);
	}
}

The part that is missing is in this method, DwgFileHeaderWriterAC18.writeFileMetaData, if you are using this repo to debug, try to put a breakpoint at the beginning of this method to see if it hits, also check that your branch is fully updated with the current master branch.

So the string is written in the main stream... this part of the code uses the submodule CSUtilities to manage the streams, this should be up to date too, in older versions the stream was copied, if that's the case this could be writing the information somewhere else, please check the version of the submodule.
One last chance that you could try is to re-download the hole repo again in a separate folder and test the same code again, to make sure that everything is up to date.
If all this fail I'll need to explore this issue with more time.

I can confirm that CSUtilities is at the latest commit.
I tried cloning the AcadSharp repo again and then init and update sumbodule but unfortunately, same behaviour as described before.

try this:
using (DwgWriter writer = new DwgWriter("Test.dwg", doc))
{
    writer.Write();
}

Well... yes, that worked, thank you :)

This also solves the issue that the stream wasn't closed successfully and the file resulted opened by another process, if I tried to open if after the write.
Closing the program closed the stream too so the file was openable.

perfect, I'll open a branch to apply a fix to manually dispose the stream to avoid this issue in the future.


Fix invalid exercise UUIDs

The previous version of configlet uuid was known to generate invalid UUIDs. The latest release of Configlet v3.6.1 fixes that issue for newly added exercises, but existing exercise UUIDs need to be updated manually.
This change pertains to exercism/configlet#99

@nywilken Most of the current UUIDs I believe were generated without configlet, but an external tool. Form reading issue 99, I am not sure exactly why the existing UUIDs need to change. Shouldn't the lint tool catch any clashes?

Also is there a way to check for invalid UUIDs and only change those?

@Stargator thanks for looking into the PR. There is actually just one invalid UUID that I am replacing in this PR "d6657d4a-0257-0c80-6667-fddd127a571f0ad1fd4". Looking at the format 8-4-4-4-19 it was most likely generated by the old version of Configlet.

I am not sure exactly why the existing UUIDs need to change. Shouldn't the lint tool catch any clashes?

The lint command checks for UUID clashes within tracks, but it does not actually check that the UUID is indeed a valid UUID (https://en.wikipedia.org/wiki/Universally_unique_identifier#Standards).
I used a WIP build of Configlet (https://github.com/exercism/configlet/pull/107) to fix the UUID. It checks a track's config.json file for any invalid UUIDs and replaces them with a new UUID if the --repair flag is provided at runtime. So only one UUID change is necessary at this time.
› configlet uuid doctor . --repair
[X] d6657d4a-0257-0c80-6667-fddd127a571f0ad1fd4 (dart:raindrops)

Please let me know if that answers your question.


Resposive does not hide multiple header row columns

Here an example fiddle
http://jsfiddle.net/UvjnT/831/

This is a known issue I'm afraid. See this issue.
Closing in favour of the existing issue.


Unable to connect to Redis with correct credentials

I'm attempting to use a newly created Redis user. However, I'm getting the following error:
error: Uncaught (in promise) Error: -WRONGPASS invalid username-password pair

    throw new ErrorReplyError(line);
          ^
    at tryParseErrorReply (https://deno.land/x/redis@v0.25.4/protocol/reply.ts:205:11)
    at readReply (https://deno.land/x/redis@v0.25.4/protocol/reply.ts:55:7)
    at async RedisConnection.connectThunkified (https://deno.land/x/redis@v0.25.4/connection.ts:97:11)
    at async RedisConnection.connect (https://deno.land/x/redis@v0.25.4/connection.ts:126:5)
    at async connect (https://deno.land/x/redis@v0.25.4/redis.ts:2287:3)
    at async file://<location>

I'm essentially connecting to the following client via the following:
export const REDIS = await connect(parseURL(Deno.env.get("REDIS_URL")!));

When using my Redis default user, this code works fine. However, when using the new user, it doesn't. I know the REDIS_URL environmental variable is correct because I've used it to access Redis via redis-cli -u <url>.
Please let me know if there's any more information you need and thank you in advance.

@isyouaint Thanks for the report! Could you tell us the format of the URL set in the REDIS_URL variable so we can investigate the cause in more detail?

@isyouaint Thanks for the report! Could you tell us the format of the URL set in the REDIS_URL variable so we can investigate the cause in more detail?

As well, I tried connecting without using parseURL and got the same error. Format of the REDIS_URL variable is:
redis://<name>:<password>@<hostname>:<port>

@uki00a, I added a username parameter to RedisConnection.authenticate and was able to get this working. Reading this gave me the idea. Hopefully, this helps come to a solution.
Before:
private authenticate(password: string): Promise<RedisReply> {
  return sendCommand(this.writer, this.reader, "AUTH", password);
}

After:
private authenticate(username: string, password: string): Promise<RedisReply> {
  return sendCommand(this.writer, this.reader, "AUTH", username, password);
}

@isyouaint I guess you are using Redis 6.
The code in your Before block only works with Redis versions prior of 6.

Any issue with me adding this functionality in a PR?

@isyouaint A PR will be welcome! :+1:

suggest you update RedisConnectionOptions to support username?: string and also update authenticate' function to check for usernameand adjust redis command as needed for password/default auth"AUTH", passwordand if exists"AUTH", username, password`
not sure if this is being progresses, if not I am more than willing to make the carious changes as a PR let me know, as I am kind of making these changes to work with redislabs cloud right now anyway.

@uki00a all good, I will add a couple tests for the new situations

password passed no username passed
password and username passed

Will let ya know when its ready to roll, I should be able to complete this tonight once other work is done (I am on GMT)
Thanks for the quick turn-around, this was a breaking issue for me so assume its same for a few others.
-Scott

@scott-ling I haven’t yet started work on a PR, so I guess it’s yours 🤙🏾

Sorry for delay, PR made.


Removing the red boarder for .err in examples

The err highlighting is messing with your examples and makes things look a little weird. Removing it.

You can preview this docs PR at http://331.docs-pr.validatedpatterns.io
Note that they get generated every five minutes, so please wait a bit.


MIN() returns an interface{}

Version
Other
What happened?
(version 1.16.0)
select min(id) from authors; creates a function that returns an interface{} instead of a NULL-able version of the id type.
#1574 talks about this for DATETIME types, but other issues indicates that it should work for simpler types, maybe?
If not, what's the workaround? Parsing the interface{} is awkward, best I can tell.
Relevant log output
No response
Database schema
No response
SQL queries
No response
Configuration
No response
Playground URL
https://play.sqlc.dev/p/96e9cf0291f2e13cc784144f8abd4d5a556c549f2bfe909a26377703f671ff61
What operating system are you using?
macOS
What database engines are you using?
MySQL
What type of code are you generating?
Go

This is still an issue in v1.18.0: https://play.sqlc.dev/p/3931aa6d071068031e5eb03f4e40bd474d22afb2e47aabe0c34e68101e76d2f1.
Adding support for CAST seems like an important thing to do as well, so I'll reopen that issue.

It didn't work for my actual use case, but I noticed that in a simple use case doing a sub-select sometimes(?) makes sqlc figure out the correct type.
select id from (select min(id) from authors) as min_author;
https://play.sqlc.dev/p/e4b7f02a9c2ab5a4cea69f216758eb0d0a9ba42576804548e4f45b8c47e79910

@kyleconroy The same is true for lead() function. Even though I could cast it to, let's say smallint, it is not nullable.


Добавил ссылки в футер Bank dashboard + Comparsion

Pull request template
Checklist

[x] I have read the CONTRIBUTING guide
[x] branch rebased on develop
[x] styleguide check npm run validate
[x] good naming
[x] keep simple
[x] video or screenshot attached
[ ] testing instruction attached
[x] check your PR once again

Description
https://github.com/swaponline/swap.react/issues/1842
Video or screenshot

What and how to test

лайтнинг еще


Keybinding Ctrl+T provides empty result

Category

[ ] fzf binary
[ ] fzf-tmux script
[X] Key bindings
[ ] Completion
[ ] Vim
[ ] Neovim
[ ] Etc.

OS

[ ] Linux
[ ] Mac OS X
[ ] Windows
[ ] Windows Subsystem for Linux
[ ] Etc.

Shell

[ ] bash
[ ] zsh
[ ] fish

I just tried out fzf today (I like the idea!), however when hitting ^T in zsh I get the fzf view but with an empty result (0/0). Invoking $> fzf directly works as expected. I reinstalled (several times) with  git clone and install, and also by the fzf package on ArchLinux. I get the same issues on a Debian system. Could you tell me what I'm doing wrong or how can I debug this problem?

CTRL-T by default uses the following command to populate the list. Does it work?
command find -L . \( -path '*/\\.*' -o -fstype 'devfs' -o -fstype 'devtmpfs' -o -fstype 'proc' \) -prune \
    -o -type f -print \
    -o -type d -print \
    -o -type l -print 2> /dev/null | sed 1d | cut -b3-

No that's just an empty output in zsh.

It is a valid command on zsh (works fine for me), so you'll have to figure out why the command does not give you proper result.


config.Duration Unmarshal is error with koanf

Code:
func TestDuration_Unmarshal(t *testing.T) {
  type d struct {
    D Duration `json:"d" yaml:"d"`
  }

  val := "d: 1m5s\n"
  expected := d{Duration{5*time.Second + time.Minute}}

  k := koanf.New(".")
  k.Load(rawbytes.Provider([]byte(val)), yaml.Parser())

  r := d{}
  err := k.Unmarshal("", &r)
  assert.NoError(t, err)
}

Received error:
* 'D' expected a map, got 'string'

Can you submit a PR for this and include a testcase?

Yes, I'm finishing it.


more command doesn't advance to the next screen of text if I press spacebar

Windows Terminal version
1.18.902.0
Windows build number
10.0.23432.1000
Other Software
I tested this in cmd and PowerShell (version info below):
Name              : Microsoft.PowerShell
Publisher         : CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US
Architecture      : X64
ResourceId        :
Version           : <IP_ADDRESS>

Steps to reproduce

Within cmd.exe or pwsh.exe, and with a file that has at least a 'screenful' of text (e.g., call it foo.txt), try using more foo.txt to view the file's contents, one screenful at a time.
After the first screenful is displayed, try pressing spacebar to advance to the next chunk.

Expected Behavior
The Terminal advances to the next page of text.
Actual Behavior
The Terminal remains at the current screen; I see the cursor flashing as normal. I also can't Ctrl+C out of this.
I don't see this behavior in retail Terminal (version 1.16.10262.0)- more behaves as I would expect there.

Aahhhh. This could be an OpenConsole crash? Can you check to see whether there's still an OpenConsole instance running for that terminal tab?
(The renderer is still working, evidenced by the cursor flashing.)
/cc @lhecker for potential buffer impact

Thanks for taking a look! OpenConsole is still running per Task Manager.

I am hitting this issue as well, 100% consistent repro. Pressing ctrl+break gets me 'unstuck' but all other key presses seem to be ignored.

I wonder if this is from the linefeed changes in #14874

This also happens in OpenConsole...!

Broken in a build made on 2023 day 81.
Works on 2023 33.
Broken on 2023 62.

@lhecker regressed in #14745 (TranslateUnicodeToOem)
I bet it's reading input with ReadConsoleInputA! 😉


route_prefix is not dynamic in views

All URLs in the views a static at the moment (i.e. {{ url('admin/dashboard') }}), this doesn't allow us to change the route_prefix in the config file.
This should be changed to {{ url(config('backpack.base.route_prefix'),'dashboard') }}.
[Effects also all other projetcts, like base, etc.]

You're right. Fixed in 3.0.12. Thanks!


Fake

Lol in the video you turn on the program and show a recorded clip also that aim is bad even with this aimbot you gotta improve a lot

🤣

I stated that it was tested on pre-recorded clip. I posted the clip of the  testing process.
Even with cheats you need to have some skills so get good


Add _nixvimTests = false to flake.lib output

In my personal configuration, I rely on nixvim.lib.${system}.helpers to get access to things like mkRaw and toLuaObject for use in my extended lib.
With the changes made in 6d7e429537ae8143d8405c44a61479248776758c, nixvim.lib.${system}.helpers can no longer be accessed directly from the nixvim input as _nixvimTests is not provided as an input attribute, so loading helpers.nix fails.
This small change restores what I think is the intended behavior of this module.

I think this should be added in lib/dafault.nix, only for the helpers import

Yes, but utils.nix is only available through helpers


Corrected wrong enterprise configuration example

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@c3272b5). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #5888   +/-   ##
=========================================
  Coverage          ?   82.98%
  Complexity        ?    12119
=========================================
  Files             ?     1428
  Lines             ?    46475
  Branches          ?     5716
=========================================
  Hits              ?    38569
  Misses            ?     5230
  Partials          ?     2676

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 c3272b5...9777f36. Read the comment docs.


thisType versus this

https://github.com/Microsoft/TypeScript/issues/9063#issuecomment-225079380
Wanted to open the discussion to possibly allowing for something other than this for polymorphic typing.
Right now...
class A<T> {
    clone():this {
       return <any> new A<T>();  // without <any> it complains.
    }
   me():this {
      return this; // doesn't complain
   }
}

And it would be really nice to be able to:
class A<T> {
    map<TResult>(mapper: (v: T) => TResult): this<TResult>{
       // ...
    }
}

But your clone method doesn't return something of type this, it returns something of type A<T>. If you extended A in class B, clone wouldn't give you something with the members that B has.
A simple way to look at it is that the this type is supposed to model the type of the expression that you're calling a method off of.
As for the second thing, I think that's a duplicate of #6223.

It is, and the biggest challenge discussed in there is that if the arity of the generic arguments changes, how is this handled.


Azure fresh deploy: HTTP Error 503.12 - WebSocket request made to a site where WebSockets are disabled.

Apologies in advance if I've done something daft!
I used the deploy to Azure capability with the stable slackin release. I created a test token based on my user name.
It all spun up fine but when I submit an email I get a 503.12 error. The log stream indicates it some sort of interface failure.
Error and config details below. Any idea how to resolve the issue?
AppSettings
aspnet:PortableCompilationOutput = true
aspnet:PortableCompilationOutputSnapshotType = Microsoft.Web.Compilation.Snapshots.SnapshotHelper, Microsoft.Web.Compilation.Snapshots, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=XXXXXXXXXXXXXXXXX
aspnet:DisableFcnDaclRead = true
SCM_GIT_USERNAME = windowsazure
SCM_GIT_EMAIL = windowsazure
webpages:Version = <IP_ADDRESS>
webpages:Enabled = true
WEBSITE_SITE_NAME = satrdays
ScmType = ExternalGit
SLACK_API_TOKEN = xoxp-XXXXXXXXXXXXXXXXXXXX
WEBSITE_AUTH_ENABLED = False
WEBSITE_NODE_DEFAULT_VERSION = 5.1.1
SLACK_SUBDOMAIN = satrdays
WEBSITE_NPM_DEFAULT_VERSION = 3.3.12
command = bash scripts/azuredeploy.sh
SLACKIN_RELEASE = stable

HTTP Error 503.12 - WebSocket request made to a site where WebSockets are disabled.
The service is unavailable.

Most likely causes:
 An invalid identity in the application pool could cause this error. The application pool is no longer running because of configuration or reaching application failure limits. The concurrent application request limit was reached.

Things you can try:
 Check the event logs and the HTTP error logs for more information.

Detailed Error Information:

Module   WebSocketMonitoringModule
Notification   BeginRequest
Handler   ExtensionlessUrlHandler-Integrated-4.0
Error Code   0x00000000

Requested URL   https://satrdays:80/socket.io/?EIO=3&transport=websocket&sid=M9HQjyCKyUGf72cpAAAC
Physical Path   D:\home\site\wwwroot\socket.io
Logon Method   Not yet determined
Logon User   Not yet determined

Hm, web sockets should be enabled during the deployment, but maybe something messed up. Can you try going through your portal and enabling web sockets manually? There should be a toggle button somewhere in the configuration page:
https://azure.microsoft.com/en-us/blog/introduction-to-websockets-on-windows-azure-web-sites/

Hmm, now it's hanging but not erroring (post websockets toggle & app restart)

That sounds awfully similar to something I experienced a couple weeks ago. What do you see in the developer console/web app logs? If it's crashing due to a null ref at lib/assets/client.js, it's because of this:
https://github.com/rauchg/slackin/commit/d6d9db70e2cad93d39a3c9c5f2cff5c6a344e121

If thats a webapp, its just a switch away.


Text to shell experiments

Putting this up for review. Not ready to merge.
Browsing the Text_to_Shell.ipynb and see what you think of the changes. Note that it attempts to handle MacOS vs. Linux better. Also, I changed one of the examples to hopefully be portable across OSes. (The "Sort all files/directories in the current directory, but no subdirectories, according to modification time and print only the recent 7 of them" example. The others were okay.)

Let me know if you guys think this is okay. No reasonable criticism refused! 🤓
Once it's merged, I'll make parallel changes to the Exec notebook.

Thanks for your comments and a great start for these notebooks! I merged to main. I'm certainly open to additional changes...


using reactive in Dashboards in Shiny for Python throws error

When using this code to add reactivity when a button is clicked inside a Quarto document
@reactive.Effect
@reactive.event(input.reset)
def reset():

it throws an error
AttributeError: 'function' object has no attribute 'reset'

Quarto version: 1.4.530
Shiny for python version: <IP_ADDRESS>00

Is your code block intentionally missing a function body for def reset(): ? If so, I don't think we'd expect that to work anyway (you'd need to add pass or ... to get a function that does nothing)?

@cpsievert I believe this issue is specifically when Shiny is used in Quarto. (I think I know why it's not able to access input.reset at page render time.)

We will have a fix for this in Quarto soon. In the meantime, there is a workaround.
If this is the code:
@reactive.effect
@reactive.event(input.go)
def do_something():
    # Code that does stuff here ...

You can change it to this:
@reactive.effect
def do_something():
    input.go()
    with isolate():
        # Code that does stuff here ...

Using input.go() there causes do_something() to take a reactive dependency on it, so when the value of input.go() changes, it causes that effect to invalidate and re-execute. Then the with isolate() makes it so code inside that block does not cause an invalidation and re-execution.
In some cases it is also be useful to put the input.go() in a req(), as in:
@reactive.effect
def do_something():
    req(input.go())
    with isolate():
        # Code that does stuff here ...

This makes it so the if the value is falsy, (like None or 0), then it will stop execution there and not run the rest of the function.


Add a self cgroup reader

What does this PR do?
Add a self cgroup reader to allow gathering of self limits (memory, for instance)
Motivation
Additional Notes
Possible Drawbacks / Trade-offs
Describe how to test/QA your changes
Code is currently not used, cannot be tested.
Reviewer's Checklist

[x] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[x] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
[x] A release note has been added or the changelog/no-changelog label has been applied.
[x] Changed code has automated tests for its functionality.
[x] Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
[x] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
[x] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[x] If applicable, the need-change/operator and need-change/helm labels have been applied.
[x] If applicable, the config template has been updated.

Thank you for this PR. I have done some quick tests and it works as expected.


Update transpile() to convert BackendV1 inputs to BackendV2 with BackendV2Converter

Summary
This PR is a step forward in unifying the transpiler internals to use the target-base model, as specified in #9256. It's currently marked as WIP/on hold as it requires #11995 to be merged first for the scheduling tests to pass.
Details and comments
The conversion to the target-based model is hidden to the user but this PR includes a couple of small user-facing changes required for the pipeline to work:

a change in convert_to_target that now allows to process calibrations for instructions without registered InstructionProperties, instead of skipping these instructions (I believe that this was not the expected behavior)
a change in BackendV2Converter that now looks for num_qubits instead of the legacy n_qubits in the backend configuration
allowing backends with no description in BackendV2Converter

Note that BackendV2 does not have any internal tracking whether the backend is a simulator, so any "simulator-based test" now uses BasicSimulator directly (test/python/transpiler/test_1q.py).
In addition to this, some unit tests were using "loopholes" in the BackendV1 model that wouldn't (and shouldn't) translate to a target properly, such as giving a coupling map that didn't match the number of qubits of the backend (test/python/transpiler/test_preset_passmanagers.py) or an instruction schedule map that contained non registered basis gates (test/python/transpiler/test_pulse_gate_pass.py). These tests have been adapted to be coherent with the new model.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

26 of 26 (100.0%)  changed or added relevant lines in 2 files are covered.
31 unchanged lines in 4 files lost coverage.
Overall coverage decreased (-0.04%) to 89.269%

Files with Coverage Reduction
New Missed Lines
%

qiskit/transpiler/target.py
1
93.74%

crates/qasm2/src/lex.rs
4
90.68%

crates/qasm2/src/parse.rs
12
96.23%

qiskit/transpiler/passes/layout/dense_layout.py
14
81.37%

Totals

Change from base Build<PHONE_NUMBER>:
-0.04%

Covered Lines:
59107

Relevant Lines:
66212

💛  - Coveralls


Updated License Info in all Source Files

Standardized license text throughout the code base.
Added copyright info: <IBM, 2018>
There's no change in the code, but I re-tested everything nonetheless.

Thanks @salmanbaset

Thanks, @pnovotnyic ! I'll merge now.


Added g++ in captain definition. Commented the link for the debit card

can you make these changes for the main branch

so pull the master branch and then change it?

closing this pr since im pulling the master and changing the master to push to the master.


Add support for government-paid hospitals from NTUH Yunlin

Context
We are building out crawlers to crawl data from Yunlin Hospital.
This PR
Adds a scraper for hospital appointments from Yunlin Hospital.
Test Plan:

cd backend;
pipenv run python
from Parsers.ntu_yunlin import *
parse_ntu_yunlin_gov_paid()
AppointmentAvailability.UNAVAILABLE

Expect no appointments because currently there are none.

Ran Black locally with no errors. This GH Action is taking too long.


Make only builds oddit console

We just need to update the makefile for the daemon and url tracing work.
Basically... @kris-nova, can you please give the makefile a once over?

Yeah working on it now


Automating the task of sending messages via setting timer(Idea)

Sometimes, we need to send birthday wishes at a specific time but we forget to do so due to our hectic schedule. We can achieve this by setting the timer beforehand and the message will be send to that person at our desired time.

May I work on this?

@Rits1272  assigned


Error on sending email through Gmail SMTP

Mail Digest job fails with the following error:
end of file reached: /usr/lib/ruby/2.5.0/net/protocol.rb:189:in `rbuf_fill'

Full error log
Agent#3: Error sending digest mail to<EMAIL_ADDRESS>end of file reached
Agent#3: Exception during check. end of file reached: /usr/lib/ruby/2.5.0/net/protocol.rb:189:in `rbuf_fill'
/usr/lib/ruby/2.5.0/net/protocol.rb:157:in `readuntil'
/usr/lib/ruby/2.5.0/net/protocol.rb:167:in `readline'
/usr/lib/ruby/2.5.0/net/smtp.rb:950:in `recv_response'
/usr/lib/ruby/2.5.0/net/smtp.rb:935:in `block in getok'
/usr/lib/ruby/2.5.0/net/smtp.rb:960:in `critical'
/usr/lib/ruby/2.5.0/net/smtp.rb:933:in `getok'
/usr/lib/ruby/2.5.0/net/smtp.rb:826:in `helo'
/usr/lib/ruby/2.5.0/net/smtp.rb:600:in `do_helo'
/usr/lib/ruby/2.5.0/net/smtp.rb:554:in `do_start'
/usr/lib/ruby/2.5.0/net/smtp.rb:518:in `start'
/app/vendor/bundle/ruby/2.5.0/gems/mail-2.7.1/lib/mail/network/delivery_methods/smtp.rb:109:in `start_smtp_session'
/app/vendor/bundle/ruby/2.5.0/gems/mail-2.7.1/lib/mail/network/delivery_methods/smtp.rb:100:in `deliver!'
/app/vendor/bundle/ruby/2.5.0/gems/mail-2.7.1/lib/mail/message.rb:2159:in `do_delivery'
/app/vendor/bundle/ruby/2.5.0/gems/mail-2.7.1/lib/mail/message.rb:260:in `block in deliver'
/app/vendor/bundle/ruby/2.5.0/gems/actionmailer-<IP_ADDRESS>/lib/action_mailer/base.rb:560:in `block in deliver_mail'
/app/vendor/bundle/ruby/2.5.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications.rb:168:in `block in instrument'
/app/vendor/bundle/ruby/2.5.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications/instrumenter.rb:23:in `instrument'
/app/vendor/bundle/ruby/2.5.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications.rb:168:in `instrument'
/app/vendor/bundle/ruby/2.5.0/gems/actionmailer-<IP_ADDRESS>/lib/action_mailer/base.rb:558:in `deliver_mail'
/app/vendor/bundle/ruby/2.5.0/gems/mail-2.7.1/lib/mail/message.rb:260:in `deliver'
/app/vendor/bundle/ruby/2.5.0/gems/actionmailer-<IP_ADDRESS>/lib/action_mailer/message_delivery.rb:114:in `block in deliver_now'
/app/vendor/bundle/ruby/2.5.0/gems/actionmailer-<IP_ADDRESS>/lib/action_mailer/rescuable.rb:17:in `handle_exceptions'
/app/vendor/bundle/ruby/2.5.0/gems/actionmailer-<IP_ADDRESS>/lib/action_mailer/message_delivery.rb:113:in `deliver_now'
/app/app/models/agents/email_digest_agent.rb:61:in `block in check'
/app/app/models/agents/email_digest_agent.rb:52:in `each'
/app/app/models/agents/email_digest_agent.rb:52:in `check'
/app/app/jobs/agent_check_job.rb:7:in `perform'
/app/vendor/bundle/ruby/2.5.0/gems/activejob-<IP_ADDRESS>/lib/active_job/execution.rb:39:in `block in perform_now'
/app/vendor/bundle/ruby/2.5.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:109:in `block in run_callbacks'
/app/vendor/bundle/ruby/2.5.0/gems/i18n-1.6.0/lib/i18n.rb:297:in `with_locale'
/app/vendor/bundle/ruby/2.5.0/gems/activejob-<IP_ADDRESS>/lib/active_job/translation.rb:9:in `block (2 levels) in <module:Translation>'
/app/vendor/bundle/ruby/2.5.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:118:in `instance_exec'
/app/vendor/bundle/ruby/2.5.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:118:in `block in run_callbacks'
/app/vendor/bundle/ruby/2.5.0/gems/activejob-<IP_ADDRESS>/lib/active_job/logging.rb:26:in `block (4 levels) in <module:Logging>'
/app/vendor/bundle/ruby/2.5.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications.rb:168:in `block in instrument'
/app/vendor/bundle/ruby/2.5.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications/instrumenter.rb:23:in `instrument'
/app/vendor/bundle/ruby/2.5.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications.rb:168:in `instrument'
/app/vendor/bundle/ruby/2.5.0/gems/activejob-<IP_ADDRESS>/lib/active_job/logging.rb:25:in `block (3 levels) in <module:Logging>'
/app/vendor/bundle/ruby/2.5.0/gems/activejob-<IP_ADDRESS>/lib/active_job/logging.rb:46:in `block in tag_logger'
/app/vendor/bundle/ruby/2.5.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/tagged_logging.rb:71:in `block in tagged'
/app/vendor/bundle/ruby/2.5.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/tagged_logging.rb:28:in `tagged'
/app/vendor/bundle/ruby/2.5.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/tagged_logging.rb:71:in `tagged'
/app/vendor/bundle/ruby/2.5.0/gems/activejob-<IP_ADDRESS>/lib/active_job/logging.rb:46:in `tag_logger'
/app/vendor/bundle/ruby/2.5.0/gems/activejob-<IP_ADDRESS>/lib/active_job/logging.rb:22:in `block (2 levels) in <module:Logging>'
/app/vendor/bundle/ruby/2.5.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:118:in `instance_exec'
/app/vendor/bundle/ruby/2.5.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:118:in `block in run_callbacks'
/app/vendor/bundle/ruby/2.5.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:136:in `run_callbacks'
/app/vendor/bundle/ruby/2.5.0/gems/activejob-<IP_ADDRESS>/lib/active_job/execution.rb:38:in `perform_now'
/app/vendor/bundle/ruby/2.5.0/gems/activejob-<IP_ADDRESS>/lib/active_job/execution.rb:24:in `block in execute'
/app/vendor/bundle/ruby/2.5.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:109:in `block in run_callbacks'
/app/vendor/bundle/ruby/2.5.0/gems/activejob-<IP_ADDRESS>/lib/active_job/railtie.rb:28:in `block (4 levels) in <class:Railtie>'
/app/vendor/bundle/ruby/2.5.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/execution_wrapper.rb:87:in `wrap'
/app/vendor/bundle/ruby/2.5.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/reloader.rb:73:in `block in wrap'
/app/vendor/bundle/ruby/2.5.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/execution_wrapper.rb:87:in `wrap'
/app/vendor/bundle/ruby/2.5.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/reloader.rb:72:in `wrap'
/app/vendor/bundle/ruby/2.5.0/gems/activejob-<IP_ADDRESS>/lib/active_job/railtie.rb:27:in `block (3 levels) in <class:Railtie>'
/app/vendor/bundle/ruby/2.5.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:118:in `instance_exec'
/app/vendor/bundle/ruby/2.5.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:118:in `block in run_callbacks'
/app/vendor/bundle/ruby/2.5.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:136:in `run_callbacks'
/app/vendor/bundle/ruby/2.5.0/gems/activejob-<IP_ADDRESS>/lib/active_job/execution.rb:22:in `execute'
/app/vendor/bundle/ruby/2.5.0/gems/activejob-<IP_ADDRESS>/lib/active_job/queue_adapters/delayed_job_adapter.rb:42:in `perform'
/app/vendor/bundle/ruby/2.5.0/gems/delayed_job-4.1.5/lib/delayed/backend/base.rb:81:in `block in invoke_job'
/app/vendor/bundle/ruby/2.5.0/gems/delayed_job-4.1.5/lib/delayed/lifecycle.rb:61:in `block in initialize'
/app/vendor/bundle/ruby/2.5.0/gems/delayed_job-4.1.5/lib/delayed/lifecycle.rb:66:in `execute'
/app/vendor/bundle/ruby/2.5.0/gems/delayed_job-4.1.5/lib/delayed/lifecycle.rb:40:in `run_callbacks'
/app/vendor/bundle/ruby/2.5.0/gems/delayed_job-4.1.5/lib/delayed/backend/base.rb:78:in `invoke_job'
/app/vendor/bundle/ruby/2.5.0/gems/delayed_job-4.1.5/lib/delayed/worker.rb:230:in `block (2 levels) in run'
/usr/lib/ruby/2.5.0/timeout.rb:93:in `block in timeout'
/usr/lib/ruby/2.5.0/timeout.rb:103:in `timeout'
/app/vendor/bundle/ruby/2.5.0/gems/delayed_job-4.1.5/lib/delayed/worker.rb:230:in `block in run'
/usr/lib/ruby/2.5.0/benchmark.rb:308:in `realtime'
/app/vendor/bundle/ruby/2.5.0/gems/delayed_job-4.1.5/lib/delayed/worker.rb:229:in `run'
/app/vendor/bundle/ruby/2.5.0/gems/delayed_job-4.1.5/lib/delayed/worker.rb:312:in `block in reserve_and_run_one_job'
/app/vendor/bundle/ruby/2.5.0/gems/delayed_job-4.1.5/lib/delayed/lifecycle.rb:61:in `block in initialize'
/app/vendor/bundle/ruby/2.5.0/gems/delayed_job-4.1.5/lib/delayed/lifecycle.rb:66:in `execute'
/app/vendor/bundle/ruby/2.5.0/gems/delayed_job-4.1.5/lib/delayed/lifecycle.rb:40:in `run_callbacks'
/app/vendor/bundle/ruby/2.5.0/gems/delayed_job-4.1.5/lib/delayed/worker.rb:312:in `reserve_and_run_one_job'
/app/vendor/bundle/ruby/2.5.0/gems/delayed_job-4.1.5/lib/delayed/worker.rb:213:in `block in work_off'
/app/vendor/bundle/ruby/2.5.0/gems/delayed_job-4.1.5/lib/delayed/worker.rb:212:in `times'
/app/vendor/bundle/ruby/2.5.0/gems/delayed_job-4.1.5/lib/delayed/worker.rb:212:in `work_off'
/app/vendor/bundle/ruby/2.5.0/gems/delayed_job-4.1.5/lib/delayed/worker.rb:175:in `block (4 levels) in start'
/usr/lib/ruby/2.5.0/benchmark.rb:308:in `realtime'
/app/vendor/bundle/ruby/2.5.0/gems/delayed_job-4.1.5/lib/delayed/worker.rb:174:in `block (3 levels) in start'
/app/vendor/bundle/ruby/2.5.0/gems/delayed_job-4.1.5/lib/delayed/lifecycle.rb:61:in `block in initialize'
/app/vendor/bundle/ruby/2.5.0/gems/delayed_job-4.1.5/lib/delayed/lifecycle.rb:66:in `execute'
/app/vendor/bundle/ruby/2.5.0/gems/delayed_job-4.1.5/lib/delayed/lifecycle.rb:40:in `run_callbacks'
/app/vendor/bundle/ruby/2.5.0/gems/delayed_job-4.1.5/lib/delayed/worker.rb:173:in `block (2 levels) in start'
/app/vendor/bundle/ruby/2.5.0/gems/delayed_job-4.1.5/lib/delayed/worker.rb:172:in `loop'
/app/vendor/bundle/ruby/2.5.0/gems/delayed_job-4.1.5/lib/delayed/worker.rb:172:in `block in start'
/app/vendor/bundle/ruby/2.5.0/gems/delayed_job-4.1.5/lib/delayed/plugins/clear_locks.rb:7:in `block (2 levels) in <class:ClearLocks>'
/app/vendor/bundle/ruby/2.5.0/gems/delayed_job-4.1.5/lib/delayed/lifecycle.rb:79:in `block (2 levels) in add'
/app/vendor/bundle/ruby/2.5.0/gems/delayed_job-4.1.5/lib/delayed/lifecycle.rb:61:in `block in initialize'
/app/vendor/bundle/ruby/2.5.0/gems/delayed_job-4.1.5/lib/delayed/lifecycle.rb:79:in `block in add'
/app/vendor/bundle/ruby/2.5.0/gems/delayed_job-4.1.5/lib/delayed/lifecycle.rb:66:in `execute'
/app/vendor/bundle/ruby/2.5.0/gems/delayed_job-4.1.5/lib/delayed/lifecycle.rb:40:in `run_callbacks'
/app/vendor/bundle/ruby/2.5.0/gems/delayed_job-4.1.5/lib/delayed/worker.rb:171:in `start'
/app/lib/delayed_job_worker.rb:6:in `run'
/app/app/concerns/long_runnable.rb:71:in `block in run!'

My configuration looks like following:
<EMAIL_ADDRESS>SMTP_DOMAIN=huginn.johndoe.com
<EMAIL_ADDRESS>SMTP_PASSWORD=secret
SMTP_SERVER=smtp.gmail.com
SMTP_PORT=587
SMTP_AUTHENTICATION=plain
SMTP_ENABLE_STARTTLS_AUTO=true
SEND_EMAIL_IN_DEVELOPMENT=true

Huginn is running as docker container (huginn/huginn-single-process).
To debug this, I logged into worker container and run
openssl s_client -connect smtp.gmail.com:587 -starttls smtp -crlf

and executed the following commands with appropriate arguments:
- helo
- auth plain
- mail from
- rcpt to
- data
- <enter email data>
- <Ctrl-D>

And I received that email.
Any idea how to make it work?

Silly me!
I had set SMTP_DOMAIN incorrectly: SMTP_DOMAIN=huginn.${DOMAIN}. The envvar was not substituted.


Remove some redundant instance constraints

A few redundant instance constraints have crept in. Remove them.
Fixes #nnnn
Scope:
Estimate:

Review checklist
The author performs the actions on the checklist. The reviewer evaluates the work and checks the boxes as they are completed.

[ ] Summary. Write a summary of the changes. Explain what you did to fix the issue, and why you did it. Present the changes in a logical order. Instead of writing a summary in the pull request, you may push a clean Git history.
[ ] Documentation. Write documentation for new functions. Update documentation for functions that changed, or complete documentation where it is missing.
[ ] Tests. Write unit tests for every change. Write the unit tests that were missing before the changes. Include any examples from the reported issue as integration tests.
[ ] Clean up. The changes are already clean. Clean up anything near the changes that you noticed while working. This does not mean only spatially near the changes, but logically near: any code that interacts with the changes!

I'll try opening a PR against a branch not in a fork. Weird failure....


Reformatting aws-ec2 in docs !!

As I was browsing through docs, I came across aws-ec2, in which all the installation of various dev stack is shown as follows:-
Install docker
Install docker-compose
Install Go
Install Kind
Install kubectl
Install helm
Suggestion to improve the same
What we can do is we can add relevant images and CLI commands to make the documentation even more impressive.
Like for example: In Docker, we can have an image, and for kind,kubectl, and helm we can have CLI commands so that a user can directly copy the very same command which ultimately reduces the hassle of searching it up.

Sounds good! All good additions

/assign


How to disable animation when changing fitBounds()?

I have tried movingMethod="jumpTo" without success. When I change fitBounds() rect, there is a long "flyTo" type animation that I don't need.

fitBoundsOptions={{duration:0}}


Bug: Ensure that layouts are loaded from the correct location

Seems like the full tests was lacking, so the file path somehow ended up being wrong.
This issue prevents validation and submission of apps, when RemoveHiddenDataPreview is active, so it would be nice if a new version can be made available on nuget pretty quick.

I will merge it and release v7.2.0-preview.5 asap


kubernetes upgrade fails when enabling EKCO with internal load balancer.

What type of PR is this?
When we try to upgrade both kubernetes and EKCO versions in the same spec along with enabling internal load balancer feature the upgrade fails as the install.sh script will try check the api server endpoint of the internal load balancer (localhost:6444) which has not been deployed yet.
Please choose from one of the following:
type::bug
What this PR does / why we need it:
With this change we fetch the api server endpoint from the cluster and performing status checks on it during the upgrade.  So the upgrade of kubernetes doesn't fail.
Which issue(s) this PR fixes:
Fixes # https://github.com/replicated-collab/forwardnetworks-kots/issues/57
Does this PR introduce a user-facing change?
None
Does this PR require documentation?
NONE

@pavanreddymaley thank you for the PR. Would you also write down the steps to reproduce this. I can make sure it gets tested and merged.

The main use case is related to upgrading the cluster from non-ha to HA using EKCO load balancer.
Steps to re-produce:

Deploy a 3 node non-HA cluster with older version of k8s (ex: 1.19,1.20).
Upgrade the k8s cluster along with EKCO enabling internal load balancer.
Details of spec used for testing: https://docs.google.com/document/d/1O4jafOiQXOB0qH4UmXdY8ApkI6YfdE8XLT2enTIf7fU/edit

Regarding : existing_kubernetes_api_address
During the kubernetes upgrade we will verify if the kubernetes api server is healthy and in the above scenario we are enabling the EKCO internal load balancer and so the function kubernetes_api_address returns localhost:6444 and the health check will fail as we haven't configured that yet. The internal load balancer will be configured after the kubernetes upgrade in the init() function.

[sc-42741]

Merging this and will kick of tests since we are unable to for external contributors at the moment.


Source is included in NPM releases

The source code is currently included in every release. I think that's generally not a good idea, but it's also causing some code navigation issues in typescript. When you click to go to implementation in vs code, it goes to the source file instead of the typescript definition. However, the internal vs-code tslint is taking into consideration the definition files. As a result, when you upgrade the version, you have no easy way to refresh ts-lint errors other than restarting typescript complication service.
Generally speaking, I think the source files should be removed anyway even if it wasn't causing issues.

Maybe this could be done during #734

personally i like when source code is included in the npm package, its also considered a good practice by some. Also in the future, people might want to use the untranspiled source code (i hope for a future where we can just publish source code instead of dealing with this transpilation mess)

I don't really have a strong preference, but imho source code belongs in the repo, properly tagged, it should be fairly easy to navigate. What people don't realize is the amount of crap you would download with each NPM package if it contains all source code. Millions of files that are basically useless, just taking up space. This is more apparent with NPM than with any other packager. NPM you can easily add one package that adds 10 more each of them 10 more. If all of them are <10 files, no big deal. But you see my point. Node_modules on most of my projects are already well over 300mb. And doing a delete or fresh install takes ages. Also, transpilation/compilation would take ages. There's a reason for compiled resources I think. Anyways, one way or another, at some point, we should probably at least look at this code navigation issue. Cause that's pretty annoying regardless of preference in terms of packaging.

Trying version 0.22.0-rc.2 results in my app not compiling since it tries to compile the source code as well which has typescript errors based off of my typescript configs. For this reason alone, removing them from the packed remo with .npmignore file is a good idea.

@seang96 can you try 0.21.0 ? i probably just pushed a broken version (i am about to fix).
can you show your error? i am not sure that it is because of included source code.

@PeterKottas @seang96 will add it to npmignore, so you can check if it helps

@seang96 This seems like an error on your end. Your build system should ignore node_modules when compiling. As long as the compiled code is there (which should be pretty straight forward to verify), it should resolve to that. AFK now boys, please check if the new version builds on your systems. Cheers!

i close this as it is now on npmignore in latest versions


hlint cannot lint haskell file

I set the haskell.hlint.executablePath to "~/.cabal/bin/hlint", after restart vscode and open any haskell source code, vscode still report cannot find hlint in my settings path.
VSCode setting:

Error messages:

Any fix for this? I'm having this issue too.

The path needs to be absolute instead of relative

For me it works if the hlint is being in PATH, and "haskell.hlint.executablePath" is set to "hlint"


pre-commit hook removes plugins from baseline (on version 0.8.8)

$ tox -e pre-commit -- run detect-secrets --all-files
[detect-secrets] Detect secrets..........................................Failed
hookid: detect-secrets

Files were modified by this hook. Additional output:

Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.
Your baseline file (.secrets.baseline) is unstaged.
`git add .secrets.baseline` to fix this.

ERROR: InvocationError: '/nail/home/louist/pg/puppet/.tox/pre-commit/bin/pre-commit run detect-secrets --verbose --all-files'
________________________________________________________________________________________________________________________________________________________ summary _________________________________________________________________________________________________________________________________________________________
ERROR:   pre-commit: commands failed

diff --git a/.secrets.baseline b/.secrets.baseline
index 70a2e0c..37fd650 100644
--- a/.secrets.baseline
+++ b/.secrets.baseline
@@ -1,19 +1,7 @@
 {
   "exclude_regex": "^(\\.git|venv|vendor|secrets)",
-  "generated_at": "2018-06-13T09:34:56Z",
-  "plugins_used": [
-    {
-      "limit": 4.5,
-      "name": "Base64HighEntropyString"
-    },
-    {
-      "limit": 3,
-      "name": "HexHighEntropyString"
-    },
-    {
-      "name": "PrivateKeyDetector"
-    }
-  ],
+  "generated_at": "2018-06-18T09:46:46Z",
+  "plugins_used": [],
   "results": {
     "Puppetfile": [
       {

So this is a little worse than I initially thought, since IIRC the pre-commit hook will remove the plugins as soon as it auto-updates the baseline.
The Why
So in secrets_collection.py we load the baseline in, but don't take plugins into account. We need to turn these into a proper tuple, the way initialize_plugins turns args.plugins into a proper tuple.
However, we cannot just call initialize_plugins as that expects e.g.
        assert args.plugins == {
            'HexHighEntropyString': {
                'hex_limit': [3],
            },
            'Base64HighEntropyString': {
                'base64_limit': [4.5],
            },
            'PrivateKeyDetector': {},
        }

Not a list we have in _load_baseline_from_dict:
[
    {
        'limit': 4.5,
        'name': 'Base64HighEntropyString'
    },
    {
        'limit': 3,
        'name': 'HexHighEntropyString'
    },
    {
        'name': 'PrivateKeyDetector'
    }
]

The Solution
So I tried to see if calling _initialize_plugin direct, would help, but since it takes *args instead of **kwargs, I could have hard-coded passing in limit from the dict, but that's bad and hard-coded.
Then I wondered how _initialize_plugin is called in the first place, from initialize_plugins:
        args = []
        if init_values:
            key = list(init_values.keys())[0]
            args.append(init_values[key][0])

        output.append(_initialize_plugin(plugin_name, *args))

This is bad b/c we're depending on the order of a .keys() to pass in *args, I think we should only be using **kwargs.
After it is fixed to use **kwargs, I can call [_initialize_plugin](https://github.com/Yelp/detect-secrets/blob/e15d0a99697900273abe96ca1387446f22c439dd/detect_secrets/plugins/__init__.py#L123-L138) directly. (From a wrapper function in plugins/__init__.py of course, not from secrets_collection.py. Though we might want to make a different file in plugins/, as putting a lot of code in __init__.py's is generally frowned upon.)

Fixed 👍 🎈


Use claim id in related search instead of title, improve results

This would fix slowness issues with long titles
Also, remove any common words from related search like an/the/and: https://lbry.tv/@BrendonBrewer:3/angry-swan:3

also:

[ ] use tag data to improve results
[ ] try to filter files with the same title from showing multiple times


official ACME observational data repository

We need an official observational data repository for ACME, and datasets in this repository need to be checked/fixed for CF-compliance and functionality with metrics code.  An initial version of a repository exists on rhea, but it is currently not clear (to the atmosphere team) if someone has responsibility for maintaining it moving forward, if it has found a permanent home, etc..

Massage all datasets used by ACME to be CF-compliant (including time axis!)
Available to everyone in ACME in a "comprehensive" version and a "minimal" version ("minimal" fields required to run "top ten" collections)

A few plots still fail due to non-CF-compliant data sets (usually the time axis is incorrectly specified).  We suggest that rather than adding more special cases to the code, we make our own CF-compliant versions of these files and store them in the "official" obs repository.
(I'm not sure whether this is the best place to track this issue, but it is important and needs a home somewhere)

Agreed!  For the ACME project, @isubsmith and I threw all obs sets we knew of into a directory on Lustre.  Instead, we need a collection of data which (1) can be redistributed to the public without restriction, (2) is good enough to be useful to climate scientists, and (3) is a set of NetCDF files conforming to the CF Conventions, and preferably a bit more.   I would also like to see (4) has been updated recently to reflect the latest available observations.
Criteria (2) and (4) require some climate scientists to get involved.  Criterion (3) requires a suitable computer scientist, such as me.

Creating the official ACME obs repo is a big task, requires many people, and hasn't even gotten started.  As an interim solution, some of us should create an un-offical non-ACME obs repo.   Also, the documentation may as well include NCAR's instructions for getting their obs sets:
svn export https://svn-ccsm-release.cgd.ucar.edu/model_diagnostics/atm/cam/obs_data_20140804/

Hi Jeff, I guess the unofficial interim solution is the directory you and Brian set up on rhea.  Thanks for adding the svn instructions here.

@painter1 you should talk to @gleckler1 and @durack1 pcmdi is way ahead of acme on this.

Just updating this to note that a discussion on this is ongoing in Confluence:
https://acme-climate.atlassian.net/wiki/display/WORKFLOW/Requirements+for+Observational+Datasets+to+be+used+for+ACME+science

I have migrated copies of all the datasets we had in obs_data into the ACME inputdata repository, which I believe could become a permanent home:
https://acme-svn2.ornl.gov/acme-repo/acme/obs_for_diagnostics/

I think the next step is for us to identify an individual who will take responsibility for being a gatekeeper for new datasets to be submitted to the repository.

This supplies all the obs sets which are built in to the present diagnostics, so I am closing this issue.
In the future we will have to find a way to supply obs sets to non-ACME users, and a way to automatically download the data.  But those are different projects.


Ensure remove link button is show in text editor (14.1 Backport)

Backport of #1160
Do not depend on link dialog and link button to be siblings in the
DOM. Instead of using an adjacent CSS selector, explicitly set a CSS
class when the dialog is shown.
REDMINE-16728

Coverage remained the same at 99.299% when pulling 0818c5c3347b1430154c5049d7280f01df372bd4 on tf:fix-link-dialog-backport into 0560252f69f731685993ddd5bddbcf275cfab2f1 on codevise:master.


Get external link and scroll to element

This does work, not sure it is perfect.
Instead of having to catch the exact time of load finish of the pages, the function waits 100ms before scrolling.
for this instance, i think this is appropiate, and easier to deal with.
Tested this with 90+ page doc, works fine. Unsetting smooth scroll as it triggers lots of page loads.
Closes #2820 and duplicate #3505
to test, try any brew url + #id

Now also works with page ids

How should this be tested?

I'm guessing you will have a lot to say about the scrolling methods, cannot remember why i did it this way.

With the removal of PPR and globally unique IDs, could we skip scrolling to page and go directly to the element instead?

With the removal of PPR and globally unique IDs, could we skip scrolling to page and go directly to the element instead?

We could, but I think scrolling to the page is the better idea and is consistent with the various link jumps we do

the various link jumps we do

...which is also behaviour that can now be reconsidered in the light of full document rendering and globally unique IDs.
That's not to say that the current behaviour is not necessarily desirous, but rather that until now, we haven't actually had the option to consider anything else.
It might be out of scope for this PR, but it's probably worth considering at some stage.

Do you mean rendering the iframe directly at that page?

.....

This PR is supposed to handle only url navigation into the page so that would make sense, specially with smooth scrolling disabled to prevent unnecessary renders. If you can point in the right direction i can try.

I firmly believe the current way is the right way. Stay page oriented.

This could probably use the newest scrolling functions

Blocked by #3484
There is some rearranging of the scrolling logic there that will interfere with this. When I get that one merged it should be more clear what changes might be needed for this PR.

Studying this one a bit, isMounted is set to true the same time the initial page rendering is started, which means the iFrame is mounted but the pages inside might not actually be done rendering. I wonder if we can add a new state for "firstRenderComplete" or something, that gets set when renderPages() completes for the first time, and use that as the check to wait for scrolling.

it seems rendering the pages is also waiting for isMounted to be true

Aaah that explains it then...
I'll try, not sure

Maybe set up a MutationObserver?
    const hash = window.location.hash;
    if (hash && iframeDoc) {
      const anchor = iframeDoc.querySelector(hash);

      if (anchor) {
        anchor.scrollIntoView();
      } else {
        // Use MutationObserver to wait for the element if it's not immediately available
        const observer = new MutationObserver((mutations, obs) => {
          const anchorElement = iframeDoc.querySelector(hash);
          if (anchorElement) {
            anchorElement.scrollIntoView();
            obs.disconnect(); // Stop observing once the element is found
          }
        });

        observer.observe(iframeDoc, {
          childList: true,
          subtree: true,
        });

Maybe set up a MutationObserver?
    const hash = window.location.hash;
    if (hash && iframeDoc) {
      const anchor = iframeDoc.querySelector(hash);

      if (anchor) {
        anchor.scrollIntoView();
      } else {
        // Use MutationObserver to wait for the element if it's not immediately available
        const observer = new MutationObserver((mutations, obs) => {
          const anchorElement = iframeDoc.querySelector(hash);
          if (anchorElement) {
            anchorElement.scrollIntoView();
            obs.disconnect(); // Stop observing once the element is found
          }
        });

        observer.observe(iframeDoc, {
          childList: true,
          subtree: true,
        });

Won't this trigger for every rerender of the preview?

Won't this trigger for every rerender of the preview?

ahem ..

            obs.disconnect(); // Stop observing once the element is found

So .. on page load it looks for the element corresponding to window.location.hash. If that target does not yet exist, then the MutationObserver is created. When it gets triggered it scrolls to it, and then deletes the observer. Subsequent rerenders are not observed, and so no further scrolling occurs.

This should be ready for merge

Ok, just cleaned up a bit. Merging now!
Thanks @5e-Cleric ! 💯 ⭐ 🎉


Purging of inputs and outputs don't work on forwarder

Setting purge_inputs and purge_outputs to true is not actually purging unmanaged settings in those files.  I have reproduced this on our forwarder on windows.  We still need to investigate if this is O/S specific and also what all purging is actually broken and fix it.

I'm trying to purge outputs.conf on linux and it is not working. Perhaps my understanding is incorrect but i would like my /etc/system/local/outputs.conf to be blank as this is controlled from our splunk admin server and the having two settings is causing the service to continuously restart

Guys, Hi. I am observing the same with "purge_inputs". Found some old traces on the subject @ https://tickets.puppetlabs.com/browse/MODULES-3520. Has this been progressed and fixed since?
Thanks in advance.
Regards, Andrei

@chiriaev Thanks for finding that ticket.

@vandelin586 this is old but in case you needed a work around you can do this:
  $hash = {
    'nothing' => {
      section => '',
      setting => '#PuppetManaged',
      value   => 'nothing',
      tag     => 'splunk_forwarder',
    }
  }

  class { '::splunk::forwarder':
    package_ensure   => '7.0.0',
    package_source   => 'http://<REMOVED>/artifactory/splunk/splunkforwarder-7.0.0.rpm',
    purge_outputs    => true,
    purge_inputs     => true,
    forwarder_output => $hash,
    forwarder_input  => $hash,
  }

Once thats added you will need to manually purge the files since purge does not currently work:
rm -f /opt/splunkforwarder/etc/system/local/outputs.conf; rm -f /opt/splunkforwarder/etc/system/local/inputs.conf
Run puppet, and the end result looks like this:
[root@<REMOVED>]# cat /opt/splunkforwarder/etc/system/local/outputs.conf
#PuppetManaged=nothing
[root@<REMOVED>]# cat /opt/splunkforwarder/etc/system/local/inputs.conf
#PuppetManaged=nothing
[root@<REMOVED>]#

Caused by https://github.com/voxpupuli/puppet-splunk/pull/87


ci: add github action to turn TODO comments into github issues

Rebase #2132

This will create a lot of issue, let's wait on merging this.


Refactor project definition to move projects from the 'targets' field…

Depends on earlier PR, https://github.com/twitter/focus/pull/26

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


go-cmdtest does not work on Windows anymore

https://github.com/google/go-cmdtest/pull/4
started using github.com/google/renameio to rename files.
https://github.com/google/renameio#windows-support indicates that renameio doesn't work on Windows.
Therefore, that commit breaks any use of this package on Windows.
@jba
@gbrlsnchs
Thoughts?

We should use build tags so Windows uses the original rename code.

We should use build tags so Windows uses the original rename code.

I agree with this solution.

I can do the work but have no way to test on Windows. Robert, can you verify the fix?

(I'm assuming you're reporting it because you ran into it.)

I ran into this because gocloud uses go-cmdtest, and includes a Windows run in its Travis configuration. So, I can verify a committed fix I think, but not easily a PR.

Fixed by #13.


[Bug] Incorrect YAML syntax

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the issue
test instead of tests at:

https://github.com/fivetran/dbt_twilio/blob/26ca6ca19baa602b551147778099b7e9e6b9d9bb/models/twilio.yml#L51
https://github.com/fivetran/dbt_twilio/blob/26ca6ca19baa602b551147778099b7e9e6b9d9bb/models/twilio.yml#L117

Relevant error log or model output
No response
Expected behavior
N/A
dbt Project configurations
N/A
Package versions
N/A
What database are you using dbt with?
snowflake
dbt Version
N/A
Additional Context
FYI @fivetran-reneeli
Are you willing to open a PR to help address this issue?

[X] Yes.
[ ] Yes, but I will need assistance and will schedule time during our office hours for guidance
[ ] No.

hey @raphaelvarieras great catch, this is certainly something we wanna fix. On your end, is this causing any failure, or are the relevant models just not being tested by dbt test?
If you're still open to contributing the fix for this, this would speed things up as we would prioritize reviewing any PR asap. If not, we will slate this into an upcoming sprint to work on

Ok, I'll prepare a PR some time soon.

@fivetran-jamie ready for your 👀 !

in v0.2.0 which is now live!


Invalid HTTP response sent

Just did a fresh install with ocaml 4.07. Tried the sample server in README on both windows and linux and got the same error:
ERR_INVALID_HTTP_RESPONSE
The `GET match does not even trigger.

@iams-wu I'd like to help but there isn't enough information in this ticket to understand what's going on. How are you issuing a request to the server you just built?

@iams-wu I'm going to need more information in order to take a look at your problem. This issue is at risk of being closed within the next week if that's not the case.


Unicode non-characters

Problem or new feature
In Language/operators the following code is given in the section on Chaining Binary Precedence.
=head2 infix C«===», infix C«⩶»

    sub infix:<===>(Any, Any)

The character is used a couple of times. It seems to be coded as %E2%A9%B5 which is out of bounds.
This seems to be a mistake.
Suggestions
If applicable, suggest something towards the solution.

I think it should be https://www.fileformat.info/info/unicode/char/2a76/index.htm (%E2%A9%B6, note the 6), the tripple equals sign.
Interestingly: https://www.fileformat.info/info/unicode/char/2a75/index.htm (%E2%A9%B5, note the 5) is the double equals sign.

In my browser I am getting an error glyph when I type ⩶ (<shift><ctrl>2a76). Checking on the links above, I get the same error.
I have tried installing Cambria, which is given above as a font that handles this Unicode glyph. But I still get the error glyph.
I originally thought this was an error in the Rakudoc source. Now I think it is a visualisation error. I have not solved it for myself yet.
Any feedback would be welcome.

raku -e 'say "\x2a76  ", "\x2a76".uninames'
⩶  (THREE CONSECUTIVE EQUALS SIGNS)

That renders for me on MacOS Mojave... so I'm not sure why that wouldn't render for you

This needs more work on my part. Now I am aware my browser is not rendering properly, I'll follow up.
Closing out this issue as not relevant to this Raku/doc source.

FWIW, it is usually connected to the level of Unicode support in the operating system.  You may need to do an OS upgrade (or some OS module)


Set seed for nextpnr

I have found that nextpnr has an option to set a seed for random number generator. I hope that this will do our synthesis results more stable.

Job to run synthesis with the new option:
https://github.com/kuznia-rdzeni/coreblocks/actions/runs/5846546722

Unfortunately it seems that nextpnr runs with fixed seed by default, until --randomize-seed, or --seed option is passed, and none of those was defined in our pipeline call.
See: https://github.com/YosysHQ/nextpnr/blob/679b662a2b870ef49779fd0c3698e6e9a356d9f0/common/kernel/command.cc#L264C5-L264C5 , https://github.com/YosysHQ/nextpnr/blob/679b662a2b870ef49779fd0c3698e6e9a356d9f0/common/kernel/deterministic_rng.h#L37C5-L37C21 , https://github.com/search?q=repo%3AYosysHQ%2Fnextpnr rngseed&type=code

Yes, you have right.


Tanya's content and Ron's feedback

Incorporating Ron's feedback. More (many) PRs to come

@merriemcgaw,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

Thanks for making the additional changes, @merriemcgaw. I think this looks ready to merge.  Should we merge this and close #477?

Thanks @rpetrusha. I'll merge this and keep plugging away at my next group of bugs.


Integrate and Test the Command Handler and Command Library Together

Description
Integrate the Command Handler and Command Library together and test their combined functionality. Completion of this issue and proper functionality of the Command Handler and Command Library together signals the completion of the Command Line Module.
Required Outcomes

[ ] Command Handler can use Command Library to validate commands
[ ] Command Handler can use Command Library to execute commands

Put into their own "Command Module" folder in src?


Merge BAM fails, no error produced

Hello,
I have an issue at the Merge BAM step, but I get no errors, it just doesn't go through and it terminates the job. This is the last line from nextflow.log file:
~> TaskHandler[id: 52; name: MergeBAM (H4K12ac_R1); status: RUNNING; exit: -; error: -; workDir: /fastscratch/myscratch/lmihalje/work/cf/1aabc8570e7f86e2382c671c7730e2]

Hi @lmihalj ! Sorry I completely missed this issue :sweat_smile: Im assuming you managed to solve the problem?

It's ok! I was using conda, so there is a glitch somewhere with picard, but then I switched to singularity and everything went smoothly!

Nice! I would have recommended for you to use Docker/Singularity anyway if possible. Glad you got it working ;)


fix: role auth

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license
Summary
(describe what this merge request does)
Implementation highlights
(describe how the merge request does for feature changes, share the RFC link if it has)
Test checklist

[ ] add new test cases
[ ] all code changes are covered by unit tests
[x] end-to-end tests

[x] deploy web console with CloudFront + S3 + API gateway
[ ] deploy web console within VPC
[ ] deploy ingestion server

[ ] with MSK sink
[ ] with KDS sink
[ ] with S3 sink

[ ] deploy data processing
[ ] deploy data modeling

[ ] new Redshift Serverless
[ ] provisioned Redshift
[ ] Athena

[ ] deploy with reporting
[ ] streaming ingestion

[ ] with Redshift Serverless
[ ] with provisioned Redshift

Is it a breaking change

[ ] add parameters without default value in stack
[ ] introduce new service permission in stack
[ ] introduce new top level stack module

Miscellaneous

[ ] introduce new symbol link source file(s) to be shared among infra code, web console frontend, and web console backend

SonarQube Quality Gate Result

Result: :white_check_mark: OK
Triggered by @tyyzqmf on pull_request

Metric
Status
Value
Error Threshold

Reliability rating
:white_check_mark: OK
1
> 1

Security rating
:white_check_mark: OK
1
> 1

Sqale rating
:white_check_mark: OK
1
> 1

Coverage
:white_check_mark: OK
83.60
< 80

Duplicated lines density
:white_check_mark: OK
8.50
> 30

Blocker violations
:white_check_mark: OK
0
> 0

Bugs
:white_check_mark: OK
0
> 0

Code smells
:white_check_mark: OK
9
> 40

Critical violations
:white_check_mark: OK
0
> 0

Major violations
:white_check_mark: OK
0
> 0

Vulnerabilities
:white_check_mark: OK
0
> 0

View on SonarQube
updated: 7/19/2024, 09:12:57 (UTC+0)

SonarQube Code Analytics
Quality Gate passed

Additional information
The following metrics might not affect the Quality Gate status but improving them will improve your project code quality.
Issues
 0 Bugs
 0 Vulnerabilities
 0 Code Smells
Coverage and Duplications
No data Coverage
No data Duplication

SonarQube Quality Gate Result

Result: :white_check_mark: OK
Triggered by @tyyzqmf on pull_request

Metric
Status
Value
Error Threshold

Reliability rating
:white_check_mark: OK
1
> 1

Security rating
:white_check_mark: OK
1
> 1

Sqale rating
:white_check_mark: OK
1
> 1

Coverage
:white_check_mark: OK
83.70
< 80

Duplicated lines density
:white_check_mark: OK
8.50
> 30

Blocker violations
:white_check_mark: OK
0
> 0

Bugs
:white_check_mark: OK
0
> 0

Code smells
:white_check_mark: OK
9
> 40

Critical violations
:white_check_mark: OK
0
> 0

Major violations
:white_check_mark: OK
0
> 0

Vulnerabilities
:white_check_mark: OK
0
> 0

View on SonarQube
updated: 7/23/2024, 06:56:31 (UTC+0)

SonarQube Quality Gate Result

Result: :white_check_mark: OK
Triggered by @tyyzqmf on pull_request

Metric
Status
Value
Error Threshold

Reliability rating
:white_check_mark: OK
1
> 1

Security rating
:white_check_mark: OK
1
> 1

Sqale rating
:white_check_mark: OK
1
> 1

Coverage
:white_check_mark: OK
83.60
< 80

Duplicated lines density
:white_check_mark: OK
8.50
> 30

Blocker violations
:white_check_mark: OK
0
> 0

Bugs
:white_check_mark: OK
0
> 0

Code smells
:white_check_mark: OK
9
> 40

Critical violations
:white_check_mark: OK
0
> 0

Major violations
:white_check_mark: OK
0
> 0

Vulnerabilities
:white_check_mark: OK
0
> 0

View on SonarQube
updated: 7/23/2024, 06:59:25 (UTC+0)

SonarQube Quality Gate Result

Result: :white_check_mark: OK
Triggered by @tyyzqmf on pull_request

Metric
Status
Value
Error Threshold

Reliability rating
:white_check_mark: OK
1
> 1

Security rating
:white_check_mark: OK
1
> 1

Sqale rating
:white_check_mark: OK
1
> 1

Coverage
:white_check_mark: OK
83.80
< 80

Duplicated lines density
:white_check_mark: OK
8.50
> 30

Blocker violations
:white_check_mark: OK
0
> 0

Bugs
:white_check_mark: OK
0
> 0

Code smells
:white_check_mark: OK
9
> 40

Critical violations
:white_check_mark: OK
0
> 0

Major violations
:white_check_mark: OK
0
> 0

Vulnerabilities
:white_check_mark: OK
0
> 0

View on SonarQube
updated: 7/23/2024, 07:00:51 (UTC+0)

SonarQube Quality Gate Result

Result: :white_check_mark: OK
Triggered by @tyyzqmf on pull_request

Metric
Status
Value
Error Threshold

Reliability rating
:white_check_mark: OK
1
> 1

Security rating
:white_check_mark: OK
1
> 1

Sqale rating
:white_check_mark: OK
1
> 1

Coverage
:white_check_mark: OK
83.70
< 80

Duplicated lines density
:white_check_mark: OK
8.50
> 30

Blocker violations
:white_check_mark: OK
0
> 0

Bugs
:white_check_mark: OK
0
> 0

Code smells
:white_check_mark: OK
9
> 40

Critical violations
:white_check_mark: OK
0
> 0

Major violations
:white_check_mark: OK
0
> 0

Vulnerabilities
:white_check_mark: OK
0
> 0

View on SonarQube
updated: 7/25/2024, 09:57:52 (UTC+0)


Mobile Searches unable to find element

Have had this running using python and pm2 so it can run in the background 24/7 for about 2 days now and was wondering if it was doing mobile searches. Today I looked at it and it seems like every account seems to error out with this same error when trying to complete mobile searches. Everything else seems to work flawlessly besides the mobile section.
   File "J:\PythonProjects\bingRewards\BingRewards\main.py", line 424, in login
     driver.find_element(By.XPATH, value='//*[@id="idSIButton9"]').click()
   File "C:\Users\johnn\AppData\Local\Programs\Python\Python310\lib\site-packages\selenium\webdriver\remote\webdriver.py", line 857, in find_element
     return self.execute(Command.FIND_ELEMENT, {
   File "C:\Users\johnn\AppData\Local\Programs\Python\Python310\lib\site-packages\selenium\webdriver\remote\webdriver.py", line 435, in execute
     self.error_handler.check_response(response)
   File "C:\Users\johnn\AppData\Local\Programs\Python\Python310\lib\site-packages\selenium\webdriver\remote\errorhandler.py", line 247, in check_response
     raise exception_class(message, screen, stacktrace)
 selenium.common.exceptions.NoSuchElementException: Message: no such element: Unable to locate element: {"method":"xpath","selector":"//*[@id="idSIButton9"]"}
   (Session info: headless chrome=114.0.5735.199)
 Stacktrace:
 Backtrace:
       GetHandleVerifier [0x0037A813+48355]
       (No symbol) [0x0030C4B1]
       (No symbol) [0x00215358]
       (No symbol) [0x002409A5]
       (No symbol) [0x00240B3B]
       (No symbol) [0x0026E232]
       (No symbol) [0x0025A784]
       (No symbol) [0x0026C922]
       (No symbol) [0x0025A536]
       (No symbol) [0x002382DC]
       (No symbol) [0x002393DD]
       GetHandleVerifier [0x005DAABD+2539405]
       GetHandleVerifier [0x0061A78F+2800735]
       GetHandleVerifier [0x0061456C+2775612]
       GetHandleVerifier [0x004051E0+616112]
       (No symbol) [0x00315F8C]
       (No symbol) [0x00312328]
       (No symbol) [0x0031240B]
       (No symbol) [0x00304FF7]
       BaseThreadInitThunk [0x750A7D59+25]
       RtlInitializeExceptionChain [0x7731B79B+107]
       RtlClearBits [0x7731B71F+191]

 During handling of the above exception, another exception occurred:

 Traceback (most recent call last):
   File "J:\PythonProjects\bingRewards\BingRewards\main.py", line 439, in login
     message = driver.find_element(By.XPATH, value='//*[@id="iPageTitle"]').text
   File "C:\Users\johnn\AppData\Local\Programs\Python\Python310\lib\site-packages\selenium\webdriver\remote\webdriver.py", line 857, in find_element
     return self.execute(Command.FIND_ELEMENT, {
   File "C:\Users\johnn\AppData\Local\Programs\Python\Python310\lib\site-packages\selenium\webdriver\remote\webdriver.py", line 435, in execute
     self.error_handler.check_response(response)
   File "C:\Users\johnn\AppData\Local\Programs\Python\Python310\lib\site-packages\selenium\webdriver\remote\errorhandler.py", line 247, in check_response
     raise exception_class(message, screen, stacktrace)
 selenium.common.exceptions.NoSuchElementException: Message: no such element: Unable to locate element: {"method":"xpath","selector":"//*[@id="iPageTitle"]"}
   (Session info: headless chrome=114.0.5735.199)
 Stacktrace:
 Backtrace:
       GetHandleVerifier [0x0037A813+48355]
       (No symbol) [0x0030C4B1]
       (No symbol) [0x00215358]
       (No symbol) [0x002409A5]
       (No symbol) [0x00240B3B]
       (No symbol) [0x0026E232]
       (No symbol) [0x0025A784]
       (No symbol) [0x0026C922]
       (No symbol) [0x0025A536]
       (No symbol) [0x002382DC]
       (No symbol) [0x002393DD]
       GetHandleVerifier [0x005DAABD+2539405]
       GetHandleVerifier [0x0061A78F+2800735]
       GetHandleVerifier [0x0061456C+2775612]
       GetHandleVerifier [0x004051E0+616112]
       (No symbol) [0x00315F8C]
       (No symbol) [0x00312328]
       (No symbol) [0x0031240B]
       (No symbol) [0x00304FF7]
       BaseThreadInitThunk [0x750A7D59+25]
       RtlInitializeExceptionChain [0x7731B79B+107]
       RtlClearBits [0x7731B71F+191]

 During handling of the above exception, another exception occurred:

 Traceback (most recent call last):
   File "J:\PythonProjects\bingRewards\BingRewards\main.py", line 1248, in mobile_helper
     mobile_search(driver, EMAIL, PASSWORD, MOBILE_SEARCHES)
   File "J:\PythonProjects\bingRewards\BingRewards\main.py", line 1208, in mobile_search
     login(EMAIL, PASSWORD, driver)
   File "J:\PythonProjects\bingRewards\BingRewards\main.py", line 448, in login
     driver.find_element(By.XPATH, value='//*[@id="idSIButton9"]').click()
   File "C:\Users\johnn\AppData\Local\Programs\Python\Python310\lib\site-packages\selenium\webdriver\remote\webdriver.py", line 857, in find_element
     return self.execute(Command.FIND_ELEMENT, {
   File "C:\Users\johnn\AppData\Local\Programs\Python\Python310\lib\site-packages\selenium\webdriver\remote\webdriver.py", line 435, in execute
     self.error_handler.check_response(response)
   File "C:\Users\johnn\AppData\Local\Programs\Python\Python310\lib\site-packages\selenium\webdriver\remote\errorhandler.py", line 247, in check_response
     raise exception_class(message, screen, stacktrace)0x00240B3B
 selenium.common.exceptions.NoSuchElementException: Message: no such element: Unable to locate element: {"method":"xpath","selector":"//*[@id="idSIButton9"]"}
   (Session info: headless chrome=114.0.5735.199)
 Stacktrace:
 Backtrace:
       GetHandleVerifier [0x0037A813+48355]
       (No symbol) [0x0030C4B1]
       (No symbol) [0x00215358]
       (No symbol) [0x002409A5]
       (No symbol) [0x00240B3B]
       (No symbol) [0x0026E232]
       (No symbol) [0x0025A784]
       (No symbol) [0x0026C922]
       (No symbol) [0x0025A536]
       (No symbol) [0x002382DC]
       (No symbol) [0x002393DD]
       GetHandleVerifier [0x005DAABD+2539405]
       GetHandleVerifier [0x0061A78F+2800735]
       GetHandleVerifier [0x0061456C+2775612]
       GetHandleVerifier [0x004051E0+616112]
       (No symbol) [0x00315F8C]
       (No symbol) [0x00312328]
       (No symbol) [0x0031240B]
       (No symbol) [0x00304FF7]
       BaseThreadInitThunk [0x750A7D59+25]
       RtlInitializeExceptionChain [0x7731B79B+107]
       RtlClearBits [0x7731B71F+191]

 Attempting to restart Mobile search in 500 seconds
 Error fetching points breakdown.```

I think I found the issue when logging into a Microsoft account for the first time on a "mobile" device, it wants you to hit continue to confirm some extra stuff on the account. It appears there isn't a check for this, as it assumes each account has already been logged in on mobile before or just was overlooked. I was able to fix it by making it not headless, and pressing the continue button as it does not ask you again after you have pressed it once. Thought you should know for others who use new accounts.


use VocalDataset + PredictTransform for core.predict

instead of current method -- implemented this, not sure why not switch

this will make it easier to fix #237 in the way that @yardencsGitHub and I discussed (off line), so moving this issue to the top of the pile
here's the to-do list:

[ ] make transforms.defaults return PredictItemTransform instead of current transform and target transforms

because we want to get back a dict with the spect_path in it, so we can use that path to get the timebin labels we need for #237
and just for for consistency with train and eval

[ ] use VocalDataset in place of UnannotatedDataset in core.predict

VocalDataset no longer requires annotation, so there's no need for separate UnannotatedDataset class really
but VocalDataset expects an "item transform" -- another reason we need the above change

[ ] fix Model.predict method to unpack batches from dict using keys, instead of current tuple unpacking
[ ] remove UnannotatedDataset class, which will now be unused


sync/atomic: CompareAndSwapPointer should be CompareAndSwap

The comment states CompareAndSwapPointer but it should be name of the function, CompareAndSwap:
https://github.com/golang/go/blob/2422c5eae5dc6539b4b7657ef7bfe58a65acb61d/src/sync/atomic/value.go#L129-L134

CC @golang/release , this is a new API for Go 1.17, and the release branch doesn't have the fix yet (see https://github.com/golang/go/blob/release-branch.go1.17/src/sync/atomic/value.go#L129 ). For your consideration, so it doesn't get lost in the shuffle on Monday.
@gopherbot please backport to 1.17


Tiberium logic

Anyone who wants know more about tiberium can visit Wikipedia first.
Planned feature:

Player can be converted into tiberium when directly contacted with any type of tiberium crystal.
Implementation as PotionEffect seems to be the best way.
Corrosion. Convert everything into itself.
Unbreakable unless use special sound-wave tool

Will players be turned into tiberium statue when they die of that PotionEffect?

At least there will be some [insert blue/green] crystal left at where they die

Well, I was just wondering if you are going to make the world's first Steve Status. (correct me if I was wrong) Anyway, it is still a good idea.
Btw, when you will be free? My ChemLib is approaching its first release. I hope you could have a look at it later. (not now, I haven't yet pushed for a long time and I'm stuck with a werid bug) Integrating it into FC may not be an easy task.
--- Original Message ---
From: "Urey.X."<EMAIL_ADDRESS>Sent: May 11, 2016 7:58 PM
To: "FrogCraft-Rebirth/FrogCraft-Rebirth"<EMAIL_ADDRESS>Cc: "Glease"<EMAIL_ADDRESS>"Comment"<EMAIL_ADDRESS>Subject: Re: [FrogCraft-Rebirth/FrogCraft-Rebirth] Tiberium logic (#19)
At least there will be some [insert blue/green] crystal left at where they die

You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/FrogCraft-Rebirth/FrogCraft-Rebirth/issues/19#issuecomment-218438259

I have a 2000+words essay which is due next Monday. Also a lab report due this Friday. Also next week is the review week for my Finals. Expect the week of Finals - usually that week won't be painful.

Well, I'll start being busy when your stuff is done, then.
--- Original Message ---
From: "Urey.X."<EMAIL_ADDRESS>Sent: May 11, 2016 10:08 PM
To: "FrogCraft-Rebirth/FrogCraft-Rebirth"<EMAIL_ADDRESS>Cc: "Glease"<EMAIL_ADDRESS>"Comment"<EMAIL_ADDRESS>Subject: Re: [FrogCraft-Rebirth/FrogCraft-Rebirth] Tiberium logic (#19)
I have a 2000+words essay which is due next Monday. Also a lab report due this Friday. Also next week is the review week for my Finals. Expect the week of Finals - usually that week won't be painful.

You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/FrogCraft-Rebirth/FrogCraft-Rebirth/issues/19#issuecomment-218470036

Beside, ChemLab integration will be in another branch, most likely a branch for 1.8. I have kinda of screwed up the integration in 1.7.10 ver.... and also 1.7.10 is fading...

Well, I know how nasty those code looks like. You seemingly don't understand how Java APIs locate a implementation without referencing them directly. It's some reflection magic with j.u.ServiceLoader. Anyway, don't worry, you can just focus on the game logic and I'll handle them all. If you are interested how it's done, you could have a look on JAXP FactoryFinder (located in almost every sub-package of package javax.xml).
Btw, Why not directly move on to mc 1.9?
--- Original Message ---
From: "Urey.X."<EMAIL_ADDRESS>Sent: May 12, 2016 4:24 AM
To: "FrogCraft-Rebirth/FrogCraft-Rebirth"<EMAIL_ADDRESS>Cc: "Glease"<EMAIL_ADDRESS>"Comment"<EMAIL_ADDRESS>Subject: Re: [FrogCraft-Rebirth/FrogCraft-Rebirth] Tiberium logic (#19)
Beside, ChemLab integration will be in another branch, most likely a branch for 1.8. I have kinda of screwed up the integration in 1.7.10 ver.... and also 1.7.10 is fading...

You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/FrogCraft-Rebirth/FrogCraft-Rebirth/issues/19#issuecomment-218578838

Waiting for IC2exp 1.9.

man, what about fluid stuff? I mean, how to handle corrosion on fluid blocks? or does it happen at all?

It does happen since I don't check what type of block it used to be.


[JAV-461]service center API change. we make it v4 as default as CI only support v4.

Coverage increased (+0.06%) to 86.41% when pulling 7090e2e59d4505f8d12d394c21a0ad8c5f420ecd on liubao68:registry-api into 518b5fe26804d884bf4c1b9a3163f09c701fafda on ServiceComb:master.