After event should be fired before calling ready handler

This issue was suggested in this comment https://github.com/fastify/fastify/pull/671#discussion_r162013010
I don't know if the current behavior is correct or not.
This PR adds a test for checking what I expected.
NB: I didn't found any tests that check that call order.

Is this still an issue? Should it be fixed?
I think this is not needed anymore, but let us know.


java.lang.ClassNotFoundException: Didn't find class "com.xxx.share.ShareActivity"

Hello,
just trying to implement share extension. Works great on IOS, but I have this error on Android, even if my class ShareActivity is in my java project.
any tips ? Thanks.

Resovled


Add interview README.md

This adds the interview of Chris Lattner with Lex Fridman some months ago.
A very insightful podcast about programming and the future of AI.
PS.: Also fixed a typo

@PriNova thank you! (Ouch, that was a really bad typo 😅 tks for that as well!)

You're welcome and thank you for merging.


[Help Wanted] TSC ServerInfo call and SignOut call Hanging/Freezing after TSC Version Upgrade

Describe the bug
After upgrading TSC from 0.19.0 to 0.22  the below lines of code cause a hanging/freezing behavior
(after experimenting I have determined these are the versions where the behavior changes, I'm actually trying to upgrade from 0.14.1 to 0.24)
I also tested all the way up to 0.25, same issue
I have to upgrade the TSC version due to a seperate issue.
Scenario 1:
server = TSC.Server(serverUrl, use_server_version = True) --- Freezes here
tableau_auth = TSC.TableauAuth(tableauAcct, tableauPwd)
server.auth.sign_in(tableau_auth)
server.auth.sign_out()
Scenario 2:
server = TSC.Server(serverUrl, use_server_version = False)
server.version = "3.17"
tableau_auth = TSC.TableauAuth(tableauAcct, tableauPwd)
server.auth.sign_in(tableau_auth)
server.auth.sign_out() --- Freezes here
Versions
Details of your environment, including:

Tableau Server version (or note if using Tableau Online) API: 3.17 Server: 2022.3.5
Python version : 3.7
TSC library version: 0.19.0 is working, 0.22 is not
Its running in a python flask app in a docker container: Flask version: 2.2.4
I can provide my dockerfile or requirements.txt if you think that would be helpful

To Reproduce
Steps to reproduce the behavior. Please include a code snippet where possible.
Run Above lines of code after deploying
Results
What are the results or error messages received?
Excecution Freezes/Hangs
After about 5 ish minutes I get this error
('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))
NOTE: Be careful not to post user names, passwords, auth tokens or any other private or sensitive information.

Sorry for the delay - this sounds like there's some kind of firewall or network condition between tsc and the server that is making the request hang. Do you have access to the server logs to see if the request is actually getting to the server?

I kind of resolved the issue.
Our Tableau instance sits behind Akamai, and Akamai was blocking the traffic as it detected it as bot traffic because all the requests were missing several headers.
I don't know why and was unable to figure out why the version change of TSC caused the headers to disappear but we kind of resolved it by making a rule in Akamai to allow traffic through from the specific IP address of where the requests are coming from.

Thanks for confirming you've got it working - I'll close this one.


yamllint: don’t check keys and add file extension to config file

Signed-off-by: Matthieu MOREL<EMAIL_ADDRESS>

What is check keys?

From the yamllint documentation:

check-keys disables verification for keys in mappings. By default, truthy rule applies to both keys and values. Set this option to false to prevent this.

Thanks

FYI, this change renamed the config file, breaking the repo sync script.


Bug: assistant auto save never worked on my tablet?

Hi,
I am using SpeakGPT on multiple devices and notice that I never could get the autosaving of the assistant to work on my tablet.
I have the latest SpeakGPT version installed and my android version is Android 12.
I have toggled ON the button "auto save chats" in the global control center. But I still notice that triggering the assistant does not save by default as it does on my phone.
I don't think it's a regression, but rather that it never worked on this specific tablet.
I'm sorry I can't give more relevant information, don't hesitate to tell me what other information to provide.
Have a nice day!
PS : great work on the recent releases!

Without additional information and feedback from other users I can't verify the information you provided is correct. This issue will receive low priority as there no ways to test it. On my tablet it worked. Officially supported Android versions: Android 9 - Android 15 Preview.

For some reason I noticed that the feature now works. The only plausible thing that I did was untoggle, then retoggle then restart my tablet. I am all the more surprised because I had been using the app on my tablet for several days with reboots in between.
And it also works on the latest version from today, thanks a lot!


1.1.0 not published

I want to use the new decimal option, but it seems that<EMAIL_ADDRESS>is not published to npm yet.

Thanks for the heads up! Fixed.


Parsing problem with CLI plugin

We have built a CLI plugin which has a flag with the following properties
name: 'name', char: 'n', hasValue: true, required: true,
When the user specifies    command -n xxx  or command --name xxx, everything works fine
But, when the user specifies -nxxx, the run function in the command receives xxx for context.flags.name.    Apparently, the parser doesnt know to reject -nxxx by requiring a space after the character shorthand

this is as expected since you can use multiple short characters like heroku command foo -abc where 'a', 'b', and 'c' are short chars

the space isn't required, is there a reason you think it should be?

Sorry if I wasnt clear - I do understand that sometimes folks use the -abc form for multiple short chars, but from working with other CLIs over the years, that can be a dangerous pattern, IMHO.
In particular IF the --xxx starts with the same letter as the short char and takes an argument, it can be a  troubling issue of easy mistakes..
I'd suggest that IF a flag/option requires a value, then it should always require being followed by a space.   For example having -nab foo is going to be hard to understand even if 'a' & 'b' are short chars for non value holding options.   And really odd if 'a' or 'b' also require a value

I don't think I agree. It's useful to be able to do things like heroku apps:restart -aappname.

There are examples out there - and yes, commands arent consistent.    grep does allow -file to be "ile", but doesnt allow -dir to be an action "ir".    git will complain if you try to do git branch -dfoobar and asks if you meant --, but will recognize git branch --del foobar without the full delete.     And it doesnt accept git -deletefoobar....
There are cases where you might want to combine single character flags that Do Not require a value - agreed and common.
But if you have flags that take a value, this gets messy fast....
ex. foo --name xxx --path zzz    and foo -n xxx -p zzz, but what does it mean to do foo -nxxxpzzz or foo -npxxxzzz.  This gets ambiguous and confused very quickly.
So, if you really want to allow combined single chars, that is viable and is commonly used.   But when you have flags that allow both a '-' form and a '--form", it really calls out for not being able to mix those with non value flags and calls out for having a separator space....
Yes, we can work around this by making sure that the single char form cant feed into any double -- form, but that starts running out of characters and the natural tendency for a user is to accept the first char as the abbreviated form (-n --name, -p --path)

It's not possible to support multiple short flags with values in the same argument like -nxxxpzzz. There is no way for the parser to delimit. That is fine though since it's just optional shorthand.
I don't follow your last point if you want to elaborate. However I am going to close this ticket as this is working as designed.


Testing / Command line questions

Hi @tonylukasavage,
I've been looking into testing within the Appcelerator ecosystem, and I always seem to come back to one of your projects, namely ti-mocha.
So, I have a few questions:

How does one set up tests for an Alloy project using ti-mocha?
Is there a way to run tests via command line? (I didn't see any commands in the example).
Is there a difference between test suites testing views and ones that test a library?

My goal is to have an alloy project set up and have tests running on travis-ci. Likewise, I want to create reusable modules installable using gittio, also built and tested on travis-ci.
Any help pointing me in the right direction would be much appreciated. Thanks in advance, and thanks for all your awesome work.

My goal is to have an alloy project set up and have tests running on travis-ci.

(emphasis by me)
I cannot really help you on the other questions, but I can point you to this .travis.yml that installs all the required dependencies and launches an app in the Travis CI environment.

Thanks @yuchi, that's pretty helpful. I'd love to have some automated tests there, but at the very least with your example I'll know that the project builds fine on Travis.

Please note that the configuration I linked is iOS only.
I built an experiment that makes tests running in both iOS and Android, both on Travis CI. You can see the resulting runs here: https://travis-ci.org/yuchi/ti-cross-ci-experiments

@fmr, could you please add a few notes on how you structured your project in the end?

@yuchi, In the end I didn't end up using ti-mocha (or any test framework for that matter, sadly). I know very little of the best practices for testing in the javascript world, much less in Titanium.
What I did manage to get working was your ti-cross-ci-experiments set up. I haven't got any tests, but at least any glaring build errors will come up on Travis for iOS and Android.
I've created a gist for what I've used: https://gist.github.com/fmr/430c45eb93a000ec1f42
A successful build looks like this:

I would still love to know how I can integrate ti-mocha or other test frameworks in a mobile app project (not just for commonjs modules, etc.) for use with continuous integration.

Closing this since it's got little to do with ti-mocha now. For anyone interested, this project looks like a good reference for testing and continuous integration: https://github.com/TheSmiths/ts.boilerplate


ragged.unique_values

https://github.com/jpivarski/ragged/blob/1890589635309e2d92998290b0889ec52bcda4ae/src/ragged/_spec_set_functions.py#L116-L133

This was done in PR#57


[Refactor] Set MetaContext to local thread in the updateMeta function(cherry-pick 2.5)

[FE Incremental Coverage Report]
:heart_eyes: pass : 0 / 0 (0%)


Add location to tasks

It would be cool to have a location for tasks.
In the edit dialog you should be able to add a map location.
Selecting a location should ask for a name and then create a marker on the global map.
If an existing marker is selected it should be connected to the task.
If the marker is updated the old version should be deleted.
The map location should be shown in the edit dialog.

I am also looking for this feature.
Additionally an option to create a note by clicking on a location and a button to move the camera to the note location.

I had a similar idea, based a little more around map tags. Originally logged it as #181, but this issue takes precedent.  text of that copied here:
I often want to associate a task with a location (e.g. build a wall at a choke point), and indeed map tags are a good alternative to an explicit todo list. - its what I used before I discovered this mod, actually!
This is obviously a large undertaking, but I think I can break it down to a few steps:
determine a way to link a task to a map tag under-the-hood (e.g. I imagine map tags have some kind of global id - YARM works with them a bit, that might be a good place to research)
Add an option to automatically make a todo list task when a map tag is manually created.
(not sure if possible) Add a 'link map tag' button to the task edit/create popup to allow the user to link a tag after the task has been created
Automatically delete the map tag once the linked task is completed (it probably won't be possible to restore a map tag if the task is un-completed - I'm fine with that)

I'm planning to work on this myself, so code review and approval is probably the only support that's needed, and I'll make that as easy as I can :)

isnomer, while you're right that it can be entered in, during my testing I wasn't able to "ping" a location on the map with the todo window open and have it generate the coordinates as it does via chat.


[stable/nginx-ingress] Support initContainers

What this PR does / why we need it:
I needed some initialization (create /var/log/nginx on a mounted volume) before the controller starts.

/assign @unguiculus

/assign

/ok-to-test

/ok-to-test

/lgtm


Poorly set text in Preferences -> console -> advanced settings

From<EMAIL_ADDRESS>on 2011-12-01T08:50:18Z
What steps will reproduce the problem?

Go to Preferences -> console -> advanced settings What is the expected output? What do you see instead? The text of the explanation is only partly visible. What version of the product are you using? On what operating system? Ubuntu 11.10, Spydre 2.1.1

Attachment: settings.png
Original issue: http://code.google.com/p/spyderlib/issues/detail?id=860

From pierre.raybaut on 2011-12-07T08:46:04Z
This issue was closed by revision e34e07565ea6 .
Status: Fixed


MiSeq Reads

Hi,
I have some Candida parapsilosis fastq files that where run on a MiSeq. I don't work with diploid organisms so can't compare them like I normally would. Can longshot work on these even thought it's the Illumina platform and short read technology?
They're patient samples so I want to look at the relatedness of them. I was hoping to use VCFtools after longshot and then see how I could make an NxN matrix and MST or MLT.
Cheers,
P

Longshot should work on Illumina data, the --no-haps option should be used. I would suggest using Illumina focused variant calling tools since we have not evaluated Longshot on Illumina data.


feat(docs): dynamic og-images

Is your feature request related to a problem? Please describe.
This week we rolled out dynamic og images for trpc: https://twitter.com/ixahmedxii/status/1603517506525732881

Would be nice with something similar for our docs too
Describe the solution you'd like to see
Dynamic OG Images for Documentation Pages
Things we can include:

Title
Description
Language
???

Could also be a good time to change up the logo to the new one Theo announced on stream this week: https://t3.gg, https://github.com/t3dotgg/t3-astro/blob/main/public/images/t3/700.svg
Describe alternate solutions
Drawback is it has some pitfalls in frameworks that's not Next.js: https://twitter.com/jullerino/status/1602346699359412225
Which might require us to do something similar to what we did in trpc and create a separate app that hosts it: https://github.com/trpc/trpc/tree/main/www/og-image
Additional information
It was a bigger job than we first anticipated but here are some useful resources:
https://github.com/trpc/trpc/pull/3382
https://github.com/trpc/trpc/pull/3402
https://github.com/trpc/trpc/pull/3406
https://github.com/vercel/satori

I hate that this might require a separate app, but these images look so nice that it's probably worth it :)

I hate that this might require a separate app, but these images look so nice that it's probably worth it :)

Solution: migrate off of Astro to Nextra

I hate that this might require a separate app, but these images look so nice that it's probably worth it :)

Solution: migrate off of Astro to Nextra

nextra is nice

Check out astro-og-image

If we enable SSR with Astro and add the Vercel adapter we can use server endpoints in Astro.
https://docs.astro.build/en/core-concepts/endpoints/#server-endpoints-api-routes
We can have a route that uses satori and the title/description within frontmatter to generate the images.
I can make a PR for this... Is there a preferred style for the OG images you guys (@c-ehrlich  @juliusmarminge) have in mind? If not I will probably do something similar to the TRPC OG images


math/rand: After ~1.5 month of valid usage, rand started consistently returning 0

What version of Go are you using (go version)?
1.17.1
Does this issue reproduce with the latest release?
Can't say, don't know how to reproduce.
What operating system and processor architecture are you using (go env)?
It was built for amd64 and linux, and running in alpine (docker in k8s).
What did you do?
I was pretty usually using math.rand, with the following code:
var seededRand *rand.Rand = rand.New(rand.NewSource(time.Now().UnixNano()))

const charset = "abcdefghijklmnopqrstuvwxyz"

func RandomString(length int) string {
	b := make([]byte, length)
	charsetLen := len(charset)
	for i := range b {
		b[i] = charset[seededRand.Intn(charsetLen)]
	}
	return string(b)
}

What did you expect to see?
Random sting, as I usually did.
What did you see instead?
I had 3 instances of this service running. After the long time of running as expected (~1.5 months) one service started consistently returning "aaaaaaaaaa" for RandomString(10) (other 2 continued working as expected).
This was a very weird situation, would someone know what might have happened, is it fixed in some new go version, or how to mitigate? I'm thinking of mitigating by changing to a new random seed if I recognize the random returning always 0....

This is strange. I don't see how the math/rand code could cause this.
Possibly there is a memory management bug that causes seededRand.src.(*rngSource).vec to be zeroed. Then it would return all zeros from then on.
Without a way to reproduce this is going to be hard to track down. If my suspicion is right, either it is a bug in the runtime, or the kernel, or some bad use of unsafe. It isn't in the rand code at all.

Of note, the only way for the algorithm math/rand uses to return more than 606 consecutive zeroes is for the entire state to be zero. No state with any nonzero element will ever become all zero on its own. So, I agree that the bug is elsewhere.

Not sure if important for investigation, but rand does not return 0 but x where x %26 == 0 (using intn). Also, function returned "aaaaaaaaaa" at least 360 times in a row, which means it generated x where x % 26 == 0 at least 3600 times in a row.

Not sure if important for investigation, but rand does not return 0 but x where x %26 == 0 (using intn).

I don't understand your point here. Could you elaborate?

Code that caused issues uses seededRand.Intn(26), and was always returning 0 after some point in time. I guess that, internally, func Int(n) is something like Int() % n. I guess that correct claim would be that rand does not consistently returns 0 but consistently returns numbers divisible by 26.
@zephyrtronium mentined that rand algorithm cannot return more than 606 consecutive zeros, it does not have to do that to cause reported issue. It just has to enter into some weird state in which it always returns numbers divisible by 26.

I see. You're just saying you merely observed Intn(26) returning 0s, but you don't know whether the internal (entire 32 or 64 bit) RNG was returning 0s.
I think it is very likely that if we're returning lots of numbers y=x%26 such that y==0, then internally we're generating lots of numbers such that x==0. There's nothing magical inside the RNG related to the number 26 that would cause lots of xs to be 0 mod 26 but not be all 0.

Note that above RandomString function is not safe to invoke concurrently from multiple goroutines. Did your service account for that and serialized the calls to it?

What's not safe about it, rand.Rand's Intn() is not routine-safe?
I do call it from multiple routines concurrently without serialization. Could that have caused the issue?

Per the package documentation on math/rand: "The default Source is safe for concurrent use by multiple goroutines, but Sources created by NewSource are not." Based on how the generator updates the feed and tap, it seems likely that this is a sufficient explanation.

Well thank you very much then! I will sync it and it will hopefully be good forever. :) Thank you very much again, good catch!
General language feedback: though documentation is important to read, devs often will not do that, especially for simple, 'everyday' stuff. It would be interesting to think whether some tooling would be able to help dev here, func annotation, warning, etc.

Running under the race detector should catch the issue described.

I'm going to close this issue for now. If you fix your races and you're still having issues, please reopen (and if you can, give us some way to reproduce ourselves).


Large Lua files have "Not showing N further errors and warnings"

How are you using the lua-language-server?
Visual Studio Code Extension (sumneko.lua)
Which OS are you using?
Windows
What is the issue affecting?
Diagnostics/Syntax Checking
Problem
Related to: #1522
In large files, you can get into a situation where there are 0 errors reported in the errors pane except for "Not showing N further errors and warnings". Obviously, this makes it impossible to actually fix the errors, since you don't know what they are.
Thus, the bug seems to be that the Lua language server is incorrectly ignoring errors suppressed by the end-user, since they are still counting towards the 250 hardcoded (?) VSCode limit
Reproduction steps
Use the following Lua file:
https://gist.github.com/Zamiell/d0ab9f0b9d0d48efe9a14c293e44f8f0/raw/272057baf5028400e2aefed958b8d31defb01f02/main.lua
With the following .luarc.json file:
{
  "$schema": "https://raw.githubusercontent.com/sumneko/vscode-lua/master/setting/schema.json",
  "diagnostics.globals": [
    "ActionTriggers",
    "ActiveSlot",
    "BabySubType",
    "BackdropType",
    "BatterySubType",
    "BedSubType",
    "BitSet128",
    "BombSubType",
    "BombVariant",
    "ButtonAction",
    "CacheFlag",
    "Card",
    "Challenge",
    "ChampionColor",
    "ChestSubType",
    "CoinSubType",
    "CollectibleType",
    "Color",
    "CppContainer",
    "DamageFlag",
    "Difficulty",
    "Direction",
    "DoorSlot",
    "DoorState",
    "DoorVariant",
    "EffectVariant",
    "Entity",
    "EntityBomb",
    "EntityCollisionClass",
    "EntityEffect",
    "EntityFamiliar",
    "EntityFlag",
    "EntityGridCollisionClass",
    "EntityKnife",
    "EntityLaser",
    "EntityNPC",
    "EntityPartition",
    "EntityPickup",
    "EntityPlayer",
    "EntityProjectile",
    "EntityPtr",
    "EntityRef",
    "EntityTear",
    "EntityType",
    "FamiliarVariant",
    "Font",
    "Game",
    "GameStateFlag",
    "GetPtrHash",
    "GridCollisionClass",
    "GridEntity",
    "GridEntityDesc",
    "GridEntityDoor",
    "GridEntityPit",
    "GridEntityPoop",
    "GridEntityPressurePlate",
    "GridEntityRock",
    "GridEntitySpikes",
    "GridEntityTNT",
    "GridEntityType",
    "GridRooms",
    "HUD",
    "HeartSubType",
    "Input",
    "InputHook",
    "Isaac",
    "ItemConfig",
    "ItemPool",
    "ItemPoolType",
    "ItemType",
    "KColor",
    "KeySubType",
    "Keyboard",
    "LaserOffset",
    "LaserSubType",
    "Level",
    "LevelCurse",
    "LevelStage",
    "LevelStateFlag",
    "LocustSubtypes",
    "ModCallbacks",
    "Mouse",
    "Music",
    "MusicManager",
    "NpcState",
    "NullItemID",
    "Options",
    "PathFinder",
    "PickupPrice",
    "PickupVariant",
    "PillColor",
    "PillEffect",
    "PlayerForm",
    "PlayerSpriteLayer",
    "PlayerType",
    "PlayerTypes",
    "PoopPickupSubType",
    "PoopSpellType",
    "ProjectileFlags",
    "ProjectileParams",
    "ProjectileVariant",
    "QueueItemData",
    "REPENTANCE",
    "RNG",
    "Random",
    "RandomVector",
    "RegisterMod",
    "RenderMode",
    "Room",
    "RoomConfig",
    "RoomDescriptor",
    "RoomShape",
    "RoomTransitionAnim",
    "RoomType",
    "SFXManager",
    "SackSubType",
    "SeedEffect",
    "Seeds",
    "ShockwaveParams",
    "SkinColor",
    "SortingLayer",
    "SoundEffect",
    "Sprite",
    "StageType",
    "StartDebug",
    "TearFlags",
    "TearParams",
    "TearVariant",
    "TemporaryEffect",
    "TemporaryEffects",
    "TrinketType",
    "UseFlag",
    "Vector",
    "WeaponType",
    "AwaitingTextInput",
    "EID",
    "Encyclopedia",
    "ModConfigMenu",
    "MinimapAPI",
    "StageAPI",
    "g",
    "gd",
    "getParentFunctionDescription",
    "sandboxGetTraceback",
    "sandboxTraceback"
  ],
  "preloadFileSize": 5000,
  "runtime.version": "Lua 5.3"
}

Then, you will see that there are Not showing 2551 further errors and warnings. in the "Problems" pane of VSCode.

Do you have any other extensions on that may be contributing other warnings/errors? I am unable to replicate. I am given many warnings and errors before receiving the “Not showing…” message.

As per your suggestion, I tried disabling all extensions except for the Sumneko one. But something weird seems to be happening.
Open opening the "main.lua" file included in my OP, I get these errors:

They seem to be relating to files inside of the sumneko extension itself.
Do you know why this is happening?

Ah, nevermind, it was create I was using a temp extensions directory of ..
I'm still not able to reproduce your results even with sumneko being on the only thing installed.
Specifically, I am using the following command to launch VSCode:
code . --extensions-dir ../temp/vscode/ --user-data-dir ../temp/vscode/

Then, I install the Sumneko extension (because it starts with everything vanilla with no extensions installed).
Then, I open up main.lua, and I get this:

If it matters, I am on Windows 10:

I also downloaded the main.lua file that is provided in the OP and I get the same problem as Zamiel

I am also on Windows 10.

This is because some low-level diagnostics are not displayed in the window, such as unused-local, tail-space

Why are they not being displayed? Is the language server bugged?

There are 4 levels of diagnostics: error, warning, information, hint.
The diagnostics of hint level are not displayed in the problems window.

I see. Why is the Lua language server outputting hints? Can we change it so that it doesn't use any hints at all?

I see. Why is the Lua language server outputting hints? Can we change it so that it doesn't use any hints at all?

Use diagnostics.groupSeverity or diagnostics.severity


Prevent list queries in graphql in GraphQL transformer V2

Which Category is your question related to?
Queries and authorization in new Transformers v2
Amplify CLI Version
7.6.2
What AWS Services are you utilizing?
Amplify
Provide additional details e.g. code snippets
Hi,
I asked this question some time ago but as we have the new GraphQL transformer V2, things changed because
enum ModelQuery { get list } enum ModelMutation { create update delete }

does not exist in the docs anymore.
https://docs.amplify.aws/cli/graphql/authorization-rules/
I have following schema
type Customer @model @auth(rules: [
  { allow: public, queries: [get], mutations: [create,update]},
  { allow: groups, groups: ["admin"] },
  { allow: groups, groups: ["partner"], queries: [get],  mutations: []}])  {
  id: ID!
  firstName: String
  lastName: String
  email: String
  phone: String
  request: [Request] @connection(keyName: "byCustomer", fields: ["id"])
}

public users can not do list queries. How does that work in GraphQL transformer V2? I can not imagine that I am the only one with that use case. When using "operation" parameter, read means list and get. Especially for security reasons it is often good not to allow list queries. I would love to upgrade to v2 but I really need this feature for our startup project.
How long can we stay in v1? Are there any plans my version is not supported anymore?
BR and thanks in advance.

Hi @dbeck121
For now you can use v1 transformer for this usecase.

Hi @dbeck121
For now you can use v1 transformer for this usecase.

@akshbhu that is good to hear. But what about the future. I do not want to come to a situation where I can't update my app anymore. Its there any plan to solve this or a workaround?

hi @dbeck121 - thank you so much for filing this issue. We're looking into bringing this feature into GraphQL Transformer v2 though we'll unlikely carry over the DX of a separate "ModelQuery" type as in the past. What are your thoughts on collapsing the feature into the ModelOperation type. Example:
type Blog @model @auth(rules: [{ allow: public, operations: [ list, create ]}]) {
  id: ID!
  name: String
}

type Customer @model @auth(rules: [{ allow: public, operations: [ get, create ]}]) {
  id: ID!
  name: String
}

If a customer has both read and at least one of get or list specified, then read takes precedence? Curious if you prefer an error here rather than an implicit assumption.

Hi @renebrandel,
sorry for the late response but today I finally got through my unread email list :)
I like just having additionally "get" and "list" in the ModelOperation. So "read" would be the same as having "get" and "list". I would prefer an error on sth like this
type Blog @model @auth(rules: [{ allow: public, operations: [read, list, create ]}]) {
  id: ID!
  name: String
}

An error like "get, list and read are not to be used together. Please use either read or get and/or list.". Would be easy to solve but finding the issue why list is not possible when having "operations: [read, get, create]" can take some time when not having a clue.


Update BigQueryIO.java

The documentation states this is only for bounded pcollection, but actually the code fails on bounded PCollections. It should read unbounded

Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Make sure there is a JIRA issue filed for the change (usually before you start working on it).  Trivial changes like typos do not require a JIRA issue.  Your pull request should address just this issue, without pulling in other changes.
[x] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue.

[x] Run mvn clean verify to make sure basic checks pass. A more thorough check will be performed on your pull request automatically.
[x] If this contribution is large, please file an Apache Individual Contributor License Agreement.

I believe the comment is correct, feel free to re-open if you feel otherwise.


chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-k8s-22-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 1235

Questions ?
Please refer to the Backport tool documentation


I lost all my Groups and Projects

All of a sudden all my Groups and Projects disappeared. How am I supposed to get them back?

hi @tarikkavaz in what version are you?
As this is saved on a file and if you edit it and it's empty i am affraid but it's lost :(
Although it should not happen in last release, I am working on a safer file/db manager.
Sorry for this :(

Hi João
Thanks for the quick reply
Atom 1.5.3
project-viewer 0.2.31
Btw I didn't open/edit or any kind of files
Hope we can make it work
Tarık Kavaz
On 29 February 2016 at 11:02:53, João Guimarães<EMAIL_ADDRESS>wrote:
hi @tarikkavaz in what version are you?
As this is saved on a file and if you edit it and it's empty i am affraid but it's lost :(
Although it should not happen in last release, I am working on a safer file/db manager.
Sorry for this :(
—
Reply to this email directly or view it on GitHub.

Can you go to Packages -> Project Viewer -> Edit file? It will open the db file, and please check if something is in there. But if you are using latest version, i believe you have lost everything :/ damn

I have no db file, it's gone I guess. damn

sorry about that :((((((((

Not sure if it's related to this bug but the result was the same, groups and projects went bye bye :unamused:
The cause was that my disk was full so project-viewer.json got trunkated. That in itself isn't the bug though, the bug is that project-viewer/atom didn't notify me that the write was incomplete :angry:
Like I said, not sure if this is the same bug (or similar), I can open a specific issue if necessary :smiley:

Damn @bkcsoft :(
I am implementing the atom.storage that itself creates a file in the storage folder and I hope they did a good handling on this.
No matter this new aproach, i will also implement an option for backup to an outsider file or other solution.
There will not be an option for edit the file though.
Do you think this is not a good solution? @bkcsoft and @tarikkavaz.

Maybe you can use gist like Sync Settings for Atom.

hey @tarikkavaz thanks for the share.
definilty will have a look at it

Hi
On Debian Jessie with last atom and project-viewer
On crash system if Atom is opened, project-viewer.json is emptied.
A temporary solution may be to have an automatic backup file.
I presume this file is in open status when Atom session is active. In this case with a simple crash, full disk, ... this file can be purged.

hi @camlafit
yes backup solution is an option on next big release/refactor.
I am deeply sorry for this as there's no solution as it is.
Just ask you for now to backup the file manually please...to be safe

:+1: Same here... all projects and groups lost somehow.  A temporary solution is to backup your ~/.atom/project-viewer.json file any time you add/remove projects.

Have been diging the atom api and other packages and i am using the atom.storageFolder().load and atom.storageFolder().store for the I/O of the file. I guess they did manage to make it stable.
Also, the saving on add/remove projects / groups is already implemented. The problem is the tree-view state that does not emit anything if changed (like collapse a folder, etc) so, that is a problem I haven't found a good solution. Saving it from time to time is a nasty hack... saving in on the destroy /deactivate of the package / Atom is also a bad hack...
So it's taking more time that I antecipated...


Failed to load CFDs: missing field should be an error

If loading from db fails, we only display a warning.
Imho this should be an error so that it is easier detectable.

Imho this should be an error so that it is easier detectable.

Does it prevent operation of the application? If it is not massively severe, a warning should be sufficient. We should definitely monitor for warnings and investigate every single one.

Does it prevent operation of the application? If it is not massively severe, a warning should be sufficient. We should definitely monitor for warnings and investigate every single one.

Yes it did. The maker was unusable unfortunately (cc @klochowicz )


terragrunt: 0.53.8 -> 0.54.0

Description of changes
https://github.com/gruntwork-io/terragrunt/releases/tag/v0.54.0
https://github.com/gruntwork-io/terragrunt/compare/v0.53.8...v0.54.0

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 273041 run on x86_64-linux 1

1 package built:

terragrunt


Song Lyrics for some songs not displayed

The Lyrics for some songs is not displayed but available on musixmatch.
I've uploaded a screenshot here: http://prntscr.com/d3dyxj
Everything else works fine

fixed on master! thx for reporting.


41 initialization method define background and text colors not randomgly

minor fixes I forgot to commit after the PR.

I forgot to merge some minor fixes on the last commit. I will close this branch after this PR. Only to fix minor things (variable names and delete comments).


UX Design - Scanning Team in Gathering Records

Title of ticket: UX Design - Scanning Team in Gathering Records
Description
Creates designs and process flow for users on Scanning Team to have the ability to upload scanned physical records into the new system
Dependencies
Expectations of Scanning Team and Process walkthrough and UX Research will Scanning Team
DOD

[x] Finish reviewing and documents provided by scanning Team
[x] Work on User Flow for how we expect Scanning Team to work in out new system
[ ] Run Flow by dev team
[ ] Create design update for UX Changes based off of completed flow
[ ] Demo design changes to Scanning Team for first level of approval
[ ] Demo out design changes and Sprint Demo

@JHarrietha-AOT, update DOD and split; close this ticket with a revised estimate and create a new ticket for the future in the backlog.


new-flow citations run off to the right

example url: https://dlibwwwcit.services.brown.edu/disa_demo/redesign_citations/

Fixed with commit to new_flow branch: https://github.com/Brown-University-Library/disa_dj_project/commit/f9fdfaefaed011672f91d5249b8a2722e0075871


Fix for failing avalon-count FPCalculator

Avalon-count calculator fails to initialize due to missing default params in FP_DEF_PARAMS dictionary. Simple fix by adding default parameters for avalon-count fingerprints.
Changelogs
Updated FP_DEF_PARAMS dictionary.

Hi @zhu0619
No problem. I have tried running black molfeat/calc/fingerprints.py
But it seems to have no effect:
black molfeat/calc/fingerprints.py
All done! ✨ 🍰 ✨
1 file left unchanged.

@zhu0619
By examining failing test logs it seems that it needed pip install black[jupyter]. Now black changed the file and tests should run correctly.


Move baselines repo to dockstring organization

After a very long delay, this is now done: https://github.com/dockstring/experiments-from-paper.


Implement the CRYPTO_secure_clear_free function

Backport of PR #4044 for 1.1.0 branch.

Merged to 1.1.0 branch.
Thanks!


chore: merge latest main

This PR is automatically generated to merge updates to main to this branch on a regular basis. This is to ensure that the Carbon 11 branch remains in sync with latest fixes and updates to the main Carbon v10 branch.
What did you change?
Merges latest changes from main.
How did you test and verify your work?
This PR should not be merged until the following checks have been made:

[ ] Any conflicts in the branch has been resolved.
[ ] yarn ci-check runs cleanly and all tests pass (done automatically as part of the PR checks).
[ ] the Netlify deploy-preview has been used to ensure that storybook runs and the main published components render correctly.

Conflicts should be addressed, but tagging @davidmenendez to look into AddSelect some more since there were pretty extensive conflicts in AddSelect and now we’re seeing some test/build issues related to it. 😓

Looks like everything is good to go here now 🎉


NiFi 5537 - Create Cypher bundle

Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[ ] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[ ] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[ ] Has your PR been rebased against the latest commit within the target branch (typically master)?

[ ] Is your initial contribution a single, squashed commit?

For code changes:

[ ] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[ ] Have you written or updated unit tests to verify your changes?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.

@mans2singh @mattyb149 H

Come to think of it, I think it needs more testing before opening a PR. That said, got approval to release today.


Camera should follow cursor when using a cursor-based weapon like Girder or Teleport

Currently the camera continually tries to re-focus on the active grub, but following the mouse makes more sense in this case.

Done, but it doesn't follow the cursor, I feel it is more natural to allow the user to pan the camera.
https://github.com/apetavern/sbox-grubs/commit/fc4dd46740caed5d56959f5ae78797eda28bf92b


[Feature request] Updating published notes

Is your feature request related to a problem? Please describe.
Currently, when editing a note that you previously published (for example, when you shared a budget breakdown with a friend and they noticed an issue), you have to re-share the note, which also involves sending a new link to the share partner.
Describe the solution you'd like
A command named something like Updated shared note would be nice that, when invoked, updates the note at the location that the previous link was already pointing to.
It would be extra useful to have a feature that causes selected notes to be updated automatically whenever they change (or whenever they're saved to disk by Obsidian).
Thanks!

Thanks for the request!
I think editing published notes is a good idea, both from a UX perspective as well as cost-saving on hosting (less duplicate content that isn't being read).
I think an Obsidian-idiomatic solution would be to put the Noteshare URL in a note's frontmatter. The plugin can then use this resource for updating (or deleting) the note.
(Note for my future self:) I'm still working out the best way to proof to the server that you are the same user client who posted the original note. The most obvious solution I could come up with is that the server generates an "ownership token" when posting a note, that serves as a authentication token for PUT/DELETE methods. That token will have to be stored in e.g. the data.json file. Another solution could be some kind of zero-knowledge proof scheme, but since pretty much everything about a note is mutable, it's pretty hard to come up with anything concrete.

closing this issue because it is encompassed by https://github.com/mcndt/obsidian-quickshare/issues/25


Handle false positive getSubtreeRoots when connectivity is down

Execution of UpdateSubtreeRootsAction is essential for rest of the sync. When it passes we assume Spend before Sync is available in lightwalletd. If it fails, we fallback to linear sync. When connectivity is not present, this action will do a fallback but that may be a false positive.

merged


Can mentions be filtered for new only?

Issue Description
Making a bot that will respond with a message every time bot's username is mentioned. Can mentions be filtered for only unread ones? Also, what's the max limit of mentions? What if new mentions surpass the limit?
Currently I'm using something like below.
for m in reddit.inbox.mentions(limit=50):
    if m.new:
        c = reddit.comment(m.id)
        c.reply()
        m.mark_read()

System Information
PRAW Version: 4.4.0

Python Version: 2.7
Operating System: ubuntu 14.4

As far as I know you cannot directly get new mentions. You can either get mentions and filter for new, as you are doing. Or you can get new inbox items, and filter for messages. Which approach is more efficient depends on your use case.
Try reddit.inbox.unread for the other approach.


Simple script referencing nuget package shows many errors

Issue Description
I'm trying to get omnisharp to work with nuget package, and I keep getting intellisense errors on every line of the script:

(Sorry for the polish language on the error, it's error: Predefined type 'System.Object' is not defined or imported.)
Some additional observations on this behavior:

If I don't load nuget package, the errors do not appear. I've tried to load different nuget package targetting .net5 and it didn't change anything.
Once those errors start appearing, removing '#r "nuget: ..."' does not help, even with reloading of omnisharp (Ctrl+Shift+P -> Omnisharp: Restart omnisharp). Only restart of vscode helps.
Just after reload of omnisharp, before I start to edit any code, intellisense hints on the methods appear correctly. Only changing any code causes errors to appear.
Running the code and even debugging works fine.

For me it looks like this could be connected to some roslyn analyzers?
Steps to Reproduce

Place following script in csx file:

#r "nuget:Newtonsoft.Json,12.0.3"

var z = 3;

var x = z.ToString();

var y = x + "asdf";

Use omnisharp.json file:

{
  "script": {

    "enableScriptNuGetReferences": true,
    "defaultTargetFramework": "net5.0"
  }
}

After reloading Omnisharp there are no errors/problems show
Type any character in editor window (space/etc)
Errors appear on every line

Expected Behavior
Editing works without any errors
Actual Behavior
Errors on every line
Logs
OmniSharp log

Starting OmniSharp server at 20.11.2020, 15:42:49
Target: c:\Users\hordy\Documents\Hokey
OmniSharp server started.
Path: c:\Users\hordy.vscode\extensions\ms-dotnettools.csharp-1.23.6.omnisharp\1.37.3\OmniSharp.exe
PID: 9876
    Starting OmniSharp on Windows 6.2.9200.0 (x64)

    DotNetPath set to dotnet

    Located 3 MSBuild instance(s)
        1: Visual Studio Community 2019 16.8.30608.117 - "C:\Program Files (x86)\Microsoft Visual Studio\2019\Preview\MSBuild\Current\Bin"
        2: Visual Studio Community 2019 16.8.30717.126 - "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin"
        3: StandAlone 16.8.0 - "c:\Users\hordy\.vscode\extensions\ms-dotnettools.csharp-1.23.6\.omnisharp\1.37.3\.msbuild\Current\Bin"

    Registered MSBuild instance: Visual Studio Community 2019 16.8.30717.126 - "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin"

    Detecting Cake files in 'c:\Users\hordy\Documents\Hokey'.

    Could not find any Cake files

    No solution files found in 'c:\Users\hordy\Documents\Hokey'

    Detecting CSX files in 'c:\Users\hordy\Documents\Hokey'.

    Found 1 CSX files.

    Searching for compilation dependencies with the fallback framework of 'net5.0'.

    Added CSX project 'c:\Users\hordy\Documents\Hokey\Test.csx' to the workspace.

    Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.CSharpFormattingWorkspaceOptionsProvider, Order: 0

    Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.Completion.CompletionOptionsProvider, Order: 0

    Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.RenameWorkspaceOptionsProvider, Order: 100

    Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.ImplementTypeWorkspaceOptionsProvider, Order: 110

    Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.BlockStructureWorkspaceOptionsProvider, Order: 140

    Configuration finished.

    Omnisharp server running using Stdio at location 'c:\Users\hordy\Documents\Hokey' on host 17176.

Environment information
VSCode version: 1.51.1
C# Extension: 1.23.6
Dotnet Information
Zestaw .NET SDK (odzwierciedlenie dowolnego pliku global.json):
 Version:   5.0.100
 Commit:    5044b93829
�rodowisko uruchomieniowe:
OS Name:     Windows
OS Version:  10.0.18363
OS Platform: Windows
RID:         win10-x64
Base Path:   C:\Program Files\dotnet\sdk\5.0.100\
Host (useful for support):
Version: 5.0.0
Commit:  cf258a14b7
.NET SDKs installed:
1.0.0-preview2-003131 [C:\Program Files\dotnet\sdk]
1.0.0-preview4-004233 [C:\Program Files\dotnet\sdk]
1.0.0-rc4-004771 [C:\Program Files\dotnet\sdk]
1.0.0 [C:\Program Files\dotnet\sdk]
1.0.1 [C:\Program Files\dotnet\sdk]
1.0.4 [C:\Program Files\dotnet\sdk]
1.1.0 [C:\Program Files\dotnet\sdk]
2.0.0 [C:\Program Files\dotnet\sdk]
2.0.2 [C:\Program Files\dotnet\sdk]
2.1.2 [C:\Program Files\dotnet\sdk]
2.1.4 [C:\Program Files\dotnet\sdk]
2.1.100 [C:\Program Files\dotnet\sdk]
2.1.101 [C:\Program Files\dotnet\sdk]
2.1.104 [C:\Program Files\dotnet\sdk]
2.1.200-preview-007517 [C:\Program Files\dotnet\sdk]
2.1.200-preview-007576 [C:\Program Files\dotnet\sdk]
2.1.202 [C:\Program Files\dotnet\sdk]
2.1.400 [C:\Program Files\dotnet\sdk]
2.1.402 [C:\Program Files\dotnet\sdk]
2.1.500 [C:\Program Files\dotnet\sdk]
2.1.503 [C:\Program Files\dotnet\sdk]
2.1.600-preview-009426 [C:\Program Files\dotnet\sdk]
2.1.600-preview-009472 [C:\Program Files\dotnet\sdk]
2.1.600-preview-009497 [C:\Program Files\dotnet\sdk]
2.1.602 [C:\Program Files\dotnet\sdk]
2.1.700 [C:\Program Files\dotnet\sdk]
3.0.100-preview6-012264 [C:\Program Files\dotnet\sdk]
3.0.100 [C:\Program Files\dotnet\sdk]
5.0.100-rc.2.20479.15 [C:\Program Files\dotnet\sdk]
5.0.100 [C:\Program Files\dotnet\sdk]
.NET runtimes installed:
Microsoft.AspNetCore.All 2.1.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.1.4 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.1.6 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.1.7 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.1.9 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.1.11 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.1.21 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.1.23 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.2.7 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.2.8 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.App 2.1.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.1.4 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.1.6 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.1.7 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.1.9 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.1.11 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.1.21 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.1.23 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.2.7 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.2.8 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 3.0.0-preview6.19307.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 3.1.7 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 3.1.9 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 5.0.0-rc.2.20475.17 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 5.0.0 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 1.0.1 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 1.0.3 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 1.0.4 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 1.0.5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 1.1.0 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 1.1.1 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 1.1.2 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.0.0 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.0.3 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.0.5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.0.6 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.0.7 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.0.9 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.2 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.4 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.6 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.7 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.9 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.11 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.21 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.23 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.2.7 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.2.8 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 3.0.0-preview6-27804-01 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 3.1.7 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 3.1.9 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 5.0.0-rc.2.20475.5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 5.0.0 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 3.0.0-preview6-27804-01 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 3.1.7 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 3.1.9 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 5.0.0-rc.2.20475.6 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 5.0.0 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
To install additional .NET runtimes or SDKs:
https://aka.ms/dotnet-download

Visual Studio Code Extensions

Extension
Author
Version

cpptools
ms-vscode
1.1.2

csharp
ms-dotnettools
1.23.6

vscode-arduino
vsciot-vscode
0.3.3

vscode-autohotkey
slevesque
0.2.2

xml
DotJoshJohnson
2.5.1

I've also tried using #r 'path to nuget dll' and I'm still gettings the same errors

according to your log you are trying to use scripting with .NET 5.0, the support for that was only merged a week ago (https://github.com/OmniSharp/omnisharp-roslyn/pull/2012) and has not been released yet.
you may try to set "omnisharp.path":"latest' which will install the pre-release OmniSharp server to see if it helps.


Demonstration for supporting bin target fsays

Hi! I'd love to be able to intall fsays using cargo but...
I'm struggling to understand whether there is a way to install the fsays binary using cargo install --bin. At first glance in the Cargo Book it seems that there might be a way to do it with cargo install ferris-says --bin fsays but that fails because there is not a bin target named fsays.
❯❯ cargo install ferris-says --bin fsays
    Updating crates.io index
  Installing ferris-says v0.2.1
error: failed to compile `ferris-says v0.2.1`, intermediate artifacts can be found at `/home/dlevin/nobackup/cargo`

Caused by:
  no bin target named `fsays`

To your knowledge, is this the right way to go about supporting cargo install for fsays?
Alternately, if there's no way to achieve installing fsays using cargo install I'd be happy to update the README with a sentence or two explaining that the user must clone the git repo and invoke cargo install --path . or something like that.

hi @mgattozzi -- I realize that tests fail on this PR, but perhaps you can understand what I'm trying to achieve here and if so, provide some guidance.
Thanks in advance!

@cryptobanana you did nothing wrong! I had just never uploaded the binary version to crates.io I just uploaded it so you should be able to install it with cargo install fsays now!

I forgot to close this PR since the issue was resolved! Going to do that now.


Use all of aqua tests

This PR adds more aqua tests and lowers the limit on the ambiguity tests.

bors r+


Allow all Variant types to be added as project settings

This makes the project settings editor's type selection consistent with the Array/Dictionary editors. Note that I intentionally exlcuded "Nil" as a valid type, since it doesn't make much sense. If this is merged, we may want to do the same in the Array/Dictionary editors as well.
Preview
These can now all be added without having to edit project.godot manually.

Thanks!


Specify width to avoid overflow

Summary of changes
Asana Ticket: 🐞 Line Diagram | IE11 stop content width overflows
Content overflows for IE in Line Diagram when the number of connections is too big. It needs to wrap.
Before:

After:

This has been checked in IE, Chrome, Firefox and Safari.

@alicia-mbta LGTM, have you verified that this change doesn't have any side-effect in Chrome/FF?

I checked Chrome, Firefox and Safari and didn't notice anything strange. I can double check and will also tag Ingrid.

@alicia-mbta looks good to me! 👍 Also, no issues observed in other browsers, also checked safari iOS.


Add Dice Game by javaScript

https://github.com/aaryan2134/Engineering-Resources/pull/12
A very similar project is already under review. You can collaborate or you can make changes as requested in the other repo.
If the changes are not made by the other person then yours will be accepted.


Screensharing via jitsi does not work via snap

My Setup

Operating System: Debian bookworm

App Version: 3.8.1

Installation type: snap

Desktop Environment: i3

[x] I have tested with the latest version

[x] I can simulate the issue easily

Description
I can't share my screen in a jitsi video call.
I have taken a look at the snap permissions, can't identify an issue there (had to enable camera manually for video to work in jitsi):
$ snap connections rocketchat-desktop
Interface                 Plug                                       Slot                             Notes
audio-playback            rocketchat-desktop:audio-playback          :audio-playback                  -
audio-record              rocketchat-desktop:audio-record            -                                -
browser-support           rocketchat-desktop:browser-support         :browser-support                 -
camera                    rocketchat-desktop:camera                  :camera                          manual
content[gnome-3-28-1804]  rocketchat-desktop:gnome-3-28-1804         gnome-3-28-1804:gnome-3-28-1804  -
content[gtk-3-themes]     rocketchat-desktop:gtk-3-themes            gtk-common-themes:gtk-3-themes   -
content[icon-themes]      rocketchat-desktop:icon-themes             gtk-common-themes:icon-themes    -
content[sound-themes]     rocketchat-desktop:sound-themes            gtk-common-themes:sound-themes   -
desktop                   rocketchat-desktop:desktop                 :desktop                         -
desktop-legacy            rocketchat-desktop:desktop-legacy          :desktop-legacy                  -
gsettings                 rocketchat-desktop:gsettings               :gsettings                       -
home                      rocketchat-desktop:home                    :home                            -
network                   rocketchat-desktop:network                 :network                         -
opengl                    rocketchat-desktop:opengl                  :opengl                          -
pulseaudio                rocketchat-desktop:pulseaudio              :pulseaudio                      -
screen-inhibit-control    rocketchat-desktop:screen-inhibit-control  :screen-inhibit-control          -
unity7                    rocketchat-desktop:unity7                  :unity7                          -
upower-observe            rocketchat-desktop:upower-observe          :upower-observe                  -
x11                       rocketchat-desktop:x11                     :x11                             -

Current Behavior
There's no desktop or window to select in the selection dialog for what to share.
Expected Behavior
It should behave as it does in a browser, showing windows and desktops to select for sharing.

You will need to enable the permission on the snap store. I don't know why but it doesn't enables by default.

@jeanfbrito thanks, but which one? They are all enabled AFAICS

The one that is disabled is not enablable.

This is a bug in Rocket Chat Server not Rocket Electron app.
https://github.com/RocketChat/Rocket.Chat/issues/25112
Although using Rocket.Chat.Electron 3.6.0 or below, will also result in a working version (apparently permissions where not checked correctly in older versions).

Facing issues in screen sharing using the desktop app.

Version of Rocket.Chat Server: 5.4.2
Operating System: 22.04.1 LTS (Jammy Jellyfish)
Deployment Method: Snap
Desktop App: 3.8.16

It was initially working for me as expected. When I do the screen sharing for the first time using the desktop app from windows, a pop-up comes asking for the permission. But for other team members, there weren't any such pop-ups appeared. After I tried to uninstall and re-install the desktop app, it doesn't work for me either.


ISSUE#1.3.1- SANTIAGO - ISSUE TESTING - README DOCUMENTATION

What would you like to share?
Weekly Build Documentation Template - Issues [Insert Issue Numbers]
Repository: [Insert Repository Name with Link]

Week [Insert Week Number] - Documentation for Issues [Insert Issue Numbers]
Objective:
Document the progress for the following issues:

Issue #X.X: [Insert Issue Title (e.g., Feature Development)]
Issue #X.X: [Insert Issue Title (e.g., Testing and Validation)]
Issue #X.X: [Insert Issue Title (e.g., Pull Request Preparation)]

Issue #X.X: [Insert Issue Title (e.g., Feature Development)]
Week [Insert Week Number] Tasks:

[ ] Define the core components of the feature or functionality.
[ ] Implement the feature in the relevant language or framework.
[ ] Ensure that input/output specifications are correctly handled.

Progress Summary:

Feature Development:

The initial design is complete, and the basic implementation has been written.
Code is modularized to enhance readability and maintainability.

Challenges Encountered:

Handling edge cases required additional consideration, such as invalid input or specific data structure constraints.

Key Commit:

feat: implemented core functionality for [Insert Feature Name]

Next Steps:

Focus on refining edge cases and improving error handling or optimization.

Issue #X.X: [Insert Issue Title (e.g., Testing and Validation)]
Week [Insert Week Number] Tasks:

[ ] Develop comprehensive test cases (typical, boundary, and edge cases).
[ ] Use appropriate testing tools (e.g., JUnit, PyTest, etc.).
[ ] Debug the implementation using test-driven development.

Progress Summary:

Test Case Development:

Basic tests for typical cases have been written.
Boundary cases (e.g., small input, large input, etc.) are also covered.

Challenges Encountered:

Handling edge cases that cause the system or algorithm to fail unexpectedly, such as invalid inputs.

Key Commit:

test: added basic and edge case tests for [Insert Feature/Functionality Name]

Next Steps:

Conduct performance and stress testing to ensure the feature handles large datasets or complex input efficiently.

Issue #X.X: [Insert Issue Title (e.g., Pull Request Preparation)]
Week [Insert Week Number] Tasks:

[ ] Prepare the code for submission in a pull request.
[ ] Ensure the repository follows coding guidelines and best practices.
[ ] Create documentation for reviewers and link related issues.

Progress Summary:

Pull Request:

The pull request draft is ready, with all changes documented and code commented for clarity.
Linked all relevant issues for proper tracking.

Challenges Encountered:

Ensuring all tests pass before submission and integrating feedback from code reviews.

Key Commit:

chore: prepared pull request and linked relevant issues

Next Steps:

Finalize the pull request submission and ensure that the feature passes all required tests.

Commit Guidelines for This Week:
Each commit will adhere to the following format for consistency:

Commit Message Format:

feat: [description of feature]
fix: [description of bug fix]
test: [description of test]
refactor: [description of refactoring task]

Example Commit Messages for this Week:

feat: implemented core functionality for [Insert Feature]
fix: handled edge cases for [Insert Feature]
test: added test cases for [Insert Feature]

Next Steps and Upcoming Tasks:

Continue refining the feature based on peer feedback.
Finalize testing and documentation for the final pull request.
Conduct performance testing and review for optimizations.

Version Control Summary:
This section summarizes all commits made during the week to ensure proper tracking of changes.

Date
Changes Made
Commit ID

[Insert Date]
Implemented basic feature functionality
[Commit ID]

[Insert Date]
Added test cases for typical and edge cases
[Commit ID]

[Insert Date]
Refactored code and prepared pull request
[Commit ID]

Documentation Guidelines and References:
For more information on how to structure the repository, make effective commit messages, and ensure security, refer to:

How to Write READMEs for Repositories
How to Write Effective Commit Messages
How to Secure Repositories

Additional information
No response

Weekly Build Documentation Template - Issues TheAlgorithms#5564
Repository: https://github.com/TheAlgorithms/Java/issues/5564
Week 5 - Documentation for Issue TheAlgorithms#5564
Objective:
Document the progress for the following issue:
Issue TheAlgorithms#5564: Adding the Travelling Salesman Problem (BFS Algorithm in Java)
Feature Development
Week 5 Tasks:
Could you describe the essential elements of the Travelling Salesman Problem (TSP) solution?
Implement the BFS algorithm in Java to solve the TSP.
Ensure that input/output specifications for the BFS solution are correctly handled.
Progress Summary:
Initial Design: Completed for TSP using Java's Best-First Search (BFS) algorithm.
Implementation: Basic functionality is working with a modular approach, enhancing readability and maintainability.
Input Handling: Designed to accommodate a distance matrix for multiple cities, ensuring scalability for various input sizes.
Challenges Encountered:
Permutation Handling: Addressed the complexity of handling a large number of city permutations, requiring optimization.
Edge Cases: Incorporated handling for circular paths and cities with zero distances, adding complexity in validating solution correctness.
Key Commit:
feat: implemented core functionality for Travelling Salesman Problem using BFS algorithm
Next Steps:
Refine the handling of cities with multiple paths of equal distances.
Optimize performance for larger inputs, ensuring scalability.
Testing and Validation
Week 5 Tasks:
Develop comprehensive test cases, covering typical, boundary, and edge cases.
Use JUnit to validate the Java BFS implementation.
Debug the BFS solution using a test-driven development approach.
Progress Summary:
Test Cases: Developed for typical cases; boundary cases for small and large city inputs.
Additional Tests: Designed for circular paths and cities with equal distances.
Challenges Encountered:
Behavior Validation: Ensuring correct BFS behavior when multiple cities have similar paths or costs.
Large Inputs: Managing performance for large datasets where optimization becomes critical.
Key Commit:
test: added basic and edge case tests for Travelling Salesman Problem using BFS
Next Steps:
Conduct performance testing to confirm that the BFS algorithm efficiently handles large datasets.
Add more test cases to validate edge scenarios, such as cities with zero distances.
Pull Request Preparation
Week 5 Tasks:
Prepare the BFS implementation for submission in a pull request.
Ensure compliance with Java coding guidelines and best practices in the repository.
Create documentation for reviewers, linking related issues for context.
Progress Summary:
Pull Request: The draft is ready, with detailed comments and documentation on the BFS approach for TSP.
Issue Linking: Linked all relevant issues to maintain tracking of performance and testing aspects.
Challenges Encountered:
JUnit Compliance: Ensuring all JUnit tests pass before submission.
Code Review Feedback: Addressing review feedback, especially regarding optimization improvements.
Key Commit:
chore: prepared to pull requests and linked relevant issues for Travelling Salesman Problem
Next Steps:
Please go ahead and finalize the pull request submission after confirming the successful performance and test results.
Ensure the feature passes all required tests before merging into the main branch.
Commit Guidelines for This Week:
Each commit will adhere to the following format for consistency:
Commit Message Format:
feat: for new features
fix: for bug fixes
test: for test cases
refactor: for refactoring tasks
Example Commit Messages:
feat: implemented core functionality for Travelling Salesman Problem using BFS
fix: handled edge cases for BFS implementation
test: added test cases for the Travelling Salesman Problem in the BFS algorithm
Next Steps and Upcoming Tasks:
Refine the BFS solution based on peer feedback.
Complete performance testing and finalize documentation.
Conduct stress testing to ensure scalability for large datasets.


Update screenshot

...I forgot in the last PR...

I see only public/images/help/dev-upload-en-catkeys.png was updated.
Can you remove the other files?

The other PNGs were optimized with "optipng -o 5", decreasing their size by about 25%.

OK, thanks!


Gradio Blocks Event Space

Hi, great work on this Gradio Space for cryptogans, would you also be interested in making a blocks version of this for the Gradio Blocks Party Event https://huggingface.co/Gradio-Blocks, or of another model, thanks!

Hey @AK391 thank you very much for the invitation, I will look into that for sure.


Our Team format

Leadership Team -
can we change it to 5 people in first row, 5 in the second row (instead of 6 and 4)

I think this is a dupe of #752, so gonna close this one :)


"Connect to Strata Scratch with Python" link is broken

The link included in the pandas tutorial notebook: Connect to Strata Scratch with Python is broken.
I found the correct link to the source notebook below:
https://colab.research.google.com/drive/1tHxAbgbxM60VUIrVQW508EwB1b3wFk5g

I opened a pull request to resolve the issue here: https://github.com/kc-ck/BUS774-G200/pull/2


Add debug mode

Add a debug mode accessed by tag on command line. Currently when an error occurs in the markdown parsing, a message is logged and the HTML is set to nothing (''). If debug mode is active, it sets the HTML to

 which is styled red and displays on output.
This would allow authors to easily see on output where errors are occurring, to complement the log file.

Previous system - outdated


community[minor] langchain[patch]: convert class tool to openai function

Covert tools to a JSON format description for Openai. Previously, the function format_tool_to_openai_function does not return the correct parameter name when given a tool that subclassing the BaseTool:
import os
from langchain.agents import load_tools
from langchain.tools.render import format_tool_to_openai_function
os.environ['SERPER_API_KEY'] = '1' * 40
tools = load_tools(["google-serper"])
format_tool_to_openai_function(tools[0])['parameters']
# {'properties': {'__arg1': {'title': '__arg1', 'type': 'string'}}, 'required': ['__arg1'], 'type': 'object'}

This patch is trying to fix it. The correct output should be {'properties': {'query': {'title': 'Query', 'type': 'string'}}, 'required': ['query'], 'type': 'object'}

Turns out it is not that easy to make it compatible with all the tools. There are lots of choices to define a tool:

a simple function
a subclass of BaseTool, which has a _run method plays the function role. For example, GoogleSerperRun
a subclass of Tool, which has a .func and/or .coroutine attribute as a function. Furthermore, the function can be a run method of Chain. For example, the Calculator

Since the function may be a method of langchain.chains.base.Chain, to identify it, we have to import langchain.chains.base.Chain. That is why I moved format_tool_to_openai_function from the community package to the langchain package.

The errors are mainly due to an extra file __init__.py in the libs folder(probably created by IDE, I didn't even notice it).

Rebase to resolve the conflicts.
The make lint_package error can be fixed if we remove the .mypy_cache and .ruff_cache folder. I've tested on my laptop.

Hi @hwchase17 , what do you think about this PR, can you run the workflow again?

Hi @baskaryan , I saw you reopen this issue. Just let you know that I have no idea how to solve the CI errors, so I do not want to waste time on this PR.
I'll be closing it for the time being. Should you be able to assist in resolving it, your help would be greatly appreciated.


About .nbs

Sorry about I don't know all the function about OpenNoteBlockStudio. How to export the song to .nbs file? I just saw the datapack, mp3 and schematic only.

NBS is just the format Note Block Studio saves their files as, so to save as NBS you just pick 'Save song'.

OK, thank you so much


Sym-link dev setup broken for web worker extensions

My dev setup has always been to create a sym-link from my extension into the code-oss. That allows me to develop/debug extensions and VS Code at the same time. Since a week or two this has been broken for web extensions, like GH issue notebooks.

Yeah, seems to go away with "enable-browser-code-loading": false

Possible, the renderer cannot and should not make requests to file:. The workbench "site" is now handled like any other website, so CORS kicks in (this was not the case before).
Refused to connect to 'file:///Users/jrieken/.vscode-oss-dev/extensions/vscode-github-issue-notebooks/dist/extension-web.js' because it violates the following Content Security Policy directive: "connect-src 'self' https: ws:".

What code produces a file URI? That looks like a missing adoption of FileAccess.asBrowserUri to me.

What code produces a file URI? That looks like a missing adoption of FileAccess.asBrowserUri to me.

Maybe, but when adding asBrowserUri before fetching the script nothing changes. Tho, I do see that the uri stay unchanged because platform.isNative reports false on desktop/webworker.

I would not think that the symlink plays a role here but rather web worker extensions in general. Is this something we ship to our users or just for dev purposes?

Is this something we ship to our users or just for dev purposes?

It is user facing. It is something we overlooked when we moved to vscode-file://. I will investigate what to do and let you know what I find out.

When running from source, the following can be used to easily troubleshoot this:
	"extensions.webWorker": true,
	"remote.extensionKind": {
		"ms-vscode.vscode-github-issue-notebooks": "web",
		"vscode.typescript-language-features": "web",
		"vscode.css-language-features": "web",
	},

Thanks!


How to calculate latency or delay?

I am trying to model non - volatile memories for hardware accelerators. I am using the eyeriss architecture as the base architecture and using the table-based plugin. Although there is a change in the value of area and energy (on changing area and energy) but no change in the number of clock cycles on changing the value of latency. Any guesses what could be the possible reason for that?
I added this to the primitive component file.
    name: STTRAM
    attributes:
      technology: sttram
      width: 64
      depth: 512
      n_rdwr_ports: 1
      n_banks: 1
      latency: 100ns
    actions:
      - name: read
      - name: write
      - name: idle`

And this as the table-based plugin
technology,width,depth,n_rd_ports,n_wr_ports,n_rd_wr_ports,n_banks,latency,action,data_delta,address_delta,energy,area
45nm,64,16384,0,0,2,32,100ns,read,0,0,5,30000
45nm,64,16384,0,0,2,32,100ns,write,0,0,5,30000
45nm,64,16384,0,0,2,32,100ns,idle,0,0,5,30000

(These are just dummy values)

Ok, I just found out that clock cycles are calculated using bandwidth instead of latency. So can I input its value using table-based plugins?

The latency in the component's hardware attributes is only used for calculating the energy and area. Timeloop captures the performance of the design with number of clock cycles. The number of clock cycles will not be affected by component hardware attributes. Please take a look at this explanation here: https://github.com/NVlabs/timeloop/issues/56

Thanks a lot, mam :-)


[Frontend] ContentAttributes support ?

Does the DVB-I reference client support DVB-I ContentAttributes , such as VideoConformancePoint element ?
Thanks in advance,
Benjamin

No, the evaluation of specified ContentAttributes against device capabilities is not provided in the current release. Player capabilities need to be exposed to the application, but then it could become part of the service instance filtering algorithm.

We can add this to the backlog

@bpeexc what would you expect from the DVB-I Reference Client if it were to example the ContentAttributes?
Should it disable any DASH delivered service instances that cannot be played in the <video> element?
How can the DVB-I application 'know' what the supported broadcast receiver codecs are?

Assuming we want the reference app to stick to standard HTML5 (and omit HbbTV extensions) then it might make sense to discard broadband service instances where MediaSource.isTypeSupported returns false.

Yes, we would need to define a mapping between DVB classification scheme terms and type for isTypeSupported().
is there some equivalent of isTypeSupported for the video/broadcast object or would any 'unplayable broadcast services' be removed during channel scan?

is there some equivalent of isTypeSupported for the video/broadcast object or would any 'unplayable broadcast services' be removed during channel scan?

Normally the latter. Additionally, the broadcast codecs supported are listed in the XML capabilities as a list of  elements whose value is one of those in either DVB VideoConformancePointsCS:2017 or a AudioConformancePointsCS:2017.

I just stumbled upon the decodingInfo API which could be used in conjunction with <VideoAttributes> and <AudioAttributes> to determine if a service instance is playable.

I just stumbled upon the decodingInfo API which could be used in conjunction with <VideoAttributes> and <AudioAttributes> to determine if a service instance is playable.

It does look widely supported - https://caniuse.com/mdn-api_mediacapabilities_decodinginfo - although how accurate the answers are remains to be seen.


certificate alerting calculates back in hours instead of days

Hi,
Found a small issue when we noticed certificates that were expiring in less than 2 weeks did not trigger an alert mail. I'm assuming of course you would calculate the amount of days back as said in the front-end but in https://github.com/codebude/cpi-dashboard/blob/master/IFlow/Source/src/main/resources/script/alertCalculateAlerts.groovy on line 67 it calculates with hours so instead of checking for 14 days it checks for 14 hours until expiry of the certificate.
KR,
Thomas

Already done that (https://github.com/engelmohr/cpi-dashboard/commit/e9b42c93d3f59d3b1484f5e40772f7d6a5e922d6). I can send you another PR with the built zip file if you like.
Also since lots of things for the setup have changed (e.g. no more unofficial APIs needed and thus no more basic auth user) I could also update the README if you want. Just let me know what you think.
Best regards,
Jan

Hi @engelmohr ,
you're right. The readme (i guess you mean this blog post: https://blogs.sap.com/2019/08/19/advanced-monitoring-and-health-check-with-realcores-cpi-dashboard/ ) doesn't reflect the current codebase in this repository. The blog still reflects the latest release (1.0.4): https://github.com/codebude/cpi-dashboard/releases
I guess updating the readme makes only sense, when also publishing the current version (1.0.5) of the dashboard as new release. But before doing so, we should see that the current codebase is strong enough for a stable build. Currently I get some 500er errors for some of the endpoints.

Let me/us first fix them, before packaging and releasing 1.0.5 and in consequence of this updating the readme. Do those errors occur for you, too?

One more side note, @engelmohr . You wrote:

[...] e.g. no more unofficial APIs needed and thus no more basic auth user [...]

I fear that's not correct. The basic auth user is still needed for the following features:

List endpoints: https://github.com/codebude/cpi-dashboard/blob/master/IFlow/Source/src/main/resources/script/loadEndpointList.groovy#L42
Get development packages:
-- For Diffutils: https://github.com/codebude/cpi-dashboard/blob/master/IFlow/Source/src/main/resources/script/diffCompareIFlows.groovy#L79
-- For version comparison: https://github.com/codebude/cpi-dashboard/blob/master/IFlow/Source/src/main/resources/script/remoteTenantArtifactsComparison.groovy#L132

For all of those there are official APIs now (https://api.sap.com/api/IntegrationContent/resource). So it should be possible to avoid the use of the basic auth credentials in the future. But right now, the basic auth credentials are still needed.

Hi @codebude,
yes, I mean your SAP blog post :)
So I just checked on our CPI and I do not see any 500 errors whatsoever for none of the endpoints. I will double-check and do a fresh re-pack of the current source as of commit https://github.com/codebude/cpi-dashboard/commit/269c701af1ad3acecd3b09a66c80fe8a3d52caed to make sure I did not miss anything.

@engelmohr  The 500 http errors were my fault. Some old password in the basic auth credential... At least this shows, that the basic auth credentials are still needed. ;-) So before releasing the current version, I/we should eliminate the usage of those unofficial APIs and thus ensure that no basic auth credentials are needed any longer.
After that, I'm fine with releasing the a new version.

You're right. I missed those instances of basic auth. I somehow thought it's not needed anymore. Anyways I will refactor this within this week given you don't want to do it yourself ;-)

Hi @engelmohr ,
No problem, take your time. I am well aware of the spare time issue. I've also too much projects/ideas for too less spare time. But every bit counts/each pull request, no matter how small it is, brings us forward. :-)

lol at my silly comment actually getting this immediate response.
It was an easy fix but boy does it have consequences irl


Dashboard with secured API don't work with another port than 8080

Do you want to request a feature or report a bug?
Bug
Did you try using a 1.7.x configuration for the version 2.0?

[ ] Yes
[x] No

What did you do?
Launched taefik with the following config:
[global]
  checkNewVersion = true
  sendAnonymousUsage = true

# Default:
[entryPoints]
  [entryPoints.web]
    address = ":80"

  [entryPoints.websecure]
    address = ":443"

  [entryPoints.traefik]
    address = ":8000"

[http.routers.my-api]
    entryPoints = ["traefik"]
    rule="PathPrefix(`/api`) || PathPrefix(`/dashboard`)"
    service="api@internal"
    middlewares=["auth"]

[http.middlewares.auth.basicAuth]
    users = [
        "test:$apr1$H6uskkkW$IgXLP6ewTrSuBkTrqE8wj/",
      ]

[api]
  dashboard = true
[ping]
[providers.docker]

What did you expect to see?
dashboard at http://localhost:8000
What did you see instead?
404 page
Output of traefik version: (What version of Traefik are you using?)
Codename:     montdor
Go version:   go1.13
Built:        2019-09-10T17:10:04Z
OS/Arch:      linux/amd64

Other notes
Note that this does work when api.insecure=true is set in the toml file.  But the auth middleware is ignored when api.insecure is true.
This is related to #5363. Since that ticket was closed, I opened a new one.

The dashboard need the API, and the API need to be secure.
Duplicate of #5363
https://github.com/containous/traefik/issues/5363#issuecomment-530729082
Maybe your problem is more related to the PathPrefix, you can follow  #5374
Duplicate of #5374

I tried removing the rule entirely and this still does not work for me.

Try to add a Host rule.
Come in our support forum https://community.containo.us/, I will help you.

I reopen because I reproduce the bug.

I made a mistake in my local configuration.
It works, so I close.

@ldez could you please let me know what was the mistake in your local configuration and what did you change.

@tanwarsatya - I believe the mistake was that the dynamic configuration was not in a separate file.
Separating the dynamic configuration into another file fixed this for me.

My mistake was just a typo in a port.


What versions of XLIFF does it support?

What versions of XLIFF does it support?

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

ID: 645a2b61-25b4-897e-2653-af01487b5c35
Version Independent ID: c4b7cb6c-8e38-ade5-7eaf-aacc705abcb8
Content: What is Microsoft Azure Cognitive Services Document Translation? - Azure Cognitive Services
Content Source: articles/cognitive-services/Translator/document-translation/overview.md
Service: cognitive-services
Sub-service: translator-text
GitHub Login: @laujan
Microsoft Alias: lajanuar

@NelsonJAbbey
Thanks for your feedback! We will investigate and update as appropriate.

Hi @NelsonJAbbey
Please go through the below link for your reference.
https://learn.microsoft.com/en-us/azure/cognitive-services/Translator/document-translation/reference/get-supported-document-formats#:~:text="format"%3A "XLIFF"%2C
            "fileExtensions"%3A [
                ".xlf"
            ]%2C
            "contentTypes"%3A [
                "application/xliff%2Bxml"
            ]%2C
            "versions"%3A [
                "1.0"%2C
                "1.1"%2C
                "1.2"
            ]

@
We are going to close this thread, if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.


[CARBONDATA-1478]update compaction documentation

In order to easier to understand, update the description about compaction.

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/107/

Build Success with Spark 1.6, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/8/

SDV Build Fail , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/734/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/156/

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/786/


Support custom attributes from GCS

As the title says.

And GCA, please! Would be lovely to be able to specify resource tracker initializers from arbitrary attributes/stats such as flavored ER variants. It's easy enough to register those attributes in GCA, but very few character sheets support them, let alone VTTs.


Data-Parallel LDE in Row-Major Form

This PR attempts to implement Data-Parallel ( using Rayon ) LDE s.t. polynomials are laid out over segments.

Superseded by #163.


Remove timezone_database.h from source control

Now that #12 is closed, make database can be added as a dependency to ensure the correct timezone database is generated before the library is compiled.

This would add a build dependency on mono/dotnet stuffs, I don't know if that's the best idea. I think something like #24 is more viable.

If we can get #24 working (which shouldn't be too difficult), I agree.


if using temporary credentials the token is needed

We use temporary credentials at the command line so need the AWS_SESSION_TOKEN to be passed to the provider.

Hi @vsilgalis :wave: Thanks for your contribution. Also, I am happy to know if you have any feedback using terradozer. You're kind of an early tester :-) terradozer is finished though, but I haven't released it yet "officially".

Hi @vsilgalis 👋 Thanks for your contribution. Also, I am happy to know if you have any feedback using terradozer. You're kind of an early tester :-) terradozer is finished though, but I haven't released it yet "officially".

Yeah, we just happen to use awsweeper and noticed an error when trying to run it.  Digging through the code pointed us here. :)

@vsilgalis I see, added support for AWS_SESSION_TOKEN in awsweeper: https://github.com/cloudetc/awsweeper/issues/81#issuecomment-592735261

Yeah saw that.  Thanks for the quick turnaround!


Add smtp_starttls flag to config

I need to work with a mail server that does not support STARTTLS.  This PR adds a config file setting (defaulting to True) to decide when to activate STARTTLS.


changed typescript plugin to accept --build parameter as it needs to …

Changes
TypeScript plugin will now be able to use other tsconfig as --build needs to be the first parameter for tsc. It could be of course workaround with switching from tsc to tsc --build someconfig.json, but it is not elegant as --build flag is the tsc param.
Testing
Tests are passing. No need to update test.
Docs
No need to update as this is a bug fix.
By the way I am interested in actively contributing to snowpack as it looks promising :).

LGTM! And sure thing, would love your help contributing!

LGTM! And sure thing, would love your help contributing!


How to use "global" domElement/domElementGetter?

Describe the bug or question
In the documentation, there is a note about using domElementGetter:

domElementGetter: (optional) A function that is given the single-spa props and returns a DOMElement. This dom element is where the React application will be bootstrapped, mounted, and unmounted. Note that this opt can be omitted. When omitted, the domElementGetter or domElementcustom single-spa props are used. To use those, do singleSpa.registerApplication({ name, app, activeWhen, customProps: {domElementGetter: function() {...}} }) or singleSpa.registerApplication({ name, app, activeWhen, {domElement: document.getElementById(...)} }). If no dom element can be found through any of those methods, then a container div will be created and appended to document.body, by default.

However, I am not able to get this running:
registerApplication({
  name: app.appName,
  app: app.loadFn,
  activeWhen: app.activeFn,
  customProps: {
    customProps,
    domElementGetter: () => {
      console.log('dom element getter');
      return document.getElementById(app.appName) // the DOM element exists in the document
    }
  }
});

It keeps throwing error that it cannot find the dom element for a specific app:

SKIP_BECAUSE_BROKEN: Cannot mount react application 'my-app' without a domElementGetter provided in either opts or props

Glad to hear that you got it working 👍


Folders menu item remains empty

As the subject says, I don't see my folders listed in the menu:

Is there a setting I need to change?

Are you sharing any folders, and does the tray is able to connect to syncthing? You should verify the preferences are correct (preferences menu item, and check with the test button) and it is able to connect to syncthing.

I am sharing several folders and they work just fine. I am presently syncing two macs and one NAS without any problems. The Macs just don't show my properly syncing folders...

Thats a weird situation, you are the first one reporting this problem.

Okay, so I bit the bullet and completely reinstalled Syncthing on both Macs and that fixed the folder issue. It took a while to recreate the sync relations, but ultimately it was worth it.

Did you have an older installation (pre v0.14.33) and copied the new installation v0.14.33-1 over it? Or are you a first time user since v0.14.33? Now your problem went away it is difficult to tell why this has happend.

Indeed, I installed over an older installation. In fact, that was one of the thoughts I had that could explain this. But all is good now.

"Check for updates" currently doesn't announce latest (v0.14.33) as it won't upgrade due to changes in bundle package signing. Its still a known issue that we need to announce the upgrade to v0.14.33 must be manually applied.


replication: add GoCDK PubSub support

btw, the build failed currently. Seems transient, but similar problem as last time. I will try to restart the build.
$ go get ./weed/...
package gocloud.dev/pubsub: unrecognized import path "gocloud.dev/pubsub" (https fetch: Get http://gocloud.dev/pubsub/?go-get=1: redirected from secure URL https://gocloud.dev/pubsub?go-get=1 to insecure URL http://gocloud.dev/pubsub/?go-get=1)
package gocloud.dev/pubsub/awssnssqs: unrecognized import path "gocloud.dev/pubsub/awssnssqs" (https fetch: Get http://gocloud.dev/pubsub/awssnssqs/?go-get=1: redirected from secure URL https://gocloud.dev/pubsub/awssnssqs?go-get=1 to insecure URL http://gocloud.dev/pubsub/awssnssqs/?go-get=1)
package gocloud.dev/pubsub/azuresb: unrecognized import path "gocloud.dev/pubsub/azuresb" (https fetch: Get http://gocloud.dev/pubsub/azuresb/?go-get=1: redirected from secure URL https://gocloud.dev/pubsub/azuresb?go-get=1 to insecure URL http://gocloud.dev/pubsub/azuresb/?go-get=1)
package gocloud.dev/pubsub/gcppubsub: unrecognized import path "gocloud.dev/pubsub/gcppubsub" (https fetch: Get http://gocloud.dev/pubsub/gcppubsub/?go-get=1: redirected from secure URL https://gocloud.dev/pubsub/gcppubsub?go-get=1 to insecure URL http://gocloud.dev/pubsub/gcppubsub/?go-get=1)
package gocloud.dev/pubsub/natspubsub: unrecognized import path "gocloud.dev/pubsub/natspubsub" (https fetch: Get http://gocloud.dev/pubsub/natspubsub/?go-get=1: redirected from secure URL https://gocloud.dev/pubsub/natspubsub?go-get=1 to insecure URL http://gocloud.dev/pubsub/natspubsub/?go-get=1)
package gocloud.dev/pubsub/rabbitpubsub: unrecognized import path "gocloud.dev/pubsub/rabbitpubsub" (https fetch: Get http://gocloud.dev/pubsub/rabbitpubsub/?go-get=1: redirected from secure URL https://gocloud.dev/pubsub/rabbitpubsub?go-get=1 to insecure URL http://gocloud.dev/pubsub/rabbitpubsub/?go-get=1)
The command "go get ./weed/..." failed and exited with 1 during .

the build still fails, only for go tip, not for go 1.12.x, 1.11.x, or 1.10.x

Need help on the redirect error. All builds are failing for go tips.

I tried to reproduce. I couldn't.

Will keep trying to repro.

Reproduced. This is a known issue: golang/go#31241.
Not sure why you want to test at tip, since it isn't stable. But we can just leave this PR here until they fix it, which should be soon.

Thanks! Merged!
Another related question: when using https://github.com/jondot/goweight to analyze the binary, the top one is github.com/ugorji/go/codec, coming from "gocloud.dev/pubsub/natspubsub". 11MB is a large portion of 59MB generated binary.
weed$ goweight
   11 MB github.com/ugorji/go/codec
  6.1 MB github.com/aws/aws-sdk-go/service/s3
  5.2 MB github.com/Azure/azure-storage-blob-go/azblob
  4.3 MB github.com/go-redis/redis
  4.1 MB github.com/DataDog/zstd
  3.8 MB net/http
  3.5 MB github.com/Shopify/sarama
  3.3 MB runtime
  3.0 MB github.com/gocql/gocql
  1.9 MB golang.org/x/net/http2
  1.8 MB github.com/golang/protobuf/proto
  1.8 MB net
  1.8 MB crypto/tls

Removed igorji/go/codec. See google/go-cloud#1776.

Thanks! Works well! The total size 59732788 bytes=> 55997588 bytes, about 3.56MB, or 6.25% reduction.
The new goweight output:
weed$ goweight
  6.1 MB github.com/aws/aws-sdk-go/service/s3
  5.5 MB github.com/DataDog/zstd
  5.4 MB github.com/Azure/azure-storage-blob-go/azblob
  4.3 MB github.com/go-redis/redis
  3.8 MB net/http
  3.6 MB github.com/Shopify/sarama
  3.3 MB runtime
  3.0 MB github.com/gocql/gocql
  1.9 MB golang.org/x/net/http2
  1.8 MB github.com/golang/protobuf/proto
  1.8 MB net
  1.8 MB crypto/tls


Update packages pointing at master on appstoreconnect-sdk fork

Fixes our package dependencies and our master build after the branch we were pointing at was deleted

Also updates minor versions of the csv encoder and argument parser