commons:<IP_ADDRESS>  (Failed to resolve material-dialogs:core:unspecified )

Hi i didn't find any issuethreads for the <IP_ADDRESS> version yet since you released it yesterday but i am getting the:  "Failed to resolve material-dialogs:core:unspecified" in android studio everytime i include "com.afollestad.material-dialogs:commons:<IP_ADDRESS>" to dependencies. (:core works fine though)
I am using the previous version for another project and it works fine, but  :commons for <IP_ADDRESS> isn't working.
Is it a jCenter or jitpack issue?
regards William

I meet this problem too , Error:Failed to resolve: material-dialogs:core:unspecified .

The problem is in commons/build.gradle. There is a local dependency to the core project.
Michael

oh i see now. I hope that it's gonna be fixed soon. Would need that to work for my app

@MichaDo that's never been an issue before.
Using the remote version there would prevent the project from even being built locally, which prevents me from being able to publish it.

@afollestad do you have any idea why it's complaining to us?

@afollestad  I need it badly. Any other way to get it. I tried some old version too but the same result.

@shabbir-dhangot did you try the <IP_ADDRESS> version? below <IP_ADDRESS> you have to include:
maven {             url "https://jitpack.io"         }
to the root build.gradle
and then in your app build.gradle include the dependencies:
compile('com.github.afollestad.material-dialogs:core:<IP_ADDRESS>@aar') {         transitive = true     } compile('com.github.afollestad.material-dialogs:commons:<IP_ADDRESS>@aar')
it works perfectly for me.

@afollestad I don't no why this works in <IP_ADDRESS> but not in <IP_ADDRESS>. But :commons found no :core in local cache or not looking for. If I use both libs completely local it works fine. If I use only :commons local, :core from remote and replace compile project(':core') with compile('com.afollestad.material-dialogs:core:<IP_ADDRESS>') in build.gradle from :commons, it works also.
Maybe it helps if you have a direct referral to the local repository in :commons build.gradle:
repositories {
    mavenLocal()
}

Same issue here:
A problem occurred configuring project ':app'.
> Could not resolve all dependencies for configuration ':app:_googleplayDebugCompile'.
   > Could not find material-dialogs:core:unspecified.
     Searched in the following locations:
         https://jcenter.bintray.com/material-dialogs/core/unspecified/core-unspecified.pom
         https://jcenter.bintray.com/material-dialogs/core/unspecified/core-unspecified.jar
         https://jitpack.io/material-dialogs/core/unspecified/core-unspecified.pom
         https://jitpack.io/material-dialogs/core/unspecified/core-unspecified.jar
         https://maven.fabric.io/public/material-dialogs/core/unspecified/core-unspecified.pom
         https://maven.fabric.io/public/material-dialogs/core/unspecified/core-unspecified.jar
         file:/home/daniele/repository/android/android-sdk/extras/android/m2repository/material-dialogs/core/unspecified/core-unspecified.pom
         file:/home/daniele/repository/android/android-sdk/extras/android/m2repository/material-dialogs/core/unspecified/core-unspecified.jar
         file:/home/daniele/repository/android/android-sdk/extras/google/m2repository/material-dialogs/core/unspecified/core-unspecified.pom
         file:/home/daniele/repository/android/android-sdk/extras/google/m2repository/material-dialogs/core/unspecified/core-unspecified.jar
     Required by:
         androidclient:app:unspecified > com.afollestad.material-dialogs:commons:<IP_ADDRESS>

With:
dependencies {
    compile 'com.afollestad.material-dialogs:core:<IP_ADDRESS>'
    compile 'com.afollestad.material-dialogs:commons:<IP_ADDRESS>'
}

Jitpack version worked (last tried with <IP_ADDRESS>).

Same here.

Same issue:
Error:Failed to resolve: material-dialogs:core:unspecified

The pom file seems to be being generated incorrectly: https://jcenter.bintray.com/com/afollestad/material-dialogs/commons/<IP_ADDRESS>/commons-<IP_ADDRESS>.pom with the unspecified version for core and that's why it fails or cycles when trying to resolve the dependency (depending on the task).

Same issue here

I have the same problems:
Error:Could not find material-dialogs:core:unspecified.
Required by:
    XXX:app:unspecified > com.afollestad.material-dialogs:commons:<IP_ADDRESS>

I think, according to @jrgonzalezg the POM file should get corrected to:
<?xml version="1.0" encoding="UTF-8"?>
<project xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd" xmlns="http://maven.apache.org/POM/4.0.0"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <modelVersion>4.0.0</modelVersion>
  <groupId>com.afollestad.material-dialogs</groupId>
  <artifactId>commons</artifactId>
  <version><IP_ADDRESS></version>
  <packaging>aar</packaging>
  <dependencies>
    <dependency>
      <groupId>com.afollestad.material-dialogs</groupId>
      <artifactId>core</artifactId>
      <version><IP_ADDRESS></version>
      <scope>compile</scope>
    </dependency>
    <dependency>
      <groupId>com.android.support</groupId>
      <artifactId>appcompat-v7</artifactId>
      <version>23.4.0</version>
      <scope>compile</scope>
    </dependency>
  </dependencies>
</project>

That should do the trick...
Can you @afollestad  change these two lines and update the POM on jcenter?

I'm also facing this issue. Any workaround for this issue?

Downgrading to <IP_ADDRESS> for now.

@audiultx in one of my PC <IP_ADDRESS> @arr not working. It always show a
Error:(21, 13) Failed to resolve: com.github.afollestad.material-dialogs:commons:<IP_ADDRESS> Show in File
Show in Project Structure dialog
Can you help me with that.

@shabbir-dhangot  have you added:
compile('com.github.afollestad.material-dialogs:core:<IP_ADDRESS>@aar') {
transitive = true
}
to the build.gradle in your "app" directory?
and  maven {
url "https://jitpack.io"
}
to the root build.gradle in your project?
it should really work.

Yes @audiultx Its perfectly working in my PC. But when my mate importing that code in his laptop error comes. I have checked everything is proper but still not working.

@shabbir-dhangot hmm, it's hard to say what could be wrong when not having it infront of you. Except from trying to remove the dependency rebuild, then add it back and  rebuild i can't give any tips unfortunately.

@audiultx  actually I tried everything. I hope @afollestad  solve main issue soon.

@shabbir-dhangot thats very strange, let's hope @afollestad  can change the POM file like @InnoDayHackathonMasta proposed soon.

This post is for 16 days ago, any solution for this issue ?
Thanks :)

@marianpavel You can include core library dependency
compile 'com.afollestad.material-dialogs:core:<IP_ADDRESS>'.
Then download sources from https://github.com/afollestad/material-dialogs/releases/tag/<IP_ADDRESS> and add commons library as a module. And in your app build.gradle include
compile project(':commons-library-module-name')

@Falcon5f I will also try that and get back with the results.

@marianpavel Also don't forget to change commons' build.gradle:
replace
compile project(':core')
with
compile 'com.afollestad.material-dialogs:core:<IP_ADDRESS>'
(if you don't include core library as module in your project and follow my previous message)

Hello guys,
I try to integrate the core library compile 'com.afollestad.material-dialogs:core:<IP_ADDRESS>' in my application that does not work, it returns me an error like this Error:Failed to resolve: material-dialogs:core:unspecified.
However the other lib compile 'com.afollestad.material-dialogs:commons:<IP_ADDRESS>' it works well
I don't know what to do?

@Falcon5f  i´ve tried your solution now and it seams to work good, thank you very much man. Everyone here should try this solution:

Download the latest project from  https://github.com/afollestad/material-dialogs/releases/tag/<IP_ADDRESS>
File -> New -> New module (select the commons from the material-dialogs-<IP_ADDRESS>) , give a name to it
In the module you just imported, open the build.gradle
change "compile project(...)" to compile 'com.afollestad.material-dialogs:core:<IP_ADDRESS>'
In your apps build.gradle add compile project(':name-of-the-module')
Run a be happy.

Thanks for your efforts @audiultx but I don't see a big deal. Here is the diff between .8 and .9:
https://github.com/afollestad/material-dialogs/compare/<IP_ADDRESS>...<IP_ADDRESS>
I think I can afford building against .8 for a few days until @afollestad fixes it :-)

@audiultx  I'm glad that I could help you)

@audiultx I think this issue should stay open. Your fix is a workaround, importing MaterialDialogs directly via Maven still doesn't work, right?

Sry i accidently closed after I wrote the last comment.  Yeah it should still be open.  No it still doesn't work for me.

@audiultx  @daniele-athome @Falcon5f but author not trying to solve this, Might be he having some problem.

He might just be not available right now. Remember guys this is not his job probably (or he's on vacation or something).

@shabbir-dhangot today is a holiday, and I'm an employed software developer full time during the week.

Hi
I build the aar commons lib and I tested it works very well, you can download here
commons-release-<IP_ADDRESS>.zip

The problem is due to project :commons depending on :core and the build system being unable to identify the correct values of group, artifact and version of core to use when filling the commons pom.
This is currently being configured applying https://raw.githubusercontent.com/afollestad/aidanfollestad.com/master/android-release-aar.gradle at the end of core/build.gradle
If you just replace the contents of https://raw.githubusercontent.com/afollestad/aidanfollestad.com/master/android-release-aar.gradle with the contents of the attached txt (or something similar to that) it should work by re-generating the artifacts (gradle clean assemble generateRelease) and uploading the new versions to jcenter. A similar process can be applied to generate a local copy of the library with the fixed poms in a local maven repo for anyone wanting to depend on <IP_ADDRESS> before it gets fixed on jcenter.
android-release-aar.txt

One "easy" way for generating a working copy on the normal mavenLocal() repository on a developer machine will be to replace the last line of both core/build.gradle and commons/build.gradle with the contents of the txt in my previous comment, but replacing the uploadArchives section with:
uploadArchives {
    repositories {
        mavenDeployer {
            repository(url: mavenLocal().url)
        }
    }
}

Finally, to use it in your projects by using this method, you also need to have mavenLocal() in the repositories section of any project / module that needs to depend on this. It should then work just as if if were coming directly from a fixed version on jcenter. Also remember when declaring the dependency in your projects that the dependency group has changed in <IP_ADDRESS> from 'com.github.afollestad.material-dialogs' to 'com.afollestad.material-dialogs'.

@afollestad we appreciate your contribution towards the community. Please don't take it wrong.

any solution?

@ashishg656 just a workaround for now
here should try this solution:

Download the latest project from https://github.com/afollestad/material-dialogs/releases/tag/<IP_ADDRESS>
File -> New -> New module (select the commons from the material-dialogs-<IP_ADDRESS>) , give a name to it
In the module you just imported, open the build.gradle
change "compile project(...)" to compile 'com.afollestad.material-dialogs:core:<IP_ADDRESS>'
In your apps build.gradle add compile project(':name-of-the-module')
Run a be happy.

I solved it by doing this :
    compile 'com.afollestad.material-dialogs:core:<IP_ADDRESS>'
    compile ('com.afollestad.material-dialogs:commons:<IP_ADDRESS>'){
        exclude module: 'core'
    }

also add these lines to my main gradle file
allprojects {
    repositories {
        ..........
        maven { url "http://dl.bintray.com/drummer-aidan/maven" }
        maven { url "http://dl.bintray.com/drummer-aidan/maven/com/afollestad" }
    }
}

enjoy ...

@omidheshmatinia   answer fix this issue. please close this issue.

It's not a fix, it's still a workaround.

i fix that problem in a pull request @daniele-athome . waiting for someone to accept&merge that

That pull request causes other issues since you will not be able to compile new versions of the library without publishing it or going back and forth with the change of that PR. The fix i proposed will work for both current and future versions without requiring any project editing for compiling on different scenarios. It will also work with normal repository declaration and normal published artifacts to jcenter.

Is there any scenario in which we have new versions that are not published ?!?! if not how do you get them ?!
Also if we want to publish a new version, It is a must to change PUBLISH_VERSION Variable, isn't it?
Both Core and Common would update parallelly and that version parameter won't hurt anyone i guess @jrgonzalezg

Of course there is @omidheshmatinia ... during development. If you are developing new features that are not yet ready it makes no sense to be publishing them to be able to test / debug them. If you raise the publish version, as you say, the build for commons and sample will fail until core is up on jcenter because before that you are depending on a yet unpublished version of core. So basically, that setup will not work well and will require either constant alternating changes on the build.gradle or publication of "debug" versions of core to test commons and sample (and waiting for it to be published too).

Seems you are right :Y
@jrgonzalezg

All that needs to happen is to change the
compile project(':core')
line should instead be
provided project(':core')
This way, the core dependency would be resolved when working on the library, but would need to be manually resolved/added by each person who uses the lib

Well, after trying out the provided solution, I take back what I said. Apparently this would work properly with pure Java libraries, but causes issues when the library is a .aar dependency

No solutions have worked so far for publishing.

@auchri @Jawnnypoo @omidheshmatinia @jrgonzalezg @daniele-athome @radityagumay @ashishg656 @vonigo @shabbir-dhangot @Falcon5f @marianpavel @AkshayChordiya @csbenz @devslava @dirkam @MichaDo @wavever
Thanks everyone, <IP_ADDRESS> should now resolve through jCenter correctly: https://github.com/afollestad/material-dialogs/releases/tag/<IP_ADDRESS>

You're welcome!. I am glad you accepted my proposed solution :)


Add attachment API method

Please, add method for task attachment creation over API.

It's now available in the development version, see here: https://github.com/fguillot/kanboard/blob/master/docs/api-json-rpc.markdown#createfile


When click in some component in vue devtools it triggers a click event inside of component

I've created a button inside my component to splice some item in the array.
And when I click on the component in dev tools it triggers the event of my button and splices the selected item of the array.
Is that the correct behavior, if my component has some event?

No, it shouldn't happen. Can you boil down the error and provide a repro using this template?
Thanks!

Closing due to inactivity. Please open a new issue with a reference to this one if you can follow up with more information.


Typescript error: Duplicate identifier 'src'

When compiling with TypeScript, I get the following error:
node_modules/vite-plugin-solid-svg/types-component-solid.d.ts:4:18 - error TS2300: Duplicate identifier 'src'.

4   export default c
                   ~

  node_modules/vite/client.d.ts:135:18
    135   export default src
                         ~~~
    'src' was also declared here.

node_modules/vite/client.d.ts:135:18 - error TS2300: Duplicate identifier 'src'.

135   export default src
                     ~~~

  node_modules/vite-plugin-solid-svg/types-component-solid.d.ts:4:18
    4   export default c
                       ~
    'src' was also declared here.

I believe this is because of the fact that this plugin replaces the built-in vite svg import.

Cn you try with skipLibCheck: true in tsconfig?


bump byteorder to 1

Coverage decreased (-96.3%) to 0.0% when pulling 25cdf733150de6a5563e8f753a30e146b84a6bb1 on ignatenkobrain:patch-1 into b3773d2061134ecd4c7404ab5df08f1a9a856b24 on luser:master.

Coverage decreased (-96.3%) to 0.0% when pulling 25cdf73 on ignatenkobrain:patch-1 into b3773d2 on luser:master.

It looks like running kcov failed, but that seems unrelated to this PR.


Improvement - Badge colors

Hi, I propose to add ability to colorize a badge. Very simple change in colors css is required.

Merged, thanks


gradlew tasks should sort tasks groups according to a lifecycle or something like that

Expected Behavior
./gradlew tasks should provide user-friendly order rather than machine-friendly one.
For instance:
Getting started tasks
IDE tasks
Source validation tasks (e.g. static analysis)
Build tasks
Build verification tasks (e.g. tests, coverage)
Documentation tasks
Publishing tasks
Release tasks

I'm not sure if that would be an overkill, but it might make sense if user could configure "dependencies between build groups" so ./gradlew tasks would do a topological sort for the task groups.
For instance, if a new build group is added (e.g. "integration test tasks") by build script author, then they could specify that "integration test tasks" group depends on "Build verification tasks" group and Publishing tasks depend on "integration test tasks" group.
That would make task group order extensible.
Alternative (or additional) option is to infer group dependency from task dependencies, however it might be resource-intensive. On the other hand, it would transparently support things like "unit test tasks group" should be printed after "build tasks group" because "test tasks" depend on "build tasks"
Just for the reference, here's a current output of tasks:
------------------------------------------------------------
Tasks runnable from root project
------------------------------------------------------------

Build tasks
-----------
allDepInsight - Shows insights where the dependency is used. For instance: allDepInsight --configuration compile --dependency org.jsoup:jsoup
assemble - Assembles the outputs of this project.
build - Assembles and tests this project.
buildDependents - Assembles and tests this project and all projects that depend on it.
buildNeeded - Assembles and tests this project and all projects it depends on.
classes - Assembles main classes.
clean - Deletes the build directory.
createDist - Copies JMeter jars and dependencies to projectRoot/lib/ folder
jar - Assembles a jar archive containing the main classes.
renderLicenseForBinary - Generate LICENSE file for binary distribution
renderLicenseForSource - Generate LICENSE file for source distribution
testClasses - Assembles test classes.

Build Setup tasks
-----------------
init - Initializes a new Gradle build.
wrapper - Generates Gradle wrapper files.

Coverage reports tasks
----------------------
jacocoReport - Generates an aggregate report from all subprojects

Development tasks
-----------------
runGui - Builds and starts JMeter GUI

Distribution tasks
------------------
distTar - Creates binary distribution with LF line endings for text files
distTarSource - Creates source distribution with LF line endings for text files
distZip - Creates binary distribution with CRLF line endings for text files
distZipSource - Creates source distribution with CRLF line endings for text files

Documentation tasks
-------------------
groovydoc - Generates Groovydoc API documentation for the main source code.
javadoc - Generates Javadoc API documentation for the main source code.
javadocAggregate - Generates aggregate javadoc for all the artifacts
previewPrintableDocs - Creates preview of a printable documentation to build/docs/printable_preview
previewSite - Creates preview of a site to build/docs/site

Help tasks
----------
buildEnvironment - Displays all buildscript dependencies declared in root project 'jmeter'.
components - Displays the components produced by root project 'jmeter'. [incubating]
dependencies - Displays all dependencies declared in root project 'jmeter'.
dependencyInsight - Displays the insight into a specific dependency in root project 'jmeter'.
dependentComponents - Displays the dependent components of components in root project 'jmeter'. [incubating]
help - Displays a help message.
kotlinDslAccessorsReport - Prints the Kotlin code for accessing the currently available project extensions and conventions.
model - Displays the configuration model of root project 'jmeter'. [incubating]
projects - Displays the sub-projects of root project 'jmeter'.
properties - Displays the properties of root project 'jmeter'.
tasks - Displays the tasks runnable from root project 'jmeter' (some of the displayed tasks may belong to subprojects).

IDE tasks
---------
cleanEclipse - Cleans all Eclipse files.
cleanIdea - Cleans IDEA project files (IML, IPR)
eclipse - Generates all Eclipse files.
idea - Generates IDEA project files (IML, IPR, IWS)
openIdea - Opens the IDEA project

Publishing tasks
----------------
publish - Publishes all publications produced by this project.
publishAllPublicationsToNexusRepository - Publishes all Maven publications produced by this project to the nexus repository.
publishToMavenLocal - Publishes all Maven publications produced by this project to the local Maven cache.
pushPreviewSite - Builds and publishes site preview

Release tasks
-------------
closeAndReleaseRepository - Closes and releases an artifacts repository in Nexus
closeRepository - Closes an open artifacts repository in Nexus
createRcTag - Create release candidate tag if missing
createReleaseTag - Create release tag if missing
getStagingProfile - Gets a staging profile id in Nexus - a diagnostic task
prepareVote - Stage artifacts and prepare text for vote mail
publishDist - Publish release artifacts to SVN and Nexus
publishSvnDist - Publish release artifacts to SVN dist repository
pushRcTag - Push release candidate tag to a remote repository
pushReleaseTag - Push release tag to a remote repository
releaseRepository - Releases a closed artifacts repository in Nexus
stageDist - Stage release artifacts to SVN and Nexus
stageSvnDist - Stage release artifacts to SVN dist repository

Test tasks
----------
generatePom - test

Verification tasks
------------------
batchTests - Executes all the batch tests (add -PallBatch to see individual batch tasks)
calculateChecksums - Calculates and prints the checksums of the project dependencies
check - Runs all checks.
jacocoTestCoverageVerification - Verifies code coverage metrics based on specified rules for the test task.
jacocoTestReport - Generates code coverage report for the test task.
rat - Runs Apache Rat audit tool
spotbugsMain - Run SpotBugs analysis for main classes
spotbugsTest - Run SpotBugs analysis for test classes
test - Runs the unit tests.
verifyChecksums - Verifies checksums of the project dependencies

Current Behavior
Currently Gradle sorts task groups by lexicographical order.
It makes it hard to understand "where" to look for the required task.
Context
I'm migrating Apache JMeter's build to Gradle, and having "sensible" task order would simplify user experience, especially for Gradle newbies.

This is still relevant

I think this is still relevant


Incorrect pattern positioning

Attach (recommended) or Link to PDF file here:
pop-bugzilla41462.pdf
poppler issue:
https://bugs.freedesktop.org/show_bug.cgi?id=41462
Configuration:

Web browser and its version: FF 61.0.1 64bit
Operating system and its version: W7
PDF.js version: latest

Steps to reproduce the problem:

start pdf.js viewer url
open file

What is the expected behavior? (add screenshot)

What went wrong? (add screenshot)

This looks like another issue where PR #6606 might be relevant.


[PowerRename] use file meta tags /meta data to rename files

📝 Provide a description of the new feature
For example, you have  folder with photos with filenames like numbers and/or dates (001.jpg, 002.jpg, etc.), you can rename the files to have the folder name ("Product X-001.jpg").
ReNamer:Meta_Tags

What is the expected behavior of the proposed feature?  What is the scenario this would be used?
Rename files based on rules of meta tags values of the file.

If you'd like to see this feature implemented, add a 👍 reaction to this post.

This will be done after we switch the UI to WinUI 3.0

You mention both folder name and meta data, which is confusing for me. Can you elaborate or be a bit more specific? :)

Any update on this? This seems like a major missing feature.
https://www.rename-expert.com/examples/use_photo_taken_date_for_file_names.aspx

I'm missing this feature myself, which is why I'd want to implement it.
Are there any specifications of what features (metadata tags) should be implemented?
The File information, Audio Tags and Photo tags defined here ReNamer:Meta_Tags sound like a good list for the start.
Also in what way should these features be implemented to rename files?
One way to implement this would be a constant like "%FILE_SIZE%", "%ARTIST%" which can be used in the replace section.
Any other ideas, specifications or help is greatly appreciated.

A first proposition would be this:

Very similar to the regular expression help. There the metadata replacements are shown and can be selected. Once applied, these identifiers get replaced by the specific file metadata.
Regarding the metadata fetching:

[x] File information is simply done via the filesystem api
[ ] Audio metadata could be accessed via taglib
[ ] For images GDI+ might be an option

If there is no other option than adding external libraries for reading out the metadata tags, then I'd greatly appreciate any and all help with setting these up.

Power Automate has an example with exactly this use case. And it allows to use four different options for time stamps.


Unexpected behavior with removeAdditional and minProperties

What version of Ajv are you using? Does the issue happen if you use the latest version?
<EMAIL_ADDRESS>Ajv options object

{
  removeAdditional: true
}

JSON Schema

{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "additionalProperties": false,
  "minProperties": 1,
  "type": "object",
  "properties": {
    "good": {
      "type": "string"
    }
  },
  "required": []
}

Sample data

{ "bad": "will be removed" }

Your code

const Ajv = require("ajv");
const ajv = new Ajv(options);

const validate = ajv.compile(schema);

console.log(validate(data));
console.log(validate.errors);
console.log(data);

Working code sample:
https://runkit.com/vladislao/65c2a14a50acdd0009747ee5
Validation result, data AFTER validation, error messages
true
null
{}

What results did you expect?
The validation is expected to fail given the constraints of minProperties: 1 and additionalProperties: false. While it may be apparent in isolated examples that removing properties can lead to such behavior, the issue becomes less obvious when Ajv is used indirectly, such as in Fastify where Ajv is the default validation tool. This situation can easily lead to errors, allowing empty objects to slip through the validation process and potentially causing unexpected behavior and security issues in applications.
Related to https://github.com/fastify/fastify/issues/5104

Hi @Vladislao I have confirmed the behaviour you have highlighted, thanks for bringing it to our attention. It is a tough one because it all comes down to the order of evaluation of the various parts of this schema / options. Changing it could impact thousands of projects relying on the specific current order.
There is a way to control the order of execution by using the allOf keyword. You can see this example here where I have split the minProperties from the rest of the schema to ensure it is evaluate after the property is removed.
https://runkit.com/jasoniangreen/ajv-issue-2376

Given the risk of changing the order of execution I think this is a wontfix.


Update mac related dependencies

I also updated winit and wayland to avoid duping them

Thanks for the PR! However, it's more convenient for me to take care of this in #1081, since there were some other changes needed for updating to winit 0.18.0.

Sure ! :+1:


reply button missing: ⚠

Expected behavior
open any message click reply
Actual behavior
reply button replaced with non functional warning triangle
Steps to reproduce
Environment
K-9 Mail version: 5.403
Android version: 444
Account type (IMAP, POP3, WebDAV/Exchange):
all IMAP

Settings -> Display -> Visible message actions

Settings -> Display -> Visible message actions

There I get Delete, Archive, Move, Copy, Spam, but no Reply

There's an overflow menu.

The Reply item is hidden very deeply in that menu. Why is it not possibly to have both "Delete" and "Reply"?


Create T3 App logo renders incorrectly when using yarn or pnpx

Describe the bug
The "Create T3 App" logo renders correctly when ct3a is invoked with npx. But when yarn or pnpx are used, the top line is shifted to the right by one character.
To Reproduce
yarn create t3-app or pnpx create-t3-app
Expected behavior
The logo should look correct regardless of which tool was used
Proposed solution
Adding a check to see which tool was used before rendering the logo seems annoying. Instead we could maybe just add another newline before the logo?
Screenshots
in order: npx, yarn, pnpx

This is a known issue, will be fixed in the next release.

After seeing that screenshot, I agree

Added a newline when using yarn or pnpm, this is how it looks. Can't test with yarn cause my yarn flips out when doing yarn create t3-app@beta.

Fixed in latest beta and will be pushed to latest in the near future.


new type: boolean

to support the new expressions that will replace constraints (#47), we need a way to represent booleans

Current modifications:
spec: https://github.com/CleverCloud/biscuit/commit/0954e322248a9d4ee855bf9d7721abd77706f83f
Rust: https://github.com/CleverCloud/biscuit-rust/commit/78a76576085e8456b674b72d217b8cddb893a237

Current modifications:
spec: https://github.com/CleverCloud/biscuit/commit/0954e322248a9d4ee855bf9d7721abd77706f83f
Rust: https://github.com/CleverCloud/biscuit-rust/commit/78a76576085e8456b674b72d217b8cddb893a237


useParams removed?

Hi, based on your README, useParams is available, but the actual package I installed doesn't. Is that expected?

Yep I am encoutering the same

https://github.com/molefrog/wouter/pull/329#issuecomment-1695136909
try this

Hi everyone!
Sorry we haven't published this version yet. Would you mind using the beta version as @luxl pointed out? I need to get the feedback on the feature first, I would appreciate if you could use it in your projects for about a week. If everything works well, I'll make the new release. Thank you!

No problemo amigo. Thank you for your response, I really enjoy working with Wouter !

Hi everyone!
Sorry we haven't published this version yet. Would you mind using the beta version as @luxl pointed out? I need to get the feedback on the feature first, I would appreciate if you could use it in your projects for about a week. If everything works well, I'll make the new release. Thank you!

No problemo amigo. Thank you for your response, I really enjoy working with Wouter !

got it. Thanks for your response! :)

@molefrog where can we give feedback for useParams. doesn't seem appropriate for me to res this thread

@mnik01 Thank you for reminding. I was initially planning to have more features in this release, but then we started actively working on v3 (which I hope is coming really soon and will include some nice features). I've published v2.12.0 feel free to use this one.


Update README.md

Add note about v5 EE / v1 OSS support.

I don't think we need this disclaimer anymore, since you can deploy v5 enterprise with these scripts.
I think we should add basic instructions + link for installing conjur-oss helm chart in cyberark/conjur README. https://github.com/cyberark/conjur-oss-helm-chart
@izgeri what do you think?

@dustinmm80 Sounds like we might want to make this change after all (though remove the v5 enterprise part) as Dustin Byrne wasn't aware that the demo scripts were enterprise only. Might as well make it explicit everywhere.

@dustinmm80 it would be nice to have instructions for OSS deployments
@jtuttle do you want to update the PR to link to some other existing docs for how to deploy v1 OSS? alternatively, I can open a separate issue for that.

Sure, I'll update it.


Clearer comments for grafana script makefile targets

What do these changes do?
I tried to fix https://github.com/ITISFoundation/osparc-ops-environments/issues/791 but could not reproduce/observe any bugs :--( [on osparc-master.speag.com]
This tries to address the potential source of the issue that export/import naming was unclear....
Related issue/s
https://github.com/ITISFoundation/osparc-ops-environments/issues/791
Related PR/s
Checklist

[ ] I tested and it works

thanks


Question

Really nice work on this, thank you for your efforts.
I am looking for a repeater environment on which to base some additional "special" functionality. Essentially, I need to operate a webserver to respond to various requests, as well as, to have the device initialize without the WiFi functionality.
Where would you suggest I begin planning/learning the least intrusive place on which to implement this other functionality?

Start with user_main.c at the end in user_init(). There is already the initialization of the simple web server, the console and the WiFi init.


Add support for ItemHold (long click/right click) event and Command

Hi.
This pull requests adds support for the aforementioned event and relative Command in your GridView.

Any reason this PR isn't merged? Is the project inactive, or?

I guess this project has been abandoned

Sorry Not abandoned. I just haven't been looking at it for awhile and git does not seem to send me notifications.  Also I'm new to the whole pull request thing. There was a conflict on the file XamarinFormsGridView/XamarinFormsGridView.Android/Resources/Resource.Designer.cs. I just removed the couple of lines that git was complaining about and clicked the merge. Hopefully that was correct.

Don't worry about that, I was considering adopting the project, but if you want I can help you with some of the issues 😊 You can safely ignore conflicts on that file and solve them however you want, it will be regenerated at compile time anyway. I'm yet to find the correct strategy for dealing with that one.

Sent you a collaboration invite which I hope should allow you edit the project without me having to merge each change. I'm still thinking that at some point Xamarin.Forms will release a proper gridview control themselves so I'm not really focused on adding a ton of features. Work away though if you think there are needed missing features. I think the main task is just keeping up with the Xamarin.Forms updates. In fact I don't know if many of the open issues are actual legitimate bugs or whether its down to issues or changes in the underlying framework.


[1.12-rc2] daemon.ID should be replaced with swarm NodeID

Currently, the output of docker info and the Daemon struct have an identifier set with the trustKey. Since this isn't really used, we should probably set this to the actual cryptographic node identity when the daemon changes to swarm mode.
This will ensure that we have a really node identity associated with an engine and ensure that it is available to users.
See docker/swarmkit#1075
cc @diogomonica @dmcgowan @aluzzardi

@stevvooe I checked the docker info, it seems that if daemon is in swarm mode, then the output will consists of a Swarm section with NodeID and IsManager field:
...
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: null host bridge overlay
Swarm: active
 NodeID: 13cjpir2ahv0ie0e12lwyghl7
 IsManager: No
Runtimes: runc
Default Runtime: runc
Security Options: apparmor seccomp
Kernel Version: 4.4.0-24-generic
Operating System: Debian GNU/Linux 8 (jessie) (containerized)
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 7.788 GiB
Name: 6d1de31cb302
ID: YGEZ:MICB:ZC6T:K2BL:X4IH:5QWC:TEKE:2Y44:IFKJ:ADAJ:QJKP:NML6
...

Maybe we could move the NodeID to top level and co-exist with the ID? As a daemon may join or leave the swarm, maybe we want to keep both NodeID and ID?

A node should probably only have an ID when it is in swarm mode.

@diogomonica Agreed, but we should probably deprecate daemon.ID, as that is fairly useless.

The trust key is still used to push schema 1 manifests. I am fine getting rid of the trust key as long as we have private key to replace it with. If a new key is only generated when swarm mode is activated then we can't get rid of the trust key. If we can generate it on first startup like we do with the trust key then I don't have a problem just importing that to use for the v1 manifests and daemon ID.

@dmcgowan We can keep the trust key, but do we have to rely on that as the source of daemon identity?

@stevvooe absolutely not, it was originally used for swarm since it was reliably unique per daemon and always generated at startup. It can be replaced with any random identifier since its cryptographic signature is never checked. It was useful for checking if a daemon signed a schema1 manifest but there was no tooling around that and schema1 manifest is now deprecated.

ping @diogomonica @dmcgowan what's the status on this one?

Should probably be done. The assumption is that no one is relying on the current ID to have the current format, and that we can simply replace it by the swarm ID.

@dmcgowan So, are we comfortable with the possibility that this node ID could change during the lifetime of the engine? For example, if a node is not part of a swarm and joins, it will get a new ID. If node joins and leaves, it will get a new id.
I think we should link these concepts, but is this a good idea overall?

I agree with Diogo that it is safe to assume the format is not being relied on, but it is possible that tooling is expecting this ID to not mutate. Could this cause problems with updating from swarm v1 to swarm mode?
I agree that basing it off the trust key is no longer useful, but why not keep the ID specific to the machine and use the Swarm NodeID when it is needed. Are we going to define some method to verify the cryptographic ID of a node, if not all we need is a UUID. The only reason we used a cryptographic key before is we had plans for using it for signing and a known hosts feature.

I agree with Diogo that it is safe to assume the format is not being relied on, but it is possible that tooling is expecting this ID to not mutate. Could this cause problems with updating from swarm v1 to swarm mode?

Unless it is specified that this is a UUID, reliance on the format of an opaque field shouldn't be considered supported.

Are we going to define some method to verify the cryptographic ID of a node, if not all we need is a UUID.

We already effectively do this with swarm. We should probably extend this functionality as a property of the nodes identity. This is a powerful concept.

We removed the use of libtrust for this ID, and instead use an ID that's stored in /var/lib/docker/engine-id (see https://github.com/moby/moby/pull/44329).
For existing installs, we copied the libtrust ID, and for new installs (or the engine-id not being present), we write a UUID to the file, but the format of the ID is not formalised (users can write their own ID to this file if they want their own form of identification).
w.r.t. using the Swarm Node ID for this purpose; we could write that ID to the file, but I think it's ok to keep them separate; docker info does  provide the node-ID in the output though, so users are able to find the node ID from both manager and worker nodes if they want to use the swarm node ID for identification;
Manager node:
Swarm: active
  NodeID: 2lm9w9kbepgvkzkkeyku40e65
  Is Manager: true
  ClusterID: abajmipo7b4xz5ip2nrla6b11

Worker node:
Swarm: active
  NodeID: n41b2cijmhifxxvz56vwrs12q
  Is Manager: false

I'll close this ticket.


bump java to 11

fixes #5

I just manually ran the CD workflow on jenkins-test-harness-htmlunit: https://github.com/jenkinsci/jenkins-test-harness-htmlunit/runs/7050646405
Based on https://github.com/jenkinsci/jenkins-test-harness-htmlunit/blob/47b052d78bca46bf07aa57fd208a408080889e65/.github/workflows/cd.yaml#L12= I thought I would get https://github.com/jenkins-infra/github-reusable-workflows/blob/v1.1.0/.github/workflows/maven-cd.yml i.e. Temurin 11.
But looking at the logs I got Temurin 8 which I did not expect:
Run actions/setup-java@v3
Resolved Java 8.0.332+9 from tool-cache
Setting Java 8.0.332+9 as the default
Java configuration:
  Distribution: temurin
  Version: 8.0.332+9
  Path: /opt/hostedtoolcache/Java_Temurin-Hotspot_jdk/8.0.332-9/x64
Creating settings.xml with server-id: github

The release happened to work because the test harness is a special core component that still supports Java 8:
+ mvn -B -V -s /home/runner/work/_actions/jenkins-infra/jenkins-maven-cd-action/v1.3.1/settings.xml -ntp -Dstyle.color=always -Dset.changelist -DaltDeploymentRepository=maven.jenkins-ci.org::default::https://repo.jenkins-ci.org/releases/ -Pquick-build '-P!consume-incrementals' clean deploy
Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63)
Maven home: /usr/share/apache-maven-3.8.6
Java version: 1.8.0_332, vendor: Temurin, runtime: /usr/lib/jvm/temurin-8-jdk-amd64/jre
Default locale: en, platform encoding: UTF-8
OS name: "linux", version: "5.13.0-1031-azure", arch: "amd64", family: "unix"

But I think if I had been trying to release e.g. Remoting or Stapler it would have failed.

Is it possible that the presence of https://github.com/jenkins-infra/github-reusable-workflows/releases/tag/v1 means that https://github.com/jenkinsci/jenkins-test-harness-htmlunit/blob/47b052d78bca46bf07aa57fd208a408080889e65/.github/workflows/cd.yaml#L12= is fetching the specific tag v1 (which is still using Temurin 8) rather than the latest tag v1.1.0 (which is using Temurin 11)?

Yes, see https://github.com/jenkins-infra/github-reusable-workflows/pull/6#discussion_r897368398. @jetersen I think we can revert the reversion and let v1 float back up to v1.1.0? If someone feels strongly otherwise, they should file a PR changing main and we can discuss, but I do not think we should deliberately hold back a v1 tag except on a temporary emergency basis.
I can also release #11 which is just sitting there.

Done. I think https://github.com/jenkins-infra/github-reusable-workflows/tags + https://github.com/jenkins-infra/github-reusable-workflows/releases should make more sense now.

Thank you!

Thanks!


[Feature Request] rcptt ecl插件

Checklist

[X] I searched exising issues and no one else requests similar feature.
[X] I think that 25%+ users are positive towards this feature.

Describe the feature
https://blog.csdn.net/mzjmzjmzjmzj/article/details/80165156
Additional context
No response

https://www.eclipse.org/rcptt/documentation/userguide/ecl/new-command-guide/


Refactor/atom effect 2

move atomEffect closer to atomEffect2. All tests are passing.
The main remaining discrepancy is the do-while loop. I'll continue to think on how to do while supporting batching.
Related: https://github.com/jotaijs/jotai-effect/pull/2

PASS tests/atomEffect.test.ts

Nice. Let me merge it.


change file from #3794 can't start kong

Summary
change kong/init.lua , kong/runloop/handler.lua , kong/runloop/plugins_iterator.lua
Steps To Reproduce
1.change file from #3794
2.kong start --vv
Additional Details & Logs

Kong version  0.14.1
Kong debug-level startup logs  kong start --vv

2018/10/22 18:37:07 [verbose] could not start Kong, stopping services
2018/10/22 18:37:07 [debug] sending signal to pid at: /usr/local/kong/pids/nginx.pid
2018/10/22 18:37:07 [debug] kill -0 cat /usr/local/kong/pids/nginx.pid >/dev/null 2>&1
2018/10/22 18:37:07 [verbose] stopped services
Error:
/usr/local/share/lua/5.1/kong/cmd/start.lua:71: /usr/local/share/lua/5.1/kong/cmd/start.lua:60: nginx: [warn] [lua] globalpatches.lua:218: randomseed(): math.randomseed() must be called in init_worker context
stack traceback:
/usr/local/share/lua/5.1/kong/init.lua:227: in function 'init'
init_by_lua:3: in main chunk
nginx: [error] init_by_lua error: /usr/local/share/lua/5.1/kong/init.lua:249: attempt to call method 'schema_state' (a nil value)
stack traceback:
/usr/local/share/lua/5.1/kong/init.lua:249: in function 'init'
init_by_lua:3: in main chunk
stack traceback:
[C]: in function 'error'
/usr/local/share/lua/5.1/kong/cmd/start.lua:71: in function 'cmd_exec'
/usr/local/share/lua/5.1/kong/cmd/init.lua:87: in function </usr/local/share/lua/5.1/kong/cmd/init.lua:87>
[C]: in function 'xpcall'
/usr/local/share/lua/5.1/kong/cmd/init.lua:87: in function </usr/local/share/lua/5.1/kong/cmd/init.lua:44>
/usr/local/bin/kong:7: in function 'file_gen'
init_worker_by_lua:47: in function <init_worker_by_lua:45>
[C]: in function 'xpcall'
init_worker_by_lua:54: in function <init_worker_by_lua:52>

Operating system
centos 6.8

You probably need https://github.com/Kong/kong/pull/3804/commits/c680b349a4d80737576e363a4acbf623c8db66e9 as well.
Anyway, those changes will be available in our next release.


problem to get the tool running

Hi,
I have a big interest in chess software development but I'm a total newbie when it comes to programming.
I tried you command line tool with the example pgn file ' ericrosen-white.pgn' that comes with the download.
If I type in command prompt:

opening-repertoire -p C:\Users\Jonathan\Downloads\Chess\opening-repertoire-master\data\ericrosen-white.pgn -c white -s e4,c5

I get this error message:

thread 'main' panicked at 'assertion failed: (left == right)
left: 65536,
right: 16384', C:\Users\Jonathan.cargo\registry\src\github.com-1ecc6299db9ec823\pgn-reader-0.15.0\src\reader.rs:553:13
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace

I probably do sommeting wrong?

I made a video capture of my attempt to run the app. I use a windows 10 64 bit system with the latest updates.
https://user-images.githubusercontent.com/40061628/103103764-b5a19f80-4623-11eb-8ddc-2daf08d364fe.mp4

Hi! The problem you are having seems to be rooted in a library we depend on: niklasf/rust-pgn-reader#17
I pinned the version to a commit that hopefully fixes this issue. Why don't you reinstall opening-repertoire, give it another go and let me know how it goes!

It looks like it works now. I don't get any error messages.
Where can a find the resulting pgn with the repertoire?
Do I have to copy the text in the command line window?

I have tree request for future updates.

For the option (-s, --starting-moves     Filter games by some comma-separated starting moves, e.g. 'e4,c5') I would like to have some additional options. I would like to use different strings at the same time by using ‘;’. Then for example 'e4,c5;e4,e5’ would create a repertoire for the Sicilian as well for the Double King’s pawn opening. Or ‘e4;d4;c4;Nf3’ would create a repertoire for these 4 white first moves.
I would like to have some options to build wider repertoires. For the moment the result has only one candidate move for the side of the repertoire. I would like to have 5 options, 1: to build a narrow repertoire like it is now, 2: to build a wider repertoire where the top main lines are included, 3: to build a wide repertoire where all main lines are included. 4: to build a repertoire where also sidelines are included. And 5: to build a repertoire where all lines are included except very rare lines that are almost never played.
And at the same time, I want to set these options independently for the other color. For example, if make a repertoire for white, I want to use option 2 for the white candidate moves, and option 4 for the black candidate moves.
I want an option to filter games according to my repertoire. Say I made a white repertoire based on the games of some model Grandmaster which playing style I like. But I can only find 2000 games in databases where he plays white. So obviously there will be many holes in the repertoire.
So, I make a second white repertoire from a huge pgn database with hundreds of thousands of games, where one of the players have a rating of +2400 Elo. The games of this model Grandmaster are also included in this huge pgn database. Now I have this second white repertoire. I want to filter this second repertoire so I get only the variations that can arise after playing the opening lines from the first repertoire. So also, the replies for white will be included when black deviates from the lines in the first repertoire. I basically want to do what’s described here: http://wbec-ridderkerk.nl/html/details1/PolyGlot.html
Under the title book merging.
I can import the best moves from the merged bin books to Opening Lines in Lucas Chess, and then export to pgn.
But I want to be able to do this directly with pgn games. There is some weird explosion of number of games if I use Lucas Chess for this.

I'm glad that you find it helpful!
I'm not a Windows user but AFAIK you should be able to redirect the output of the program into a file by adding > filename.pgn at the end of the command. It should create (or overwrite) a file inside the folder where you run the command. Something like
opening-repertoire -p input.pgn -c white > output.pgn

I'm glad you found it helpful!
I'm not a Windows user but AFAIK you should be able to redirect the output of the program into a file by adding > filename.pgn at the end of the command. It should create (or overwrite) a file inside the folder where you run the command. Something like
opening-repertoire -p input.pgn -c white > output.pgn

I'm glad that you find it useful!
I'm not a Windows user but AFAIK you should be able to redirect the output of the program into a file by adding > filename.pgn at the end of the command. It should create (or overwrite) a file inside the folder where you run the command. Something like
opening-repertoire -p input.pgn -c white > output.pgn

I'm glad you found it useful!
I'm not a Windows user but AFAIK you should be able to redirect the output of the program into a file by adding > filename.pgn at the end of the command. It should create (or overwrite) a file inside the folder where you run the command. Something like
opening-repertoire -p input.pgn -c white > output.pgn

Yes this works to save the output as pgn on windows to. Thanks for the tip.
This issue can be closed I think? I'm not sure how this works? Do I have to close it or do you close it?

Feel free to close an issue if you feel like it has been resolved!


Web based IDE for the DB

So that all projects that import this can have a DB Web GUI to help with working on development.
HTMX would be the way to build it.

This is interesting! Thanks @gedw99

I found a great one to use in the end based on htmx..


Text restructure and realignment

Closes #1013
Moved instruction text into blue header section. Adjusted spacing within the header as well and added breakpoint styling for small screen. May have to adjust the alignment of the instructions below the blue header.
Testing
Relevant links
http://localhost:3000/join-index/how-to-add

@mealthebear does the text margin/padding match the figma for this breakpoint?  Seems like there should still be some left/right padding or margin here

For summary css Dennis you have given color:white, I also used like this before but I was asked to use the colors using this link http://localhost:3000/guides/colors. you can use theme.palette.text.secondary or Typography color='textSecondary' whichever works for you

Thanks bhaggya, I was wondering if there was a palette for text colors.


feat: add typos-lsp

I believe I got the architectures specified correctly. Let me know if things like linux_x64_gnu should simply be linux_x64.


Include output from interactive cells in Foyle requests

This fixes a bug in the serializaiton of the notebook before sending it to Foyle that caused the output of interactive cells not to be included in the requests.
The problem is that we need to call addExecInfo before converting the VSCode NotebookData representation to the proto. That handles copying the output of the interactive terminals into the NotebookData structure.
This necessitated some code refactoring. In order to call addExecInfo we need an instance of the kernel.
We create a new Converter class to keep track of the kernel and also provide reuse in the logic for converting notebook data to protos for Foyle.
Since addExecInfo is async we need to change buildReq to return a promise and refactor some of the logic to be non blocking.

Fix jlewi/foyle#286

@sourishkrout this is ready when you are.

@sourishkrout I updated the code to use async; I left a question for you in the comments can you please take a look?
The other thing is it doesn't look like interactive cells are properly triggered if you have a long running command. I was hoping #1744 fixed this but it looks like #1744 only fixed it for non-interactive. I'll update jlewi/foyle#309


PC-1044 Streaming runs

Pull request outline
Checklist:

[ ] Docs updated
[ ] Tests written
[ ] Check for breaking changes in Resource
[ ] Version bumped

Added:

A list of new things

Changed:

A list of things changed

Removed:

A list of things removed

Related issues:
none

You can add a reference to an issue using hash followed by the issue number
If a checklist item is to be ignored it must be struck through

@paulcjh I wonder if we should make the streaming endpoint in the container a separate endpoint, as we're doing with the backend API, since previously we've tried to keep /v4/runs consistent between the container and pcore?

the only other thought I had (and maybe we can always do this later) was whether it makes sense to return the full run result schema every time, or just the raw outputs? Since I have a feeling all of the serialising JSON in and out of Pydantic objects may add a bit of overhead. We could always add a separate endpoint for that later though. Maybe also an endpoint where the results are streamed directly from the resource too without going via catalyst and pcore


Add a new impersonate user and update email signature sample

As previously told, updating from 0.8 to 0.9 has been a very painful process, with very few real world samples.
This samples show authenticate with a service account, how to impersonate someone , and how to update his email signature

Coverage remained the same at 94.811% when pulling 3c65f4d7dbc59bc133fca1ac9138c4621a3341ea on thomasdarde:master into 90d90d00b28e4e3bac2369829ca9cf121c6fc4b8 on google:master.

Previous comments aside, lgtm.

Coverage increased (+0.008%) to 94.819% when pulling 27028838d8162a38af219e586a3ec1adc7c3ed3b on thomasdarde:master into 90d90d00b28e4e3bac2369829ca9cf121c6fc4b8 on google:master.


Plans to publish on PyPi

Do you have any plans to publish Mandala on the python package index? I've got a couple of environments that can't install from git, but can pull from PyPi so it would definitely be useful for me!

Thanks for the suggestion! I'll look into it

Awesome, thank you!

Hi, sorry for the delay - this is ongoing, I'm trying get ownership of the mandala project on PyPi to avoid having to change the name.

No worries at all! Thanks for the update! You could always go with mandala-engine or something if that proves impossible.

The project is now on PyPi under the name pymandala: https://pypi.org/project/pymandala/0.2.0a0/ !
You should be able to install the current PyPi version via pip install pymandala.
The project should still be imported as import mandala, etc. Let me know if there are any issues!

Thank you so much! This works so far!


Prompt hangs when using Kubecontext and minikube

When using the functionality on the next branch kubecontext.  If someone has minikube installed locally and is currently pointing to minikube for kubernetes context.  Zsh will hang for several seconds for each prompt and ^C does not terminate, on the kubectl version command.  As the kubectl version command is designed to just test to see if you have kubernetes installed a kubectl version --client will suffice.

Fixed by merge of #554


[Skype For Business] Greet Message In Skype For Business

Bot Info

SDK Platform: .NET
Bot Builder Version: <IP_ADDRESS>
Active Channels: Skype For Business
Deployment Environment: Azure Bot Service, Azure App Service

Issue Description
Hi , I want to display a welcome message in SfB but as SfB interprets "ConversationUpdate" event differently the greet message is only displayed after user sends first message.I want the bot to initiate the conversation as is possible in other channels including Skype but in SfB i am unable to reproduce the same behavior.

In Skype for business, check for the ContactRelationUpdate activity type.  This will only fire when someone adds the bot for the first time.  I have no idea why S4B set up things this way, but the conversation update ActivityType is not sent.

I have tried "ContactRelationUpdate" as well. For testing purpose i implemented tracing and logging in database and wrote the code to display welcome message on "ContactRelationUpdate" activity type as well, what i figured out is this activity is not fired in S4B as no trace is logged in database on adding bot to my contacts. This is not working for me in S4B , while it works fine in Skype as i have already implemented same in Skype channel.
Also, the "ContactUpdate" is logged in database but welcome message is shown only after first message has been sent. This also works in Skype but not in S4B.
Code Example:
else if (activity.Type == ActivityTypes.ContactRelationUpdate)
{
Utility.savetodatabase("Start Of ActivityType.ContactRelationUpdate ", null, activity.From.Id, "Trace");
IContactRelationUpdateActivity contactupdate = activity;
var reply = activity.CreateReply();
using (var scope = DialogModule.BeginLifetimeScope(Conversation.Container, activity))
{
var client = scope.Resolve();
if (contactupdate.Action.Equals("add"))
{
reply.Text = "Welcome";
await client.Conversations.ReplyToActivityAsync(reply);
}
}
Utility.savetodatabase("End Of ContactRelationUpdate ", null, activity.From.Id, "Trace");
}

Unfortunately we Bot Framework support engineers do not have a S4B tenant to help test and diagnose S4B issues with.  the Skype for Business team is supposed to monitor this forum and provide support, but I have not seen them around in months.  You would probably have better luck asking your question on stack overflow or posting on their usevoice.


Support loglikelihood mechanism

Loglikelihood approach is needed to check accuracy of a model on popular datasets and tasks like MMLU and BigBench. Particularly HuggingFace leaderboard bases on such tasks only.
Notes:

Log softmax calculation is transferred onto TVM side. It should be up-streamed before merge. Just now the branch with method implementation is started from tvm/unity, but current 3d-party tvm is gotten from mlc-ai/relax. They have some conflicts and need additional efforts for upstreaming. Need to discuss.
Loglikelihood requires sequence of logits after prefill-like inference. But in mlc-llm on the model topology side the last logits set is splitted from all. In test the split op was skipped, but it requires more work for correct work of chat. Need to discuss.

Draft:
Test is in progress. Results from mlc-llm likelihood is upstreamed with lm-evaluation-harness (master branch) on samples from Hellaswag task on Llama2-7b-q0f16 and Llama2-7b from HF.

Hello @tqchen! I need your help and expertise to discuss how to better implement things described in notes. My quick understanding: 1. Transfer my work branch from tvm/unity to mlc-ai/relax; 2. allow the topology return all logits and cut the last one on chat side.

mlc/relax is doing weekly sync with tvm/unity, so no actions needed. we are looking into a possible regression, after that is cleared, it should be updated

Close due to development was transferred to octoml/mlc-llm


How to download PDF File for this questions

How to download PDF File for this questions

Open any Action in https://github.com/sudheerj/reactjs-interview-questions/actions
Scroll to the bottom
Click "Output" under Artifacts
Voila!

Open any Action in https://github.com/sudheerj/reactjs-interview-questions/actions
Scroll to the bottom
Click "Output" under Artifacts
Voila!

need account login, otherwise cannot download!

@random-play I think just a github account would do

@random-play I think just a github account would do

yeah, just a github account

Why don't you use ctrl + p and save it in pdf format :-)


Got

https://github.com/sindresorhus/got

Extracting into a separate library would be grand, see: https://github.com/sindresorhus/gh-got

Mission :/


Enable toggle for X% of users

Closed this card as the toggle can now be handled via UI, the dev work/deploy for this card is no longer needed


got invalid value

Describe the bug
the detail as below picture
Altair GraphQL Client version is 3.2.2

Hello @shaokun11 Please provide more details. Did you check that what you uploaded is valid?

Hello @shaokun11 Please provide more details. Did you check that what you uploaded is valid?

Thanks your focus!!!!
this is my code error, and now it working.


Refactoring body system to use containers and general body cleanup

About the PR

Why / Balance

Body system was running into issues with networking and was reinventing the wheel with its bodypart relationships.
Technical details

This converts body system to use container slots instead of the bodyslot system it was using before. This should help prevent networking related bugs and generally is a lot cleaner to use. Additionally, bodyparts and organs now store their children in a container tree which is required to allow parts to stay together when their parents are detached from a body. (This is required for surgery)
Media

[ ] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

The body system API has been changed to remove depreciated code (component.Owner), additionally some functions had their arguments reordered to make more sense.
Changelog

Still need to fix tests but this should be good for people to start reviewing

Tests are fixed

also tests are broken even though they passed the first time. (it also causes maprenderer to explode)


add agorapp to showcase.json and add agorapp svg logo

Thank you for your contribution to the IC Developer Portal.
Before submitting your Pull Request, please make sure that:

[x] You have updated the .github/CODEOWNERS file according to your changes.
[x] You have registered new documents to /sidebars.js if any.

Notes:
The video field in showcase.json points to our youtube video because we weren't able to minify the grant submission's presentation enough.

Dear @RiccardoBiosas,
In order to potentially merge your code in this open-source repository and therefore proceed with your contribution, we need to have your approval on DFINITY's CLA.
If you decide to agree with it, please visit this issue and read the instructions there. Once you have signed it, re-trigger the workflow on this PR to see if your code can be merged.
— The DFINITY Foundation


istio-proxy not respecting app container restart and sending traffic during app terminating state

Bug Description
We have a pod with an app container and istio-proxy container running. Due to the failure of liveliness and readiness probes on the app container, a SIGTERM signal was sent to the app container, and the app container went to a terminating state. We have a prestop hook written on the app container to check for active connections and if active connections are 0 it will stop the server and stop the container.
During this terminating phase of the app container, technically speaking istio-proxy container should stop sending new traffic to the terminating container and redirect new traffic to other pods. But in this scenario even when the app container is in a terminating state istio-proxy is sending traffic to this terminating container. This is leading to a state where terminationGracePeriodSeconds is reached and executing requests are sent 503.
Version
$ istioctl version
client version: 1.17.1
control plane version: 1.15.3
data plane version: 1.15.3 (42 proxies)

$ kubectl version --short
Client Version: v1.23.14
Kustomize Version: v4.5.7
Server Version: v1.23.14-eks-ffeb93d

$ helm version --short
v3.9.3+g414ff28

Additional Information
Attaching the pod.yaml of the application
kind: Pod
metadata:
  labels:
    app: netsuite-webservices-adaptor
  name: netsuite-webservices-adaptor-free-67cfc4985d-w524p
  namespace: io
spec:
  containers:
    - image: netsuite-webservices-adaptor:ml-<IP_ADDRESS>.0
      imagePullPolicy: IfNotPresent
      lifecycle:
        preStop:
          exec:
            command:
              - sh
              - '-c'
              - >-
                expected="0"; count=""; while ! [ "$count" == "$expected" ]; do
                count=$(curl -XGET 'http://localhost:5000/openConnections');
                sleep 1; done; curl -XGET 'http://localhost:5000/stopServer';
                echo "Done";
      livenessProbe:
        failureThreshold: 1
        httpGet:
          path: /app-health/netsuite-webservices-adaptor/livez
          port: 15020
          scheme: HTTP
        initialDelaySeconds: 20
        periodSeconds: 1
        successThreshold: 1
        timeoutSeconds: 1
      name: netsuite-webservices-adaptor
      ports:
        - containerPort: 5000
          name: http
          protocol: TCP
      readinessProbe:
        failureThreshold: 1
        httpGet:
          path: /app-health/netsuite-webservices-adaptor/readyz
          port: 15020
          scheme: HTTP
        initialDelaySeconds: 20
        periodSeconds: 1
        successThreshold: 1
        timeoutSeconds: 1
      resources:
        limits:
          cpu: '1'
          memory: 1Gi
        requests:
          cpu: 200m
          memory: 512Mi
    - args:
        - proxy
        - sidecar
        - '--domain'
        - $(POD_NAMESPACE).svc.cluster.local
        - '--proxyLogLevel=warning'
        - '--proxyComponentLogLevel=misc:error'
        - '--log_output_level=default:info'
        - '--concurrency'
        - '2'
      env:
        - name: EXIT_ON_ZERO_ACTIVE_CONNECTIONS
          value: 'true'
        - name: JWT_POLICY
          value: third-party-jwt
        - name: PILOT_CERT_PROVIDER
          value: istiod
        - name: CA_ADDR
          value: 'istiod.istio-system.svc:15012'
        - name: POD_NAME
          valueFrom:
            fieldRef:
              apiVersion: v1
              fieldPath: metadata.name
        - name: POD_NAMESPACE
          valueFrom:
            fieldRef:
              apiVersion: v1
              fieldPath: metadata.namespace
        - name: INSTANCE_IP
          valueFrom:
            fieldRef:
              apiVersion: v1
              fieldPath: status.podIP
        - name: SERVICE_ACCOUNT
          valueFrom:
            fieldRef:
              apiVersion: v1
              fieldPath: spec.serviceAccountName
        - name: HOST_IP
          valueFrom:
            fieldRef:
              apiVersion: v1
              fieldPath: status.hostIP
        - name: PROXY_CONFIG
          value: |
            {}
        - name: ISTIO_META_POD_PORTS
          value: |-
            [
                {"name":"http","containerPort":5000,"protocol":"TCP"}
            ]
        - name: ISTIO_META_APP_CONTAINERS
          value: netsuite-webservices-adaptor
        - name: ISTIO_META_CLUSTER_ID
          value: Kubernetes
        - name: ISTIO_META_INTERCEPTION_MODE
          value: REDIRECT
        - name: ISTIO_META_WORKLOAD_NAME
          value: netsuite-webservices-adaptor-free
        - name: ISTIO_META_OWNER
          value: >-
            kubernetes://apis/apps/v1/namespaces/io/deployments/netsuite-webservices-adaptor-free
        - name: ISTIO_META_MESH_ID
          value: cluster.local
        - name: TRUST_DOMAIN
          value: cluster.local
        - name: ISTIO_KUBE_APP_PROBERS
          value: >-
            {"/app-health/netsuite-webservices-adaptor/livez":{"httpGet":{"path":"/livez","port":5000,"scheme":"HTTP"},"timeoutSeconds":1},"/app-health/netsuite-webservices-adaptor/readyz":{"httpGet":{"path":"/readyz","port":5000,"scheme":"HTTP"},"timeoutSeconds":1}}
      image: 'docker.io/istio/proxyv2:1.15.3'
      imagePullPolicy: IfNotPresent
      name: istio-proxy
      ports:
        - containerPort: 15090
          name: http-envoy-prom
          protocol: TCP
      readinessProbe:
        failureThreshold: 30
        httpGet:
          path: /healthz/ready
          port: 15021
          scheme: HTTP
        initialDelaySeconds: 1
        periodSeconds: 2
        successThreshold: 1
        timeoutSeconds: 3
      resources:
        limits:
          cpu: '2'
          memory: 1Gi
        requests:
          cpu: 100m
          memory: 128Mi
      securityContext:
        allowPrivilegeEscalation: false
        capabilities:
          drop:
            - ALL
        privileged: false
        readOnlyRootFilesystem: true
        runAsGroup: 1337
        runAsNonRoot: true
        runAsUser: 1337
      terminationMessagePath: /dev/termination-log
      terminationMessagePolicy: File
      volumeMounts:
        - mountPath: /var/run/secrets/workload-spiffe-uds
          name: workload-socket
        - mountPath: /var/run/secrets/credential-uds
          name: credential-socket
        - mountPath: /var/run/secrets/workload-spiffe-credentials
          name: workload-certs
        - mountPath: /var/run/secrets/istio
          name: istiod-ca-cert
        - mountPath: /var/lib/istio/data
          name: istio-data
        - mountPath: /etc/istio/proxy
          name: istio-envoy
        - mountPath: /var/run/secrets/tokens
          name: istio-token
        - mountPath: /etc/istio/pod
          name: istio-podinfo
        - mountPath: /var/run/secrets/eks.amazonaws.com/serviceaccount
          name: aws-iam-token
          readOnly: true
        - mountPath: /var/run/secrets/kubernetes.io/serviceaccount
          name: kube-api-access-cbthq
          readOnly: true
  dnsPolicy: ClusterFirst
  enableServiceLinks: true
  initContainers:
    - args:
        - istio-iptables
        - '-p'
        - '15001'
        - '-z'
        - '15006'
        - '-u'
        - '1337'
        - '-m'
        - REDIRECT
        - '-i'
        - '*'
        - '-x'
        - ''
        - '-b'
        - '*'
        - '-d'
        - '15090,15021,15020'
        - '--log_output_level=default:info'
      image: 'docker.io/istio/proxyv2:1.15.3'
      imagePullPolicy: IfNotPresent
      name: istio-init
      resources:
        limits:
          cpu: '2'
          memory: 1Gi
        requests:
          cpu: 100m
          memory: 128Mi
      securityContext:
        allowPrivilegeEscalation: false
        capabilities:
          add:
            - NET_ADMIN
            - NET_RAW
          drop:
            - ALL
        privileged: false
        readOnlyRootFilesystem: false
        runAsGroup: 0
        runAsNonRoot: false
        runAsUser: 0
      terminationMessagePath: /dev/termination-log
      terminationMessagePolicy: File
      volumeMounts:
        - mountPath: /var/run/secrets/eks.amazonaws.com/serviceaccount
          name: aws-iam-token
          readOnly: true
        - mountPath: /var/run/secrets/kubernetes.io/serviceaccount
          name: kube-api-access-cbthq
          readOnly: true
  preemptionPolicy: PreemptLowerPriority
  priority: 0
  restartPolicy: Always
  schedulerName: default-scheduler
  securityContext: {}
  serviceAccount: netsuite-webservices-adaptor
  serviceAccountName: netsuite-webservices-adaptor
  terminationGracePeriodSeconds: 86400
  tolerations:
    - effect: NoExecute
      key: node.kubernetes.io/not-ready
      operator: Exists
      tolerationSeconds: 300
    - effect: NoExecute
      key: node.kubernetes.io/unreachable
      operator: Exists
      tolerationSeconds: 300
    - emptyDir: {}
      name: workload-socket
    - emptyDir: {}
      name: credential-socket
    - emptyDir: {}
      name: workload-certs
    - emptyDir:
        medium: Memory
      name: istio-envoy
    - emptyDir: {}
      name: istio-data
    - downwardAPI:
        defaultMode: 420
        items:
          - fieldRef:
              apiVersion: v1
              fieldPath: metadata.labels
            path: labels
          - fieldRef:
              apiVersion: v1
              fieldPath: metadata.annotations
            path: annotations
      name: istio-podinfo
    - name: istio-token
      projected:
        defaultMode: 420
        sources:
          - serviceAccountToken:
              audience: istio-ca
              expirationSeconds: 43200
              path: istio-token
    - configMap:
        defaultMode: 420
        name: istio-ca-root-cert
      name: istiod-ca-cert
    - name: kube-api-access-cbthq
      projected:
        defaultMode: 420
        sources:
          - serviceAccountToken:
              expirationSeconds: 3607
              path: token
          - configMap:
              items:
                - key: ca.crt
                  path: ca.crt
              name: kube-root-ca.crt
          - downwardAPI:
              items:
                - fieldRef:
                    apiVersion: v1
                    fieldPath: metadata.namespace
                  path: namespace```

Kindly help us debug the issue and let us know if are missing any configurations.

The server proxy does NOT stop accepting new connections immediately, that is intentional. Servers should accept incoming connections during termination as there is propogation delays during a pod shutdown.
What should happen, however, is that clients stop sending requests. Its not clear from your issue what the clients are. do they have Istio proxies as well? Is it HTTP or TCP traffic?
For HTTP, the outbound istio proxy should backoff and connect to a new one. For TCP traffic, though, we have no way to do this

Thank you John for your comments
It's http traffic and client do not stop sending requests and thy don't have Istio proxy enabled, We are seeing 503 errors in this case and how to avoid requests drops and 503. It's the app container getting to unhealthy state , Istio proxy remains healthy.
Hope this help , Appreciate your help here.

Either to have sidecar injected with client or do reconnect when get 503. This behavior should be same as without istio at all

If its HTTP, the server proxy will send connection: close or GOAWAY. If the client doesn't respect those and disconnect... nothing we can do.

Sorry @howardjohn  but I didn't get, during the terminating phase of the main container, does the sidecar accepting new requests yet that will be then dropped since the other container is dying?

istio-proxy@example-c4944957-hfb4h:/$ curl -i -X GET http://localhost:3260/metrics
curl: (7) Failed to connect to localhost port 3260 after 0 ms: Connection refused
to notice that the application is still running, making a graceful shutdown and the /metrics endpoint should answer to such requests.
I would expect something different since I have:

What you are saying and what is happening is not consistent. I am confident that at the time you sent that curl your app was not accepting requests. Istio is completely irrelevant to this - its entirely in your application.

    proxy.istio.io/config: '{ "terminationDrainDuration": "90s" }'

This only tells the proxy to live for 90s. It does not impact your app.

Basicly while the main app is dying I would like to mantain /metrics endpoint enabled.

Then you need to change your application to not shutdown the metrics endpoint.

Just to re-iterate, the problems and solutions here are purely in your application and k8s configuration, not Istio config/code.


LoadData has wrong return type

The LoadData method has (IDataView trainSet, IDataView testSet) retrurn type in article text.
However, the returning variable has TrainCatalogBase.TrainTestData type.
So, the code is not compilable.
If we look at the sample code at github we'll see that it has correct return type: https://github.com/dotnet/samples/blob/master/machine-learning/tutorials/SentimentAnalysis/Program.cs#L56

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

ID: c8e22825-c4ee-5a36-f911-8ad456970ecc
Version Independent ID: ad0bf640-7dfc-1184-077c-358bb14277a7
Content: Use ML.NET in a sentiment analysis binary classification scenario
Content Source: docs/machine-learning/tutorials/sentiment-analysis.md
Product: dotnet-ml
GitHub Login: @JRAlexander
Microsoft Alias: johalex

Thanks, @Skybladev2, for the feedback! This has been fixed.


Adding an option for providing user theming

Just nice to be able to provide my own logo, etc.

This would need tests and a CHANGELOG entry to be merged (we're trying to be more disciplined here ;)).
That said, it seems hacky. I wonder whether we'd be better served to refactoring the ERB into partials and to let you assemble a custom index.html.erb yourself out of them. You don't have to use this ERB already, you might as well roll your own that looks the way you want, but we could make it easier to do.

Absolutely.  It was late and I needed to keep moving.  Consider it a
feature request rather than a contribution. ;-)
On Fri, Feb 6, 2015 at 5:44 PM, Daniel Doubrovkine (dB.) @dblockdotorg <
<EMAIL_ADDRESS>wrote:

This would need tests and a CHANGELOG entry to be merged (we're trying to
be more disciplined here ;)).
That said, it seems hacky. I wonder whether we'd be better served to
refactoring the ERB into partials and to let you assemble a custom
index.html.erb yourself out of them. You don't have to use this ERB
already, you might as well roll your own that looks the way you want, but
we could make it easier to do.
—
Reply to this email directly or view it on GitHub
https://github.com/TinkerDev/grape-swagger-rails/pull/3#issuecomment-73327029
.

--
Alex Agranov
Director/Sr.Engineer
Morphogenic Productions
www.morphogenic.net
www.linkedin.com/in/alexagranov
(917) 509-1856

In case you still want to merge, cleaning up my late night sloppiness.

Thanks @alexagranov! I think I'd rather not merge this in favor of a more modular approach as described above. Curious to hear what others think, will let this sit here for a bit.

+1000!

Cleaning this up, just realized I've been committing willy nilly...

@alexagranov Please do consider contributing a better implementation, this would be a very useful feature!


Invalid Request access the sso path (OIDCRedirectURI)

Environment

mod_auth_openidc - version <IP_ADDRESS>
Apache version - Apache/2.4.6
platform/distro - CentOS

Expected behaviour
Error in the first access or logged user
If the user access the sso url, the same that I configure in the OIDCRedirectURI, the cookie is not setted with mod_auth_openidc_state_ and the user is not redirected to login page.
https://{domain}/sso
I see that setting OIDCDefaultURL it works on IE.
I need to aceess the OIDCRedirectURI end to be redirect to OIDCDefaultURL
Submitting... Script need to executed
Actual behaviour
On Chrome or Firefox if the final user access the OIDCRedirectURI direct, he will see the invalid request error.
In IE it  is working but in Chrome or Firefox I have a error:
Error:
Invalid Request
Description:
You've hit an OpenID Connect Redirect URI with no parameters, this is an invalid request; you should not open this URL in your browser directly, or have the server administrator use a different OIDCRedirectURI setting.
ap_headers_error_filter()
Minimized example
OIDCRedirectURI https://{domain}/sso
OIDCProviderMetadataURL https://{some domain/openid-configuration
OIDCClientID xxx
OIDCClientSecret xxx
OIDCResponseType 'code'
OIDCPreservePost On
OIDCProviderAuthorizationEndpoint xxx
OIDCProviderTokenEndpoint xxx
OIDCProviderTokenEndpointAuth client_secret_post
OIDCProviderEndSessionEndpoint xxx
OIDCProviderUserInfoEndpoint xxx
OIDCCryptoPassphrase random1234
OIDCResponseMode form_post
OIDCPassIDTokenAs payload
OIDCPathAuthRequestParams xxx
OIDCCacheShmEntrySizeMax 65536
#OIDCStateTimeout 28800
OIDCStateMaxNumberOfCookies 7 true
OIDCDefaultURL https://{domain}

<Location />
    AuthType openid-connect
    Require valid-user
    SetHandler dispatcher-handler

    RequestHeader set "X-KO-SALT" "S4LT_K3Y_G03S_H3R3"
</Location>

Configuration and Apache server log files
Config and logs for the minimized example, possibly provided as attachments.
Logs
log with error in chorme
log-qa.txt
log working in IE
log-from-IE-working.txt
Request from Chrome
Request URL: https://{domain}/sso
Request Method: POST
Status Code: 200 OK
Remote Address: <IP_ADDRESS>:443
Referrer Policy: no-referrer-when-downgrade
Response Header
Connection: Keep-Alive
Content-Length: 541
Content-Type: text/html
Date: Wed, 27 Mar 2019 21:33:44 GMT
Keep-Alive: timeout=15, max=91
Server:
request Header
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,/;q=0.8,application/signed-exchange;v=b3
Accept-Encoding: gzip, deflate, br
Accept-Language: pt-BR,pt;q=0.9,en-US;q=0.8,en;q=0.7
Cache-Control: no-cache
Connection: keep-alive
Content-Length: 22
Content-Type: application/x-www-form-urlencoded
Cookie: mod_auth_openidc_session={..}
Host: {domain}
Origin: https://{domain}
Pragma: no-cache
Referer: https://{domain}/sso
Upgrade-Insecure-Requests: 1
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.75 Safari/537.36
form data
response_mode: fragment
Request from IE Eorking
Name	Protocol	Method	Result	Content type	Received	Time	Initiator
https://{domain}/sso	HTTPS	POST	302	text/html	229 B	247.61 ms	document
request header
Accept: text/html, application/xhtml+xml, image/jxr, /
Accept-Encoding: gzip, deflate
Accept-Language: en-US
Cache-Control: no-cache
Connection: Keep-Alive
Content-Length: 24
Content-Type: application/x-www-form-urlencoded
Cookie: mod_auth_openidc_state_XiBDKppwryTgibylRWyqo-HYh1U={...}
Host: {domain}
Referer: https://{domain}/sso
response header
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) like Gecko
Connection: Keep-Alive
Content-Length: 229
Content-Type: text/html; charset=iso-8859-1
Date: Wed, 27 Mar 2019 21:39:49 GMT
Keep-Alive: timeout=15, max=99
Location: https://{domain}/
Server:
Strict-Transport-Security: max-age=31536000; includeSubDomains
Response payload
Connection: Keep-Alive
Content-Length: 229
Content-Type: text/html; charset=iso-8859-1
Date: Wed, 27 Mar 2019 21:39:49 GMT
Keep-Alive: timeout=15, max=99
Location: https://{domain}
Server:
Strict-Transport-Security: max-age=31536000; includeSubDomains

please set the server log level to debug and inspect the logs to find out what is happening in the case of "sometimes" as opposed to the regular case; there's not much more to be done with this info


Simpy does not work

I've cloned the repo and did everything correct but nginx does not serve my website at port 80 even though it should proxy the nuxt server thats working properly at localhost:3000

What is the environment you are working with? Windows Server, Ubuntu? Usually, runnning port number lower than 1024 (including port 80 for nginx) will require user to have more priviledge than usual. [https://www.w3.org/Daemon/User/Installation/PrivilegedPorts.html]
I'm not sure if user permission is the case here or not. If you can provide more information, maybe I can help.

My bad, my Nginx config had to be configured properly, took me a few days to find but at last I did it 😬


Transact-SQL snapshot backups: Please share the .cmd script

[Enter feedback here]
Thanks for the demo. But the critical part was step2 initializing snapshot backup.  I wonder if you could share with us how this implemented in Azure blob with the .cmd script.

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

ID: 8840ba86-332c-33fc-509b-9e7e08671c7a
Version Independent ID: 8840ba86-332c-33fc-509b-9e7e08671c7a
Content: Create a Transact-SQL snapshot backup - SQL Server
Content Source: docs/relational-databases/backup-restore/create-a-transact-sql-snapshot-backup.md
Service: sql
Sub-service: backup-restore
GitHub Login: @perrysk-msft
Microsoft Alias: peskount

@glmios I'm closing this issue, as we are tracking it internally.
AB#70883

Duplicate of #9235.

@glmios This is the response from the product group for now.

Thank you all for your interest in T-SQL Snapshot Backup!
With T-SQL snapshot backup in SQL Server 2022 we provide commands to freeze and thaw the database and not commands to perform the actual snapshot. Taking the actual snapshot of the disk still falls under the responsibility of the customer. Customers can use 3rd party tools of their choice or implement their own solution to take the snapshot of the disk.
In the video, we are using an internal SQL trace flag that allows copying the .mdf and .ldf files to another disk (simulating a disk snapshot backup) while SQL is still running. The TF is used only for demo purposes, and we are not exposing that TF externally.
An alternative to testing T-SQL Snapshot Backup is by using an Azure VM and this PS script:
https://github.com/microsoft/sql-server-samples/blob/master/samples/features/t-sql-snapshot-backup/snapshot-backup-restore-azurevm-single-db.ps1 might be the best option.

Given that what you likely saw was the use of an undocumented trace flag, this is as far as I can take the resolution of this issue. I appreciate your patience while I got the information, even if it isn't what you wanted to hear.


Bug fixed; --metadata option, allows the user to specify key/value pairs for encoding metadata (Should be used with --add-metadata)

Please follow the guide below

You will be asked some questions, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your pull request (like that [x])
Use Preview tab to see how your pull request will actually look like

Before submitting a pull request make sure you have:

[x] At least skimmed through adding new extractor tutorial and youtube-dl coding conventions sections
[x] Searched the bugtracker for similar pull requests
[x] Checked the code with flake8

In order to be accepted and merged into youtube-dl each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[x] Bug fix
[ ] Improvement
[ ] New extractor
[x] New feature

Description of your pull request and other information
Explanation of your pull request in arbitrary form goes here. Please make sure the description explains the purpose and effect of your pull request and is worded well enough to be understood. Provide as much context and examples as possible.

$ python -m youtube_dl --add-metadata --metadata "album = Movie Title artist= Various Artists" -f 140 https://www.youtube.com/watch?v=EL8e2ujXe8g
[youtube] EL8e2ujXe8g: Downloading webpage
[youtube] EL8e2ujXe8g: Downloading video info webpage
[youtube] EL8e2ujXe8g: Extracting video information
[download] Destination: Stop Whining-EL8e2ujXe8g.m4a
[download] 100% of 30.12KiB in 00:00
[ffmpeg] Correcting container in "Stop Whining-EL8e2ujXe8g.m4a"
[fromuser] album: Movie Title
[fromuser] artist: Various Artists
[ffmpeg] Adding metadata to 'Stop Whining-EL8e2ujXe8g.m4a'

Fix the rest of the issues I've mentioned.

Hi,
I already replied to your comments,
===================================
@dstftw
Collaborator
dstftw commented 3 days ago
Have you even tried to check your changes? It does not work since it's not wired into the code.
It must not do anything apart from taking user provided metadata. No extraction from description, etc.
Core tests are broken.
Duplicate of #6064.
@dstftw dstftw closed this 3 days ago
@vayalil
vayalil commented 3 days ago •
Sorry, it will work if you used --add-metadata option as well. Since this --metadata is just providing additional metadatas, so I thought it would be better in that way.
Same as above, it will extract 'artist's name from the file description if used with --add-metadata.
But it is not still added to the main.
I will try to fix core test issues.
Regards
Niras

From: Sergey M<EMAIL_ADDRESS>Sent: Saturday, February 17, 2018 10:25 AM
To: rg3/youtube-dl
Cc: vayalil; Author
Subject: Re: [rg3/youtube-dl] Bug fixed; --metadata option, allows the user to specify key/value pairs for encoding metadata (Should be used with --add-metadata) (#15627)
Fix the rest of the issues I've mentioned.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/rg3/youtube-dl/pull/15627#issuecomment-366387738, or mute the threadhttps://github.com/notifications/unsubscribe-auth/Aiv3w-ZVDla8uGkmL25YjkbQHeBpfj4Aks5tVg5wgaJpZM4SJDum.


[Callout] Expects  for callout-inner, Inky generating

None of the callout examples are working on the docs website.  Using firefox, switch the tag from a td to th for a callout-inner and the coloring magically works.
http://foundation.zurb.com/emails/docs/callout.html
What did you expect to happen?
Coloring/border should be visible when using callout
What happened instead?
Coloring/border was not visible when a  was used with class callout-inner.
Test case
Give us a link to a CodePen or JSFiddle that recreates the issue.
https://jsfiddle.net/yhpd3ysn/
Fixed the primary callout; the other callouts are broken.

fixed it here: https://github.com/zurb/inky/commit/a43da5653e54d684209cf48090515228abb23313
Thanks for the report! We'll be putting out a patch today!

Quick question, how do I update an existing project once the patch is out? Thanks!

cd "project_folder"
npm update
npm outdated (if there's no result's you are GOLDEN)

Fixed in Inky 1.3.4