More details needed for build environment

The 'build' docs page implies that the only requirement for running hail is Gradle. However, I've just tried to build hail on Debian Jessie and Ubuntu 16.04, and both failed in different ways. On Jessie,  I was able to figure out that the version of Gradle was too old. On Ubuntu 16.04, I get
:compileJava UP-TO-DATE
:compileScala FAILED

FAILURE: Build failed with an exception.

* What went wrong:
A problem was found with the configuration of task ':compileScala'.
> No value has been specified for property 'zincClasspath'.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED

A quick Google around doesn't reveal any obvious answers to this.
What version of Gradle is needed? Is Scala a prerequisite? It would be very useful to provide detailed instructions on how to build hail from scratch on a fresh installation of some Linux distribution.

Hi Jerome!  Are you using Gradle 2.10?  We've seen some build problems under 2.10 that got resolved by upgrading to 2.12 or 2.14.

Ubuntu 16.04 has Gradle 2.10. Is there any way of fixing the build problems other than me building Gradle manually? I'm a big believer in using package managers!
I'm looking forward to taking hail for a spin!

It looks like you have two options:

Install the Gradle ppa:  https://launchpad.net/~cwchien/+archive/ubuntu/gradle

In a nutshell, uninstall the previous version of Gradle and then run:
sudo add-apt-repository ppa:cwchien/gradle
sudo apt-get update
sudo apt-get install gradle-2.14.1

Download the the latest complete distribution of Gradle 2:

https://gradle.org/gradle-download/
Go to Previous Release and select 2.14.1 and download the complete distribution.  Gradle is written in Java and it is pre-compiled.  No need to build it.  Run gradle-2.14.1/bin/gradle and you should be good to go.
Gradle 3 was just released a few days ago.  We haven't tested against it, so I would recommend Gradle 2 for now.
I'll update the documentation to warn about Gradle 2.10.
Let me know if either of these work for you.

OK, a third option:
Gradle has support for something called a Gradle wrapper, a set of distribution scripts that download and run a specific version of Gradle.  I just added a Gradle wrapper for 2.14.1 to the master branch.  You should now be able to build the local version of Hail with gradlew installDist or ./gradlew shadowJar to build the shadow (fat, uber) jar to run against a Spark cluster.

This is great, thanks @cseed! I've tried the gradlew option, and it worked well on Debian Jessie with java-8-oracle.  ./gradlew installDist worked, and the majority of the tests passed in ./gradlew check (4 failed; I can give you the details if this is useful).
On Ubuntu 16.04 with java-8-openjdk (the default) I get an error:
:compileJava UP-TO-DATE
:compileScala
/home/jk/github/hail/src/main/scala/org/broadinstitute/hail/expr/Type.scala:80: not enough arguments for constructor AnnotationPathException: (msg: String)org.broadinstitute.hail.annotations.AnnotationPathException
      throw new AnnotationPathException()
            ^
/home/jk/github/hail/src/main/scala/org/broadinstitute/hail/expr/Type.scala:98: not enough arguments for constructor AnnotationPathException: (msg: String)org.broadinstitute.hail.annotations.AnnotationPathException
      throw new AnnotationPathException()
            ^
/home/jk/github/hail/src/main/scala/org/broadinstitute/hail/expr/Type.scala:424: not enough arguments for constructor AnnotationPathException: (msg: String)org.broadinstitute.hail.annotations.AnnotationPathException
        case None => throw new AnnotationPathException()
                           ^
three errors found
:compileScala FAILED

FAILURE: Build failed with an exception.

Is this a dependency on java-8-oracle do you think?
My immediate problem is solved, as I have hail running now, so this is just out of curiosity really. l think it would be good for new users if you could nail down the dependencies a bit more precisely. For testing and development, it's also really useful to be able to spin up a quick Ubuntu VM, apt-get install a few packages and make a fresh install.

Hi Jerome, this AnnotationPathException issue is something we've seen before.  It seems to be caused sporadically by gradle's build caching, and can usually be fixed by running gradle clean.
The tests that failed are probably the ones that require external tools available on the command line:
FisherExactSuite (requires Rscript)
ImportPlinkSuite (requires plink 1.9)
ExportPlinkSuite (requires plink 1.9)
LoadBgenSuite (requires qctool)

Thanks @tpoterba, the gradle clean worked nicely. If it's any use, the  test failures are the following:
$ ./gradlew check | grep FAILED
Gradle suite > Gradle test > org.broadinstitute.hail.io.ExportPlinkSuite.testBiallelic FAILED
Gradle suite > Gradle test > org.broadinstitute.hail.driver.GRMSuite.test FAILED
Gradle suite > Gradle test > org.broadinstitute.hail.methods.ImputeSexSuite.testImputeSexPlinkVersion FAILED
Gradle suite > Gradle test > org.broadinstitute.hail.io.LoadBgenSuite.testBgenImportRandom FAILED

Thanks for the help, and please feel free to close this issue whenever suits.

Hi Jerome, yup, the first three require plink 1.9 and the fourth requires qctool. I'm surprised FisherExactSuite didn't fail as well, perhaps you have R installed or pulled Hail before that went into master. Thanks for the feedback, super helpful!

We added the list of test dependencies to the "Running the tests" subsection of Getting Started so I'm going to mark this as closed.


Learning resources

Do you have a blog post that shows how one would use your libraries?  I was thinking of using a Maybe for a situation where I was originally using a ternary expression that returned an object or undefined.  I think this might be a good candidate.  I'm really trying to refactor some of my code to be more functional, and any resources you have may be of great help.
Thanks again for making such an awesome suite of libraries, I cant wait to share this with some of my friends! 👍

Hey Matt, there is no additional documentation at this time. I'd love to see us develop these sorts of tutorials in our wiki. What kinds of things would you like to see explained in more depth?
Your use case sounds like a great use of Maybe. Do you have any particular questions about them now that I could try to help you with?
I'm glad you're enjoying the libraries. They're stable and used in a production environments.

@TylorS Thanks for the reply.  To give you some context, I'm currently working on an AST Parser, and because ASTs are deeply nested structures, I think FP could be a great candidate for working with finding the various types in the AST.
I've been finding myself constantly checking types really, and I am wanting the code to be clean, concise, and predictable, and with all this checking, procedure, iteration, things can get unwieldy pretty fast. I'm pretty new to typescript, but loving the type safety, and really want to try to use more functional types as well since I'm using types and all!
So just to give you a small taste, here is a small amount of some functions I have written to type check of whether or not this is a NodePath, or Node, and then what kind of Node it is:
export function isPath(prop: PathOrNode): prop is NodePath {
  return prop instanceof NodePath;
}
export function isNode(prop: PathOrNode): prop is Node {
  return (prop as Node).start !== undefined;
}

export function getVariableId(prop: PathOrNode): string | void {
  if (isPath(prop)) return getVariableIdFromPath(prop);
  if (isNode(prop)) return getVariableIdFromNode(prop);
}

export function getVariableIdFromNode(node: Node): string {
  if (isVariableDeclarator(node) && isIdentifier(node.id))
    return getIdentifierName(node.id);
}
export function getIdentifierName(node: Identifier) {
  if (isNamedIdentifier(node)) return node.name;
}
export function getIdNameFromPath(path: NodePath<Identifier>): string {
  return getIdentifierName(path.node);
}
export function getVariableIdFromPath(path: NodePath<Node>): string {
  return getVariableIdFromNode(path.node);
}

export function isNamedIdentifier(node: Node): node is INamedIdentifier {
  return isIdentifier(node) && node.name !== undefined;
}

I've been spending an immense amount of time on this project, (near 100 hours) and really I find myself constantly refactoring how I'm resolving these node types because I keep thinking there has to be a cleaner and more concise way...

Wow, what a cool project! I've been thinking of building something pretty much identical to docsense 👍
If you are familiar with Ramda a lot of our APIs are the same or very similar, in particular @typed/list shares a lot of functions with Ramda. The biggest difference is we use a couple of data structures throughout the codebase like Maybe and Either. For example our implementation of findIndex returns a Maybe<Index>. So rather than using -1 to signal "not found", Nothing would be the indicator of the same state. However with a Maybe you can still continue to call functions like map and perform other operations. If the Maybe is in a Nothing state no work is ever actually performed and only when you absolutely need the value do you need a function like fromMaybe which can be a clean way to provide fallback values you'd generally require an if statement or a ternary.
Just going with findIndex I'll try to come up with a small example usage of Maybe
// without typed
function replaceChildById<A extends { id: string }>(newValue: A, values: Array<A>): Array<A> {
  const { id } = newValue

  // Try to find index by id
  const index = values.findIndex(value => value.id === id)

  // If the value can not be found return the original array
  if (index === -1)
    return values

  // immutably replace the old value
  const newValues = values.slice()
  newValues[index] = newValue

  return newValues
}

// with typed
import { pipe, partial, __ } from '@typed/functions'
import { propEq } from '@typed/logic'
import { findIndex, update } from '@typed/list'
import { map, fromMaybe } from '@typed/maybe'

function replaceChildById<A extends { id: string }>(newValue: A, values: Array<A>): Array<A> {
  const { id } = newValue
  return pipe<Array<A>, Array<A>>(
    findIndex(propEq('id', id)), // find the index by id
    map(partial(update, [__, newValue, values])), // immutably replace old value
    fromMaybe(values) // default to returning original values
  )(values)
}

I hope this helps at least a little bit!

@MattMcFarland needs documentation for typed to continue his documentation generation project, which, once complete, @TylorS can use to generate documentation for typed.


Catch java components missing exception and show message to the user

fixes #876

Pending new release of the common lib

@patflynn @meltsufin

Error text should ideally be highlighted somehow.  Maybe using red?
On Mon, Sep 12, 2016 at 5:22 PM, Etan Shaul<EMAIL_ADDRESS>wrote:

Assigned #884
https://github.com/GoogleCloudPlatform/google-cloud-intellij/pull/884
to @patflynn https://github.com/patflynn.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/google-cloud-intellij/pull/884#event-786668242,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHf5Hc0KfuDlBiTifjqs-PrM2Bosnzwqks5qpcKygaJpZM4J7C6h
.

I don't see any way to have the error text highlighted. I'm using RemoteOperationCallback#errorOccured to print the message (and indicate failed deployment) which doesn't give any options for customizing the look of the text.
I can look into this more separately in a different PR.

LGTM assuming the log level thing is right.


Bump editor and plugins and introduce RDFa aware editing

Overview
Bump editor and plugins to:
{
  "@lblod/ember-rdfa-editor": "^9.10.0",
  "@lblod/ember-rdfa-editor-lblod-plugins": "^19.2.0"
}

This release adapts embedded to RDFa (RDF in Attributes) aware editing, based on the changes in ember-rdfa-editor version 9.6.0
Setup

Checkout
pnpm i
pnpm run start

How to test/reproduce
Make sure editor still works 🫡 and the styles are not broken 🤔
Checks PR readiness

[X] UI: works on smaller screen sizes
[X] UI: feedback for any loading/error states
[X] Check cancel/go-back flows
[X] Check database state correct when deleting/updating (especially regarding relationships)
[X] changelog
[X] npm lint
[X] no new deprecations

It may make most sense to switch the visual part off, merge this, then add the option to edit RDFa later.

Will follow this one 🙏🏻


Bayoumi

Hello! Thanks for attempting to contribute to OMRChecker. But may I know what this is about?

@Abdulrahman-Bayoumi would you like to respond?


Trip Card Modules

On the trip page, we will need to create a component that will be used to populate some trip info. -

Use a bootstrap card to contain the elements
Have a Title, Picture, Cost, Location, Date and Time, Description (maybe a condensed description instead of full length), and anything else that might be neccassary
Make the Card itself a linkable item using Next.js Link element
Make sure title, pictures, and descriptions are inherited from the props of the component for re-usability

Completed on Branch feature/tripCard and merged to development


[Feature Request] Select with Button instead of Input

Existing Component
Yes
Component Name
El-Select
Description
Is it or will it be possible to have select functionality on button click?
I would like to have a button with an icon and on click to see selection.

What's the difference from a normal dropdown?

What's the difference from a normal dropdown?

The difference is multiselection and showing selected item. But now i see that this functionality could be build around dropdown with custom dropdown element and managing selected items by ourselves. I don't know why i was so fixed on select element...


It doesn't work with Internet Explorer 11?

It seems that this plugin doesn't work with Internet Explorer 11. Edge works fine.
Any idea on how to fix it?

Can you elaborate on "doesn't work"? It should work down to IE 9, at least.

@ljharb It doesn't work at all. The component to select the date don't even appear. Do you want to know something specific?

On your site, or on the storybook?

@ljharb After your comment I decided to check it out. it isn't working on our website but I think that I followed everything mentioned in the README. Do I need to do something more to make it work?

@ljharb you an check it out here: https://www.hole19golf.com/portugal/club-de-golfe-quinta-do-peru

Well... I guess no help will come from this.

@igorescobar please have patience, this (and the last two weeks) is holiday time in the US.

In IE 11 I have the error which is linked with: "Array.from" -- is indicated, that property "from" is not supported. It seems need to use polyfill: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/from

@Valentin1918 could you perhaps point me to a line number? That's something that'd be relatively trivial to fix.

It is in lib/components/DayPicker.js line 116

Thanks, all fixed for the next release.

@ljharb any idea when it will be released?

I can try for today or tomorrow.

v4.3.1 published.

Thanks. Also in src/components/DayPicker.jsx (line 241) need to be called calculateDimension but not this.calculateDimension

v4.3.2 has been published.

Has there been an IE11 regression since then? I'm getting multiple errors including Array.from etc on version 11.0.1.

@warn4n Part of v11's breaking changes was that it required Set and Array.from - you now need to use https://npmjs.com/airbnb-js-shims or the equivalent (you should be doing this regardless in older browsers like IE 11)

@ljharb Great, I'll try that out! Thanks so much for your very quick response!!

Hello, I import react-dates DateRangePicker in my project and testing in IE9 return error "SCRIPT5007: Unable to get value of the property 'isDayBlocked': object is null or undefined", and file initialize.js has const and IE9 not understand const, I changed const to var.
Any idea on how to fix it?

@corohsnk https://github.com/airbnb/react-dates/blob/master/initialize.js doesn't have const, and neither does<EMAIL_ADDRESS>- how are you importing it into your project?

@ljharb I checked in my project, it was with version 13, I updated to the current version (15.0.0) but it still gives error of isDayBlocked: object is null or undefined in IE9

@corohsnk can you file a new issue, and include the stack trace as well as how you're using react-dates? Also, please confirm (in the issue) that you're using airbnb-browser-shims or the equivalent?


HAWQ-1514. TDE feature makes libhdfs3 require openssl1.1

use environment HDFS_DEPENDENCY_INSTALL_PREFIX to indicate "libhdfs" used openssl path
do function check before HAWQ compilation in configure file

LGTM

LGTM
+1

+1 LGTM, thanks!


feat: Add Mixedbread AI Integration

Hey guys! This is from Mixedbread AI. With mixedbread we're building SOTA models and tools to streamline retrieval. So far, we trained some of the most widely used open-source embeddings and reranking models (https://huggingface.co/mixedbread-ai).
We notice that Unstructured is providing embeddings integrations. We would love to partner up and contribute to this project.  @MthwRobinson

@vangheem @potter-potter would love to hear your thoughts on this!

Thanks for the contribution @huangrpablo ! We'll review this as soon as we're able.

CI for this PR is running on #3392

Looks like potentially some dependency conflicts. Running make pip-compile from a Python 3.9 environment will likely fix that.

https://github.com/Unstructured-IO/unstructured/actions/runs/9911978833/job/27385814239?pr=3392

From the CI on the "clone PR", you may also need to update the version in unstructured/__version__.py (see this job)

@MthwRobinson just made the fixes. make pip-compile also resulted in the dependency changes of other connectors.

@MthwRobinson hey, I put the dependencies of other integrations back to untouched. But I think dev.txt, test.txt and changelog need manual conflict resolution. Could you have a look and run the CI again? Thanks!

@MthwRobinson Hey, would love to hear any update on this!

@MthwRobinson Hey, would love to hear any update on this!

@huangrpablo I'll take over for Robinson from here. I'm gonna check it out today.

@potter-potter hey, any update on this?

copying this over to
https://github.com/Unstructured-IO/unstructured/pull/3513
so that its easier to run CI, etc.


Feature request: Enhanced Backpacks

Firstly, I am really glad that someone finally ported the backpacks that better storage added. They are in my opinion the most exceptionally well made and "realistic" backpacks added by any mod, and it was a huge disappointment to see them left behind in 1.7.10 (not anymore of course XD). I am thrilled to see them return, and I hope you will be open to bringing back more than just the standard backpacks.
In the better storage mod, there were two special backpacks as well as the normal ones.

The first type is called the Ender Backpack. Like its name suggests, it is an ender chest that the player can carry as a backpack. There is no crafting recipe in survival, so there is only one way to get one. A player that wants one must find an enderman in the world that is wearing one, place an ender chest nearby, and get that enderman to pick up the ender chest. If the enderman picks up the chest, the backpack will be placed down where the chest was. The player can then equip the backpack by breaking it while holding shift like any other backpack. If the player attempts to break the pack without holding shift, the pack will teleport away like a dragon egg.
Also if I recall correctly, The endermen that wear ender backpacks are a separate entity added by better storage. They are called Friendly Endermen and they do not attack the player and can never be provoked.

The second backpack is actually part of the better storage mod's integration with Thaumcraft 4. The Thaumaturge's backpack is a backpack with 2 or 3 times more slots than the normal backpack. Obviously having the thaumaturge's backpack is not possible at this point in time since TC6 is still in development. With that said though, it would be nice to have some larger mod integrated backpacks that require special crafting methods. A few ideas would be to make a bound backpack for Blood Magic and an end game Gaia backpack for Botania. Perhaps when the time finally rolls around, the Thaumaturge's Backpack can make an appearance when TC6 gets released too.

One last side note, the original Better storage had a config option to enable/disable a keybind that allows the player to open a worn backpack without taking it off. I believe it was disabled by default.
I hope you like what you see. :)
Thanks,
63502

I'm currently not actively working on the mod but these are certainly features I'd like to re-implement.

Ender Backpacks - Before I can tackle these, I have to finish the part of the mod that allows non-player entities to wear backpacks. While the bulk of the work is done. The friendly enderman will make a return, though I'm not sure if I'm keeping the obscure and annoying trading mechanic.
Thaumaturge's Backpack - The texture is already (or rather, still) there. What I hope I can do is implement a backpack for every major mod, each with its own mod-related feature. It works well to reward the player for getting into these mods and help a little with the large amount of unique items when playing with lots of mods. The size of those backpacks was just 44% larger than the normal one, by the way, though this time around I plan to make the sizes completely adjustable (per item, and both width and height). I also plan to add specialized backpacks that don't hold items, like a fluid backpack? (Might be modeled as a barrel?)
Key to open equipped backpack - Technically easily possible, though I want to implement config setting synchronization when joining a server.

For what it's worth, I think the enderman trading mechanic was fun and unique. Much better than just crafting it, it made the ender backpack something to be proud of.

Indeed. I only succeeded at doing it in survival once.

Small update: Opening backpacks using a key has been implemented in 6e613203f640d70a0b951d5537bb4edf4aebc57e.

Like a Iron / Golden / Diamond Backpack?
Otherwise something along the lines that has the same armor points as an Iron / Diamond chestplate?
Simply Jetpacks solved this by adding armor plating so you could have the same leather backpack while having increased armor points.

Like a Iron / Golden / Diamond Backpack?

The only tiered backpacks I'm going to add are ones gated behind other mods' progression trees, ones where you actually have to put in effort and time to create, instead just relatively easy to get Vanilla resources. Otherwise... you're just going to make the highest tier backpack and where's the fun in that? I do advertise my mod for being balanced, after all.
Also, ideally, they'd serve some function together with the other mod, like allowing certain items from it to still function or draw resources from the backpack. A Thaumcraft backpack might allow items to repair inside it, and also be compatible with the Repair enchantment itself. A Botania backpack would allow you to draw mana from items inside the backpack, and repair automatically using mana, as well. Stuff along those lines. Maybe I can come up with some neater, unique features for them, too.
Alternatively, people can use MineTweaker or similar to add a recipe for a backpack with a custom size.

Otherwise something along the lines that has the same armor points as an Iron / Diamond chestplate?

Again, if you make it an option, people will just use it, and that destroys a big balance point in the mod: Trading armor for storage. Also, with the config option that allows you to wear both armor and a backpack, that feature is already in the mod in spirit, better than I could ever implement "armor plating": You can wear any armor you like at the same time.

Now, with both of those suggestions separately out of the way, I had considered adding an armored backpack with more defense but less storage, though I decided against it since it simply doesn't feel right.
Ender backpacks will likely end up being the only other item storage backpack you'll be able with just Vanilla, unless I come up with a unique feature for another one. Liiike... one that's only able to store shulker boxes, but allows easy access to them without having to place them?
Other than that, I'm planning to use enchantments (likely dungeon loot?) to add additional features, instead of relying on new backpack types or upgrades in the form of items or crafting recipes.

You're right and I appreciate your well-constructed feedback and opinion.
I entirely agree with your balancing mechanics and I'm looking forward for future additions.

A Botania backpack would allow you to draw mana from items inside the backpack.

While this sounds very handy, I think Botania already adds something in that line?
http://botaniamod.net/lexicon.php#baubleBox
Not sure if it lets you draw mana from it but I believe it does.

I had considered adding an armoured backpack with more defense but less storage / unless I come up with a unique feature for another one.

I would argue, rather than one to store shulker boxes, to maybe add a way (as an anvil-enchant or otherwise) to add an Elytra to your Backpack but removes the enchantability from it.
Aside from armor, a portable 3x3 crafting grid is always nice to have but maybe that is getting the mod a little bloated for what promotes.

I would argue, rather than one to store shulker boxes, to maybe add a way (as an anvil-enchant or otherwise) to add an Elytra to your Backpack but removes the enchantability from it.

I don't think anyone would use an elytra backpack in Vanilla if it's just going to break easily. Also that's the same thing as with the armor plating in the end. Mods doing this I find are just taking a very easy, non-dynamic approach.
If in Vanilla end-game, you have to decide between lots of storage (shulker boxes add to that - storing them in your backpack will allow massive amounts of storage) and the ability to fly, that's exactly the kind of hard decision I want players to make. Storage or armor. Flying or massive storage. Players who don't necessarily care about the design decision behind this have the choice to change the config setting allowing you to wear both backpacks and armor.
I simply don't think there's any better way to implement either a balanced or a "beautiful" way to mush these together, let alone both. Beautiful as in.. not sure how to explain, but avoiding hardcoded approaches like X + Y = XY, simply crafting and upgrades without real drawback.
The only thing I could imagine is an upgrade or enchantment that would be beautiful, but not necessarily balanced, is a way to upgrade the backpack so it doesn't take up your chest armor slot anymore (just as if the config setting was off). But that's not really balanced anymore. Maybe I'll add an NBT setting that would do the same thing, and add per-backpack options? This way, modpack creators could fiddle with the balance themselves, too.
And no, I'm not the kind of person who gates (in my opinion) overpowered things behind end-game content such as nether stars. I prefer end-game unlocking new, fun ways of playing the game without invalidating the old.
Elytra + fireworks for example I don't like, no matter how fun they are. Who needs to walk anywhere if you can just fly? Horses? Minecarts? Pff! Without the instant boost, people came up with neat launchers and ways to get around, now flying is just a rightclick away! Blegh. </rant>

Aside from armor, a portable 3x3 crafting grid is always nice to have but maybe that is getting the mod a little bloated for what promotes.

Oh yes, that's true. An item storage backpack that comes with a crafting grid is certainly worth considering.

1 hope that the arrow in the backpack can be fired.
2 would like to join the bag tied to the leg.

hope that the arrow in the backpack can be fired.

A backpack is not a quiver and I don't know if appropriate hooks exist to override bow drawing behavior.

would like to join the bag tied to the leg.

If I understand correctly... A belt pouch would be neat but it both is difficult to design a natural way to interact with it and it sort of doesn't fit into the mod. Also the uses I could come up with for it can already be found in other mods, such as a belt that allows you to switch your hotbar with the belt's inventory.

So is this Ender backpack still planned? Would be a phenomenal addition and would for all intents are purposes perfect this mod in standard modpacks.

This would be up to the current maintainers to decide, if they can get the time and motivation. I don't quite know anymore how much code is in place to support multiple types of backpacks easily.


A way to avoid the animation

I can't navigate the app because there's too much animation. If I click on the menu button, an animated menu slides in from the left.

Just curious, how is the animations causing issues for you?

I don't remember which animations it uses. But a lot of types of animation can blind me, disorient me, trigger my migraines, and trigger nausea.

this should honor the os accessibility setting available through prefers-reduced-motion
https://web.dev/articles/prefers-reduced-motion


React warning Step component

Hi all,
Could you please have a look at this?
Warning: The  component appears to be a function component that returns a class instance. Change Step to a class that extends React.Component instead. If you can't use a class try assigning the prototype on the function as a workaround. Step.prototype = React.Component.prototype. Don't use an arrow function since it cannot be called with new by React.
Kind Regards,
Brecht

Hey there, @brechtarnou! Can you provide more context, please?


i18n(ko-KR): update content.mdx

Description (required)

update content.mdx
#9724

Related issues & labels (optional)

Closes #
Suggested label:

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale
File
Note

ko
community-resources/content.mdx
Localization changed, will be marked as complete.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.


[Java Client]: query.withTx(writeTransaction).execute() returns empty list when type mismatch

SCHEMA:
define
person sub entity,
has person-id,
plays employee;
company sub entity,
has name,
plays employer;
employment sub relationship,
relates employee,
relates employer;
person-id sub attribute datatype double;
name sub attribute datatype string;
JAVA CLIENT:
InsertQuery insertQuery = Graql.match(
var("p").isa("person").has("person-id", "1"),
var("c").isa("company").has("name", "grakn"))
.insert(var("e").isa("employment").rel("employer", "c").rel("employee", "p"));
Grakn.Transaction writeTransaction = session.transaction(GraknTxType.WRITE);
List insertedId = insertQuery.withTx(writeTransaction).execute();
=> RETURNS an EMPTY LIST; but should return an error saying attribute type person-id is of datatype double.

This bug was actually fixed by the addition of server-side schema validation, albeit not in a pretty way. The query now returns the following error:
[QRY16] Invalid Query Pattern: The pattern '{{ $p isa person; $p has $_0;
$_1 isa name; $_1 = "grakn";
$c has $_1; $c isa company;
$_0 = "1"; $_0 isa person-id; }}' is illegal in the current schema.

I've raised:

https://github.com/vaticle/typedb/issues/6727
https://github.com/vaticle/typedb/issues/6728

We can now close this issue.


Track computational time of each step

This should be exported in the CSV file

added in 122a306

added in 122a306


ENH: provide a way to open into memory rather than save the data product download

A follow-up to https://github.com/fornax-navo/fornax-cloud-access-API/pull/4, not necessarily a fornax issue.

I'm closing this one as https://github.com/astropy/astropy/pull/13238 provides a solution for this, for fits files, and I don't think other file types are on the radar atm (and even then, those should likely be dealt with upstream).


Could you put GPU version python package for windows to PyPi

I want to use mxnet python package on windows OS. I have found a GPU version on PyPi (https://pypi.python.org/pypi/mxnet-cu80/0.11.0), but not CPU version. Could you put one on the website https://pypi.python.org/pypi/mxnet/0.11.0?

It's now available thanks to @yajiedesign. Closing for now. Let me know if you have any trouble using it.

I have seen it. Thank @szha @yajiedesign very much!


Randomly generated Id is rendering snapshot testing useless (mui-id)

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
A randomly generated label-Id gets passed down to inner Typography component which means that every time a snapshot is generated, it's going to have a different Id. Example of where this happens:
https://github.com/mui-org/material-ui/commit/ae3c25193bf666ab9c8ca194f35fe200cc5d8504#diff-f92b445636d789b46906505273654e5eR106
Expected Behavior 🤔
At least allow us to override this value so that we can resume snapshot testing
Steps to Reproduce 🕹
Steps:

Set up a snapshot testing that uses TablePagination component
Generate a snapshot
Watch as it generates a random id for the caption

Context 🔦
Trying to get snapshot testing working. Everything was fine in the previous version (4.10.0)
Your Environment 🌎

Tech
Version

Material-UI
v4.10.1

Duplicate of #21293


SPIKE: USWDS and Node Upgrade

USWDS 3.0 and Node 18 have been released, current versions used across CAMPD and ECMPS will potentially eb depcreciated.
Research which versions will be implemented across apps in IPI 8 &P

[ ]  Moved down in priority, but waiting on Trustworks shifting to USWDS 3.0, and when cloud.gov starts supporting node 18

Ticket no longer needed


{AKS} az aks mesh: Add warnings for out of support asm revision in use

Related command
az aks mesh
Description
This change adds warnings to the az aks mesh commands for an out of support asm revision in use in the cluster.
Testing Guide
az aks mesh enable -- revision asm-1-18 -g rgName -n clusterName
This command should print a warning about asm-1-18 being out of support.

This checklist is used to make sure that common guidelines for a pull request are followed.

[x] The PR title and description has followed the guideline in Submitting Pull Requests.

[x] I adhere to the Command Guidelines.

[x] I adhere to the Error Handling Guidelines.

AKS

Please fix CI issues

Please note Azure CLI is in a release process and cannot merge PRs of the main repo.
Once the release is complete on 07-09, we can merge it.

/azp run


Web server

I can't seem to find a server config to change ports, or anything. Is there a guide on how to setup for web access?

Hi,
you have configuration parameters in :
Configuration/Plugins/Servers

I am attempting to run it on headless Linux. I have just started getting into Linux. What would be the folder path for the chnsges to be made to? I'll get the actual error when I get home, but I think it is from ports. I was getting a w11 error I think? When I get home, I'll post the actual error.

Or. Better yet, have you attempted to run MTG on heroku?

Decided to switch it over to windows. Easier time for me.

By default, Linux doesn't allow opening port 80 ... maybe by changing port to something like 8080 or else.. can you send me your linux log ?


[ie/Telecinco] Fix extractor: Add headers

*IMPORTANT: PRs without the template will be CLOSED
Description of your pull request and other information
add referer header to _extract_m3u8_formats
Return http_header to mitele for proper origin and referer headers
Properly usage of geo restriction. Allowing download with geo-restrict-proxy
follow yt-dlp coding conventions, use traverse_obj

Fixes https://github.com/yt-dlp/yt-dlp/issues/10986
And fixes https://github.com/yt-dlp/yt-dlp/issues/11106
Template
Before submitting a pull request make sure you have:
At least skimmed through [contributing guidelines](https://github.com/yt-dlp/yt-dlp/blob/master/CONTRIBUTING.md#developer-instructions) including [yt-dlp coding conventions](https://github.com/yt-dlp/yt-dlp/blob/master/CONTRIBUTING.md#yt-dlp-coding-conventions)
[Searched](https://github.com/yt-dlp/yt-dlp/search?q=is%3Apr&type=Issues) the bugtracker for similar pull requests

In order to be accepted and merged into yt-dlp each piece of code must be in public domain or released under Unlicense. Check all of the following options that apply:
I am the original author of this code and I am willing to release it under [Unlicense](http://unlicense.org/)
I am not the original author of this code but it is in public domain or released under [Unlicense](http://unlicense.org/) (provide reliable evidence)
partial code reference: https://github.com/yt-dlp/yt-dlp/issues/10986#issuecomment-2348156339 by @n0ttr

What is the purpose of your pull request?
Fix or improvement to an extractor (Make sure to add/update tests)

This commit was based on @grqz https://github.com/yt-dlp/yt-dlp/pull/11142 but with small modifications to make Mitele extractor also work ok.

does this pr also fix #11106? Please include it in your description if so

does this pr also fix #11106? Please include it in your description if so

Yes it does indeed fix that error. I tested locally. I didnt add any tests since i am outside the geo location, so i was not sure if those would work.

does this pr also fix #11106? Please include it in your description if so

is not fixing it for me: https://github.com/yt-dlp/yt-dlp/issues/11106#issuecomment-2386903822

@DarkZeros I'd like to help you get this merged by testing on my end. I'm located within Spain and have no trouble playing videos on cuatro.com.
I'm on MacOS Sonoma 14.7, running homebrew yt-dlp 2024.10.07.
On that release, I get the failure this is meant to fix:
mleon@Matthews-MacBook-Air yt-dlp % yt-dlp 'https://www.cuatro.com/callejeros/programas-completos/20240808/cuerpo-precio-programa-video_18_013209696.html'
[Telecinco] Extracting URL: https://www.cuatro.com/callejeros/programas-completos/20240808/cuerpo-precio-programa-video_18_013209696.html
[Telecinco] cuerpo-precio-programa-video_18_013209696: Downloading webpage
[Telecinco] ec988c1e-df01-4547-896e-87414eaec94d: Downloading config JSON
[Telecinco] ec988c1e-df01-4547-896e-87414eaec94d: Downloading JSON metadata
[Telecinco] ec988c1e-df01-4547-896e-87414eaec94d: Downloading JSON metadata
[Telecinco] ec988c1e-df01-4547-896e-87414eaec94d: Downloading JSON metadata
[Telecinco] ec988c1e-df01-4547-896e-87414eaec94d: Downloading m3u8 information
ERROR: [Telecinco] cuerpo-precio-programa-video_18_013209696: Failed to download m3u8 information: HTTP Error 403: Forbidden (caused by <HTTPError 403: Forbidden>)

As some help to this PR. I got this error downloading from cuatro.com and the branch solved the issue.

I can also confirm this fixes #11106

Please test my changes (to both extractors); if everything works OK then this can be merged

Please test my changes; if everything works OK then this can be merged

@bashonly tested with https://www.cuatro.com/callejeros/programas-completos/20240718/alquileres-imposibles-programa-video_18_013059088.html
master fails with a 403 on the m3u8.
Your changes succeed in downloading.


Way to split VueJS components / instances to many *.js files to make performance better

Hi.
Is there a way ? Or is there any improvement planned to split the compiled code into many small .js files or Vue instances and to be able to use them later only for needy subpages to improve performance?
I mean we have many components and we mix them with normal blade files. For now when we want to use any we need to inject app.js file to this page. So if our app.js file is few MB or even more we need to get thie every time we change poge or smth. If we could only include part of components we need for actual page it could improve the performance of the application and make it work faster even when we are using it on lower cpu devices or something.

https://webpack.js.org/guides/code-splitting/#dynamic-imports

Do like below, it should work.
<template>
    <div>
        <sample-component></sample-component>
    </div>
</template>
<script>
    const SampleComponent = resolve => require(['./components/SampleComponent.vue'], resolve);

    export default {
        components:{
            SampleComponent
        }
    }
</script>

Thanks for your replay :)

@lrembacz Did that work for you?

@lrembacz Thanks, Works perfect!
Is there some way to automatically create a legacy build so browsers like IE11 use that build?
I know Vue-cli 3.0.0 provides that option 'https://cli.vuejs.org/guide/browser-compatibility.html#modern-mode'. Here some more info: 'https://philipwalton.com/articles/deploying-es2015-code-in-production-today/'

@lrembacz Thanks.
Only one problem I see is that I have versioning enabled (mix.version()). Lazy loaded files does not get their version.

@muffeen https://github.com/JeffreyWay/laravel-mix/pull/1557


[Bug] Smoothing Separated Surfaces

Is ReltimeCSG difficult to support smooth separated object surfaces? I want to smoothing like this edges.

You can select the surfaces you want to smooth between and press the smooth button in the tool window in surface edit mode

oh, My question is bad. Can I smooth the surfaces of the different objects.

Looks like something got broken, that's supposed to work :(

That's great! I hope you fix that soon.

I'll look at it tonight. It must be a small thing that broke this since I didn't actually touch this code in a long time.. so it should be easy to fix

This issue is fixed in version 1.309 which is available on the update site
( http://prenominal.nl/updates/index.php )
I will close this ticket when it's available on the asset store

Thanks fast supports!
I have tried smoothing, but it still doesn't work. I made two same shapes with the box tool and the free draw tool. The free draw tool is good smoothing, but the box tool is not.
I checked on the scene view which drawing face normals.

ReatimeCSG 1.309

Did you select the surfaces + press smooth in the surface edit mode?
If you did, can you sent me those two shapes to my email address so that I can take a closer look?
You can find my email address on the top right corner at https://logicalerror.github.io/
Thanks

Ok, I confirmed that there's something wrong with the smoothing. I'll look into it.

This issue is fixed in version 1.311 which is available on the update site
( http://prenominal.nl/updates/index.php )
I will close this ticket when it's available on the asset store

Fix is in the version that's on the asset store now, so closing ticket


NTR: electrocyte

def: a specialized muscle or nerve cell that generates electricity, as found in
an electric organ

possibly:
is_a: CL:0000211 ! electrically active cell

but an electrocyte isn't really a signaling cell. Consider changing def of 211?

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 24 Feb 2013 at 4:55

Reference for when this becomes a formal NTR...
PMID:23761470
Current text definition of CL:0000211 'electrically active cell':
"A cell whose function is determined by the generation or the reception of an electric signal."


Introduce inherent digests

What This Is
Inherent digests are digests that are provided to the runtime by the consensus algorithm.  They are inherent because the runtime trusts them implicitly, although the consensus algorithm does verify them.
This PR passes the digests in the header to the runtime via initialize_block.  It does not, however, provide any means for runtimes to actually use the information.  This will be provided later.
Changes to digest items
The DigestItem::Seal variant had been deprecated in an earlier PR.  This PR removes the deprecation, and changes it to contain ConsensusEngineId and a SealSignature.  It also adds the variant DigestItem::PreRuntime for pre-runtime digests.
A consequence of these changes is that the following invariants must be upheld:

Runtimes MUST NOT produce a DigestItem::Seal or DigestItem::PreRuntime.  Only consensus engines can produce these varients.
Consensus engines MUST NOT produce any variants other than DigestItem::Seal or DigestItem::PreRuntime.  Furthermore, there MUST be exactly one DigestItem::Seal per combination of block and consensus engine, and they must come after all other digests.
The SRML reserves DigestItem::ChangesTreeRoot for itself.  Runtimes that use the SRML MUST NOT produce any DigestItem variant except DigestItem::AuthoritiesChange and DigestItem::Consensus.

These invarients are currently not checked.  However, I plan on improving the API to catch violations of them at compile-time, by making illegal states unrepresentable.
Backwards compatibility
There isn’t any.  Versions of Substrate that include this PR are 100% incompatible with versions that came before.  Attempting to combine incompatible versions will result in blocks failing to import.
If necessary, I can include read-only backwards-compatibility support.  This will allow nodes including this PR to import blocks generated by older nodes, but not create blocks that can be imported by older nodes.
Cargo.lock changes
Much of the changes are to Cargo.lock files, as some of the code depends on newer versions of dependencies.  Reverting these dependencies is trivial, but I believe that upgrading dependencies is a good thing, so that Substrate can take advantage of upstream bug-fixes.  This is especially true of libraries like ring, which do not do any backports at all.
Fixes #2232

@rphmeier the test failure is bogus (failure to download a Docker image).

@rphmeier ready for a second review i think

Still a couple grumbles to resolve

@rphmeier can you take another look at this?  All tests pass, and the digests are not being stripped.

Some conflicts. If there's nothing left, it'd be good to get this merged. Feel free to bother some reviewers about it.

This will break the flaming fir network, I'm not sure whether we should have some backwards-compatibility support (just to import old seals), or whether we should reset flaming fir after we deploy this. I don't have a very strong opinion on it, but I also don't want us to spend too much effort dealing with backwards compatibility on flaming fir (the idea of the network is to run master with no stability guarantees).

i'm fine with reseting it.


Add Required and Title AttributeBindings

For HTML5 inputs which are to have the required attribute, this component should be configurable.
Given the current approach, I suggest adding required: false to the component.  Then, in the template:
{{input type=type name=name value=value placeholder=placeholder class=inputClass focus-out="mailcheck" disabled=disabled required=required title=title}}

Note, as well, the addition of title, such that the browser can display any custom messages when validation fails.

Agreed, will publish this shortly. Thanks!

Published to npm as<EMAIL_ADDRESS>

Possibly merit for another issue, but the span element should be replaced with a label element; the current configuration is inaccessible to screen readers, as there is no label associated with the input.

I've been pondering this as well. I've been considering adding a label option for the component so one can pass {{mail-check value=email label='email'}} with a template like:
{{#if label}}
  <label>{{label}}</label>
{{/if}}

{{input}}

This would ensure that the label is associated with the input. Thoughts?

@johnotander, no, that would not associate with the input.  You would need a for attribute, which is missing in your example.  There should always be a label, regardless of whether the user specified one.  I think that the label should get the visuallyhidden treatment if the user does not specify one.


feature: Add edit_form_query method

This PR resolves #733.
The changes here should allow users to customize the query that populate the edit form for their models, so that they can filter the relationships to show just the relevant information (see this discussion post for reference).
Because the default function behaviour requires the primary key of the object for the form, I changed the scope of this PR to address the edit form, instead of both the edit and create forms.
The example that I added to the docs in the optimize_relationship_loading.md file has been tested locally. I didn't add it to the project, as the test_model.py file doesn't have the Parent or Child classes. If you'd like me to add the test for the sake of completeness, I can do so.

@aminalaee can you review this PR when you have some free time?

@aminalaee can you review this PR when you have some free time?
Sure, I will do that today or tomorrow. Thanks for the PR 👍

Thanks for the explanation. I think it should be up to the user to use this properly. The default behaviour workws, and they can override the method and make sure it ia working again. We cannot control what the User might do with the query.
The reason I changed your code was that it was relying on a private method and the public one was checking if it was overridden which again is an anti-pattern.


Implement JWT verification

Added JWT verification using jose4j. I used that library instead of JJWT (as suggested on https://github.com/ekoshkin/teamcity-azure-active-directory/issues/6) mainly because this class drastically simplifies the azure signing key rollover requirement.

@ekoshkin I reverted the changes regarding the login error details. Do you suggest to open an issue on teamcity?

Nice!
I'll handle TeamCity core issue. Will post a link here.
Thank you for your PR once again!

TeamCity issue https://youtrack.jetbrains.com/issue/TW-48217


[visit-struct] Update to 1.1.0 and prefix targets with unofficial

This PR updates visit-struct to 1.1.0 after the recent tag: https://github.com/cbeck88/visit_struct/releases/tag/v1.1.0 . As I also noticed that the targets installed were not complaint with the mantainer guide, I also fixed those.

[x] Changes comply with the maintainer guide
[x] SHA512s are updated for each updated download
[x] The "supports" clause reflects platforms that may be fixed by this new version
[x] Any fixed CI baseline entries are removed from that file.
[x] Any patches that are no longer applied are deleted from the port's directory.
[x] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[x] Only one version is added to each modified port's versions file.

The usage has been tested successfully locally.
find_package(unofficial-visit_struct CONFIG REQUIRED)
target_link_libraries(main PRIVATE unofficial::visit_struct::visit_struct)

Thanks!


Created Pipelined Pease FFT

Builds a pipelined PEASE FFT.

I think we have to swap to z3 to make this pass - currently timing out due to discharge because I added more to the test harness.

Tests pass now, LMK whether the stuff in the apps directory is organized well, and then we should be able to merge this.


Replace deprecated babel package

Warning when installing the package:
warning @bagaar/ember-graphql-mocking > ember-cli-babel ><EMAIL_ADDRESS>This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-private-methods instead.

Guess we should move to using https://www.npmjs.com/package/@babel/plugin-transform-private-methods

I think we need to move this ticket to the ember-cli-babel repo.

Closing, as I believe this should be addressed over in https://github.com/emberjs/ember-cli-babel.


Facility Not Disassociating When Unchecked in Quick Edit

Current Behavior:
When attempting to disassociate a facility from a facility group by unchecking the associated checkbox in the quick edit mode, the facility remains associated despite the checkbox being unchecked. Additionally, the toast notification erroneously indicates that the association was successful.
Expected Behavior:
The facility should be successfully disassociated from the facility group when the associated checkbox is unchecked in the quick edit mode. The toast notification should accurately reflect the status of the disassociation process.
Steps to Reproduce the Issue:

Click on the quantity on the facility card.
Select "Quick Edit" from the options.
Uncheck the checkbox corresponding to the facility that needs to be disassociated.
Save the association changes

Watch the screen recording here: https://jam.dev/c/5acb682b-f7a3-4de1-8a23-4b11636ae183

Website URL:
https://facilities.hotwax.io/find-groups
Device and browser info:
Chrome 120.0.6099.199 (1440x813) | Mac OS (arm) 10.15.7
Date and time:
February 21st 2024 | 2:04pm UTC
View developer information (console logs, network requests & timing):
jam.dev/c/5acb682b-f7a3-4de1-8a23-4b11636ae183

Captured with jam.dev

Unable to regenerate this issue.


Is it possible to have shuffle and repeatAll mode enabled together?

Yes, audioPlayer.mode = [.shuffle, .repeatAll]


cmd/cue: intermittent #FileInfo errors when parsing cue

Originally opened by @tonyhb in https://github.com/cuelang/cue/issues/1043

v0.4.0

Does this issue reproduce with the latest release?
Yes
What did you do?
	cfg := &load.Config{
		Dir:        "/",
		ModuleRoot: "/",
		Overlay:    map[string]load.Source{},
	}
	cfg.Stdin = strings.NewReader(input)
	instances := load.Instances([]string{"-"}, cfg)

	if len(instances) != 1 {
		return nil, errors.Errorf("unsupported number of instances: %!d(MISSING)", len(instances))
	}

	runtime := cuecontext.New()
	inst := runtime.BuildInstance(instances[0])
	if err := inst.Err(); err != nil {
		buf := &bytes.Buffer{}
		cueerrors.Print(buf, err, nil)
		return nil, errors.Wrap(ErrInvalidConfig, buf.String())
	}

Every 1 in ~8 times, Cue will error when validating it's own cue files:
#FileInfo.definitions: could not parse arguments: cannot convert non-concrete value bool:
    types.cue:26:2
#FileInfo.optional: could not parse arguments: cannot convert non-concrete value bool:
    types.cue:27:2
#FileInfo.const
raints: could not parse arguments: cannot convert non-concrete value bool:
    types.cue:28:2
#FileInfo.keepDefaults: could not parse arguments: cannot convert non-concrete value bool:
    types.cue:29:2
#FileInfo.incomplete: could not parse arguments: cannot convert
non-concrete value bool:
    types.cue:30:2
#FileInfo.imports: could not parse arguments: cannot convert non-concrete value bool:
    types.cue:31:2

What did you expect to see?
No errors, as the cue input is valid.
What did you see instead?
Errors parsing cue's own internal definitions.

@tonyhb apologies for the delay in getting round to this, we've been busy migrating to a new home.
Please can you provide a repro that gives the errors you are seeing above? I'm not able to reproduce this given the snippets included above. Thanks

Also running into this:
could not parse arguments: #FileInfo.definitions: cannot convert non-concrete value bool

The weird thing is that it works when I run it via the cli. I've tried to simplify to get reproduction steps but so far I haven't been able to...
@tonyhb Did you find a solution to this? How did you reimplement the dependency resolution?

Still no idea what's triggering this but what made it work for me is this:
--- a/internal/filetypes/types.cue
+++ b/internal/filetypes/types.cue
@@ -289,6 +289,7 @@ forms: data: {
 // encodings: "": error("no encoding specified")

 encodings: cue: {
+       forms.schema
        stream: false
 }

In the calls to filetype.FromFile the b.Form field was empty so the FileInfo was indeed never fully filled in.

@jgillich please can you provide a full repro that shows the problem here?
Per my comment in https://github.com/cue-lang/cue/issues/1043#issuecomment-889213976 I haven't been able to reproduce this using the snippets above.

@myitcv I've tried to make a repro but couldn't, although now I have. The issue was concurrent access of cue.Build and load.Instances, which use a shared runtime behind the scenes. This is why I've only been able to reproduce this issue from within my operator, and synchronizing access fixed it. A better fix would be using cuecontext if not for #1484, but it can't be used with loader, right?
Here's that repro if you still want it: https://github.com/jgillich/cue-fileinfo
Remove the mutex calls and you should get either the FileInfo error or a panic: not properly initialized

@jgillich @tonyhb - I've moved this to https://github.com/cue-lang/cue/issues/1746 which includes a repro. Thanks for helping to narrow down the problem here.

@myitcv I see the FileInfo error even with the mutex in place with v0.4.3.
We do load.Instances and then cuecontext.New().BuildInstance.
The first call does not panic with a global mutex, but we see a FileInfo error when we get a Value from the instance and check for an error. A fully unwrapped error is below
#FileInfo.definitions: could not parse arguments: cannot convert non-concrete value bool (from types.cue:26:2)
types.cue:27:2 #FileInfo.optional: could not parse arguments: cannot convert non-concrete value bool (from types.cue:27:2)
types.cue:28:2 #FileInfo.constraints: could not parse arguments: cannot convert non-concrete value bool (from types.cue:28:2)
types.cue:29:2 #FileInfo.keepDefaults: could not parse arguments: cannot convert non-concrete value bool (from types.cue:29:2)
types.cue:30:2 #FileInfo.incomplete: could not parse arguments: cannot convert non-concrete value bool (from types.cue:30:2)
types.cue:31:2 #FileInfo.imports: could not parse arguments: cannot convert non-concrete value bool (from types.cue:31:2)
types.cue:26:2 #FileInfo.definitions: could not parse arguments: cannot convert non-concrete value bool (from types.cue:26:2)
types.cue:27:2 #FileInfo.optional: could not parse arguments: cannot convert non-concrete value bool (from types.cue:27:2)
types.cue:28:2 #FileInfo.constraints: could not parse arguments: cannot convert non-concrete value bool (from types.cue:28:2)
types.cue:29:2 #FileInfo.keepDefaults: could not parse arguments: cannot convert non-concrete value bool (from types.cue:29:2)
types.cue:30:2 #FileInfo.incomplete: could not parse arguments: cannot convert non-concrete value bool (from types.cue:30:2)
types.cue:31:2 #FileInfo.imports: could not parse arguments: cannot convert non-concrete value bool (from types.cue:31:2)
types.cue:26:2 #FileInfo.definitions: could not parse arguments: cannot convert non-concrete value bool (from types.cue:26:2)
types.cue:27:2 #FileInfo.optional: could not parse arguments: cannot convert non-concrete value bool (from types.cue:27:2)
types.cue:28:2 #FileInfo.constraints: could not parse arguments: cannot convert non-concrete value bool (from types.cue:28:2)
types.cue:29:2 #FileInfo.keepDefaults: could not parse arguments: cannot convert non-concrete value bool (from types.cue:29:2)
types.cue:30:2 #FileInfo.incomplete: could not parse arguments: cannot convert non-concrete value bool (from types.cue:30:2)
types.cue:31:2 #FileInfo.imports: could not parse arguments: cannot convert non-concrete value bool (from types.cue:31:2)

So I think this one is separate from the concurrency issues.
Very hard to reproduce though...


Don't create NFS shares for ephemeral hubs

With #123, we can create ephemeral hubs that don't have
any attached storage. However, an NFS share is still
created for these hubs, and unnecessary helm values are
set. We should clean it up, only creating the share when
needed.
Persistent storage is a facet of all hubs, and needs to
be a bit dynamic - so we should probably pay special
attention to how it can be configured. Perhaps a top-level
item in the config, rather than just JupyterHub overrides?

Ephemeral hubs don't exist anymore, with #361.


Set generated ssh key after packer workflow to readonly 0400

It is not possible to change file permissions on a Windows file system using the chmod command typically used in Unix-like systems. Packer is written in Go, therefore we cannot change the file permissions in a cross os-compatible.
Windows uses a different system for managing file permissions called Access Control Lists (ACLs). ACLs provide more fine-grained control over permissions compared to the traditional Unix file permission system.
To change file permissions in Windows, you would typically use the icacls or cacls commands depending on the version of Windows you are using.
For example, to grant read-only access to the owner on a file using icacls, you could use the following command:
icacls "C:\path\to\file" /grant:r "OwnerUsername":R

This command grants the user specified by "OwnerUsername" read-only access rights on the file located at "C:\path\to\file".
Please note that these commands are specific to Windows and may vary slightly based on the version of Windows you are using.
We must aim for a seamless cross-os experience or resign to a clear workaround. This workaround will be detailed in the documentation.
Another workaround could be adding a ps1 script but that would complicate things as we would need to account for admin access as well as the right user running the command.
This makes it harder to test as we would to have two scripts. One for windows and another one for unix-like systems.
Therefore we opt for adding the workaround to our documentation


adding a client when source is not added

server is up and running, but registry does not have yet the source. Both remote node and remote registry don't successfully process link message.
The connection is set up so  client side won't retry connection, but link message should be send again.
The solution would be

service discovery - sending request only when service is available
storing sent requests for which we didn't got init message back. Those need to be re-send with some repeat time period

This more of a olink protocol change, right?
All implementations should behave similar.

depends- service discovery yes
server storing request until they are handled (or with some timeout) and init sent back - doesn't change olink

On the two separate issues:

This is a different feature request adding a zeroconf on top of olink -> create new issue
Make sure documentation, tests and examples only start listening on the server side once all sources are set up


feat: Update qc sites

Description

Update list of websites
Remove weird non-unicode characters from data collected during scrapes

I will rebase this on top of the latest PR with the working model to make sure everything works well once it gets merged to master


Update lifecycle-badges.md

Update badges so img informative

Closing as it is now implemented in #127


executor: add PC to kcov_comparison_t

KCOV comparisons support is in the kernel mm tree already, and the
patch contains an additional uint64_t to store PCs of functions calling
__sanitizer_cov_trace_XXX().
Change kcov_comparison_t accordingly.

PTAL

PTYAL


fix save and resume load

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.wangguoxia seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Error while executing python preprocess_img.py script

Hi, I have encountered the below error on executing preprocess_img.py script. can you please help on this issue.

The preprocessing method use GPU explicitly. If you do not have a GPU, you may remove the gpu assignment here:
https://github.com/microsoft/Deep3DFaceReconstruction/blob/5b131a3e67597da67409486e20db50007f48427d/preprocess_img.py#L127


Add Function/Lambda Layer

Working on this currently, IMO a major functionality addition to the Layer API we currently have. This would allow for any differentiable function to be wrapped around and added as a layer in a model.
Also avoids API redundancies for layers like reshape, padded etc.
I'm currently getting the error that the layer doesn't conform to protocol of Layer and that a call function is needed. As far as i understand, for a structure to inherit a protocol, you need to extend and define all the functions in the protocol, something like abstract classes theoretically. Any thoughts on where i might be going or doing it wrong?

Which toolchain are you using? Seems to compile fine on the June 17 nightly, thought I haven't tested it.

@dan-zheng Yeah on it.

Alright @rxwei , @dan-zheng I'd like to ask a few things:

Are there any layers that we need to remove which are just wrapper functions currently?
Could I write a tutorial about this functionality, and if yes how could i go about doing that?

Also the build and tests pass locally, I'm just getting the documentation right now.

Are there any layers that we need to remove which are just wrapper functions currently?

We don't need to remove anything at the moment. But now that I think about it, I think that a protocol for function layers could be interesting. Any conforming type can get an automatically-implemented callAsFunction(_:) method.
public protocol FunctionLayer: Layer {
    @noDerivative
    var function: @differentiable (Input) -> Output { get }
}

public extension FunctionLayer {
    func callAsFunction(_ input: Input) -> Output {
        function(input)
    }
}

With this, you can redefine a Tanh layer like this:
struct Tanh<Scalar: TensorFlowFloatingPoint>: FunctionLayer {
    @noDerivative var function = tanh
}

But yeah, it is still a wrapper, not the best interface. It would be great if Swift supported function conforming to protocols, in which way all differentiable functions can conform to Layer. This is one of the directions we can look into later with the Swift community.

Could I write a tutorial about this functionality, and if yes how could i go about doing that?

It is great that you are looking to write a tutorial about it! However, as you've seen in the test case, this functionality is a bit cumbersome in that it requires the user to spell out the Input and Output types. I'd suggest holding off on this until we figure out a better way to make this functionality available, without the cost of requiring explicit generic arguments.

@rxwei So we discussed that layers like zero padding are just wrapper functions, So I'll mark them as done in the list with this functionality?

I put some more thoughts to this. I believe that it is still valuable to have layers ZeroPadding1D, ZeroPadding2D and ZeroPadding3D as structs defined in the library for API completeness (completing the layer list you presented!). After all layers have been ported, we can think about what to do in the long-term for reducing the boilerplate in these layer definitions.


Release/0.8.0

Missing open notification commit - will be added shortly.

Coverage decreased (-2.3%) to 63.235% when pulling d0fcf42c3898806c7bd1b45db8e741d1b5047823 on release/0.8.0 into 2ae91e49e4a67fb5bfae8973322b17566e036442 on master.

Looking good - please add a "Prepare for release" commit which updates CHANGELOG, README etc (see previous releases for examples)

Hey @mhadam - I am getting some problems here when I am trying to prepare for release (per https://github.com/snowplow/snowplow-objc-tracker/issues/337):
I am running:
$ pod lib lint --allow-warnings

And getting:
 -> SnowplowTracker (0.8.0)
    - ERROR | xcodebuild: Returned an unsuccessful exit code. You can use `--verbose` for more information.
    - WARN  | [OSX] xcodebuild:  FMDB/src/fmdb/FMDatabaseQueue.m:83:9: warning: 'dispatch_queue_set_specific' is only available on macOS 10.7 or newer [-Wunguarded-availability]
    - NOTE  | [OSX] xcodebuild:  /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.13.sdk/usr/include/dispatch/queue.h:1216:1: note: 'dispatch_queue_set_specific' has been explicitly marked partial here
    - NOTE  | [OSX] xcodebuild:  FMDB/src/fmdb/FMDatabaseQueue.m:83:9: note: enclose 'dispatch_queue_set_specific' in an @available check to silence this warning
    - WARN  | [OSX] xcodebuild:  FMDB/src/fmdb/FMDatabaseQueue.m:152:54: warning: 'dispatch_get_specific' is only available on macOS 10.7 or newer [-Wunguarded-availability]
    - NOTE  | [OSX] xcodebuild:  /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.13.sdk/usr/include/dispatch/queue.h:1272:1: note: 'dispatch_get_specific' has been explicitly marked partial here
    - NOTE  | [OSX] xcodebuild:  FMDB/src/fmdb/FMDatabaseQueue.m:152:54: note: enclose 'dispatch_get_specific' in an @available check to silence this warning
    - WARN  | [OSX] xcodebuild:  FMDB/src/fmdb/FMDatabase.m:245:49: warning: 'arc4random_uniform' is only available on macOS 10.7 or newer [-Wunguarded-availability]
    - NOTE  | [OSX] xcodebuild:  /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.13.sdk/usr/include/stdlib.h:279:3: note: 'arc4random_uniform' has been explicitly marked partial here
    - NOTE  | [OSX] xcodebuild:  FMDB/src/fmdb/FMDatabase.m:245:49: note: enclose 'arc4random_uniform' in an @available check to silence this warning
    - NOTE  | xcodebuild:  /Users/alex/Development/snowplow/snowplow-objc-tracker/Snowplow/SPUtilities.h:24:9: fatal error: 'UserNotifications/UserNotifications.h' file not found
    - ERROR | xcodebuild:  /Users/alex/Development/snowplow/snowplow-objc-tracker/Snowplow/SPUtilities.h:197:59: error: 'UNNotificationAttachment' is unavailable: not available on tvOS
    - NOTE  | xcodebuild:  /Applications/Xcode.app/Contents/Developer/Platforms/AppleTVSimulator.platform/Developer/SDKs/AppleTVSimulator11.3.sdk/System/Library/Frameworks/UserNotifications.framework/Headers/UNNotificationAttachment.h:13:12: note: 'UNNotificationAttachment' has been explicitly marked unavailable here
    - WARN  | [tvOS] xcodebuild:  /Users/alex/Development/snowplow/snowplow-objc-tracker/Snowplow/SPEmitter.m:320:26: warning: 'sendSynchronousRequest:returningResponse:error:' is deprecated: first deprecated in tvOS 9.0 - Use [NSURLSession dataTaskWithRequest:completionHandler:] (see NSURLSession.h [-Wdeprecated-declarations]
    - NOTE  | [tvOS] xcodebuild:  /Applications/Xcode.app/Contents/Developer/Platforms/AppleTVSimulator.platform/Developer/SDKs/AppleTVSimulator11.3.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSURLConnection.h:401:1: note: 'sendSynchronousRequest:returningResponse:error:' has been explicitly marked deprecated here

[!] SnowplowTracker did not pass validation, due to 2 errors.
You can use the `--no-clean` option to inspect any issue.

@alexanderdean forgot to mention the lint errors should be gone now

Legend! Thanks @mhadam, will give it a spin...


[Godot 4.3 Dev 3 Net] GodotTools.OpenVisualStudio.exe is missing

Tested versions
4.3 Dev 3
System information
Godot v4.3.dev3.mono - Windows 10.0.22631 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3060 Ti (NVIDIA; <IP_ADDRESS>33) - Intel(R) Core(TM) i5-10400F CPU @ 2.90GHz (12 Threads)
Issue description
While using Visual Studio as dotnet editor in 4.3 Dev 3, Godot fails to find OpenVisualStudio.exe in GodotSharp tools. Looking at the location, the file doesn't exist. Though the exe is there in 4.3 Dev 2.

/root/godot/modules/mono/editor/GodotTools/GodotTools/GodotSharpEditor.cs:279 - Error when trying to run code editor: VisualStudio. Exception message: 'An error occurred trying to start process 'E:/Godot/Godot_v4_3-dev3_mono_win64-b59039bd/Godot_v4.3-dev3_mono_win64/GodotSharp/Tools\GodotTools.OpenVisualStudio.exe' with working directory 'D:\Godot\4.3Testing'. The system cannot find the file specified.'

Steps to reproduce

Set Dotnet external editor to Visual Studio
Launch any .cs script from godot.

Minimal reproduction project (MRP)
4.3Test.zip

There are actually files there, just none of them have the .exe extension

Duplicate of https://github.com/godotengine/godot/issues/88447


Preparing for PyPI submittal

Would love to help you put django-jsonbfield in the cheese shop (pypi).  I'd like to put it in the  requirements.txt files for valrious TotalGood and Talentpair Django 1.8 apps that want to have a smooth upgrade to 1.9.

You might also want your repo to have the version tag so that the download link from PyPi works ;)
git tag -a v0.1.0 -m "Initial Release: Version 0.1.0"
git push --tag

python setup.py register -r pypitest worked after fixing the Topic string, so it's good to go with official pypi registration as soon as a tag v0.1.0 is created on the HearstCorp repo and this PR is merged

:+1: for this getting on pypi


The training details

Thanks your nice work. I am curious when you are convenient to release the training config.

Hi @kleinzcy, Thanks for your interest in this work!
Which training config file are you looking for?
We are working on an extension of the previous framework; the new framework is with an instance mixing module and is expected to support LiDAR panoptic segmentation as well. The training details and model checkpoints will be made publicly available by next month.

I am looking for semantickitti voxel lasermix.
Looking forward your updated framework.

Hi @kleinzcy, for training with LaserMix on SemanticKITTI using a voxel-based backbone, we recommend you first take a look at this implementation in MMDetection3D. We have now supported training Cylinder3D, MinkUNet, and SPVCNN with LaserMix.
For the updated framework: We will try to finalize this as soon as possible and let you know once the upgrade is ready. Thanks for waiting!


Frame.pose and frame.timestamp_micros not relating to the same thing?

Hi,
I would like to clarify one thing in the dataset.proto file. Each Frame  message contains pose and timestamp_micros and I always operated under the assumption that the pose defines the position of the car at time timestamp_micros. However, the frame.pose is the same as the pose in  frame.images[0].pose but the  frame.images[0].pose_timestamp * 1e6 != frame_timestamp_micros. Upon reading through the issues, I think now believe that frame.pose defines the pose of the car at the middle of the lidar spin (and the moment when front camera is triggered as they are synchronized), but on the other hand frame.timestamp_micros is he timestamp of the start of the lidar frame. Is my understanding correct now?
If this is actually the case, I think it should be explicitly noted in the dataset.proto that frame.timestamp_micros is not the timestamp of frame.pose as other researchers might also assume that.
Thank you for your help
Zan

Hi Zan,
Thanks for your feedback! You are right that frame.pose and frame.timestamp_micros are not corresponding. We understand that this is confusing, especially since there exists such a correspondence in CameraImage between pose and pose_timestamp, and we also understand that it is also not clearly documented.
You are right that frame.timestamp_micros is the timestamp of the start of the LiDAR spin, and frame.pose defines the vehicle pose near the middle of the LiDAR spin. One caveat is that frame.pose is not guaranteed to always exactly equal the front camera image pose because of slight synchronization differences, although it can be the case.
We will revise the documentation in dataset.proto to reflect this more clearly. Please let us know if you have any other questions or additional feedback.
Best,
Vincent, on behalf of the Waymo Open Dataset team


RUMM-1920 Do not override 'service' property for WebView tracked events

What does this PR do?
We do not override anymore the service property in the RUM events received through the JSBridge with out own internal value.
Motivation
What inspired you to submit this pull request?
Additional Notes
Anything else we should know when reviewing?
Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] Make sure you discussed the feature or bugfix with the maintaining team in an Issue
[ ] Make sure each commit and the PR mention the Issue number (cf the CONTRIBUTING doc)

Codecov Report

Merging #815 (dd54214) into feature/hybrid-application (c20beba) will decrease coverage by 8.81%.
The diff coverage is 91.86%.

@@                       Coverage Diff                        @@
##             feature/hybrid-application     #815      +/-   ##
================================================================
- Coverage                         89.27%   80.46%   -8.81%
================================================================
  Files                               212      254      +42
  Lines                              6767     8474    +1707
  Branches                            766     1449     +683
================================================================
+ Hits                               6041     6818     +777
- Misses                              499     1310     +811
- Partials                            227      346     +119

Impacted Files
Coverage Δ

.../datadog/android/core/internal/thread/ThreadExt.kt
83.33% <ø> (+58.33%)
:arrow_up:

...g/android/rum/internal/domain/scope/RumRawEvent.kt
61.83% <0.00%> (-38.17%)
:arrow_down:

...om/datadog/android/rum/webview/RumWebViewClient.kt
100.00% <ø> (ø)

.../com/datadog/android/tracing/TracingInterceptor.kt
76.99% <0.00%> (+1.13%)
:arrow_up:

...n/com/datadog/android/core/internal/CoreFeature.kt
93.07% <50.00%> (+0.46%)
:arrow_up:

.../internal/rum/WebViewRumFilePersistenceStrategy.kt
54.55% <54.55%> (-1.98%)
:arrow_down:

...oid/src/main/kotlin/com/datadog/android/Datadog.kt
75.83% <66.67%> (-0.40%)
:arrow_down:

.../android/rum/internal/domain/scope/RumViewScope.kt
95.99% <66.67%> (-0.05%)
:arrow_down:

...rnal/system/BroadcastReceiverSystemInfoProvider.kt
97.06% <75.00%> (+18.27%)
:arrow_up:

.../android/rum/internal/monitor/DatadogRumMonitor.kt
94.48% <75.00%> (-2.09%)
:arrow_down:

... and 191 more

LGTM 👌, however I wonder if we won't be still overriding service from here:
https://github.com/DataDog/dd-sdk-android/blob/c73d65ea3fd0f1f342683e5f814c9e7674589537/dd-sdk-android/src/main/kotlin/com/datadog/android/rum/internal/net/RumOkHttpUploaderV2.kt#L33
We have the same logic in dd-sdk-ios, where service is sent as query parameter (in contrast - we don't write it in events). What will be the result of processing it on BE if service A is given by event, but service B is given in query?

@ncreated that is a very good observation and I actually do not know the answer. I will take this further with Louis next week to see if there are any implications.

I am actually not even sure if the service at the event level is used, probably is the same situation as with the source and the tag is created directly from the service in the query parameters. If that's the case I think to support the sub - apps we will have to drop this and only use the service at the event level.


[Bug] drop 'ALL' is not covering the 'CAP_NET_RAW' inside capabilities for securityContext, throws warnings

Kyverno Version
1.8.x
Kubernetes Version
1.23.x
Kubernetes Platform
Other (specify in description)
Description
Despite using drop 'ALL' , in capabilities inside securityContext, get events throws warnings asking for to drop 'CAP_NET_RAW' , as seen in code snippet below:
securityContext:
      allowPrivilegeEscalation: false
      capabilities:
        drop:
        - ALL
      readOnlyRootFilesystem: true
      runAsGroup: 1001
      runAsNonRoot: true
      runAsUser: 1001
      seccompProfile:
        type: RuntimeDefault

warnings seen for these values as below:
**Warning   PolicyViolation     deployment/yard-umbrella-proxy              policy drop-cap-net-raw/autogen-require-drop-cap-net-raw fail: validation failure: Containers must drop the CAP_NET_RAWcapability.**
Steps to reproduce

securityContext:
allowPrivilegeEscalation: false
capabilities:
drop:
- ALL
readOnlyRootFilesystem: true
runAsGroup: 1001
runAsNonRoot: true
runAsUser: 1001
seccompProfile:
type: RuntimeDefault

kubectl get events -n
Expected behavior
No warnings
CAP_NET_RAW is covered by 'ALL'
Screenshots
No response
Kyverno logs
No response
Slack discussion
No response
Troubleshooting

[X] I have read and followed the documentation AND the troubleshooting guide.
[X] I have searched other issues in this repository and mine is not recorded.

Kyverno's policy language is additive in nature. If you have two policies, one saying to require drop ALL and another to say drop CAP_NET_RAW, a Pod will have to do both to not get caught by any other rule. You can make adjustments here by using the policy spec level setting applyRules here: https://kyverno.io/docs/writing-policies/policy-settings/

just to clarify more,
is this not okay:
securityContext:
     capabilities:
         drop: ["ALL"]

if i want to use drop capabilities to drop all ,
or is it that i need to use
securityContext:
    capabilities:
        drop: ["ALL" , "CAP_NET_RAW"]

i get the warnings to drop "ALL" in deployment object and also drop "CAP_NET_RAW" in pod object of the same namespace.

The first is fine if you want to drop all capabilities.

I have tried using just the ALL option, but then i get the warning in the get events logs for the same namespace in deployment object asking containers to drop CAP_NET_RAW like I mentioned in warnings above. To get rid of this i have to specifically use option 2
securityContext:
    capabilities:
        drop: ["ALL" , "CAP_NET_RAW"]

As I said, it's because you also have a policy that says to drop CAP_NET_RAW.

@chipzoller what is the intent of the https://github.com/kyverno/policies/blob/main/best-practices/require_drop_cap_net_raw/require_drop_cap_net_raw.yaml policy?
Is it not to verify that the underlying container does not have access to this capability? If that is the case, "ALL" would also succeed in doing so.
If that is not the case, is there any advantage, in terms of security, to verifying only for explicit dropping of CAP_NET_RAW?

The intent of that policy is only to drop one specific capability. Yes, we understand ALL would also do the job, but some users want explicit control, and that's what this policy does. Policies in the library are just "options" that are available. They're not designed to be taken all together.
I'm closing this issue since it doesn't seem to be a bug but happy to continue discussions.

@fadecore I think what you've written make sense, but I think this would be easier to have this discussion in context of actual changes to actual policies you're proposing. I would recommend you open a PR against the policies in question, make the changes you think are best, and explain in the comments section, succinctly, why you think they're best. I'm glad to discuss with you there.

If you do choose to open such a PR, please mention this issue number for tracking purposes.


return the stderr stream with "Bash wrote one or more lines to the standard error stream." for troubleshooting

Troubleshooting
Checkout how to troubleshoot failures and collect debug logs: https://docs.microsoft.com/en-us/vsts/build-release/actions/troubleshooting
Environment

Server - VSTS or TFS on-premises?

If using VSTS, provide the account name, team project name, build definition name/build number:

VSTS
account name: watchmixer

Agent - Hosted or Private:

If using private agent, provide the OS of the machine running the agent and the agent version:

private
CentOS Linux release 7.4.1708 (Core)
agent version: 2.127.0

Issue Description
When a release task is set to fail on stderr, not enough feedback is provided on failure to troubleshoot the problem.
The only feedback is "Bash wrote one or more lines to the standard error stream."
This makes it very difficult to troubleshoot those errors. It would be nice to have the stderr output.
Right here, it looks like you could accumulate the data (stderr stream) into a string, then pass it along with the error message.
https://github.com/Microsoft/vsts-tasks/blob/b6ca8a23cbdc5f825ebe3d260664073e079f1f1e/Tasks/CmdLine/cmdline.ts#L50-L52
I'm currently looking for a workaround to get those error messages, as they aren't being printed from my scripts.

it should be in the log, correct?

queue: hosted linux preview
steps:
- bash: echo hello from stderr 1>&2
  failOnStderr: true

Yes, it writes it to the log
https://github.com/Microsoft/vsts-tasks/blob/b6ca8a23cbdc5f825ebe3d260664073e079f1f1e/Tasks/CmdLine/cmdline.ts#L42
Reactivate if you're not seeing it in the log

We are not seeing the error in the logs, please, reactivate.

@farrukh-normuradov can you download the logs zip and check there? Sometimes the streaming console can miss a web event. But I would expect to see the error in the downloaded log.

@ericsciple, I did that. The logs file contains the same logs that are presented through the UI. I also turned on debug mode and agent diagnostics.
The only error containing phrase is this:

I search for "err" in the logs and do not find an error.
I ran build multiple times.
Some extra info:

It is npm install that fails
I load packages from private registry
When I remove private registry package, the issue persists
Only when I remove most of the dependencies, and leave lodash I get a green build

+1 on the issue. Unable to find the errors. It is an "ant" command that is run inside the bash task. Build is successful but bash complains of errors.
Error: #[error]Bash wrote one or more lines to the standard error stream.
Task         : Bash
Description  : Run a Bash script on macOS, Linux, or Windows
Version      : 3.148.2

We have 5000 lines of output in a build that succeeds completely, but that prints this error and marks the build as failed. It is impossible to figure out which of the 5000 lines was written to stderr. This is not a usable feature without a way to distinguish stderr output from stdout output.
If the UI could just color stderr output red, or call it out separately, or write it to a stdout.log file, or any of a number of things we could be easily unblocked.
As a workaround we have added this to the end of our script run. It will print "STDERROR" before the lines that were printed to stderr, and the extra >&2 make sure the result is still actually printed to stderror so the build will fail.
2> >(while read line; do (>&2 echo "STDERROR: $line"); done)
This is a pretty silly workaround, there should be a first class way of debugging this.

Same issue. Running a shell script that completes and exits with 0 but the job/task fails with:
Error: #[error]Bash wrote one or more lines to the standard error stream.
But I run this script on multiple environment and 50% fails and the other 50% succeeds.

Having the same error. Any idea?

==> Downloading from https://github-production-release-asset-2e65be.s3.amazonaws.com/45861018/d7233980-b740-11e8-8a89-b30a1e0ac118?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20191025%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20191025T032427Z&X-Amz-Expires=300&X-Amz-Signature=3b8eb6339119ea8413ec2b27a14273171621c38b47d64e9fa132b7e185313db8&X-Amz-SignedHeaders=host&actor_id=0&response-content-disposition=attachment%3B%20filename%3Dgit-credential-manager-2.0.4.jar&response-content-type=application%2Foctet-stream
🍺  /usr/local/Cellar/git-credential-manager/2.0.4: 4 files, 2.4MB, built in 4 seconds
Cloning spec repo `msblox` from `git@ssh.dev.azure.com:v3/msblox/CocoaPods/CocoaPods`
##[error]Bash wrote one or more lines to the standard error stream.```

Same problem here. Maybe it does indeed redirect the error to stdout, but since it's indistinguishable from the regular output there's no way of knowing which line that's the culprit.

Same problem here. Maybe it does indeed redirect the error to stdout, but since it's indistinguishable from the regular output there's no way of knowing which line that's the culprit.

Yes @denravonska that is correct.
The script I pasted above is intended to allow you to annotate the output of bash with STDERROR for anything that goes there, for example
bbuzbee@bbuzbee-dev:/$ (ls broken || ls .) 2> >(while read line; do (>&2 echo "STDERROR: $line"); done)

Will print
STDERROR: ls: cannot access 'broken': No such file or directory
bin  boot  cdrom  dev  etc  home  initrd.img  initrd.img.old  lib  lib64  lost+found  media  mnt  opt  proc  root  run  sbin  snap  srv  swapfile  sys  tmp  usr  var  vmlinuz  vmlinuz.old

This has been invaluable for my team to diagnose what actually failed when shelling our to a sufficiently complex command.
I suggest you folks bang on PR #9391 since @damccorm made a simple fix for this a year ago that is being soundly ignored and simply needs to be looked at by an area owner at Microsoft like @stephenmichaelf @jtpetty.

@benbuzbee Thanks, I'll try it out. I just assumed that failure triggers would verbosely be printed in the logs.

@benbuzbee Your suggestion worked perfectly, without it I would have had no idea how to track down the issue. It goes to show how important such a trivial feature is to the users.

@bryanmacfarlane was this issue ever fixed?

This issue still needs to be fixed for AzureCLI@2 tasks


Starting equipment

I'd be pretty sweet to be able to select what equipment to start with, e.g. starting with 10 bombs in Zelda.

Putting this down for future reference. While Archipelago doesn't support an initial inventory for SMZ3, it does support it for both Z3 and SM (even though VARIA does not unless I'm missing it). We may be able to use that to figure out how to implement starting equipment for SMZ3.


Code duplication between model and analysis document editors

Following #164, there is significant code duplication between ModelDocumentEditor and AnalysisDocumentEditor: the code for the resizable/collapsible panels is copy-pasted. We should refactor this to ensure a consistent UI over time.

Resolved as a by-product of #199. I suspect that we will have to revisit this in the future, since the split pane UI is generally useful, but closing for now.


apstra_ipv6_pool allocation issue - 0.61.0

Hello,
We have tried a new Apstra provider version 0.61.0 as well as 0.60.0 and we got the same error each time. Version 0.59.1 works fine.

resource "apstra_ipv6_pool" "ZAM_DC1_LO0_IPV6" {
name = "ZAM_DC1_LO0_IPV6"
subnets = [
{ network = "XXXXXXXXXXXXXX::/56" }
]
}
resource "apstra_ipv6_pool" "ZAM_DC1_TRANSFER_EXTERNAL_IPV6" {
name = "ZAM_DC1_TRANSFER_EXTERNAL_IPV6"
subnets = [
{ network = "XXXXXXXXXXXXXX::/56" }
]
}
Regards,
Piotr

Hi @pyspiotr,
Thank you for opening this issue.
Is the problem consistently reproducible, or is it an intermittent sort of thing?
Thanks!

Hi Chris,
The problem can be reproduce each time.
Regards,
Piotr
W dniu pon., 22.07.2024 o 16:50 chrismarget-j @.***>
napisał(a):

Hi @pyspiotr https://github.com/pyspiotr,
Thank you for opening this issue.
Is the problem consistently reproducible, or is it an intermittent sort of
thing?
Thanks!
—
Reply to this email directly, view it on GitHub
https://github.com/Juniper/terraform-provider-apstra/issues/737#issuecomment-2243152645,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOFECNIR5G7BZBJU4QDS4OLZNUL2DAVCNFSM6AAAAABLIOIBLKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENBTGE2TENRUGU
.
You are receiving this because you were mentioned.Message ID:
@.***>

Hi @pyspiotr,
There have been a number of problems with the the various "pool" resources since they were originally conceived. This one seems have cropped up with provider v0.60.0's upgrade of github.com/hashicorp/terraform-plugin-framework from v1.5.0 to v1.9.0.
I don't think this problem (or any of the previous ones) are an issue with the plugin framework. Rather, they are fallout from an unfortunate design decision to capture mutable values (percent used, pool state, etc...) as Computed (read-only) resource attributes.
There are a handful of reasons that supporting these attributes cause problems. Worse, the values of these attributes can't really be trusted because they're only updated when Terraform's plan phase determines a modification to the resource is required. If the resource is never modified after creation, these values are guaranteed to become inaccurate as elements get consumed from the pool.
So, I'm proposing a breaking change to all of the "pool" resources: All mutable read-only attributes (total, status, used, etc...) will always be set to null.
If values from these attributes are needed in your Terraform project (to select the least-used ASN pool or whatever), you'll need to run the complementary data source for that object. Use of the data source will be an improvement over relying on the resource for these values because data sources are refreshed with each terraform apply while resources only get refreshed when the plan phase detects that a modification is required.
Does this work for you, or do you have any concerns about it?
cc: @bwJuniper @rajagopalans @michaelbhughes

Hi Chris,
It will work for me. Thank you.
Regards,
Piotr

Hi Chris,
Thanks for the notice. No concerns from me.
Regards,
Michael Hughes

v0.62.0 has the changes proposed in this discussion.
Please let me know if it solves the problem?

Hi Chris,
I got the same error as before,
Regards,
Piotr

Thank you @pyspiotr.
Would you please share the output of terraform version run from within the project directory?

Hi Chris,
Here you go: v1.7.5.

Regards,
Piotr

Hey @pyspiotr,
Can you please clarify what's going on with the provider version? You've rolled back to 0.59.1, but got the most recent error with 0.62.0?
Thanks!

Hi Chris,
I rolled back to 0.59.0 after the errror.
Regards,
Piotr

Update: I've reproduced the error:

terraform 1.7.5
plugin 0.59.1
create an IPv6 pool
upgrade plugin to 0.62.0
terraform apply

Will keep you posted.

Update 2: The same process does not produce an error with terraform 1.9.0 (the version I'd been testing with)
The procedure I've been using:
set v0.59.1 in the provider configuration
tfenv use 1.7.5
rm -rf .terraform* terraform.tfstate*
terraform init
terraform apply --auto-approve
terraform plan # expect no updates
set v0.62.0 in the provider configuration
terraform init --upgrade
terraform apply # expect state churn + error
tfenv use 1.9.0
terraform apply # expect no state churn, no error

I need to look into upstream terraform a bit. It might be worth trying things out with a newer version of terraform CLI.

Hi Chris,
It works now. Also with 0.64.0. Thank you for quick fix.
Cheers,
Piotr

Great!
Thank you for following up.


Use settlement date for effective date for data drawn from NSW VG PSI data

I actually used the date published instead as it seems to be the data at which this information was extracted from the NSW land registry service.
More here https://github.com/AKST/Australian-Address-Boundaries-Land-Property-Price-Database/wiki/meta.event-and-the-source-of-their-effective_dates


feat: Provide an addSource function on the OrderedReadable stream

Closes #19
This adds the addSource function to the returned stream, which can be used to push more streams onto the list of ordered sources.

cc @sttk


overdue list filter amendment

[days:due[0]] contrary to what we expect, only gives those tiddlers due today, on this day only, tiddlers due yesterday or before are omitted
[!days:due[-1]] gets the tiddlers that were due yesterday and before
so we need them both i think (or is this not the intended behaviour for the core filter?)
sorry for any typos i am cloning on mobile! also first time using the pull request on mobile, sorry if i've done it the wrong way
warmest wishes, maki

Thanks, that's a leftover from the old behavior, which was only showing items due today.

@makiaea I went with a slightly different implementation. I added the filter in filters.tid, you can see the commit here 4b4bc1c.

Thanks for noticing the bug and taking the time to open a PR though :+1: