Failure in building Ubuntu 2204 image

We started getting the following error message effective today:

2023-03-02T18:26:34.9819577Z     azure-arm.build_vhd: Error — Either HTTP response code for 'https://dl.google.com/android/repository/commandlinetools-linux-9477386_latest.zip
2023-03-02T18:26:34.9823918Z     azure-arm.build_vhd: commandlinetools-linux-9645777_latest.zip
2023-03-02T18:26:34.9829150Z     azure-arm.build_vhd: commandlinetools-linux-9644228_latest.zip' is wrong - '200000000' or exit code is not 0 - '6'. Waiting 30 seconds before the next attempt, 19 attempts left
2023-03-02T18:27:08.6926940Z     azure-arm.build_vhd: Error — Either HTTP response code for 'https://dl.google.com/android/repository/commandlinetools-linux-9477386_latest.zip
2023-03-02T18:27:08.6930948Z     azure-arm.build_vhd: commandlinetools-linux-9645777_latest.zip
2023-03-02T18:27:08.6936179Z     azure-arm.build_vhd: commandlinetools-linux-9644228_latest.zip' is wrong - '200000000' or exit code is not 0 - '6'. Waiting 30 seconds before the next attempt, 18 attempts left
2023-03-02T18:27:40.0008634Z     azure-arm.build_vhd: Error — Either HTTP response code for 'https://dl.google.com/android/repository/commandlinetools-linux-9477386_latest.zip
2023-03-02T18:27:40.0012821Z     azure-arm.build_vhd: commandlinetools-linux-9645777_latest.zip
2023-03-02T18:27:40.0024019Z     azure-arm.build_vhd: commandlinetools-linux-9644228_latest.zip' is wrong - '200000000' or exit code is not 0 - '6'. Waiting 30 seconds before the next attempt, 17 attempts left
2023-03-02T18:28:11.1161656Z     azure-arm.build_vhd: Error — Either HTTP response code for 'https://dl.google.com/android/repository/commandlinetools-linux-9477386_latest.zip
2023-03-02T18:28:11.1166057Z     azure-arm.build_vhd: commandlinetools-linux-9645777_latest.zip
2023-03-02T18:28:11.1171523Z     azure-arm.build_vhd: commandlinetools-linux-9644228_latest.zip' is wrong - '200000000' or exit code is not 0 - '6'. Waiting 30 seconds before the next attempt, 16 attempts left
2023-03-02T18:28:42.8183498Z     azure-arm.build_vhd: Error — Either HTTP response code for 'https://dl.google.com/android/repository/commandlinetools-linux-9477386_latest.zip
2023-03-02T18:28:42.8188112Z     azure-arm.build_vhd: commandlinetools-linux-9645777_latest.zip
2023-03-02T18:28:42.8193530Z     azure-arm.build_vhd: commandlinetools-linux-9644228_latest.zip' is wrong - '200000000' or exit code is not 0 - '6'. Waiting 30 seconds before the next attempt, 15 attempts left
2023-03-02T18:29:14.7422271Z     azure-arm.build_vhd: Error — Either HTTP response code for 'https://dl.google.com/android/repository/commandlinetools-linux-9477386_latest.zip
2023-03-02T18:29:14.7426379Z     azure-arm.build_vhd: commandlinetools-linux-9645777_latest.zip
2023-03-02T18:29:14.7431695Z     azure-arm.build_vhd: commandlinetools-linux-9644228_latest.zip' is wrong - '200000000' or exit code is not 0 - '6'. Waiting 30 seconds before the next attempt, 14 attempts left
2023-03-02T18:29:45.3858832Z     azure-arm.build_vhd: Error — Either HTTP response code for 'https://dl.google.com/android/repository/commandlinetools-linux-9477386_latest.zip
2023-03-02T18:29:45.3862874Z     azure-arm.build_vhd: commandlinetools-linux-9645777_latest.zip
2023-03-02T18:29:45.3868354Z     azure-arm.build_vhd: commandlinetools-linux-9644228_latest.zip' is wrong - '200000000' or exit code is not 0 - '6'. Waiting 30 seconds before the next attempt, 13 attempts left
2023-03-02T18:30:16.2499116Z     azure-arm.build_vhd: Error — Either HTTP response code for 'https://dl.google.com/android/repository/commandlinetools-linux-9477386_latest.zip
2023-03-02T18:30:16.2503284Z     azure-arm.build_vhd: commandlinetools-linux-9645777_latest.zip
2023-03-02T18:30:16.2508757Z     azure-arm.build_vhd: commandlinetools-linux-9644228_latest.zip' is wrong - '200000000' or exit code is not 0 - '6'. Waiting 30 seconds before the next attempt, 12 attempts left
2023-03-02T18:30:47.0776538Z     azure-arm.build_vhd: Error — Either HTTP response code for 'https://dl.google.com/android/repository/commandlinetools-linux-9477386_latest.zip
2023-03-02T18:30:47.0780607Z     azure-arm.build_vhd: commandlinetools-linux-9645777_latest.zip
2023-03-02T18:30:47.0785821Z     azure-arm.build_vhd: commandlinetools-linux-9644228_latest.zip' is wrong - '200000000' or exit code is not 0 - '6'. Waiting 30 seconds before the next attempt, 11 attempts left
2023-03-02T18:31:18.2482382Z     azure-arm.build_vhd: Error — Either HTTP response code for 'https://dl.google.com/android/repository/commandlinetools-linux-9477386_latest.zip
2023-03-02T18:31:18.2486815Z     azure-arm.build_vhd: commandlinetools-linux-9645777_latest.zip
2023-03-02T18:31:18.2491964Z     azure-arm.build_vhd: commandlinetools-linux-9644228_latest.zip' is wrong - '200000000' or exit code is not 0 - '6'. Waiting 30 seconds before the next attempt, 10 attempts left
2023-03-02T18:31:50.8730167Z     azure-arm.build_vhd: Error — Either HTTP response code for 'https://dl.google.com/android/repository/commandlinetools-linux-9477386_latest.zip
2023-03-02T18:31:50.8734672Z     azure-arm.build_vhd: commandlinetools-linux-9645777_latest.zip
2023-03-02T18:31:50.8739880Z     azure-arm.build_vhd: commandlinetools-linux-9644228_latest.zip' is wrong - '200000000' or exit code is not 0 - '6'. Waiting 30 seconds before the next attempt, 9 attempts left
2023-03-02T18:32:21.8498290Z     azure-arm.build_vhd: Error — Either HTTP response code for 'https://dl.google.com/android/repository/commandlinetools-linux-9477386_latest.zip
2023-03-02T18:32:21.8502637Z     azure-arm.build_vhd: commandlinetools-linux-9645777_latest.zip
2023-03-02T18:32:21.8507831Z     azure-arm.build_vhd: commandlinetools-linux-9644228_latest.zip' is wrong - '200000000' or exit code is not 0 - '6'. Waiting 30 seconds before the next attempt, 8 attempts left
2023-03-02T18:32:52.6230790Z     azure-arm.build_vhd: Error — Either HTTP response code for 'https://dl.google.com/android/repository/commandlinetools-linux-9477386_latest.zip
2023-03-02T18:32:52.6235698Z     azure-arm.build_vhd: commandlinetools-linux-9645777_latest.zip
2023-03-02T18:32:52.6241043Z     azure-arm.build_vhd: commandlinetools-linux-9644228_latest.zip' is wrong - '200000000' or exit code is not 0 - '6'. Waiting 30 seconds before the next attempt, 7 attempts left
2023-03-02T18:33:23.7646518Z     azure-arm.build_vhd: Error — Either HTTP response code for 'https://dl.google.com/android/repository/commandlinetools-linux-9477386_latest.zip
2023-03-02T18:33:23.7651980Z     azure-arm.build_vhd: commandlinetools-linux-9645777_latest.zip
2023-03-02T18:33:23.7657932Z     azure-arm.build_vhd: commandlinetools-linux-9644228_latest.zip' is wrong - '200000000' or exit code is not 0 - '6'. Waiting 30 seconds before the next attempt, 6 attempts left
2023-03-02T18:33:54.7310483Z     azure-arm.build_vhd: Error — Either HTTP response code for 'https://dl.google.com/android/repository/commandlinetools-linux-9477386_latest.zip
2023-03-02T18:33:54.7314935Z     azure-arm.build_vhd: commandlinetools-linux-9645777_latest.zip
2023-03-02T18:33:54.7320099Z     azure-arm.build_vhd: commandlinetools-linux-9644228_latest.zip' is wrong - '200000000' or exit code is not 0 - '6'. Waiting 30 seconds before the next attempt, 5 attempts left
2023-03-02T18:34:25.9124051Z     azure-arm.build_vhd: Error — Either HTTP response code for 'https://dl.google.com/android/repository/commandlinetools-linux-9477386_latest.zip
2023-03-02T18:34:25.9128382Z     azure-arm.build_vhd: commandlinetools-linux-9645777_latest.zip
2023-03-02T18:34:25.9133492Z     azure-arm.build_vhd: commandlinetools-linux-9644228_latest.zip' is wrong - '200000000' or exit code is not 0 - '6'. Waiting 30 seconds before the next attempt, 4 attempts left
2023-03-02T18:34:56.9730816Z     azure-arm.build_vhd: Error — Either HTTP response code for 'https://dl.google.com/android/repository/commandlinetools-linux-9477386_latest.zip
2023-03-02T18:34:56.9735212Z     azure-arm.build_vhd: commandlinetools-linux-9645777_latest.zip
2023-03-02T18:34:56.9740362Z     azure-arm.build_vhd: commandlinetools-linux-9644228_latest.zip' is wrong - '200000000' or exit code is not 0 - '6'. Waiting 30 seconds before the next attempt, 3 attempts left
2023-03-02T18:35:28.1015871Z     azure-arm.build_vhd: Error — Either HTTP response code for 'https://dl.google.com/android/repository/commandlinetools-linux-9477386_latest.zip
2023-03-02T18:35:28.1020134Z     azure-arm.build_vhd: commandlinetools-linux-9645777_latest.zip
2023-03-02T18:35:28.1025413Z     azure-arm.build_vhd: commandlinetools-linux-9644228_latest.zip' is wrong - '200000000' or exit code is not 0 - '6'. Waiting 30 seconds before the next attempt, 2 attempts left
2023-03-02T18:35:58.7471148Z     azure-arm.build_vhd: Error — Either HTTP response code for 'https://dl.google.com/android/repository/commandlinetools-linux-9477386_latest.zip
2023-03-02T18:35:58.7476208Z     azure-arm.build_vhd: commandlinetools-linux-9645777_latest.zip
2023-03-02T18:35:58.7481950Z     azure-arm.build_vhd: commandlinetools-linux-9644228_latest.zip' is wrong - '200000000' or exit code is not 0 - '6'. Waiting 30 seconds before the next attempt, 1 attempts left
2023-03-02T18:36:30.6204673Z     azure-arm.build_vhd: Error — Either HTTP response code for 'https://dl.google.com/android/repository/commandlinetools-linux-9477386_latest.zip
2023-03-02T18:36:30.6208895Z     azure-arm.build_vhd: commandlinetools-linux-9645777_latest.zip
2023-03-02T18:36:30.6214305Z     azure-arm.build_vhd: commandlinetools-linux-9644228_latest.zip' is wrong - '200000000' or exit code is not 0 - '6'. Waiting 30 seconds before the next attempt, 0 attempts left
2023-03-02T18:37:00.6226144Z     azure-arm.build_vhd: Could not download https://dl.google.com/android/repository/commandlinetools-linux-9477386_latest.zip

Just an FYI, it ain't just you ... ;-}
I've been having this issue for a couple days, even when running on a local machine per the instructions from https://msftplayground.com/2021/02/private-azure-devops-agent-pool-based-the-microsoft-hosted-agents/. IOW ... it isn't Yannick's stuff that's blowing up.

@SamBonavika That's what I guessed too! I think it makes sense to open this issue on Microsoft's github.

@SamBonavika @YannickRe I reported this issue to Microsoft.

Yeah, most likely this is because they use their repo as a "work-in-progress" and I just copy from that latest version of their code, bleeding edge. There have been discussions to make adjustments so we by default take the code base from the latest release of each of the images, but no one has gotten around to implement that just yet.
MS is pretty quick to fix their issues, so it could be that this has been resolved tomorrow but for continuous work, it be better if we based on stable releases.


[Feature]: make Calendar et al. useable with uncontrolled forms

What problem does this feature solve?
I would like to use the calendar component and its different flavours (DatePicker, DateRangePicker) as uncontrolled form fields. Currenty the only way to extract the value is to pass state to the component, if I want to add this to the outgoing formData i think the only way would be to do some trickery with the outgoing onSubmit event and then hook the value in somehow.
The components could include an <input type="hidden" name={props.name} value={state.currentValue} /> within them so that form onsubmit could detect the value automatically.
What does the proposed API look like?
The proposed API is as follows:
Add something like <input type="hidden" name={props.name} value={state.currentValue} /> to each component somewhere, not directly in the Calendar component itself, then serialised accordingly (for eg. DateRangePicker would have 2 value).

@tompeace would you mind sharing an example where the Calendar elements are not working for uncontrolled forms? They appear to work in the stories

Hi @tompeace, were you able to use the calendar with uncontrolled forms?


Add prefix and reverse notation to schema [phab:D1924]

Created by djrenren at 2017-09-06 22:01:17:
This changes updates the schema docs to include mention of the
implicit /kythe prefix and % notation for reversed edges.

djrenren wrote at 2017-09-06 22:02:21:
Pictures of the changes:
{F23162}
{F23164}

djrenren wrote at 2017-09-06 22:03:46:

Forgot the space in "Reverse Edges"

jrtom commented inline (context lost during migration) at 2017-09-06 22:14:48:
missing phrase, suggest reword to: "validator will automatically prepend '/kythe' to all fact names and edge kinds unless the name or kind begins with a /."

jrtom commented inline (context lost during migration) at 2017-09-06 22:14:48:
I don't think that this sentence belongs in the schema definition.

zarko commented inline (context lost during migration) at 2017-09-06 22:17:52:
s/validator/verifier/
Edge kinds are implicitly /kythe/edge/foo

zarko commented inline (context lost during migration) at 2017-09-06 22:17:52:
We'd discussed this a bit and it's tripped enough people up that it's worth adding here.
Also, %/kythe/edge/defines/binding instead of %/kythe/defines/binding

djrenren wrote at 2017-09-06 22:19:25:

Update wording

djrenren commented inline (context lost during migration) at 2017-09-06 22:20:43:
It's a strange place but it seems the most likely to help people who are looking for what it means. Open to suggestions of where to put it though.

jrtom commented inline (context lost during migration) at 2017-09-06 22:21:56:
But isn't whether reverse edges are emitted by indexers a statement about the indexer design, not the schema?
Perhaps this might be better:
"Reverse edges are not necessarily emitted by indexers, but may be constructed during post-processing."

zarko commented inline (context lost during migration) at 2017-09-06 22:26:52:
Oh, sorry, I'd skipped a key word. Yeah--I agree that the sentence starting "Reverse edges..." should just be dropped.

djrenren wrote at 2017-09-06 22:49:29:

Document edge prefixes...

djrenren wrote at 2017-09-06 22:50:31:
Moved namespacing to a top-level header as it was getting bulky under a tip:
{F23166}

zarko commented inline (context lost during migration) at 2017-09-06 22:55:38:
Update: I have been convinced that we should mention that indexers should not emit reverse edges.

djrenren wrote at 2017-09-06 23:02:40:

Update wording about reverse edges

djrenren wrote at 2017-09-06 23:08:22:

Use "NodeA" instead of "A" to increase readability

zarko commented inline (context lost during migration) at 2017-09-06 23:11:10:
nit: long line

zarko accepted this revision at 2017-09-06 23:11:10

djrenren wrote at 2017-09-06 23:15:37:

Fix long line

djrenren closed via commit ff32fcc234fa6c260e93efdcf86a0c3bad980fdf at 2017-09-06 23:16:34

jrtom commented inline (context lost during migration) at 2017-09-07 01:21:35:
So for those of us who missed the conversation in which that was resolved, could you briefly summarize?  This still seems like a weird thing to have in the schema, independent of whether it's something that we want to contractually guarantee about reverse edges or not.


How do Search images using input search  box.

I want to add the Search box for searching the images.. How to can implement?
Issue # 728
Issue # 995
I can't understand how to implement search box as Issue # 995 is done....any demo available?
or written documentation
Packages Info

Operating system :Windows 10
Laravel version :^8.12
Package version :^2.2

Hi @Zubair-Iftikhar
I did it using jQuery, so you don't need to change the Item Controller

Same issue
@Zubair-Iftikhar can you provide more details  and/or sample code?

Hi @Zubair-Iftikhar
great job
can you share you code ?
thanks

$(document).ready(function(){
$("#keyword").on("keyup", function() {
// var value = $(this).val().toLowerCase();
show_list = $(this).data('display');
loadItems();
});
});
path: public/js/script.js
i use this, but only work on current directory


fix: Bring back Cxx TurboModule autolinking via registerCxxModuleToGlobalModuleMap

Summary:
Reverts the PR https://github.com/facebook/react-native/pull/45967 from @philIip to bring back the registerCxxModuleToGlobalModuleMap(..) function, which I use in Nitro Modules and MMKV.
Ontop of that, this also removes the "experimental" RCT_EXPORT_CXX_MODULE_EXPERIMENTAL macro, which I think was the original intent of this PR as this macro is a bit unsafe.
I also added some small docs to registerCxxModuleToGlobalModuleMap while I'm at it.

Changelog:

Test Plan:
Build Nitro Modules. Worked for me! :)

thank you!!!


Copy Documents upon Save

This should be done after #54 is merged.
Before this PR, setData did not copy Map and Arrays when saving data. Therefore, modification to the data passed as the argument of setData, add, and updateData resulted in affecting the documents held by cloud_firestore_mocks.

This should be done after #54 is merged. Closing this for now.

This is superseded by #56


Tests not run based on Groups when  tag is at test level

TestNG Version
7.1.0
Expected behavior
Only methods that match the provided Group are run
Actual behavior
All methods in all classes are run. Groups are ignored
Is the issue reproductible on runner?

[ ] Shell
[x] Maven
[ ] Gradle
[ ] Ant
[ ] Eclipse
[ ] IntelliJ
[ ] NetBeans

Test case sample
@Test(groups = {"foo"})
	public void testA() {
		System.out.println("foo test");
	}
	@Test(groups = {"bar"})
	public void testB() {
		System.out.println("bar test");
	}

test xml:
<suite name="Test suite" verbose="1" parallel="tests" thread-count="2" preserve-order="false">
	<groups>
		<run>
			<include name="foo" />
		</run>
	</groups>
	<test name="Test 1">
		<classes>
			<class name="myclass" />
		</classes>
	</test>
</suite>

If the groups tag is defined within the test tag, it works fine. However, I'm trying to build a test suite with multiple  that are all using the same group. A workaround is simple moving the groups tag within each test but it just makes things too long/annoying when reading the test suite.

@QAthulhu - I am not able to reproduce this issue.
Test class
import org.testng.ITestResult;
import org.testng.Reporter;
import org.testng.annotations.Test;

public class SampleTestClass {

  @Test(groups = {"foo"})
  public void testA() {
    System.out.println("foo test");
    printSuite();
  }

  @Test(groups = {"bar"})
  public void testB() {
    System.out.println("bar test");
    printSuite();
  }

  private void printSuite() {
    System.err.println("Printing the suite being used");
    ITestResult result = Reporter.getCurrentTestResult();
    System.err.println(result.getTestContext().getCurrentXmlTest().getSuite().toXml());
  }
}

Suite xml
<!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd" >
<suite name="SampleTestSuite" verbose="2" parallel="false" thread-count="1">
  <groups>
    <run>
      <include name="foo"/>
    </run>
  </groups>
  <test name="Test 1">
    <classes>
      <class name="com.rationaleemotions.github2336.SampleTestClass"/>
    </classes>
  </test>
</suite>

Execution output
...
... TestNG 7.1.0 by Cédric Beust<EMAIL_ADDRESS>...

foo test
Printing the suite being used
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE suite SYSTEM "https://testng.org/testng-1.0.dtd">
<suite thread-count="1" guice-stage="DEVELOPMENT" verbose="2" name="SampleTestSuite">
  <groups>
    <run>
      <include name="foo"/>
    </run>
  </groups>
  <test thread-count="1" verbose="2" name="Test 1">
    <classes>
      <class name="com.rationaleemotions.github2336.SampleTestClass"/>
    </classes>
  </test> <!-- Test 1 -->
</suite> <!-- SampleTestSuite -->

===============================================
SampleTestSuite
Total tests run: 1, Passes: 1, Failures: 0, Skips: 0
===============================================

Process finished with exit code 0

@krmahadevan thank you for your sample. It seems all tests are being run when I am running my test suite from within another test suite. I'll explain.
I run a main test suite like this:
<!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd">
<suite name="Sanity Test Suite">
	<suite-files>
		<suite-file path="sanity-tests/suite.xml"></suite-file>
	</suite-files>
</suite>

The suite.xml can be your sample:
<!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd" >
<suite name="SampleTestSuite" verbose="2" parallel="false" thread-count="1">
  <groups>
    <run>
      <include name="foo"/>
    </run>
  </groups>
  <test name="Test 1">
    <classes>
      <class name="com.rationaleemotions.github2336.SampleTestClass"/>
    </classes>
  </test>
</suite>

When I run the tests this way, I get this output:
foo test
Printing the suite being used
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd">
<suite thread-count="4" guice-stage="DEVELOPMENT" verbose="0" name="SampleTestSuite" parallel="tests">
  <test thread-count="4" verbose="0" name="Test 1" parallel="tests">
    <classes>
      <class name="ph.iwant.tests.authentication.SampleTestClass"/>
    </classes>
  </test> <!-- Test 1 -->
</suite> <!-- SampleTestSuite -->

bar test
Printing the suite being used
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd">
<suite thread-count="4" guice-stage="DEVELOPMENT" verbose="0" name="SampleTestSuite" parallel="tests">
  <test thread-count="4" verbose="0" name="Test 1" parallel="tests">
    <classes>
      <class name="ph.iwant.tests.authentication.SampleTestClass"/>
    </classes>
  </test> <!-- Test 1 -->
</suite> <!-- SampleTestSuite -->

I have moved the groups tag to the outer xml file and it has solved the problem!
Just wondering, is this the expected behavior or encouraged standard? Should I put parameters in the outer xml file as well?

@QAthulhu - TestNG is working as designed.
When you work with a suite of suites (Which is what you are using), the group definition should be present in the master group and that is what will get used for execution.
In your master suite, you dont have any group definitions created and that is why TestNG is running everything.
Closing this with resolution as working as designed
Relevant code snippet that you can refer to https://github.com/cbeust/testng/blob/b20ba401de49bc61795d20766f6307a8c6d5aa85/src/main/java/org/testng/xml/XmlSuite.java#L879-L888


Add generic support for CSV files

add support csv files with and without headers

I would split this task into:

[ ] saving (exporting) data from table-views into CSV
[ ] opening CSV files as table


SPARKC-399: Removed CassandraSQLContext

Build against Scala 2.11 finished with failure

Build against Scala 2.10 finished with failure

Build against Scala 2.11 finished with success

Build against Scala 2.10 finished with success

@alexliu68 - yes, it works with dots now.

Build against Scala 2.11 finished with success

Build against Scala 2.10 finished with success

+1


[AutoPR advisor/resource-manager] Run spellcheck against changed json file in PR

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/7140

(message created by the CI based on PR content)


Can't get futbin data on special cards

When pressing F to find out the futbin prices on a special card it shows the regular card price

Dupe of #48.


Added Cel Shading effect to Levels

Added

Cel Shader
Toon Shader Plugin

Uses Toon Shader to add Cel shader effect to Tutorial & In-game level.

 Cel Shading Art Style


Background Slider

Is your feature request related to a problem? Please describe.

Describe the solution you'd like.
The image has to be slided along with the background.
Describe alternatives you've considered.
.
Add any other context or screenshots about the feature request here.
No response

Kindly assign this issue to me


ToolTip

Issue

Create a tooltip on InfoIcon.
When hover and click on InfoIcon and
You can find it in Login.jsx and Signup.jsx.

The issue has been resolved in #69


Skip synthetic ServiceEntry test

Please provide a description for what this PR is for.
And to help us figure out who should review this PR, please
put an X in all the areas that this PR affects.
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[x] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

@howardjohn I will take a look at the flakes shortly, however some of those flakes look new.

@Nino-K: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
1daab01d5b9863dda93394a4608676dd7ed5968c
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@Nino-K: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
1daab01d5b9863dda93394a4608676dd7ed5968c
link
/test integ-telemetry-k8s-tests_istio

integ-framework-k8s-tests_istio
1daab01d5b9863dda93394a4608676dd7ed5968c
link
/test integ-framework-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

In response to a cherrypick label: new pull request created: #17971


HAWKULAR-530 pass around paths not IDs

Do not merge/release until the UI is changed so it passes resource paths, and not IDs.


Create insite.txt

Please add this college

@shermes641 I am sorry, the domain insite.4cd.edu is removed from our trusted domains list because the school allows to register an email address there even if you are not a student of the school. If you are the student of this school, please apply with official document (OFFICIAL DOCUMENT tab at https://www.jetbrains.com/shop/eform/students).


Allow to check for unstable releases

Description
This PR allows the Jadx updater to check for unstable releases. This will be useful for a later PR I'm working on which will allow for auto-updates, without the need to manually download the zip and extract it.
Many of us are using the unstable build as stable builds typically take a lot of time to be released and we always want the latest fixes and features (and bugs :P)
In a future PR which will be based in this code, I will add the option for jadx to auto-update just like other software do.
A settings option has been added to choose between the STABLE release channel (default, as always has been) or UNSTABLE (new behavior).
I chose to convert the code to kotlin since it looks a bit cleaner and has convenient features when handling Closeables and null checking.

It looks like the checks have not passed due to an internal github error while processing the jobs @skylot

@iscle looks good :+1:

checks have not passed due to an internal github error

Manual re-run didn't help, looks like github issues not fixed yet. Will try to run again later.


Rewrite DdsIdentifier to handle non-b-numbers

Handle CALM forms with slashes
Handle CALM forms with underscores
Instantiate from any form, yield canonical form
Extend the analysis to determine what kind of identifier it is
Allow hook for possible lookup in future

How does it distinguish between b12312312_0001_0004 and PPCRI_A_2?
DdsIdentifier.Bnumber is used to identify the “package”
ATM it’s just the first part of the identifier. You can get the b number, given a volume identifier (or an issue identifier for C&D).
The idea of identity in DDS needs to be generalised. The biggest decision is how much generalisation to do now - is it Goobi or Archivematica; if it looks like a b number it’s Goobi and it’s digitised; if it looks like a CALM id it’s Archivematica and born digital.
A CALM id might not have any / or _ in it if it’s a single catalogued item. Like MS.126
First pass - assume bnumber at start means digitised and Goobi.
If it or its first part is a b number:

it’s /digitised/ with a Goobi-style METS file.
Its storage manifest may be obtained from /digitised/bnumber.

If it or its first part is not a b number:

It’s born-digital from Archivematica.
-Its storage manifest is at /born-digital/identifier

…where identifier is the WHOLE identifier, with slashes (and not underscores)
We don’t need premature optimisation now, but in future, the DDS may need to do more looking up, given an identifier, because it will no longer be able to infer some things from the id itself. We can cross that bridge when we come to it, but make sure we are aware that the DDS could need to support this in future - so don’t do anything that makes this harder, leave a hook.

One particular non-premature optimisation, which will need revisiting if a third source of identifiers is later introduced, is the assumption that:

if the identifier starts with a b number, then its PackageIdentifier is the b number, but
if the identifier does not start with a b number, then its PackageIdentifier is the whole identifier string...
...with any underscores in that string converted to slashes.

This last point is only possible because CALM ids never have underscores in them.
Why might it come about? Because a URL-safe form of the identifier has been used.
The PackageIdentifier for A/B/C is A/B/C, the PackageIdentfier for A_B_C is A/B/C, and the PackageIdentifier for b12121313_0004 is b12121313.
The underscore to slash behaviour is completely avoided if you only use the slash form, even in places like dashboard URLs. We'll see...


Investigate undoing fusion with RULES

Assuming #27 gets merged, we should look at RULES so that we can write the fusable versions back to toView/fromView implementations in the case where fusion didn't fire.

I'm going to close this until we (perhaps) get a viable fusion framework for which it's relevant.


didSaveMergeChangesWith callback never called

Hey!
I'm having a similar issue as @tjosten in #277 - I see all baselines/events appearing in my app, even ensemble:shouldSaveMergedChangesIn:... is being called but I never see ensemble:didSaveMergeChangesWith being called. Also there is no data actually appearing in my NSPersistentContainer-managed CoreData.
Can you give me any hint what to try/debug?

That is very odd. And you are returning 'true' from the should-save-merge-changes? You aren't releasing the ensembles object somewhere?

Wow that was a quick reply :D
I returned true there, now commented out the implementation to check whether that changes anything (it doesn't).
Pretty sure I'm not releasing it, I hold a reference from my AppDelegate to the object - I also see logs appearing from CDECloudManager and all that - just never actually merging.

So the completion block of the merge method is never called? Is it possible perhaps that the did-merge isn't called, because it discovers there were no changes in the sync data. I think that can happen. The completion block should always be called though, data or no data.
If the merge is completing, but you don't see any data, the most likely culprit is simply that iCloud Drive has not yet transferred the data over. When using the simulator, you might need to use the Debug menu in Xcode to trigger the transfers.

Having lunch + trying gain worked. I actually found an Ensembles error 204 (wrong model version) hiding in the log -> Wiped iCloud drive & restarted apps -> Working.
Thanks a bunch :)

For future reference: Be sure to implement didFailToSaveMergedChangesIn as it might get called, like in my case, with a nice error: I had a unique constraint that failed and prevented almost all merges, just in some cases it seems to have merged it when I reset stuff and had the timing just right that recreated it.
@drewmccormack As I think I haven't seen the error without implementing the callback: Might it be useful to provide a default implementation for this that logs this error very prominently?
func persistentStoreEnsemble(_ ensemble: CDEPersistentStoreEnsemble!, didFailToSaveMergedChangesIn savingContext: NSManagedObjectContext!, error: Error!, reparationManagedObjectContext reparationContext: NSManagedObjectContext!) -> Bool {
    print("Merge failed \(error)")
    return false
}

Isn’t there any error in the merge completion block? I would expect the merge should fail.
Drew

On 24 Sep 2018, at 10:11, Tim Buchwaldt<EMAIL_ADDRESS>wrote:
For future reference: Be sure to implement didFailToSaveMergedChangesIn as it might get called, like in my case, with a nice error: I had a unique constraint that failed and prevented almost all merges, just in some cases it seems to have merged it when I reset stuff and had the timing just right that recreated it.
@drewmccormack As I think I haven't seen the error without implementing the callback: Might it be useful to provide a default implementation for this that logs this error very prominently?
func persistentStoreEnsemble(_ ensemble: CDEPersistentStoreEnsemble!, didFailToSaveMergedChangesIn savingContext: NSManagedObjectContext!, error: Error!, reparationManagedObjectContext reparationContext: NSManagedObjectContext!) -> Bool {
print("Merge failed (error)")
return false
}
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.


Adds a created_at column to cart.

This allows us to always return the cart in the same order to client at all times.
This haven't been tested, so if someone is willing that would be great.

Should also be fixed so it decrements the quantity on the products


Update/homepage improvements

What are you changing in this pull request and why?
Changes as outlined in the Asana task

[x]  When announcement bar is not present, make sure diamonds in hero do not overlap the header
[x]  Make the spacing between the rows of cards is an even 2rem across the board
[x]  Card fonts - font size is 20, line height is 30

[x]  Also for “Latest from Developer Blog”

[x]  Icon width is 25px
[x]  50px padding on left and right of entire page.
[x]  Latest from Dev Blog Section

[x]  Reduce space between each card - 30px
[x] Transparent gradient on sides of swiper container

Hey @breezyfasano , question -- I saw this in your notes:

Card fonts - font size is 20, line height is 30
Also for “Latest from Developer Blog”

"Latest from Developer Blog" looks to be 25px/41px. Is this correct?

And super-duper narrow on Galaxy S8+ (admittedly I'm not an Android user and I have no idea if anyone uses these any more, lol).

Team - I went ahead and removed the shadow per Emily's request on the Asana thread!
Still adjusting working on the Swiper card widths on mobile per @lfracalossiFA's feedback.
Thanks for your comments, all!

@lfracalossiFA and @john-rock - re-requesting a review on this with some changes!

I've removed the gradient from the carousel re: Emily's comment in Asana
I've also adjusted the carousel on mobile to reflect a less scrunched view!

Let me know what y'all think & if this addressed your changes.
https://deploy-preview-3012--docs-getdbt-com.netlify.app/

@lfracalossiFA that's okay, the warnings have been in there. We just setup ESLint for PRs, and only sorted out the blocking errors so far, but could always go back and clean up the warnings at some point


Create the public docker image using the docker registries like dockerhub/gcr

@yoheinakajima  Can we create a organization with "instagraph"
Create the docker image with the same. Like other technologies have the dockerhub account and image with the organization name.

Not 100% sure what this means as I'm relatively new to GitHub but I don't see why not! I think I've seen this elsewhere.

@JinnaBalu currently we don't have many docker image means for this organization published this project as an open source, In future more project converted to Opensorce then this will be benefit.


Fixed description

Fixed version of bootstrap in description

The description is for all branches, best to say 3/4

Better yet just remove both TWBS and CakePHP versions from the descriptions. They can be specified in READMEs of respective branches.


storage.delete does not seem to use Namespace causing entries not to be deleted.

Hi Plasmo team,
Not sure if this is an intended behavior but Storage.prototype.remove does not seem to consider the namespace, causing the workers that are using the namespace to fail to remove items with corresponding keys.
src/index.ts
await this.#primaryClient.remove(key)

Should this also use  getNamespacedKey(key) like get and set and have a rawRemove to remove entries directly?
  remove = async (key: string) => {
    const nsKey = getNamespacedKey(key)
    if (this.isCopied(nsKey)) {
      this.#secondaryClient?.removeItem(nsKey)
    }

    if (this.hasExtensionApi) {
      await this.#primaryClient.remove(nsKey)
    }
  }

I'd also be happy to work on a fix if this is unintended.

@shuntksh Thank you so much for the issue! This is indeed unintended - the namespace feature was made quickly to experiment with the concept, and I indeed missed some of the places that need to incorporate the namespace along the way xD

I'd also be happy to work on a fix if this is unintended.

That would be greatly appreciated - thank you 🙏

Thanks, @louisgv! I've submitted a PR to the main repository. I'm not certain if that's the right approach, so please let me know if you'd prefer me to open a PR in this repository instead. Also, if there's anything I missed in the changes, just let me know!
Here's the link to the PR: https://github.com/PlasmoHQ/plasmo/pull/573

@louisgv  - Sorry I realized the original PR did not include the change I made to the sub-module, as it is pointing to the wrong repository. I reopened it as a draft PR in this repository. Let me know if this is the correct repository for the change.
Thanks!


What is your email address?

OK, in all fairness to myself, I did scour the Internet for your contact information, and came up empty. I just became your project's first Patreon sponsor and would like to reach out to you via email to discuss my project involving PHP-Websockets. You can find my email here: http://www.phpexperts.pro/

Responded through email. If you haven't received it, let me know.


initializeWithClusterA: firstCluster clusterB: secondCluster assertion logic

initializeWithClusterA: firstCluster clusterB: secondCluster
	"Private - Initialize the receiver"

	super initializeWithClusterA: firstCluster clusterB: secondCluster.
	self assert: [ firstCluster size = secondCluster size ].

why not
initializeWithClusterA: firstCluster clusterB: secondCluster
	"Private - Initialize the receiver"

        self assert: [ firstCluster size = secondCluster size ].
	super initializeWithClusterA: firstCluster clusterB: secondCluster.

Fixed


Fix image in "Create a Role" article

PLEASE READ
Following a recent back-end update, all contributors with a local clone or fork of our repository are required to run yarn install. This does not apply to direct page edits.

[x] Yes, I've run yarn install
[ ] No, does not apply to me

Purpose of this pull request
This pull request fixes an image and some text in the following section per a request in Slack:
https://help.sumologic.com/docs/manage/users-roles/roles/create-manage-roles/#create-a-role

Select the type of change:

[x] Minor Changes - Typos, formatting, slight revisions, .clabot
[ ] Update Content - Revisions, updating sections
[ ] New Content - New features, sections, pages, tutorials
[ ] Site and Tools - Updates, maintenance, dependencies, new packages for the site (Docusaurus, Gatsby, React, etc.)

Thanks, @kimsauce!


Initial commit of Office365Api.Groups sample

Just noticed the font license for fabric restricts its use to Office Add-Ins. Should I update the project?

Also, cla has already been submitted.

@pschaeflein, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR.
Thanks, MSBOT;

I'll close this based on the discussion in email around aligning the naming. Thx for the your contribution and looking forward for new PR.


Improve elastchsearch query

The current query used to search in the Elasticsearch is toooo simple. We should study how to improve it and use the Elasticsearch rank to sort the results and etc.

The API is using the ES for a while now. If we need to improve it we can open another issue.


OSD update 2.4 -> 4.1 issues

Hello. I have some issues after updating the library from v.2.4.2 to v4.1.0
The main problem is that if I try to toggle navigator or annotations the app crashes with error Failed to execute 'removeChild' on 'Node': The node to be removed is not a child of this node.  It comes from these lines:
/** @lends OpenSeadragon.Control.prototype */
  $.Control.prototype = {
    /**
     * Removes the control from the container.
     * @function
     */
    destroy: function destroy() {
      this.wrapper.removeChild(this.element);
      if (this.anchor !== $.ControlAnchor.NONE) {
        this.container.removeChild(this.wrapper);
      }
    },

I guess the issue is in the way I'm working with the OSD instance - it is recreated with useEffect hook each time navigator or annotations are toggled. After that it is destroyed with a cleanup function to prevent viewer duplicates. The error appears when I try to call destroy() on viewer instance. Is there a more correct way of toggling additional controls than creating a new instance of OSD again and again?
I've tried also changing style for Navigator to make it visible and vice versa but after making in visible it stays blank.

Interesting. That certainly seems like a bug! It certainly shouldn't throw an exception on destroy. I've just tried a basic repro and I'm not getting that exception, so it must be something to do with how your viewer is set up (or maybe the timing). If you'd like to pursue this, it would be good to get a simple repro. Or, if you prefer, you can debug directly in the OSD code.
At any rate, destroying the viewer every time you want to toggle the navigator on/off seems pretty extreme! It looks like we don't have a feature for that... Could be a nice thing to add. If you're interested in developing that, I could point you in the right direction.
Otherwise, you can probably make it happen without modifying the OSD code. When you hide the navigator element, did you use display:none? That changes the size of the navigator to 0; I'm not surprised it couldn't recover from that (though that's something that could be improved as well). You might have more luck with visibility:hidden or opacity:0.

@msalsbery Sounds great!

I've just ran into the same (or similar issue)
In the application I'm working on, the navigator is moved from its orignal wrapper to a custom element with
$(`#${viewer.navigator.id}`).detach().appendTo(`#navigatorWrapper${viewerId}`);

thus this line in the $.Control.destroy() does not work anymore as this.wrapper is not the parent node of this.element
this.wrapper.removeChild(this.element);

Substituting the above line with the following in the OSD source code removed the error :
this.element.parentNode.removeChild(this.element)

@SebDelile Good point! Seems like a good fix.
@vadzimvashchanka Does that fix work for you?
Would one of you be up for making a PR for this?


Version 2 Review

@trowski @bwoebi @rdlowrey I reviewed Amp v2.0 and here are my comments.
Internal\WhenQueue
How important is the layer of indirection? If we're worried about the call stack, should we instead resolve promises asynchronously?
It could also be renamed to a more generic name like CallbackQueue or CallQueue.
Internal\Placeholder
Annotation for $onResolved is callable|\Amp\Internal\WhenQueue|null, should be ?WhenQueue or ?WhenQueue|null instead.
Coroutine
Why does it not accept a callable as constructor parameter in addition of generators?
Emitter
if ($this->resolved) {
    return;
}

^ Does that ignore double resolution silently?
Pause
Do we really need $value there? What about keep_alive = false?
Internal\LazyPromise
Why is this one internal? Why is Amp\lazy suggested to be used only? Why do we even have Amp\lazy? Instead of using arguments to Amp\lazy, those parameters can just be use'd in a closure by the user instead of providing them as arguments.
Amp\wrap vs. Amp\coroutine
It is weird to have both and usage will be confusion for users.
Amp\timeout
I think Amp\timeout shouldn't keep the loop running. The watchers should probably be unreferenced.
Amp\lift
Do we need lift? I always ask that when reading the docs regarding it.
Amp\filter
Amp\filter filters observables now instead of promises.

Regarding Emitter, I do not see any case where that branch ever shall be hit … looks like dead code to me which we can remove.
Agree on timeout() and Pause regarding keep-alive.
Why shall Coroutines accept callables? It is only appending () on caller side. Being explicit here is very cheap and thus I do not see any issue with accepting only Generators.
The difference between wrap() and coroutine() is that the one calls rethrow() and the other returns the promise. I'm not sure here. Having wrap reduces possibility that it's forgotten to manually rethrow on the caller side, but at the same time it's more confusing. I wish to hear others opinion here.
/ For the other functions, better ask @trowski

@bwoebi Just the same reason why we accept callable for Amp\resolve, too. A simpler API if you pass a anon function. /cc @DaveRandom

I do not think that was a good decision back then and the status quo [in v2] presents a better solution.

If you argue that way, we should probably also remove all wrappers like Amp\execute and Amp\onReadable.

Internal\WhenQueue is used only if there are multiple callbacks registered on a promise. It's not really about indirection as reducing the amount of logic in promises, only creating an array of callables if needed. I'm indifferent on naming, though __invoke()'s arguments are specific to when(), so…
The annotation in Internal\Placeholder for $onResolved is correct. If anything, it could just be ?callable.
I agree with @bwoebi, the Coroutine constructor should just accept generators.
The path in Amp\Emitter can be reached if the coroutine tries to emit a promise that then fails. See https://github.com/amphp/amp/blob/master/lib/Internal/Producer.php#L60-L64. The observable will then be resolved before the when callback on the coroutine is invoked. It's not ignoring double resolution, rather preventing double resolution of the observable.
Amp\lazy() is something I copied from JS implementations, but have never actually used. It is a nice way to create a set of dependencies even if you are not aware of what will be used - the typical example is module loading - but as you suggest there are other ways. We should make it a non-internal class like Pause if we want to keep it, or just drop the concept entirely.
I agree, Amp\timeout() should not keep the loop running.
The value for Amp\Pause is pretty pointless… a keep-alive argument would be much more useful. What should the promise resolve with? Maybe the the time slept?
Amp\lift() is used in Amp\map(), but beyond that I've never used it… I could just roll the code into Amp\map().
Amp\filter() could be renamed and the old function added again (or vice versa). So far the missing function hasn't come up, so I wonder if it was needed.

@trowski I'm not sure whether observables should completely fail if one emit fails.
Regarding lazy, I have a use case for it. It's useful for a session middleware that assigns the session to a local request variable and loads it only on first need. I just think the additional indirection of a function is not needed here.
Amp\Pause should probably just resolve to void, so null. I'm fine with the time, too, but usually you just do yield new Pause($ms), so you have the time there already.
I have seen the use of Amp\lift, but IMO it's hard to follow what the code actually does.
I don't know whether I used Amp\filter, but I think it could make sense to keep BC here, so it's easier to upgrade for people using version 1 currently.

The API looks really good. Great review too @kelunik.
Regarding the proxy functions - such as execute() and stop() - are they really necessary? They increase the surface area of the public API with all the costs that incurs.
E.g.
execute($fn);
// vs
Loop::execute(wrap($fn));

Using the functions directly also seems much more explicit to me, whereas execute() provides something additional to learn and understand.

@bwoebi @trowski What do you think about the proxy functions?

I disagree that it is additional stuff to learn. Developers don't need to learn the Loop stuff unless they want to do very advanced things. Thus the only thing devs have to learn is the proxy functions which handily auto-wrap for you.

@bwoebi They have to, assuming Amp isn't the only implementation. It's two ways of doing the exact same thing without providing real benefit. Most onReadable / onWritable handlers etc. aren't coroutines anyway.

@kelunik Why? Other implementations will need to use their own proxy/the loop funcs directly, but someone who uses Amp can use libraries from other impls without needing to know about the loop funcs??
Only in case where you would want to use the other library, sure. But why would you?

can use libraries from other impls without needing to know about the loop funcs

I'd say people should know about Loop, they should use it.

Only in case where you would want to use the other library, sure. But why would you?

Any library you use and might dig into might use another async helper library.

@bwoebi In general the discussion should be why we should have them instead of why we might not need them. The public API should be as minimal as possible. That's not only less to document, less bugs, it's also less to read and learn when starting.

We're talking about the same - We should have it, because it isn't an extra API (i.e. I disagree people should need to know about Loop) and is the most useful API for people.

@bwoebi We're not talking about the same. I want to remove those functions, you want to keep them.

I disagree people should need to know about Loop

Are you suggesting 1) people shouldn't need to know that the loop is there or 2) that they simply shouldn't need to know the interop loop API?
If 1) then what do we expect people to think stop() means for example? Stop what? The description of the function even says Stop the loop, with a link to the interop docs.
If 2) then what makes these proxy functions superior to the interop Loop methods? Are they simply there to provide insulation or are they there to add coroutine support? As a user I think I'd always code against interop so that I could swap out implementations, but using amp I'd be a bit confused about why I had an additional way of operating on the loop.

I mean 2), and it has both benefits, a bit of insulation (e.g. in case the spec ever changes!?) Both.
Also, you anyway won't be able to swap simply. the Promise API. The helper functions. The coroutine class. Too many dependencies.

a bit of insulation

That gains us nothing. The spec should be pretty stable at this point.

Also, you anyway won't be able to swap simply. the Promise API. The helper functions. The coroutine class. Too many dependencies.

I still think we should separate those into separate packages. The helper functions and coroutine class are useful for any promise implementation.

I still think we should separate those into separate packages.

That gains us nothing. People may include amp without using all the available functions and classes.

It does. We can update observables should a need to standardize them arise without requiring all packages using coroutines to upgrade to a new major version.

That's nonsense. We could then as well just create a separate repo for every single function, because they might need to be changed somewhen.
Realistically, you end up having observables at least as an indirect dependency if you use anything from amphp.

Realistically, you end up having observables at least as an indirect dependency if you use anything from amphp.

I think observables are a separate problem to the proxy functions because they have a clear reason to exist, but I certainly think they would benefit from being standardised in the same way that Promises have been (i.e. an interface).

I think the proxy functions are unnecessary magic and largely just fluff (as in the case of Amp\stop(), Amp\enable(), and other like functions that are nothing more than wrappers around Loop::*()). Amp\wrap() should be required when a callable should be run as a coroutine. Additionally, Amp\wrap() should again call Amp\rethrow() if the function returns any promise. This way a callback can invoke something async without having to be a coroutine itself.
We currently have a situation where callbacks are sometimes able to be coroutines, but usually they are treated as regular functions. It's difficult to remember under what circumstances a function will be run as a coroutine, so I'd rather remove this magic and require users to be explicit by wrapping callbacks with Amp\wrap() when the function will be a coroutine.

I think we should separate the stream functions into either their own namespace of give them a prefix. map makes sense for both, streams and promises. Same for filter.

All important issues have been resolved.


added go-ndn encoding to forwarder

One commit for go-ndn encoding changes, no management changes or files in this one.

I need to check the code locally so merge first before code review.


has many error : invalid association []

Your issue may already be reported! Please search on the issue track before creating one.
What version of Go are you using (go version)?
go version go1.9.2 darwin/amd64
Which database and its version are you using?
mysql 5.7
Please provide a complete runnable program to reproduce your issue. IMPORTANT
package main
import(
_ "github.com/go-sql-driver/mysql"
"github.com/jinzhu/gorm"
"fmt"
"time"
)
var(
	db *gorm.DB
)

type Article struct{
	gorm.Model
	Title string `gorm:"size:256;unique;"`
	Context string `gorm:"size:256"`
	Replays []Replay `gorm:"FOREIGNKEY:ArticleTitle,ASSOCIATION_FOREIGNKEY:Title;"`
}
type Replay struct{
	Article Article `gorm:"FOREIGNKEY:ArticleTitle;"`
	ArticleTitle string `gorm:"size:256"`
	Context string `gorm:"size:256"`
}

func main(){
	var err error
	args := fmt.Sprintf("%s:%s@tcp(%s:%s)/%s?charset=utf8&parseTime=True&loc=Local",
		"xxx", "xxx", "xx.com", "3306", "test")
		db, err = gorm.Open("mysql", args)
	if err!=nil{

	}
	db.DB().SetMaxOpenConns(10)
	db.DB().SetMaxIdleConns(100)
	db.DB().SetConnMaxLifetime(time.Hour)
	db.DropTableIfExists("articles","replays")
	db = db.Set("gorm:table_options", "ENGINE=InnoDB CHARSET=utf8 auto_increment=1")
	db.CreateTable(&Article{},&Replay{})
	db.LogMode(true)

	db.Save(&Article{
		Title:"new1",
		Context:"new article1",
	})
	db.Save(&Article{
		Title:"new2",
		Context:"new article2",
	})

	db.Save(&Replay{
		ArticleTitle:"new1",
		Context:"new replay for new1",
	})
	db.Save(&Replay{
		ArticleTitle:"new2",
		Context:"new replay for new2",
	})

	n1:=Article{
		Title:"new1",
	}
	db.Model(&n1).Select("context").Related(&n1.Replays)

	for _,r:=range n1.Replays{
		println(r.Context)
	}
}

when i use db.Model(&n1).Select("context").Related(&n1.Replays)
error: invalid association []
the  gorm:"FOREIGNKEY:ArticleTitle,ASSOCIATION_FOREIGNKEY:Title;" is not work.
when i use db.Model(&n1).Select("context").Related(&n1.Replays,"article_title")
the debug sql is SELECT context FROM replays  WHERE (article_title = '0')
but the sql should be SELECT context FROM replays  WHERE (article_title = 'new1')
when i use db.Model(&n1).Select("context").Related(&n1.Replays,"title")
the debug sql is SELECT context FROM replays  WHERE (`` = 'new1')
how can i get all replay context where title = new1

i read the source code.
i got it.
i should set Replays []Replay gorm:"FOREIGNKEY:ArticleTitle;ASSOCIATION_FOREIGNKEY:Title;"``
and when has many should use
db.Model(&n1).Select("context").Related(&n1.Replays,"Replays")


rm Compat

since we're now only on julia v1, we don't need this package anymore (which seems to cause [the uncertain compat problem in #291)

@mpastell @pfitzseb I'm going to merge this since it seems to be right thing to do within the current compat specification as mentioned in #291.


⚠ Bofrost.lu has degraded performance

In 7c002e1, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 2197 ms

Resolved: Bofrost.lu performance has improved in 5be0cad after 35 minutes.


Let the user provide specific versions of docker/compose

Read .docker-url and .docker-compose-url special files with URLs to specific downloads

Latest version of docker-compose is utterly broken. It would be nice to be able install previous stable version until fix is released.


Only Uploaded error

Hi,
When I try uploading with upload_photos_by_exif.py   the only thing I get is:
No sequence file existing
Found 47 pictures to upload
Uploaded error
Uploaded error
Uploaded error
Uploaded error
Uploaded error
Uploaded error
Uploaded error
Uploaded error
Uploaded error
Uploaded error
Uploaded error
Uploaded error
Uploaded error
Uploaded error
Uploaded error
Uploaded error
Uploaded error
Uploaded error
Uploaded error
Uploaded error
Uploaded error
Uploaded error
Uploaded error
Uploaded error
Uploaded error
Uploaded error
Uploaded error
Uploaded error
Uploaded error
Uploaded error
Uploaded error
Uploaded error
Uploaded error
Uploaded error
Uploaded error
Uploaded error
Uploaded error
Uploaded error
Uploaded error
Uploaded error
Uploaded error
Uploaded error
Uploaded error
Uploaded error
Uploaded error
Uploaded error
Uploaded error
Finish uploading form dir:  with sequence id: 14568
What am i doing wrong?

@kertase hi can you provide us a link with some samples with your images.
Thanks

Well you will find a sample here: http://3d4pi-avenches.alsenet.com/panos/
Normally to upload to services like yours I still add some extra metadata such as Orientation and XMP data for panoramas if they are need but since I did not find documentation on the needed tags I was going to look into it…

Hi i think the problem are the panoramas photos... Can you try with normal photos to upload? Thanks for reporting.
I'm keep going to investigate this issue and when we solve it i'l let you know
Thanks again 👍

First of what are you maximum size upload limits?
What kind of support do you have support for panoramas?
What tags do you use and would be nice for you for them to be present in the image metadata?
Unfortunately I could not find any documentation answering those questions…

Hi,
Could you tell me please at least what upload size limits you have on   your servers?
Or point me towards the documentation that could tell me?
Thanks you very much
K.

Hi sorry for late response.
In the next 2 weeks we will publish the documentation.
However maximum file size: 20mb/photo
If i can help you with anything let me know.
Thanks for reporting


Change import for examples

It would be nice to require in the name of the project for examples sake. This for reference.

This will not play nice during development of components unless we do it in the webpack configuration. It should be as simple as using a webpack alias, but then this means that we need to have dynamic webpack configurations based on the current component project. It was in the pipeline for other nifty things (dynamic examples, etc.) but it's something that will take a bit more effort.
I'm bumping it to the v1.1.0 milestone. This feature can easily be backwards compatible with the current functionality & it isn't a major deal breaker (though I agree, a minor inconvenience).


Missing documentation on multiple icebergs

Documentation about multiple icebergs is missing.
Need to add it.

Done.


Fixes LGTM logger errors and warnings

Contains
Fixes the following LGTM errors and warnings from #3510:

Missing format argument
Unused format argument

Note that the logging statements previously would log less information than expected, since the unmatched argument would simply be omitted from the formatted log statement.
How to test
Either reproducing the conditions that cause the logging to occur, or instead forcing the condition to occur by attaching a debugger and manually changing the state to force the logging code path.

Can one of the admins please verify this patch?

This pull request fixes 9 alerts when merging 09933aa2a4da9d293a900c18ca9462913235cf01 into 9118708ad3f34f0bc05572fe54ad47538c3164bb - view on LGTM.com
fixed alerts:

8 for Unused format argument
1 for Missing format argument

Comment posted by LGTM.com

Thanks for the cleanup! :-)
Added you to the game credits while I was in there

No problem! Thanks for the credit :-)


chore(295): add support for mdx stories

Adds support for the newer mdx story format

Saw this PR and wanted to see if we can get "controls" (or "essentials") added while we're at it?
Might need to update main.js to take advantage after installing
Also I'd like to help test this out, but can't figure out how to point to the commit, updating the package.json to use
"@pixeloven/cli-addon-storybook": "pixeloven/pixeloven#mdx-stories"
didn't work for me, how do I do it?

@twilliams15 ok things should be good to go. Instructions for testing

yarn install if you never have, this will install Lerna
yarn all:bootstrap this will install all other package stuff
yarn all:compile && yarn all:linker this will build the packages and symlink them
cd packages/examples/component-library && yarn start:storythis will start storybook in the example package, go to the url printed in consol


Why is not Path("test.txt").parent.parent a valid path?

Hello.
I love the concept of path.py, but this is the first time I use it and I am a bit disappointed.
While working with relative paths, I was wondering why Path("test.txt").parent.parent and Path("test.txt").parent return both "" instead of  "../somefolder/" and ".".
My use case is very simple. The user gives me some string path where I need to create a file. So, I first need to create the folder where the file will be located.
Path("test.txt").parent.makedirs_p()

This raises a FileNotFoundError because path Path('') does not exist.
By extension, I notice that parent.parent will unfortunately not return a relative path starting with ...
I have the feeling that we miss the opportunity for a very useful feature here.
Do you think this would make sense to implement this?

You're putting in a relative path, then trying to work from it as thought it were absolute. Use abspath to convert it first:
from path import Path
Path("test.txt").abspath().parent

As I see it, the main use case comes from the abstraction of the path type which eases the use of the library while dealing with user inputs paths.
This would mean that one could work indifferently with absolute or relative paths.
The only thing that would change would be the display output.
Compare print(path.parent) to print(path.abspath().parent.relpath()).
The relative / absolute attribute is not intrinsic to the path, it is just a way to display it.
Suppose my working directory is /home/user/, then Path('file.txt') and Path('/home/usr/file.txt') represent the same file, why would their .parent be different?

I like the proposed concept in principle. Could it be made to work in the general case? What is the parent of "test.txt" is it "test.txt/.." or simply ""? Should parent assume the current path is a directory or does it even make sense to ask for a parent of a file? I feel uneasy calculating a parent relative to a working directory implicitly.
I guess the concept of a parent of a path doesn't feel well defined to me. If we could either cite or design a definition of a parent that is intuitive and meets the expectations of the OP, I could endorse it.

Perhaps something like this:
>>> Path("foo/bar").parent # Currently works
Path('foo')
>>> Path("foo/bar").parent.parent
Path('.')
>>> Path("foo").parent.parent
Path('..')
>>> Path("foo").parent.parent.parent
Path('../..')

Preferably, this would only be implemented on Path.parent and not Path.dirname.

After considering it more closely, perhaps it is a false good idea...
I looked a bit at what was being done in other implementations.

C++
Rust
Python

Python's documentation explictly states that "this is a purely lexical operation".
This is why the equivalent of Path("../..").parent returns Path("..") in the three listed languages.
Is it the desired behavior for path.py? Would Path("../../..") seem more logical?

At first I thought we could simply use an absolute path internally, but of course it is a bad idea (a relative path converted to absolute will be incorrect if initialized in a different folder).
I think my initial misunderstanding comes from the fact that some methods of a Path() object act on the real and "physical" path (the file on the hard drive), while others work only on the string of the path. Path "strings" and Path "files" are two different things, and we have to be careful about what the method or attribute we are using is doing.
The thing is that some properties like .ctime will translate a relative path automatically in order to retrieve the value, while .parent or .name will directly perform on the string. On the other hand, methods like .dirname() returns a result with respect to the string while most other methods are related to the pointed file.
While doing some research, I found two issues that were somehow related to what I am describing: https://github.com/jaraco/path.py/issues/26 and https://github.com/jaraco/path.py/issues/58.
My opinion on this: a property which works on the file itself will, at least implicitly, convert a relative path into an absolute path to retrieve the information it needs. This is an important context-dependent operation, and should therefore be a method rather than an attribute.
So, ctime would become ctime() and getctime() could be removed.
Quite conveniently, we could then have Path("../..").dirname == Path("..") and Path("../..").parent() == Path("../../..").
Sorry to get away from the initial problem, just sharing some thoughts.

It's also useful these days to reference pathlib, which seems to have settled on a similar concept, but uses object-oriented techniques to separate a "pure" path from a "concrete" path. I prefer that concept to using the method/property distinction, as it's conceivable (likely) that pure paths will have a use for methods (as is illustrated by the pathlib API).
I've mentioned in other places the desire to align with pathlib where that doesn't compromise the advantages path has over pathlib.

If the current path is /, what is Path(toto.txt).parent.parent ? Relative paths are harder to get right than absolute paths. Trying to play with .. may work in some cases, but it may be harder to manage when things break, because the behaviour will be less staightforward.

Hey @jaraco!
I'm not sure to understand what is "that" referring to in your question about the impact on my original use cases. For now, whenever I want to deal with the containing folder of a file, I have first to explicitly convert it to an absolute path before accessing its parent. If I forget to do so, sometimes it will work (if the file path is folder/file.txt), sometimes it will fail (if the file path is file.txt).
I have been thinking periodically to this issue since I opened it, but I still don't know what is the best way to handle this. I mean, sometimes operating on the string makes sense, other times it is much more convenient to obtain the "real" parent.
You are right that this is somehow similar to the PurePath() / Path() distinction made in pathlib, and I later realized that the method / attribute distinction I proposed was actually a terrible idea.
So, it looks I'm coming back to my first proposal. What about path.dirname() staying a lexical-only operation while path.parent() being equivalent to pathlib.Path(path).resolve().parent?

What about path.dirname() staying a lexical-only operation while path.parent() being equivalent to pathlib.Path(path).resolve().parent?

That might work. Does resolve() mean to resolve the path relative to the current working directory?
Why not always have path.parent() always return Path(path / '..') and leave it to the user to resolve that (or error if it represents an invalid path)?

Yeah, resolve() would actually convert a relative to absolute path, which is a side-effect probably not expected while calling .parent()...
Adding ".." to the path as you suggest is probably the best way to handle this, I considered it in the past but discarded it for a reason I can't remember now.
Note that using path like "somefile/.." (which would happen if we need the directory of a file path provided by the user) would often raise NotADirectoryError when used with functions like os.listdir().

Note that using path like "somefile/.." would often raise NotADirectoryError when used with functions like os.listdir().

That seems perfectly reasonable to me; if we define parent() as a lexical operation and there's no lexical operation to get the parent of a file, I'd expect .parent() of a file to cause some sort of error.

That seems perfectly reasonable to me; if we define parent() as a lexical operation and there's no lexical operation to get the parent of a file, I'd expect .parent() of a file to cause some sort of error.

Yeah, but in the end, it does not solve the initial issue, Path("test.txt").parent().makedirs_p() would still not work. Instead, Path("test.txt").parent().abspath().makedirs_p() should be used, which is very similar to the already existing solution Path("test.txt").abspath().parent.makedirs_p().
Is it better to replace the current .parent behavior from "remove /xyz from this end" to "add /.. to the end"? I don't know, at least it avoid the redundancy between .parent and .dirname, but I am not sure of which use case it solves.
My initial thoughts was about practicality.
If I receive a Path(), no matter if it an absolute or relative directory or file, I can get its parent and list what it contains without needing a safety call to .abspath().

As I revisit this issue, I realize that there's a fundamental ambiguity in Path('something'). You can't tell without more context whether that path refers to a file or a directory. And the meaning of "parent" is possibly different depending on the context.
In your primary use-case, you have that context. You know that Path("test.txt") is meant to be a filename, so Path("test.txt").parent should be a directory, but since it is blank, it doesn't represent a valid directory.
I do think it may be possible to achieve what you're after with something like this:
class Concrete(Path):
    def __new__(cls, orig, base=None):
        return super().__new__(cls, orig)

    def __init__(self, orig, base=None):
        super().__init__(orig)
        self.base = Path.getcwd() if base is None else base

    @property
    def parent(self):
        res = self.base / self / Path('..')
        return Concrete(self.base.relpathto(res), self.base)

The Concrete subclass stores the "base" - the location that makes this instance concrete... and then when computing the parent, does that relative to the base.
And at least for your use-case, this has the desired properties:
>>> cp = path.Concrete('test.txt')
>>> cp.parent
Concrete('.')
>>> cp.parent.parent
Concrete('..')

I'm worried this concept doesn't generalize well. I'm also fairly sure there are issues with other methods, as anything that invokes self._next_class() will have a base from Path.getcwd().
Perhaps that can be addressed with:
    def _next_class(self, val):
        return self.__class__(val, base=self.base)

I've pushed this code to the feature/concrete-path branch. Maybe have a peek and let me know what you think.

Hi @jaraco. Sorry for the late answer. I woke up this morning remembering about your comment I did not replied!
Thanks for revisiting this issue and taking the time to experiment new features.

As I revisit this issue, I realize that there's a fundamental ambiguity in Path('something'). You can't tell without more context whether that path refers to a file or a directory. And the meaning of "parent" is possibly different depending on the context.

I don't understand how is the meaning of "parent" related to something being a file or not. Whether something is a file or a directory, its parent can be defined as "the directory which contains something". What is the ambiguity I'm missing?
However, I do agree that the implementation may require to address several concerns which are discussed in this issue but to which I have no proper solution.
I think your suggestion  to use a Concrete() object is a good approach. Actually, in my initial use case, I expected Path("test.txt") to represent the test.txt file on my current working directory, so I expected getting the parent folder of this file to be straightforward. In reality, Path("test.txt") does not represent any concrete file until it has been explicitly resolved. I guess my initial expectations was to all Path() objects to actually be concrete paths.
In the end, I'm not sure it worth complicating path.py API with a new Concrete() type of path, especially as you raise concerns about possible edge cases which may break unexpectedly.

I don't understand how is the meaning of "parent" related to something being a file or not. Whether something is a file or a directory, its parent can be defined as "the directory which contains something". What is the ambiguity I'm missing?

As I read this now, almost a year later, I don't know what I was thinking at the time, but I agree with you, there does not seem to be any ambiguity.
In #194, I've added the proposal, basically unchanged from how I drafted it at the time of this discussion. Given that I've not had a use-case for this myself and that even the OP is not confident this behavior is needed, I'm going to suggest users interested in this feature try out a copy of Concrete locally. If it serves a useful purpose, please feel free to revisit this issue and report its usefulness (and any issues you might have encountered)... and this project will happily host it if it serves a need.


pull request for issue #96 m/s/ucliccfg

#96 – different priv modes may want different level/priority control.  mcliccfg, scliccfg, ucliccfg instead of single cliccfg.  Place at different byte offsets in case implementation wants to overlap m/s/u regions and control priv access in a method not using separate address ranges.
changed references to cliccfg to xcliccfg

Discussed some changes to this in the TG meeting 2021/9/28:
Current design

0x0000 xcliccfg
0x1000 per-interrupt bytes
One aperture per priv mode.
S-mode PMP NAPOT 0x0000-0x1FFF
Memory map for overlapping CLIC apertures, where assumption is bus
transactions carries privilege mode and CLIC interface modifies
behavior based on bus transaction privilege mode.

0x0000 M-mode aperture
0x0000 mcliccfg
...   (reserved, future M-mode config registers)
0x0400 HS-mode aperture
0x0400 hscliccfg
...
0x0800 S-mode aperture
0x0800 scliccfg
...
0x0C00 U-mode aperture
0x0C00 ucliccfg
...
0x1000 per-interrupt bytes (all modes)
...
S-mode PMP range  0x0800-0x1FFF (but intended for use with priv mode
on bus transactions)
Using shifted per-mode cfg with separate apertures:

0x0000 mcliccfg
0x1000 per-interrupt bytes (M-mode)

...
0x0400 HS-mode
0x1000 per-interrupt bytes (HS-mode)

...
0x0000-0x07FF reserved
0x0800 scliccfg
0x1000 per-interrupt bytes (S-mode)

...
0x0C00 ucliccfg
0x1000 per-interrupt bytes (U-mode)

Discussion was that allowing mode-specific difference in functionality at same address would be problematic in general, and even in this specific case.  For example, an M-mode routine trying to access S-mode register would have to know to use mstatus.mprv feature to change effective mode on access.  For more general case in other specifications, we've adopted policy of not having mode-specific functional differences on allowed accesses to the same address.

closing this.  created pull #183 instead.


Create logo for SIBCI

@fungs @pbelmann I've created a logo. It's an update from what I initially used which was just copied from nucleotid.es. Any feed back is welcome.

:+1:

I will close this issue as we now have a logo.


(site/cp/role/foreman) add dhcp static routes for yagan multus subnets

Broken out of #731 as these changes are already live and may be merged now to allow the summit foreman instance to be switched back to the production branch.


Surrealist depends on libwebkit2gtk-4.0-37, but its replaced by libwebkit2gtk-4.1-0

Describe the bug
Cant install or open the *.deb package of surrealist.
It will result in the error that there is no libwebkit2gtk-4.0-37 found (because Ubuntu 24.04 has libwebkit2gtk-4.1-0).
To Reproduce
Steps to reproduce the behavior:

Install Ubuntu 24.04
Download the 2.0.5-deb file from Releases
Install it
See error

Expected behavior
I can install it with the libwebkit2gtk-4.1-0 package.
Environment:
1. Ubuntu 24.04
2. Surrealist 2.0.5
3. Surreal 1.4.2

Same problem here. i found a possible workaround for now here.

temporary workaround that worked for me:
Install:

then install surrealist

Got it from:

temporary workaround that worked for me:
Install:
https://answers.launchpad.net/ubuntu/noble/amd64/libjavascriptcoregtk-4.0-18/2.43.3-1
https://answers.launchpad.net/ubuntu/noble/amd64/libwebkit2gtk-4.0-37/2.43.3-1
then install surrealist
https://github.com/surrealdb/surrealist/releases/download/surrealist-v2.0.5/surrealist_2.0.5_amd64.deb)
Got it from:
https://github.com/clash-verge-rev/clash-verge-rev/issues/866#issuecomment-2073876022

This should be fixed in the next release


Python3

Hi again Daniel,
So this is the Python 3 version I talked about on the other message, I mostly replaced the string formatting everywhere I could and the use of urllib/urllib2.
However I also made change on how the data is returned, I don't really understand why but tags and content of the note was returned as bytes. I just took out the code that did that, which is why on the screenshot below you will see the unicode test fail (also 2 note length tests, that fail because of login into simplenote.. My guess is that it happens kind of randomly because of fast multiple requests on the get_note_list method)

Bye!

Following on from what I said on #12 if we can figure out a version that is compatible for Python 2/3 you may then want to get involved in #11 as so far I've just targeted Python 2 there.

I did some digging but I can't use that API because I couldn't get a key and also for the app I'm working on (Sublime Text plugin) I can't have the key in the code exposed to everyone I think. :(

Yes, exactly, can't use it yet, because we are waiting for Simplenote/Simperium to roll it out properly. It's just something to be aware of.
The last I heard from Simperium was almost a year ago when they said "So on our end, we plan to allow users to grab a 3rd party API token from the Simplenote website (settings page)". Hasn't happened yet, obviously.
To test locally with the Simperium API you have to log onto the website and from the javascript console get the value of "simperium_opts['token']"

I will start looking at this now I've closed out #12. It'll probably take me a bit of time.

A couple of thoughts/comments:

I plan on comparing the results of running through 2to3 to the changes in this pull request
Since it's looking like only minor changes are required to get Python 3 compatibility, we could then manually adapt this to keep compatibility with Python 2.
But I might also look into using Six or Python-Future as a way of keeping one code base that is 2 and 3 compatible

Just to provide an update on this issue, I tried 2to3 and the results
weren't as good as what you provided on this pull request. So, working
with your pull request as a basis, I've been adding in changes to make
it also work under Python 2 again.
I've got all the tests passing under Python 2 and 3 apart from
Unicode/UTF-8 under Python 2. I'll have to go and add back in all that
encoding code for Python 2, but trying to do it in as nicely as I
possibly can since 3 doesn't need it.
I'll push what I have so far up to a new branch soon.

Just pushed up changes that bring the utf-8 encoding and decoding back
to Python 2. I actually don't mind the sys.version conditionals and
don't think it is too untidy.
At this point all tests pass under Python 2 and 3. Before I merge into
master I want to do the following though:

Run some manual checks to make sure everything is ok, perhaps extend
test suite if necessary
Look into is_utf-8 in test_simplenote.py to see if I can do things
a better way for Python 3
Look into using codecs library as an alternative to using decode
on response.read().decode('utf-8') for Python 3. Might be a bit
cleaner, might not make any real difference though.

Will probably be another week or so until I get around to doing all
that.

Further update. Did some manual testing, looks good to me. I think
mainly I just want to look at using the codecs library now before we
can start thinking about merging this in.

I looked into improving the is_utf8 check for Python 3, but couldn't
think of a better way than just comparing the strings.
I looked into using the codecs library instead of .decode('utf-8'),
but couldn't get it to work (and as far as I'd got wasn't any tidier).
So I think this is pretty much good to merge in. However, I'll leave
it another week before doing that just to give others a chance to give
things a look over, etc, if they want to.

Right, this is closed out and merged in now. As suspected the builds
half failed on Travis. I'm pretty sure it is because it tried to run
Python 2 and 3 concurrently. However, as long as one passes it still
deploys to PyPi (I suppose that's ok).
However, since then I've found the concurrency setting on Travis which
should fix this problem in the future.


validate package url to sanitize %7E

This is basically a reminder to myself. Will likely provide a PR for it.
I had a mistake in my class config with a package url including a %7E for ~, as I copy'n'pasted the link from Firefox into Hiera.
This lead to strange "already installed" errors for the package. Validating the URL before using it for the package name or validating the package name to include correct chars should beware people from falling in this pitfall.

Module transitioned to here:  https://github.com/vshn/puppet-gitlab


Cart, Product, Single Product done Orders ongoing

Cart page done - It cannot be refreshed when refreshed it would crash
Product page and Single Product page - UI changes
Order - Model created

I will review this when I get help articles done


Customizing compact picker

How can we keep just a few colors and remove the rest. If we can do customization like that, would be awesome. Great work!

Ditto, need to be able to set swatches up for this one to be workable.

we did this:
<compact-picker :palette="palette" :value="colors" @input="updateValue" />
and then:
private palette = ['#B0BC00', '#68BC00', '#16A5A5', '#009CE0', '#7B64FF', '#FA28FF'];


Syncthing translations not working

The chromium instance does not pass the correct accept-language header to show the translated syncthing UI.

Fantastic, thanks!
There's an errant commit at the start of this PR, but I'll rebase that out

Oh my, not my best GIT days ;) Need to clean my fork.


cmd/compile: improve error message to suggest that perhaps builtin is missing variable declaration

Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (go version)?
$ /home/mh-cbon/.gvm/gos/go1.8/bin/go version
go version go1.8 linux/amd64
$ /home/mh-cbon/.gvm/gos/go1.8/bin/go env
GOARCH="amd64"
GOBIN="/home/mh-cbon/gow/bin"
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/mh-cbon/gow"
GORACE=""
GOROOT="/home/mh-cbon/.gvm/gos/go1.8"
GOTOOLDIR="/home/mh-cbon/.gvm/gos/go1.8/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build249841147=/tmp/go-build -gno-record-gcc-switches"
CXX="g++"
CGO_ENABLED="1"
PKG_CONFIG="pkg-config"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
What did you do?
wrote,
expr, err := I.ReadExpressionBlock(templated, glanglexer.NlToken, close)

and ran
go run main.go
# github.com/mh-cbon/gigo/interpreter/glang
interpreter/glang/glang.go:802: use of builtin close not in function call
interpreter/glang/glang.go:830: use of builtin close not in function call
interpreter/glang/glang.go:1274: ret.Init undefined (type *"github.com/mh-cbon/gigo/struct/glang".BranchedStmtBlock has no field or method Init)
interpreter/glang/glang.go:1282: ret.Body undefined (type *"github.com/mh-cbon/gigo/struct/glang".BranchedStmtBlock has no field or method Body)
interpreter/glang/glang.go:1284: undefined: Body

What did you expect to see?
That the type checker detect the use of a reserved keyword into
that call expression and assume it is either,

a missing variable declaration of close
use of builtin close not in function call

thus,
use of builtin close not in function call, or missing variable declaration of <close>

It happened because i copy pasted code and forgot to duplicate the close var declaration.
What did you see instead?
I got a message that can be improved,
use of builtin close not in function call

/cc @griesemer @mdempsky
I wonder though if this suggestion's effect heads towards the slippery slope that was raised in https://github.com/golang/go/issues/4697's CL https://go-review.googlesource.com/c/37392.

I don't think or missing variable declaration of <close> makes the error message easier to understand. The fact that close resolved to the builtin definition implies there weren't any shadowing declarations. If the user expected it to refer to something else, it should be obvious that it didn't.

Thanks for taking the time to file an issue. I agree with @mdempsky on this; going to close as "won't fix".


Remove empty paths

Codecov Report

Merging #11 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master      #11   +/-   ##
=======================================
  Coverage   78.42%   78.42%
=======================================
  Files          17       17
  Lines         570      570
=======================================
  Hits          447      447
  Misses        123      123

Impacted Files
Coverage Δ

lib/support/osx.js
80.24% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Get Lane County Zip Code boundaries and update task that loads them

For setup instructions look at README.Docker.md. Once we have complete local environment setup instructions (a few tickets need to be finishing) we will update README.md.

Zip Code boundaries appear to be loaded with a rake task. Try running the task with docker-compose run frontend rake populate_zip_boundaries. It looks like the project was using data.washingtonpost.com to get boundaries and other attributes, the service appears to no longer work. Confirm it no longer works and check if it's an easy fix. Otherwise, locate a source for the Zip Code boundaries (check with Matt Sayre, he was talking to County/City, or find a free source online) and update the task to load from the file. Host the file somewhere (S3, Dropbox, Google Drive), we will sort out final location later. Update README.Docker.md with instructions for downloading and loading the data.
The boundary data loaded in the database appears to be an array of lat+long pairs and should look like [[lat1,long1],[lat2,long2],...,[latN, longN]]. See the code and DB schema for more details.

Chris from M-Lab mentioned that County and Zip boundaries are available in a BigQuery dataset.


Fix mistypes

 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.:x: laimonas sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Sorry, but we are not accepting PRs across different feature areas or across the whole code base. See https://github.com/microsoft/vscode/wiki/How-to-Contribute#pull-requests for guidance. Thanks and Happy Coding.


Setting native window position

Is your feature request related to a problem? Please describe.

I need to be able to set the window position of the window.
Describe the solution you'd like

Adding a window_position field of type Vec2 to the NativeOptions struct should be enough.

Sounds good! PR welcome.
(It should be Pos2 rather than Vec2 though)

NativeOptions has an initial_window_pos, but I'll keep this issue open for adding a epi::Frame::set_window_pos too (for changing window position at runtime).


AMPI should check for truncated messages

Original issue: https://charm.cs.illinois.edu/redmine/issues/1159

tests/ampi/mpich-test/pt2pt/trunc fails because AMPI doesn't check for truncation on recv at all right now.
Add a check for it and return MPI_ERR_TRUNCATE, probably in processMessage and the likes of it.

Original date: 2016-08-11 22:34:08

For now, just abort on recv'ing a message larger than the matching recvbuf from ampi::processMessage. the mpich-test/pt2pt/trunc test now aborts accordingly.
~~https://charm.cs.illinois.edu/gerrit/#/c/1354/~~ https://github.com/UIUC-PPL/charm/commit/e8d65db08c5c600550b924256d07ee7fdf867091
To implement full support for this we'd have to:

Make ampi::processMessage return MPI_SUCCESS or MPI_ERROR_TRUNCATE based on msg->length and recvbuf len.
Return the right errcode from blocking routines.
Set the 'MPI_ERROR' field in the status object passed in to all nonblocking communication completion routines (Test*, Wait*).
Expand the error handling in the completion routines to support MPI_ERR_IN_STATUS.


Screenshot sometimes gets stuck at getting screenshot

Screenshot works but sometimes it gets stuck at Getting Screenshot and I can't use it.I have to close the terminal and re-execute the (.exe) on the victim pc to get it work again.

Hello,
A know issue is the screenshot crash if the screen is locked.
I corrected a process on screenshot that leaves the payload busy by a moment on victim side.
If you maybe can clone CHAOS again and test it.
Check in what situation the payload crash, if the system are suspended, screen locked or something like that.

@tiagorlampert Thanks for your reply.I'll reclone and try again tomorrow and report back.I'll attach screenshot here if the payload will crash again.

It worked 2 times as in the screenshot but third time it gets stuck.On victim side is watching a youtube video.

I did test here and it worked more than two times. I really don't know what can be happening on your machine. Probably it should be taking longer than normal to take and send the screenshot.

It's random.Sometimes it's stuck after taking more than 2 screenshots.

Hello,
This issue is very old. Could you try again with the new version, and send me a feedback?

@tiagorlampert Okay I'll try in a few days and report back.

I'm closing this old issue.
If the problem persist, please open a new issue.


Fix storageClass name passed to configMap Get

/cherry-pick oadp-1.2

We are updating the storageclass parameter to be used for fetching the datamover volume options configmap from VSB Status to source PVC spec. This change was needed because there might be boundary cases when the VSB status is yet to have storageclass name and the configmap comes out to be nil, in such cases the mirrored PVC will not use the intended storageclass from volume options mapping and it will end up using the incorrect one.


Previously entered data is populating fields when New Additional Documents

@bferguso - can you clarify whether this is an Arches core bug or not?
When adding additional documents to a record, the new records include information from the previous document submitted (displayed document type and text in Document Description) instead of being blank. User has to remove old data before including new data.
Steps to reproduce

Go to heritage site resource model
Go to documents section
Upload first document completing the document type and document description field
Click "Add New" top right corner

Actual Results
New document card opens and includes data from previous record entered
Expected Results
New document card should open and fields should be blank

Closing issue because can't be replicated and not noticing issue now. Likely Arches core randomness.


Database trouble with AJAX requests

I have a form to create a new Address. The form includes the id of the parent model (in this case a Customer) that owns the Address. When submitting the form the AJAX request goes to the AddressesController which responds with JavaScript. The problem is that sometimes, the parent model is sometimes found and sometimes not.
This works in RSpec:
before do
    click_link add_address
    fill_in country_field, with: country
    fill_in city_field, with: city
    fill_in street_field, with: street
    fill_in postal_code_field, with: postal_code
    click_button submit_address
    expect(page.title).to eq(show_page_title)
end

it { is_expected.to have_content(address_created) }

But when I move the expect(page.title).to eq(show_page_title) from the before-statement to an own test (which of course is better):
it { is_expected.to have_title(show_page_title) }
it { is_expected.to have_content(address_created) }

I get the following error:
ActiveRecord::RecordNotFound:
  Couldn't find Customer with 'id'=1

If I add puts Customer.count last in the before-statement as well as in the AddressesController where the request is received, I get 1 from the line in the before-statement but 0 from the controller! How is this possible?

Seams that Automatically wait for ajax with Capybara solved my problem, though I'm not sure why. In my opinion, that should not affect the database...

I can now confirm that the solution above solved my problem. I'm not sure why because the Customer should be created before the tests are run since I create it with a let!(:customer) { FactoryGirl.create(:customer) } statement.

Solution available above.


chore(ENG-884): add semantic release into project

Description

Add semantic release into the Github Actions

Issue(s)
ENG-884
How to test
npx semantic-release -d -b 'ENG-884' --debug

Checklist

[ ] Add Github Token to project secrets

:tada: This issue has been resolved in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


508 Issues from pa11y-rails

Results can be recreated using HTML_CodeSniffer
Results for https://pages.18f.gov/agile/

Error This element has insufficient contrast at this conformance level. Expected a contrast ratio of at least 4.5:1, but text in this element has a contrast ratio of 3.95:1. Recommendation: change text colour to #0069be.

WCAG2AA.Principle1.Guideline1_4.1_4_3.G18.Fail
#repositories > ul > li:nth-child(2) > a > h4

agile

Error This element has insufficient contrast at this conformance level. Expected a contrast ratio of at least 4.5:1, but text in this element has a contrast ratio of 3.95:1. Recommendation: change text colour to #0069be.

WCAG2AA.Principle1.Guideline1_4.1_4_3.G18.Fail
#repositories > ul > li:nth-child(2) > a > p

Main repository

Summary
Errors: 2

Checking with #g-accessibility to confirm the latest audit I ran confirms these have been addressed.
One item that is also needed is an update to the logo https://github.com/18F/agile/pull/45.
I suspect it doesn't show up in the scan because it's an image file.  Though the image itself (being a text based image) is the old logo (which wasn't compliant).

Note: the audit was run using the Accessibility Developer Tools in Chrome, not the HTML-Codesniffer used to originally submit the issue.

@porta-antiporta since we've addressed the logo issue and moved to the new template, I think we can close this up. How does that sound to you?


[Usage] mm_projector weights go to inf

Describe the issue
Issue:
Hey there - huge fan of your work.
I'm trying to integrate LLaVa into a training framework I've been running into the same issue again and again. When I try to train LLaVa outside of your framework (i.e. by loading it and passing it through my own training loop) something breaks and I get nan loss.
I've managed to isolate the issue to the mm_projector weights, which go to inf after the first training step. This doesn't seem to be an issue with exploding gradients since the grad norm stays low (<10) and the issue persists even with tiny learning rates (<1e-5).
Command:
debug.py:
from llava.model.builder import load_pretrained_model
import numpy as np
import torch

# Load the model
tokenizer, model, image_processor, context_len  = load_pretrained_model("liuhaotian/llava-llama-2-7b-chat-lightning-lora-preview",
                                                                            model_base = "meta-llama/Llama-2-7b-chat-hf",
                                                                            model_name = "llava-llama-2-7b-chat-lightning-lora-preview")
# Unfreeze the mm projector
for p in model.get_model().mm_projector.parameters():
    p.requires_grad = True

optimizer = torch.optim.Adam(model.parameters(), lr=1e-3)
for i in range(10):

    optimizer.zero_grad()

    # Dummmy inputs
    imtensors = [np.random.rand(256,256,3)]
    input_images = image_processor(imtensors, return_tensors="pt",
                                            ).pixel_values
    input_images = torch.tensor(input_images).to(model.device).type(model.dtype)

    inputs = tokenizer(["This is a test"], return_tensors="pt").input_ids.to(model.device)

    results = model(input_ids = inputs, labels=inputs, images = input_images)
    print(f"Loss: {results.loss}")

    results.loss.backward()
    optimizer.step()

conda activate llava
python debug.py
Log:
Loss: 4.4296875
Loss: nan
Loss: nan
Loss: nan
Loss: nan
Loss: nan
Loss: nan
Loss: nan
Loss: nan
Loss: nan

Any ideas as to why this might be happening?

@haotian-liu I'm sure you're very busy with all these issues, I'm still struggling with this and it would mean a lot if you could take a look - even just to point me in a new direction. My advisor has been asking lots of questions about it and it's been hard to make progress :(

Thank you for your interest in LLaVA, and sorry for the delayed response.
You would probably need to set model.to(dtype=torch.bfloat16) or model.to(dtype=torch.float32), as float16 may have gradient overflow.

That seems to have done the trick. Thank you!