Having a slash inside a lookup seems to cause infinite recursion

While working in the ${file...} lookup, I discovered that having a slash inside the lookup, such as:
${file parameterized-b64:file://userdata.txt}
causes infinite recursion in Variable.resolve, on line 118 (while self.lookups). Simply removing the slashes in the path above avoids the problem.
I haven't looked into the root cause yet.

I'm taking a guess, but it's likely due to this line: https://github.com/remind101/stacker/blob/master/stacker/variables.py#L11 - you might need to include \/ in the idpattern.  @mhahn will know best.

@phobologic indeed, that fixes it. I'll put in a simple PR just for that fix right now.


Add IoC \ TinyIoc

IoC \ TinyIoc https://github.com/grumpydev/TinyIoC
An easy to use, hassle free, Inversion of Control Container for small projects, libraries and beginners alike. Single file!

We just removed this because this is no longer supported.

So from this he did not stop working. I use this because there are no external relocations, just one file and easy use

I also use this extensively

Looks like it's not maintained anymore. I've used this a few times too.
@grumpydev say it isn't so?

Any full real world samples using It?
El 11/09/2017 15:46, "SlowLogicBoy"<EMAIL_ADDRESS>escribió:

I also use this extensively
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/quozd/awesome-dotnet/pull/567#issuecomment-328533816,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABJYDc2tPi4sFbDfXBJxIEr8j62IrsZhks5shTmygaJpZM4PTDe_
.

TinyIOC can be used in PCL and Xamarin.

Nancy uses TinyIoC as default IoC container

Its not abandoned no, it's actively used as Nancy's default container for one. There are a few reasons it hasn't been updated for a while. Firstly, the last year or so, for various personal and professional reasons, I've had very little time for OSS work. Secondly, the version in Nancy I think has diverged from the version in the main repo, so I need to consolidate before I do much more work on it, and finally I have (thankfully I think) managed to avoid any of the .net core/standard/vnext stuff so far, and the main "issues" I see discussed are all around that, although Nancy itself supports netstandard with TinyIoC inside, so I think that issue is "ok", but referring back to the previous point.
After the consolidation I intend to work on the way the child containers work, as currently you have to make registrations directly in the child container, rather than being able to specify a "child lifetime" on the parent container (which would be more efficient and less code for the consumers).

@grumpydev sounds awesome. And, thanks for the update.


StreamsBuilderFactoryBean#start blocks Spring application startup with large global stores

Affects Version(s):  All
StreamsBuilderFactoryBean#start calls the KafkaStreams instance's start() method directly on the main thread. This is usually no problem as KafkaStreams#start to be mostly non-blocking. However, the method does block until all global state stores have been fully restored:
https://issues.apache.org/jira/browse/KAFKA-7380
This means that if the Kafka Streams application has large global state stores, StreamsBuilderFactoryBean#start may block the Spring application startup for several minutes. In our case, not even Netty and Actuator is started in this timeframe, which leads to our application being repeatedly killed by our Kubernetes cluster because the liveness probe is not reachable.
Perhaps Spring Kafka could work around this issue by running KafkaStreams#start in a separate thread.

We may reconsider the behavior as you suggest, but of course better to have a normal fix from the upstream Kafka Streams library.
Meanwhile as a workaround I would suggest to have that StreamsBuilderFactoryBean in a setAutoStartup(false) in the config and call its start manually somewhere later when an application is ready already, e.g. listening for the ApplicationReadyEvent or implement an ApplicationRunner instead. This way those liveness probes should be OK and you may control what thread to use to start that StreamsBuilderFactoryBean on background.

Specifically, with Spring Boot:
spring.kafka.streams.auto-startup=false

@Bean
public ApplicationRunner runner1(StreamsBuilderFactoryBean sbfb) {
	return args -> {
		sbfb.start();
	};
}

Hi,
Thank you for the suggested workaround. Unfortunately, we don't use Spring Kafka directly, but via Spring Cloud Stream, which calls start() of each StreamsBuilderFactoryBean on its own and doesn't seem to offer any customization on this matter.

With the other binders, you could set the binding autoStartup property to false and start the binding manually from your code but, unfortunately, the Kafka Streams binder does not currently support the autoStartup property.
cc/ @sobychacko

StreamsBuilderFactoryBeans are unconditionally started in StreamsBuilderFactoryManager.start().

https://github.com/spring-cloud/spring-cloud-stream-binder-kafka/issues/1126

@garyrussell Shall we close this issue since the binder issue is already addressed?


Fix testutils featkey

Codecov Report
Attention: Patch coverage is 0% with 15 lines in your changes are missing coverage. Please review.

Project coverage is 61.67%. Comparing base (376bdc0) to head (c7d56b2).

Files
Patch %
Lines

testutils/containers.go
0.00%
15 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #15      +/-   ##
==========================================
- Coverage   61.98%   61.67%   -0.31%
==========================================
  Files          16       16
  Lines         997     1002       +5
==========================================
  Hits          618      618
- Misses        359      364       +5
  Partials       20       20

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


calculate scrollbar width correctly

Fixes #64
Scrollbar width is still calculated repeatedly; once for every component.

I don't have internet access on our Windows VM for testing IE, so I can't verify this, but my best guess is that the new jQuery version calculates .width() and .innerWidth() differently, as they both seem to exclude the scrollbar width. I changed the logic a bit and now it should work regardless of the version used.

I improved the logic even more. We now don't even need to sniff for Firefox.

The scrollbar thickness is now mesaured once in a service and cached from there on.

@buschtoens can you resolve conflicts and fix any failing test cases?

Yeppa. Did this as the last thing before going home. 😅
I'll fix this as the first thing tomorrow. :)

@offirgolan Ready for your eyes. :eyes:
I'm tempted to say that this one failing test actually isn't this PR's fault.

This is the only test failing and only for the ember-release scenario.
https://travis-ci.org/alphasights/ember-scrollable/jobs/214383533#L921-L931
not ok 31 Chrome 57.0 - Integration | Component | scroll content element: Horizontal: Initial offset triggers a scroll event
    ---
        expected: >
            Max depth.,Max depth.
        stack: >
                at Object.<anonymous> (http://localhost:7357/assets/tests.js:532:14)
                at fn (http://localhost:7357/assets/vendor.js:11483:18)
                at invokeWithOnError (http://localhost:7357/assets/vendor.js:10914:16)
                at Queue.flush (http://localhost:7357/assets/vendor.js:10973:9)
                at DeferredActionQueues.flush (http://localhost:7357/assets/vendor.js:11097:15)
                at Backburner.end (http://localhost:7357/assets/vendor.js:11167:23)

I'll see if I can replicate this locally.

The test results appear to be pretty inconsistent. When I run yarn test the tests run in Chrome and randomly fail. :worried:
The test in question is:
not ok 22 Chrome 57.0 - Integration | Component | ember scrollbar: Horizontal: onJumpTo first argument is true when click to the left of handle
    ---
        actual: >
            false
        expected: >
            true
        stack: >
                at Object.<anonymous> (http://localhost:7357/assets/tests.js:329:14)
                at Backburner.join (http://localhost:7357/assets/vendor.js:20057:31)
                at Function.run$1.join (http://localhost:7357/assets/vendor.js:39007:28)
                at http://localhost:7357/assets/vendor.js:29015:37
                at flaggedInstrument (http://localhost:7357/assets/vendor.js:38434:14)
                at http://localhost:7357/assets/vendor.js:29014:48
        message: >
            towardsAnchor should be true if going towards anchor
        Log: |
    ...

Ironically, the test case that failed in Travis, never fails locally.

Running the tests manually in Chrome succeeds consistently. I guess this is some very unfortunate race condition.

@buschtoens  do we need to update https://github.com/alphasights/ember-scrollable/blob/master/tests/integration/components/ember-scrollbar-test.js#L169 ?

@buschtoens do we need to update https://github.com/alphasights/ember-scrollable/blob/master/tests/integration/components/ember-scrollbar-test.js#L169 ?

I don't think so. At least the current setup seems to work for Firefox, Chrome and surprisingly IE as well.
However...
Running tests manually in Firefox, it fails consistently for a different case. But it does so on master as well. So that's a different issue (#66).
Acceptance | ember-scrollbar: When element resized from no-overflow => overflow => no-overflow, no scrollbar is visible on mouseover (3, 4, 7)

> there is no overflow as 18 < 200px
  Expected: 18
  Result: 19

> there is overflow as 494 > 200px@ 1247 ms
  Expected: 494
  Result: 509

> failed
  Expected: 18
  Result: 19

Running tests in IE is a different nightmare: #77

After applying #68, there are no new failing test cases in IE compared to master, or #68 for that matter.

Rebased on the current master. All tests pass now (on Travis).
Before that I accidentally rebased onto my own origin/master instead of upstream/master and the tests still passed on Travis. So it was a random fail / race condition after all.

*sigh... The struggles of web dev.

@buschtoens do we still need the includePolyfill option? I thought the last merged PR solved that issue.

@offirgolan of course you're correct. I forgot to remove the commit. 🙈
I'm currently commuting to work. I'll remove it, when I'm there. 😉

Commit removed and tests still pass. :white_check_mark: :grin:

@buschtoens awesome job! Thanks for seeing this through! 😄


Add utilize eye in hand calibration sample

Add new sample in C# similar to the one we have in C++ (https://github.com/zivid/zivid-cpp-samples/blob/master/source/Applications/Advanced/HandEyeCalibration/UtilizeEyeInHandCalibration/UtilizeEyeInHandCalibration.cpp)
Im not sure if I added the dependencies correctly. Now they are inside the folder "Packages" in the sample folder...

Did you accidentally add a lot of build artifacts here?

Did you accidentally add a lot of build artifacts here?

I was not sure about what to do with the build artifacts (the entire packages folder actually), so I thought it was better to add it and then remove it than the other way around. This is the first sample in C# where we depend on some third-party libraries.

I was not sure about what to do with the build artifacts (the entire packages folder actually), so I thought it was better to add it and then remove it than the other way around. This is the first sample in C# where we depend on some third-party libraries.

Adding these to the repo sounds like the wrong approach. Did you consider using a pacakge manager such as nuget?

I was not sure about what to do with the build artifacts (the entire packages folder actually), so I thought it was better to add it and then remove it than the other way around. This is the first sample in C# where we depend on some third-party libraries.

Adding these to the repo sounds like the wrong approach. Did you consider using a package manager such as nuget?

Yes, I will write how to install the two packages (using nugget) in the readme. This way I dont need any of the artifact dependencies

Ready for next round!

 Ready for next round

Looks good to me @chrisasc
I would squash into one commit called 'Add __ sample and move __ sample'.
Have you double checked that it works well?

Looks good to me @chrisasc
I would squash into one commit called 'Add __ sample and move __ sample'.
Have you double checked that it works well?

I separated them into two commits because of Anders comments; "I also suggest you make one separate commit for moving the old sample and one for adding the new one. It makes it easier to see what's going on when you aren't doing two things at the same time."
but i can squash them together.
I've tested them and they work on my computer

Looks good to me @chrisasc
I would squash into one commit called 'Add __ sample and move __ sample'.
Have you double checked that it works well?

I separated them into two commits because of Anders comments; "I also suggest you make one separate commit for moving the old sample and one for adding the new one. It makes it easier to see what's going on when you aren't doing two things at the same time."
but i can squash them together.
I've tested them and they work on my computer

I see. Having two commits works just as fine. However, in that case I would not have this third commit 'Update main readme and add hand-eye folder readme' but rather have those (appropriate) code changes in the first two commits.
The point is that each commit does one complete change. As you have it now, the third commit is just something that should have been done in the first too.

I see. Having two commits works just as fine. However, in that case I would not have this third commit 'Update main readme and add hand-eye folder readme' but rather have those (appropriate) code changes in the first two commits.
The point is that each commit does one complete change. As you have it now, the third commit is just something that should have been done in the first too.

That makes sense, I squashed the readme and add UtilizeH... into one commit.

There's one commit that says "Move HandEyeCalibration sample to new folder" but also does some seemingly unrelated updates to the README. I suggest splitting this one in two.

I think there's something wrong in the sample data. I've installed the sample data according to https://zivid.atlassian.net/wiki/spaces/ZividKB/pages/450363393/Sample+Data. When I try to run the sample, I get this error message:
Reading camera pose in end-effector frame (result of eye-in-hand calibration)
Reading end-effector pose in robot base frame
Error: (Line: 1, Col: 1, Idx: 0) - (Line: 1, Col: 6, Idx: 5): While scanning a directive, found unexpected non-alphabetical character.
Press any key to continue . . .

The exception happens the first time I reach yaml.Load(reader); in readTransform.  The transformFile argument is C:\ProgramData/Zivid/EyeInHandTransform.yaml, and the content of that file is
%YAML:1.0
---
PoseState: !!opencv-matrix
   rows: 4
   cols: 4
   dt: f
   data: [ -1.52643966e-02, -9.99315023e-01, 3.37116420e-02,
       -2.68839798e+01, -9.65478182e-01, 5.96248358e-03, -2.60415733e-01,
       6.69086380e+01, 2.60036349e-01, -3.65229435e-02, -9.64907885e-01,
       -3.33924942e+01, 0., 0., 0., 1. ]

I don't know much about yaml, but when I try to paste that into http://www.yamllint.com/, it says the file is not valid yaml.
Does this work on your machine at all?

I think there's something wrong in the sample data. I've installed the sample data according to https://zivid.atlassian.net/wiki/spaces/ZividKB/pages/450363393/Sample+Data. When I try to run the sample, I get this error message:
Reading camera pose in end-effector frame (result of eye-in-hand calibration)
Reading end-effector pose in robot base frame
Error: (Line: 1, Col: 1, Idx: 0) - (Line: 1, Col: 6, Idx: 5): While scanning a directive, found unexpected non-alphabetical character.
Press any key to continue . . .

The exception happens the first time I reach yaml.Load(reader); in readTransform. The transformFile argument is C:\ProgramData/Zivid/EyeInHandTransform.yaml, and the content of that file is
%YAML:1.0
---
PoseState: !!opencv-matrix
   rows: 4
   cols: 4
   dt: f
   data: [ -1.52643966e-02, -9.99315023e-01, 3.37116420e-02,
       -2.68839798e+01, -9.65478182e-01, 5.96248358e-03, -2.60415733e-01,
       6.69086380e+01, 2.60036349e-01, -3.65229435e-02, -9.64907885e-01,
       -3.33924942e+01, 0., 0., 0., 1. ]

I don't know much about yaml, but when I try to paste that into http://www.yamllint.com/, it says the file is not valid yaml.
Does this work on your machine at all?

It says that it is not valid because of the ":".
I did some digging on this. I was not able to read the yaml file either (saw that I had modified it a bit locally). The reason is that yamlDotNet supports Yaml v1.1 and v1.2, but not v.1.0. In v.1.0 the correct syntax is "%YAML: 1.0", while in the newer versions its "%YAML 1.1" (without the :).
I also found out that OpenCV uses v1.1 when creating .yaml files. That is why all of our robot-related .yaml files start with

%YAML:1.0

OpenCV saves files as 1.0, but it can read yaml files from of all versions.
YamlDotNet can only read 1.1 and 1.2 yaml files.

Ready for next round.

Ready for next round.

The first commit says "Restructure: Move HandEyeCalibration sample to new folder". It seems it doesn't move the sample though, but duplicates it. It also introduces a README file which is not mentioned in the commit message, and which describes a new UtilizeEyeInHandCalibration sample which does not exist yet in that commit.
Can you please fix this and force push? Then ping me so I can get started on the proper review (a force push in the middle of a review is often cumbersome, so I'd rather wait with the details to after the force push).

Back to this PR again!
Changes since the last review:

Updated the code so that it accepts both versions of YAML files. (Same as how Robert does it in https://github.com/zivid/zivid-csharp-samples/pull/34).
Updated links to our new KB.
Fixed commit messages so that the first one only moves the existing HE sample and the second commit adds this new same.

Ready for another round of review. The sample has been tested on Windows 10 with VS 2019.

I'm not much involved in samples these days, so I'll leave it up to someone from @zivid/customer-success to approve of what the sample does and how it does it, how it fits in the big picture, what the documentation is like etc. I added a few tiny comments, but otherwise this seems good from my point of view now. There's an unrelated update to README.md which could have been a separate commit, but I guess it's unlikely that we'll revert this anyway so I don't really mind it.
I have not tested this again since last time btw, so someone in @zivid/customer-success other than @chrisasc should probably do that.

I'm not much involved in samples these days, so I'll leave it up to someone from @zivid/customer-success to approve of what the sample does and how it does it, how it fits in the big picture, what the documentation is like etc. I added a few tiny comments, but otherwise this seems good from my point of view now. There's an unrelated update to README.md which could have been a separate commit, but I guess it's unlikely that we'll revert this anyway so I don't really mind it.
I have not tested this again since last time btw, so someone in @zivid/customer-success other than @chrisasc should probably do that.

I have reviewed it and it looks good to me. I added a small fixup commit to fix the build path. Rebase, squash, merge @chrisasc


Support tests cases against SLES15

Update code to support SLES15
Update code to skip some cases against SLES15

@LiliDeng @juhlee-microsoft I just realized that this exclusion based on distro will not be fully accurate.
Consider that other kernels might be install on top of SLES15, so the modules might differ built-in vs external.
Adding a case for SLES15 to skip the entire test will not give accurate results when using any other kernel on it.
Please check this method that we've used in other scripts to better handle this situation:
https://github.com/LIS/LISAv2/blob/ebab176c3e65997cca3eec6bfc15304e80b36cfd/Testscripts/Linux/BVT-CORE-VERIFY-LIS-MODULES-VERSION.sh#L45

you need to solve the conflicts before merge

@juhlee-microsoft @lizzha fix code based on comments. also fix an issue which bring in by latest commit for case BVT-CORE-TIME-CLOCKSOURCE.
@ader1990 Thanks for review, and I solved the conflicts.


Intro to Arrays

Description
Inside arrays folder create a doc named Intro_to_Arrays.md.
Add syntax to declare an array in your preferred languages. Add examples as well.
Programming language

[ ] C
[ ] C++
[ ] Java
[ ] Python

Are you contributing under any open-source program ?

Hacktoberfest

Would love to get assigned to this task @siddhi-244

Sure. Please take care of the folder structure. Happy contributing !🎊🎊🎊🎊🎊

I am participating in hacktoberfest and new to open source. Can you assign any issue please

I am participating in hacktoberfest and new to open source. Can you assign any issue please

It's already assigned.  You can create a new issue.


Not working with gunicorn + gevent workers

I'm trying to use the threading_timeoutable decorator on a function.
It works if I run the script directly, but doesn't work when running via gunicorn using gevent workers.
Any ideas on making it work?

Hi @anshulk , the theading part of stopit is designed for standard CPython threading inners.
I'm not familiar with gevent plumbing, but I suspect you should tailor the async_raise function to the inners of gunicorn/gevent. AFAIK gevent monkey patches lots of Python stdlib low level APIs.

Hi @anshulk , I  have still no fix for this issue. As long as there's no PR that fixes this, I'll mention this in a "known issues" section of the doc, and close this.

This also seems to affect gunicorn's sync workers, not just gevent workers.

Thanks @jrial , I'll mention this too.
Any PR that fixes this bug or test case that shows it is welcome.


Curious about curling json outputs from SCREEN and feeding them back into the API.

Hello,
Super happy with the database that you have put together. This is an awesome resource for researchers.
So from some experiments in my lab I have a list of DMRs from DNA methylation data and I wanna use SCREEN to search for all the cCRE in these regions as part of my analysis.
I could go through and search each one using the browser GUI one-by-one but that's tedious and I'm a coder so I know there is a better way.
I wanna iterate through my DMRs and curl out the cCREs in each region as well are information like if the mark is proximal or distal and if other epigenetic modifications are above that ~1.6 cutoff and are enriched for that cCRE.

Is this going in the right direction for the output that I'm trying to get? Do you have any resources for people trying to scrape the SCREEN database and the best way to do that?
Also, after I pull out all of cCREs Accession numbers, I wanna start running them through your API.
https://api.wenglab.org/screen_graphql/graphql
Could you send over any resources/manuals for using that API so I can read through them and get a better idea of how to write my scripts and what kind of outputs I can get if I convert my DMRS into a list of accession EM**********s ?
Thanks!

 [weng-lab/SCREEN] Curious about curling json outputs from SCREEN and feeding them back into the API. (Issue #139)

 [weng-lab/SCREEN] Curious about curling json outputs from SCREEN and feeding them back into the API. (issue #139)


Provide an option to show last typed character briefly in TextField when obscureText is true on IOS

Use case
I have a flutter app with a password textfield
TextFormField(
  obscureText: true,
)

I run the app on Android, the password is obscured, it shows the last letter for a while, like this

But when running the app on iOS, the last letter is hidden immediately so user can't see the last letter. However, I want it to be displayed last letter in the same way on Android.
Proposal
I have no ideals

Im facing with the same issue, How can i do it ?

Thanks for filing this issue. There seems to be an issue currently open that describes this issue. Kindly upvote and follow up on this issue for updates. Closing this as a duplicate of https://github.com/flutter/flutter/issues/115359


Unable to load shared library HID.Node

Hello There-
I came across your module and was trying to load it up.  At the moment I am getting the following error output.
https://gist.github.com/1591014
We think we need to be able to run the wcsript file but are unsure how to do so on OSX.
Any help would be appreciated, would love to help move this forward.
Cheers,
Brian

I am using Node JS
$ node show-devices.js
node.js:201
throw e; // process.nextTick error, or 'error' event on first tick
^
Error: Unable to load shared library /Developer_NodeJS/hanshuebner-node-hid-4d685b5/src/node_modules/HID.node
at Object..node (module.js:463:11)
at Module.load (module.js:351:31)
at Function._load (module.js:310:12)
at Module.require (module.js:357:17)
at require (module.js:368:17)
at Object. (/Developer_NodeJS/hanshuebner-node-hid-4d685b5/src/show-devices.js:1:73)
at Module._compile (module.js:432:26)
at Object..js (module.js:450:10)
at Module.load (module.js:351:31)
at Function._load (module.js:310:12)

I am assuming (perhaps wrongly) that the wscript is producing HID.NODE?

On Tue, Jan 10, 2012 at 10:02 PM, Brian Jones
<EMAIL_ADDRESS>wrote:

I am assuming (perhaps wrongly) that the wscript is producing HID.NODE?

It is.  The (missing) build instructions are:
node-waf configure build
That should leave you with HID.node, try
node show-devices.js
to try it out.  All that from the src/ directory.  Let me know if that works.
-Hans

I put up some instructions in README.md - My day is over, but please
let me know if you can get it to run or need further help.
-Hans

OK. Got it running that 'node-waf configure' did the trick. My next step is to call 'read' on the device object.  going to use that super helpful Powermate.js to get started.

Curious.
I am  trying to figure out how to read incoming data from my usb powerMate object.
It seems that 'this.hid.read(this.interpretData.bind(this));'   is called via PowerMate.interpretData() but I am not sure which type of .bind() method this might be

bind() is a method of the function object:
https://developer.mozilla.org/en/JavaScript/Reference/Global_Objects/Function/bind
The call is there so that the callback, when invoked, has this bound to the right object.

Hey many thanks for that. I was getting a million different .bind() docs from JQuery to Prototype.js
How would one structure a method call to read from the USB device?
Powermate.();


use privatekey failed

I test in my private network, and the address of the account has 10 eth.
when I truffle migrate, it failed.
truffle migrate --reset
Using network 'development'.

Running migration: 1_initial_migration.js
  Replacing Migrations...
Error encountered, bailing. Network state unknown. Review successful transactions manually.
insufficient funds for gas * price + value

const privateKey ="05530B3575CD37DA646E51AABDC9E02271809DE......";
The private key was exported from metamask.
here is my network config
development:{
        // gas:    7500000,
        // gasPrice:<PHONE_NUMBER>,
        provider:function(){
            return new HDWalletProvider(privateKey,"http://<IP_ADDRESS>:8555")
        },
        network_id: "*"
      }

This feature seems indeed broken. For some reason, when using a private key, it maps to the wrong address.
Don't know if it's fixed in the version integrated in truffle.
If somebody with repo write access reads this, it would help to remove description of that feature from the documentation.


chore: release 1.7.0

:robot: I have created a release *beep* *boop*
1.7.0 (2022-01-17)
Features

support<EMAIL_ADDRESS>(6a3db36)

Performance Improvements

ctx.request.url extends from whatwg url api (96dd049)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/keq-request/keq/releases/tag/v1.7.0 :sunflower:


HTTP1ConnectionsProvider.state needs to become private

Right now, HTTP1ConnectionsProvider.state is internal and some tests modify the state without HTTP1ConnectionsProvider knowing about this.
That cannot be right because HTTP1ConnectionsProvider cannot clean up stuff it didn't know happened. Therefore we see extremely fragile and ugly cleanup code in some tests.

when this is fixed, HTTP1ConnectionProvider.closePromise must become private too, there's no reason for the tests to fulfil  internal promises of the provider.


Wrong resolver created on @connection when primary partition key name differs from "id" for "one-to-one" relations (also sort key doesn't included in resolver)

Describe the bug
I've created following schema in Graphql Transform language:
type User @model {
  id: ID!
  nickname: Nickname @connection(name: "UserNickname", keyField: "partKey", sortField: "sortKey")
}

type Nickname @model @key(fields: ["partKey", "sortKey"]) {
  partKey: ID!
  sortKey: ID!
  owner: User! @connection(name: "UserNickname", keyField: "nicknameOwnerId")
}

When I had pushed this schema I received following resolver for connection (User.nickname.req.vtl) :
{
  "version": "2017-02-28",
  "operation": "GetItem",
  "key": {
      "id": $util.dynamodb.toDynamoDBJson($util.defaultIfNullOrBlank($ctx.source.partKey, "___xamznone____"))
  }
}

And as result I have next bug when I'm trying to perform query connected relation: The provided key element does not match the schema
I could manually replace this resolver with right one, and then query succeeds.
Expected behavior
In case of one-to-one relations I should receive something like this:
{
  "version": "2017-02-28",
  "operation": "GetItem",
  "key": {
      "partKey": $util.dynamodb.toDynamoDBJson($util.defaultIfNullOrBlank($ctx.source.partKey, "___xamznone____")),
      "sortKey": $util.dynamodb.toDynamoDBJson($util.defaultIfNullOrBlank($ctx.source.sortKey, "___xamznone____"))
  }
}

Also for one-to-one connection with partition key and sort key next input data did generated:
input CreateUserInput {
  id: ID
  partKey: ID
}

istead of:
input CreateUserInput {
  id: ID
  partKey: ID
  sortKey: ID
}

Hey @lenarmazitov, we have a work item on the backlog to add a new directive that allows creating relationships but that leverages the @key directive. In the meantime, you can implement this use yourself by writing a customer resolver that uses the @key index (see https://aws-amplify.github.io/docs/cli-toolchain/graphql#custom-resolvers). You should also be able to drop the correct input type definition and the transform will not overwrite it.

@mikeparisstuff
So how about this type of transform schema:

@mikeparisstuff
But how about thing when I write this in transform syntax:
type User @model {
  id: ID!
  nickname: Nickname @connection(name: "UserNickname", keyField: "partKey", sortField: "sortKey")
}

After compilation I get only keyField generated nor sortKey in input type in schema.graphql:
input CreateUserInput {
  id: ID
  partKey: ID
}

Is this right behaviour?
Also resolver for relation, we described that it consists from partition key and sort key in connection directive...
Sorry, but seems like sortField functional is incomplete yet, may be I wrong...


Sniffer egg

Im trying to fish for the sniffer egg however im only getting fish and i got a single junk item

Is your water pool big enough for you to fish for treasures (see https://minecraft.wiki/w/Fishing#Items_obtainable)?
Anyway, you have to fish a little longer... (1/(5% * 30%) = ~66.7 times)


Special formatter for .http files

Hello!:)
I think this extension will be better, if you will add special formatter for files with .http type.
Now, i can use js formatter, but it do all files invalid (red), and i want to know which red show, really error or js validation error

No, there is no formatter at the moment. To implement this feature a LSP would be needed. See issue AnWeber/vscode-httpyac#101. A PR for this feature is welcome, but it needs some free time.


Dataset link is not working

Hi, when I open the following link from download.sh, its not working, 404 error is shown.
https://www.dropbox.com/s/d1kjpkqklf0uw77/celeba.zip?dl=0
Is there a new link to download the data?

Hi, you can download celebA data set by changing the .sh code like this:
if [ $FILE == "celeba" ]; then
# CelebA images and attribute labels
URL=https://drive.google.com/uc?id=0B7EVK8r0v71pZjFTYXZWM3FlRnM
ZIP_FILE=./data/celeba.zip
mkdir -p ./data/
gdwon $URL -O $ZIP_FILE
unzip $ZIP_FILE -d ./data/
rm $ZIP_FILE

Thanks, that worked.


Cropped Image filename

When I crop an image, an 8 character string is appended to the end of the filename.
For example, when cropping an image example-image, the cropped image is saved as example-image-mQAC1DqF.
Since there is already an option to output cropped images to a different folder, I think removing this string would improve the user experience.
I'm a fan of the plugin!

@womackj1 I've added a new setting to toggle on/off the file appending random ID.

New version found here: https://github.com/gapmiss/croppie-for-obsidian/releases/tag/0.2.0-beta


Revert "Events for txn status changes"

Reverts AugurProject/augur#2716
@brianosaurus -- These changes are broken.
makeSigner isn't part of the types for ganache, and ganache.Account isn't exported.
Furthermore, all the imports in TransactionStatus.test.ts are referring to the specific build subdirectory of augur-tools, etc and that's incorrect.
Merging breaks the build, I'm reverting.

@brianosaurus -- Restored the branch, 2635-emit-transaction-state-changes
After you fix TransactionStatus.test.ts please PR again.


Implement entrypoint in go

Rewrite entrypoint in go so that it's extendable.

ideally new processes could be added without editing the files. i've added this PR to clean up as part of https://github.com/Alluxio/alluxio/issues/17522


Unflake functional tests

Ran CI 3 times and test suite locally a dozen of times with different concurrency parameters, looks legit :)

CI is failing in #167 which is rebased on top of this one (https://github.com/revault/revaultd/pull/167/checks?check_run_id=2322656567), I don't think the problem is introduced in #167

Hmm. I'll add a commit to run with DEBUG=1 to investigate CI failures and restart it here once again to see if it was a one time flakiness..

Got another timeout on CI, i can't manage to reproduce it locally and increasing the CI wait TIMEOUT by another minute would be insane. So we'll live with that.

ACK 664d416

ACK 664d416c9d87b7ca159cc71bb42beeba5eb08545 - tested locally multiple times, never had failures


Ubuntu 22.04: sudo modprobe evdi failed: ERROR: could not insert 'evdi': Exec format error

Are you using the latest driver?
yes. its 5.6

Are you using the latest EVDI version?
yes. 1.11.0

If you are using a DisplayLink device, have you checked 'troubleshooting'
on DisplayLink's website?
yes

Is this issue related to evdi/kernel?
yes

Ubuntu 22.04

Linux kernel 5.15.0-40-generic

I have installed Ubuntu 22.04 and installed the latest release of displaylink driver 5.6. Installation finished okay but the driver is not working. I see the following error.
module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 000000001c54c643, val ffffffffc1f44651
modprobe: ERROR: could not insert 'evdi': Exec format error

Am I missing something? Please advise..

its very similar to #301

I had the same problem. It was somehow due to incompatible kernel headers. I uninstalled all the linux-headers-* packages and then reinstalled the one of my current kernel version 5.13.0-52-generic. Then I uninstalled DisplayLink, reinstalled it. Then it worked.
We will see if this survives the next kernel update.

already tried that but didn't work

this https://github.com/DisplayLink/evdi/issues/215#issuecomment-889771551 worked


Multi-GPU loading of models produces gibberish

Here's another bug on Oobabooga's project that is unresolved...
https://github.com/oobabooga/text-generation-webui/issues/2923
I realized that the ExLlama team may have a solution....
So I posted this there, and a maintainer replied, the problem's with HIP -
https://github.com/turboderp/exllama/issues/281
So I'm writing here in the hopes that someone will resolve the issue.
Here's the guide I wrote to get everything working on AMD kit...
https://github.com/nktice/AMD-AI
Models load fine when it is only on one card, here are some results :
https://github.com/nktice/AMD-AI/blob/main/SallyAIRiddle.md
Multi-card loading only spits out gibberish, here's an example :
pha golden Riv. Jcatred (ProcSN proc Dre -:// Mindly means for the and in a Nich říct Forest Rav Rav fran fran fran gaz Agrcastle castleasiacliordinate advers Mem advers Basibenkooor paste Singapore refugeermeanny intellectualsafe Shakespe contempor Mallmanual Quantmousektr Ge Mil shadownehfdzekADmobile Und Euenf Next Dominbuchcock Infoengo Hann NAT ]] Ferr' -.-- -,-

    ason, rang,-, –-

(,,

--,.,

alter

,-

(

-on,-.

I,- .

1

V

V. film-

N

    –on.,on,.

(, for.

and of- is. . and –on, –,. and

In in

film school and I on and with and I ":

.

` andon util –

Do you have a simple HIP Sample where this issue is reproduced?

Here is more info about what the issue was on another thread -
https://github.com/ROCm/rocBLAS/issues/1346#issuecomment-1905404797
[ As I mentioned there, at the bottom of that thread - it is now resolve. ]
Here's the guide I wrote with the instructions I used and have it working -
https://github.com/nktice/AMD-AI/blob/main/ROCm6.0.md

Here is more info about what the issue was on another thread -
https://github.com/ROCm/rocBLAS/issues/1346#issuecomment-1905404797
[ As I mentioned there, at the bottom of that thread - it is now resolve. ]
Here's the guide I wrote with the instructions I used and have it working -
https://github.com/nktice/AMD-AI/blob/main/ROCm6.0.md


Document clock drift parameters in guide

Closes: #3139
Description

Adds a new "Handling Clock Drift" section to the Hermes guide. The docs still need some more context on the issues that may arise when the clock drift parameters are mis-configured. @ancazamfir is doing some testing on this, and we'll add those details to this section when she has done this.

PR author checklist:

[ ] Added changelog entry, using unclog.
[ ] Added tests: integration (for Hermes) or unit/mock tests (for modules).
[ ] Linked to GitHub issue.
[ ] Updated code comments and documentation (e.g., docs/).
[ ] Tagged one reviewer who will be the one responsible for shepherding this PR.

Reviewer checklist:

[ ] Reviewed Files changed in the GitHub PR explorer.
[ ] Manually tested (in case integration/unit/mock tests are absent).

Left some comments, most of them editorial. We need to find a reference to the FLA attacks. @josef-widder anything in the spec that talks about this?

What does FLA stand for?

Thanks @josef-widder! I think the ADRs are sufficient 🙂


rsconnect not found after running setup-rsconnect

When running these steps,
    steps:
      - uses: actions/setup-python@v2
      - uses: r-lib/actions/setup-r@v2-branch
        with:
          r-version: 4.2.3
          use-public-rspm: true
      - uses: rstudio/actions/setup-connect@main
      - uses: actions/checkout@v3

      - shell: bash
        run: cd src && Rscript -e 'rsconnect::writeManifest()'

Got,
Run cd src && Rscript -e 'rsconnect::writeManifest()'
Error: Error in loadNamespace(x) : there is no package called 'rsconnect'
Calls: loadNamespace -> withRestarts -> withOneRestart -> doWithOneRestart
Execution halted
Error: Process completed with exit code 1.

Shouldn't rsconnect be installed?

I think this might be the issue,
R CMD INSTALL --configure-vars='INCLUDE_DIR=... LIB_DIR=...'
-------------------------- [ERROR MESSAGE] ---------------------------
tools/version.c:1:10: fatal error: openssl/opensslv.h: No such file or directory
    1 | #include <openssl/opensslv.h>
      |          ^~~~~~~~~~~~~~~~~~~~
compilation terminated.
--------------------------------------------------------------------
ERROR: configuration failed for package 'openssl'
* removing '/home/runner/_work/_temp/Library/openssl'

The downloaded source packages are in
	'/tmp/RtmpcJ6jBP/downloaded_packages'
Installing package into '/home/runner/_work/_temp/Library'
(as 'lib' is unspecified)
ERROR: dependencies 'curl', 'openssl' are not available for package 'rsconnect'
* removing '/home/runner/_work/_temp/Library/rsconnect'
Warning messages:
1: In i.p(...) : installation of package 'curl' had non-zero exit status
2: In i.p(...) :
  installation of package 'openssl' had non-zero exit status
3: In i.p(...) :
  installation of package '/tmp/RtmpcJ6jBP/remotes13e96fb89254/rsconnect' had non-zero exit status
Installed rsconnect

Looking at the code, it seems to not catch the exit status correctly https://github.com/rstudio/actions/blob/main/setup-connect/src/setup-connect.ts#L62


Update faq.md

Typo in - How can I move a project to another workstation?
The Issue
How This PR Solves The Issue
Manual Testing Instructions
Automated Testing Overview

Related Issue Link(s)
Release/Deployment Notes

Not needed, the page is correct as is with the latest version of DDEV.


Spring

A few straightforward changes/additions for FormPlayer. Only real change is to FormIndex.toString() which was broken in:
https://github.com/dimagi/javarosa/commit/adf2a444e7790ca21a83fd14bac0a02c866e045a
Also changed this to remove the trailing comma (since 1) this is cleaner and 2) it matches extant Touchforms behavior)

Damn, sorry about https://github.com/dimagi/javarosa/commit/adf2a444e7790ca21a83fd14bac0a02c866e045a

@phillipm npb.


the bot just straight up isnt working most of the time, but hat works fine

from just now: not working

from last night: not working

from earlier last night: working fine

this has been going on for the past month, for 70% of the times we use the bot. what is going on behind the scenes? clearly the destroy command somewhat works, because it still shows the cooldown when i try to destroy again, and also sometimes works for real during random times of day. it's very sporadic. not anything against the bot, just really curious as to why in the world it just sometimes doesnt want to work at all lately.
edit: just witnessed it before my very eyes

Pretty sure the servers are just overloaded. My video eventually loaded, it just took 10 minutes.

Pretty sure the servers are just overloaded. My video eventually loaded, it just took 10 minutes.

still happening


'yyyy' vs 'YYYY'

Expected behavior
I'm using Moment.js and react-datepicker.
Also I use YYYY-MM-DD for both packages.
For the same date Moment.js gives me 2019-02-08
react-datepicker gives me 2019-02-39
<DatePicker
  selected={this.state.tempDate}
  showTimeSelect={false}
  className="form-control"
  dateFormat="YYYY-MM-DD"
  placeholderText="Add date to exclude"
  onChange={date => this.setTempDate(date)}
/>

Moment.js was removed as part of v2.0.
I am also experiencing problems with react-datepicker showing a days corresponding "number" in a year rather than the date. Have you found a solution yet?

@mvenaas nope (

I downgraded from v2.0 to v1.8 and continued with Moment.js while in search for a better solution.

@ArtemBernatskyy  @mvenaas since there is no more Moment.js dependency you should use date format in your case like so dateFormat={'yyyy-MM-dd'}

@markokosir the problem is in inconsistency.
Date is the same but dateFormat differs from moment.js - which is very bad.

I'm switching from moment to date-fns and encountered the same issue. Take a look at https://blog.date-fns.org/post/unicode-tokens-in-date-fns-v2-sreatyki91jg.

Day.Js is a nice alternative to me, supper small and the same date format. May be we could consider using it as a replacement of date-ins
⏰ Day.js 2KB immutable date library alternative to Moment.js with the same modern API
https://github.com/iamkun/dayjs


Ignore heap-profiler functions on Flamegraph

Currently, we are not ignoring the heap-profiler scripts in the analysis and it affects the entire flamegraph.

how much? When I tested this it was not massive really

Code:
const Fastify = require('fastify')
const fastify = Fastify({ logger: true })

function soManyAllocations() {
  const A = [];
  for (let i = 0; i < 10000; i++) {
    A.push(new Array(2000));
  }
  return A;
}

fastify.get('/', (req, reply) => {
  const arr = soManyAllocations()
  reply.code(200).send('Hello World')
})

fastify.listen(3000, (err) => {
  if (err) throw err
})

node-version: v16.6.0
command: clinic heapprofiler --autocannon [ / --method GET -d 120 ] -- node index.js

Dang, let's just skip it.

I was looking at this issue in specific and I got some interesting findings:
If you run the script more than once you will get differing results, not entirely sure, but I think that it's due to some V8 optimizations in the first memory hits. Is that expected @mcollina? Well, it also might be because the script doesn't allocate big blocks of memory and it turns the graphs indeterministic? (Images at end)
I did a comparison with "Allocation Sampling" in the DevTools and the results look more consistent, however, it's important to mention that when I was running: ./bin.js heapprofiler --autocannon [ / --method GET ] -- node example.js I was getting an autocannon result of: 520k requests in 11.01s, 85.8 MB read.
But when I did the sampling in DevTools by running: node --inspect example.js -> start allocation sampling -> start autocannon the results were: 44k requests in 10.02s.
Any thoughts? I'll keep going with tests before land #49.
Samples HeapProfiler
Run 1

Run 2

Run 3

Samples Allocation Timeline
Run 1

Run 2

Run 3

Script utilized:
const Fastify = require('fastify');
const app = Fastify({ logger: false })

app.get('/', function (req, res) {
  res.send('Ok')
})

app.listen(3000);


[Release] Release Request for 0.0.1 to development

Release Version
0.0.1
Target Environment
development

/approve


Getting channel ID by channel channel name

Hey team!
Im wondering if there is a way to get a specific slack channel ID by the channel name.
I know I can use the "list" method but when you have thousands of channels this gets pretty hairy...
Is there any method to get it by name? something like channels.getByName(channelName)
I went over slack API but I did not find any way of doing that.
Thanks in advance!

Hi @galElmalah, thanks for asking the question!
I do understand that this is inconvenient but the only approach that we can suggest is to traverse all the pagination results of conversations.list API calls until you find the channel in response.
To manually find a specific channel's ID, you can check the ID value in the channel details in the UI:
https://user-images.githubusercontent.com/19658/159142611-34f8a5bf-b2b1-4745-9efa-2107fc55136c.mp4
I hope this was helpful to you.

Hey 😄  Thanks for the speedy reply!
It validates my assumption which is good enough


Adjust fee in PSBT if Output doesn't contain tweaked key

https://github.com/rgb-org/rgb-core/blob/4e29b8082c0a69cc906fa8d4f604f2980dad17f5/src/stash/anchor.rs#L206-L207

Deprecated with change of the commitment schema to tapret


Cannot read property 'reloadAll' of null

Editing .less files in Atom dev mode displays the following error in the console:
Uncaught TypeError: Cannot read property 'reloadAll' of null c:\Users\jerone\AppData\Local\atom\app-0.194.0\resources\app.asar\node_modules\dev-live-reload\lib\dev-live-reload.js:42
(anonymous function) c:\Users\jerone\AppData\Local\atom\app-0.194.0\resources\app.asar\src\command-registry.js:238
module.exports.CommandRegistry.handleCommandEvent c:\Users\jerone\AppData\Local\atom\app-0.194.0\resources\app.asar\src\command-registry.js:3
__bind c:\Users\jerone\AppData\Local\atom\app-0.194.0\resources\app.asar\src\command-registry.js:153
module.exports.CommandRegistry.dispatch c:\Users\jerone\AppData\Local\atom\app-0.194.0\resources\app.asar\src\window-event-handler.js:71
(anonymous function) events.js:77
emitOne events.js:166
emit events.js:166

Confirmed this working correctly in 0.192.0. Maybe related to https://github.com/atom/atom/pull/6313
Windows 7 64-bits
Atom 0.194.0

Do you remember if you ran this command right at startup up? Or had Atom been running awhile?

I did not run this command myself. It showed up in the console after saving an edited .less file.
Just tried reproducing, but it doesn't give me the error anymore. Changes to an .less file still aren't applied.

This will be fixed in the next Atom release 0.195, thanks for reporting it.

Great work!

Still having this issue in 1.0.19
Uncaught TypeError: Cannot read property 'reloadAll' of null


Move alexbilbie/proton to protonphp/proton

I've decided to move this off my personal account and into its own organisation as I've had some inspiration to turn Proton into more of a fully fledged framework

:+1: Awesome news, I have had a great deal of success in building out application using Proton as a launchpad, I look forward to seeing where it is heading.


Integration with SadTalker

Would be awesome if you can add SadTalker integration. The best free alternative to D-ID. This functionality would complete the features listed on the roadmap.
Repo: https://github.com/OpenTalker/SadTalker

Great idea. Can you join our discord: https://discord.com/invite/WkBkzVEp ? and we can speak more about UI / UX there.


Breakpoints disappears from gutter when debugging Node in Docker

Reported by @johnpapa
Breakpoints disappears from gutter when debugging Node in Docker, but are still hit.
Details: Insiders + Node 6 + Inspector protocol

What happens if you click on the breakpoint pane on the routes.js breakpoint?
What happens if you click on the gutter after the breakpoints have disappeared?
Can you reproduce this constantly? If yes, please provide reproducable steps so we could investigate (like a repository on github and steps to get into this state)

Please do not close. I was at MS Ignite last week, and a week is not enough to reply if someone is out.
What happens if you click on the breakpoint pane on the routes.js breakpoint?
It show the breakpoints.

What happens if you click on the gutter after the breakpoints have disappeared?

it does not appear while running. if i stop it, it does.

Can you reproduce this constantly? If yes, please provide reproducable steps so we could investigate (like a repository on github and steps to get into this state)

The repo is here https://github.com/Azure-Samples/angular-cosmosdb/tree/develop
Use the readme to get started. Be sure to be on the develop branch. I run npm docker-local to start it. Then attach the debugger using the config in the project.
cc @chrisdias @auchenberg

Since the brekapoints disapear while you are running and they appear back when you stop my bet is that the node2 debug adapter is updating the brekapoints to some other location -> assigning to @roblourens to investigate further.

i have not seen this issue happen in over 6 months on my machine. I'm not sure if that is because I moved on to Node 8+ or the issue has been fixed.
Since nobody else has reported anything since then, I think it is safe to close this one


wip: Testing #6521

Motivation

Something is wrong with #6521. I'm going to try bisecting it.
Test plan

See included automated tests.

We have a policy of testing changes to Sorbet against Stripe's codebase before
merging them. I've kicked off a test run for the current PR.  When the build
finishes, I'll share with you whether or how it failed. Thanks!
Stripe employees can see the build results here:
→ https://go/builds/bui_MjDUDlLeS2TcA2
→ https://go/builds/bui_MjDUJrQ0TyJKuR

We have a policy of testing changes to Sorbet against Stripe's codebase before
merging them. I've kicked off a test run for the current PR.  When the build
finishes, I'll share with you whether or how it failed. Thanks!
Stripe employees can see the build results here:
→ https://go/builds/bui_MjENJcrONUqAd1
→ https://go/builds/bui_MjENUJvXnqDwGQ

Current dependencies on/for this PR:

master

PR #6534   👈

PR #6521

This comment was auto-generated by Graphite.

We have a policy of testing changes to Sorbet against Stripe's codebase before
merging them. I've kicked off a test run for the current PR.  When the build
finishes, I'll share with you whether or how it failed. Thanks!
Stripe employees can see the build results here:
→ https://go/builds/bui_Mk3fbBeyu1GFYk
→ https://go/builds/bui_Mk3fqjGcTKV5Af


Tests hang in chromium on docker

Are you requesting a feature or reporting a bug?
bug
What is the current behavior?
Whenever I try and run my tests in chromium through docker I get this issue:
ERROR The HeadlessChrome 63.0.3239 / Linux 0.0.0 browser disconnected. This problem may appear when a browser hangs or is closed, or due to network issues.
What is the expected behavior?
Run through the test normally like when I run the same tests in firefox through docker.
How would you reproduce the current behavior (if this is a bug)?
Run testcafe through docker and have chromium selected as your browser in the command line
Provide the test code and the tested page URL (if applicable)
Tested page URL:
Test code
// Simplest test I run
import { Selector } from 'testcafe';
import config from './config';

fixture `Login Test`
    .page `${config.baseUrl}`;

test('Login Test', async t => {
    await t
    	.resizeWindow(parseInt(`${config.width}`), parseInt(`${config.height}`))
        .typeText('#app > div > div > div > aside > div.container.fluid.fill-height > div > div > div > div.card__text > form > div:nth-child(1) > div.input-group__input > input[type="text"]', '[USERNAME HERE]')
        .typeText('#password', '[PASSWORD HERE]')
        .click('#login > div')

        .expect(Selector('#create > div > div > div > div.card__title > h3').innerText).eql('Systems')
        .takeScreenshot('login1.png');
});

Specify your

operating system: macOS High Sierra [10.13.4 (17E199)]
testcafe version: 0.19.2
node.js version: v8.11.1
Docker version: 18.03.1-ce, build 9ee9f40

Hi @GregoryCBT! I need access to your testing page to reproduce the problem. This error means that the browser has crashed. You could try to run your tests on directly on your machine without docker, or customize the official image and try to use X11 SSH Forwarding or pass-through  X11 socket into virtual machine to see what's going on with the browser.

I will close the issue because no activity has been encountered for a long time.
Feel free to reopen the issue if the problem persists and you can provide an example to reproduce it.


Add support for FCM V1 configuration

ref

https://expo.dev/blog/expo-push-notifications-migrating-to-fcm-v1
https://github.com/expo/expo-server-sdk-node/commit/5a3f2e3e7f20d212cde757a5d706e4227d9666db
https://expo.dev/blog/expo-adds-support-for-fcm-http-v1-api

due to change of FCM V1, some of tests are failed.

test_get_push_notification_receipts これを修正する


Effect not working on wordpress PLEASE Help

Hi Team,
I'm looking to get a cool looking effect added to my WordPress site, i'm using elementor to design the site and am having a hard time adding it.
I'm not sure if it's the Jquery version please help

Sounds like you need help on Wordpress and/or Elementor and not specifically this plugin. Therefore I'm closing this. If you can show some evidence there is something wrong with the plugin specifically that is preventing you from adding it to your website I'll open it again.


Code-as-attributes doesn't work, e.g. src=static_path(@conn, "x.css")

This gives a "missing terminator" error:
link rel="stylesheet" href=static_path(@conn, "/css/app.css")

This works, though:
link rel="stylesheet" href="#{static_path(@conn, "/css/app.css")}"

The equivalent of the first example works in the Ruby version of Slim.
Maybe it could make sense to include a valid example of a dynamic attribute value in the README docs?

Thanks @henrik, this looks like a bug.

Glad to see this library is alive and well and being maintained :) Thanks so much for all the hard work!
Sent from my iPhone

On 09 Sep 2015, at 07:17, Sean<EMAIL_ADDRESS>wrote:
Thanks @henrik, this looks like a bug.
—
Reply to this email directly or view it on GitHub.

  Myself or @Rakoth will take a look at these bugs.  Thanks again for taking the time to file them.  :+1:

Hi @henrik, we have some problems with elixir code with spaces as attribute values.
link rel="stylesheet" href=static_path(@conn,"/css/app.css")

should work for you now

This one is going to take some regex magic to sort out.  The offending regex at parser.ex#L25, specifically this part: [^\s"'][^\s]+[^\s"'].  We need to update the regex to allow spaces within () if present.

@Rakoth Thanks for the workaround!
Regarding the regex, I believe checking for balanced parentheses (if we want to allow hrfg=foo(a, b()) but not href=foo(a, b() is one of those things that "pure" regexps can't support. But Erlang/Elixir's flavor seems quite full-featured, so I'm sure there's something in there. More info: http://stackoverflow.com/questions/133601/can-regular-expressions-be-used-to-match-nested-patterns
If all else fails, I guess parse_attributes could do something beyond regexps.

This seems applicable: http://www.erlang.org/doc/man/re.html#sect20
No time to dig further into it now I'm afraid, but maybe later if you don't beat me to it (feel free).

Experimenting with the linked regexp, I get this:
re = ~r/
^
  \w+
  (
    \(
      ([^()]++|(?1))*
    \)
  )
$
/x

[
  "foo()",
  "foo(bar, baz(a(), 5, :dog, b(c, 123)))",
  "foo('a (')",
  "foo(()",
  "foo(bar, baz()",
] |> Enum.each fn (string) ->
  IO.puts "#{String.match?(string, re)} for #{string}"
end

With output:
true for foo()
true for foo(bar, baz(a(), 5, :dog, b(c, 123)))
false for foo('a (')
false for foo(()
false for foo(bar, baz()

So it handles nested parentheses but parentheses inside a string can mess it up. Handling those (and maybe accounting for escaped quotes inside strings…) could get hairy. I'm thinking if this should be handled perfectly, a regexp probably isn't the way to go.

@doomspork Is there any progress on this issue?

@dannote I don't believe anyone has worked on this since there is a reasonable work-around, though it would be nice to resolve.


typos in comments

Assume if some of this gets merged, squash merge is used. Let me know if I should squash though.

I see the typos under 'deps' can't be fixed here. I'll revert those.


fix(lnd): use static ports for production builds

Description:
Use port 11009 (rpc) and 8180 (rest) for lnd when running in production mode.  When running in dev mode, user a random range bound port for both rpc and rest.
Motivation and Context:
This ensures that users have a consistent port that they can connect to.
How Has This Been Tested?
Manually - run app in dev mode and production mode, at same time.
Types of changes:
Enhancement
Checklist:

[x] My code follows the code style of this project.
[x] I have reviewed and updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes where needed.
[ ] All new and existing tests passed.
[x] My commits have been squashed into a concise set of changes.

Coverage increased (+0.05%) to 19.309% when pulling 1a5da16766b5485669957b9d4ababf5235e4f4bb on mrfelton:fix/port-conflict into c5876ad8827a8175697873980bed72ee6c519e1f on LN-Zap:master.

Coverage increased (+0.05%) to 19.309% when pulling 1a5da16766b5485669957b9d4ababf5235e4f4bb on mrfelton:fix/port-conflict into c5876ad8827a8175697873980bed72ee6c519e1f on LN-Zap:master.

Coverage increased (+0.05%) to 19.309% when pulling 1a5da16766b5485669957b9d4ababf5235e4f4bb on mrfelton:fix/port-conflict into c5876ad8827a8175697873980bed72ee6c519e1f on LN-Zap:master.


Multi-node CCF deployment on ACC VMs

Docker-based multi-node CCF deployment on SGX enabled ACC VMs. Tested via a two-node CCF deployment. Not tested outside of ACC.
Signed-off-by: prakashngit<EMAIL_ADDRESS>

@prakashngit This was closed while moving from master to main. Please reopen it (and rebase it on main) if necessary.


Unable to use custom callable metric

Steps to reproduce the behavior
from openTSNE import TSNE
from scipy.spatial.distance import jensenshannon

tsne = TSNE(
    perplexity=30,
    metric=jensenshannon,
    n_jobs=8,
    random_state=0,
    verbose=True,
)
embedding_train = tsne.fit(scores_list)
plot(embedding_train, ids)

The above code throws an error:
TypeError                                 Traceback (most recent call last)
Cell In[36], line 97
     88     ax.legend(handles=legend_handles, **legend_kwargs_)
     90 tsne = TSNE(
     91     perplexity=30,
     92     metric=jensenshannon,
   (...)
     95     verbose=True,
     96 )
---> 97 embedding_train = tsne.fit(scores_list)
     98 plot(embedding_train, ids)

File [~/anaconda3/envs/openmmlab/lib/python3.9/site-packages/openTSNE/tsne.py:1246](https://vscode-remote+wsl-002bubuntu-002d20-002e04.vscode-resource.vscode-cdn.net/home/tc/open-mmlab/tracker/~/anaconda3/envs/openmmlab/lib/python3.9/site-packages/openTSNE/tsne.py:1246), in TSNE.fit(self, X, affinities, initialization)
   1243 if self.verbose:
   1244     print("-" * 80, repr(self), "-" * 80, sep="\n")
-> 1246 embedding = self.prepare_initial(X, affinities, initialization)
   1248 try:
   1249     # Early exaggeration with lower momentum to allow points to find more
   1250     # easily move around and find their neighbors
   1251     embedding.optimize(
   1252         n_iter=self.early_exaggeration_iter,
   1253         exaggeration=self.early_exaggeration,
   (...)
   1256         propagate_exception=True,
...
--> 247 self.index = AnnoyIndex(data.shape[1], annoy_metric)
    249 random_state = check_random_state(self.random_state)
    250 self.index.set_seed(random_state.randint(np.iinfo(np.int32).max))

TypeError: argument 2 must be str, not function

Hmm. AFAIK this is not supposed to work like this.
You can try metric="jensen-shannon" which will call pynndescent (which you should install for this work).

Thanks for your advice!


⚠ Bofrost.at has degraded performance

In 5232c16, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1418 ms

Resolved: Bofrost.at performance has improved in 44e3227.


refactor(MarkdownEditor): guard web component imports

Approach
This PR proposes a convention for dependencies intending to run only on the client. For components looking to use these dependencies, they can use a bare import to a file under src/web-components. This file should include a check to see if the current runtime supports the DOM before using a dynamic import() to bring in the dependency.
// src/web-components/markdown-toolbar-element.ts
import { canUseDOM } from '../utils/environment';

if (canUseDOM) {
  import('@github/markdown-toolbar-element');
}

// src/path/to/component
import '../web-components/markdown-toolbar-element';
export default function ExampleComponent() {
  // ...
}

Files under src/web-components/* are treated as side effects to make sure that they are included in the bundle even if no imports are used.
Caveats
Dynamic import is not supported in environments like Jest until support lands for ESM in Node.js VMs^1. We can use babel-plugin-dynamic-import-node locally to polyfill this in Node.js environments. However, downstream teams may not be using this plugin and will run into an unexpected error if we ship with this change.
As a result, we have a couple of options:

Create Node.js specific bundles which include this plugin

Try and feature detect to determine if we should use import() or require(). This could potentially look like:
import {canUseDOM} from '../utils/environment'

if (canUseDOM) {
  if (typeof require === 'function') {
    Promise.resolve().then(() => {
      require('@github/markdown-toolbar-element')
    })
  } else {
    import('@github/markdown-toolbar-element')
  }
}

Looking forward
One concern that is not implemented is if a component would like to listen to when the module is available before rendering. If this scenario comes up, we could use a convention where each module exposes a ready() or register() function that returns a Promise that resolves when the module is loaded (or rejects if there is an error)

FYI @koddsson @iansan5653 here is another approach we could take for @github deps that can guard rendering to only the client (or DOM-like environments in the case of tests/JSDOM)


Power Module Rev D Fixes

[x] U19 pin 1 indicator
[x] Better precision resistors for solar charger divider (Input and output regulation)
[x] More space monitors and sense resistors
[x] More space around charger/regulators
[x] U27 wrong package
[x] D3 wrong package
[x] Add reset button on watchdog

Before you spin Rev D, it would be good to check if the watchdog firing actually turns off and back on the power rails correctly. (Probably a deadbugged chip and some wires)

U27 is the watchdog - so I don't have a good way

[ ] VSOL- must be connected to VBAT-. Watchdog only shuts off battery connection to ground, solar panel could still power device. Change charger GND connections to VSOL-/VBAT-.

[ ] Think about Load Switches on a per module basis

[ ] WHY IS THE RESET BUTTON SO HARD TO PRESS??


Updated Point Blank to 3.9.0

The parser pattern also needed updating; I've done both changes myself.


5.6.0 breaks builds using TypeScript 3.5

5.6.0 changes typescript compiler from 3.6.0 to 3.7.0 and this generates type definition file that is not working with us who still use earlier versions.
node_modules/google-auth-library/build/src/auth/googleauth.d.ts(61,9): error TS1056: Accessors are only available when targeting ECMAScript 5 and higher.

This appears to be the exact same issue that was reported for node-gtoken 3 weeks ago. https://github.com/googleapis/node-gtoken/issues/244
Environment details

Node.js version: 8.16.2
npm version: 6.4.1
google-auth-library version: 5.6.0
Typescript version: 3.5.3

This hits us too.
This is an epidemic with the Google libraries. It seems that every other day a library breaks our build with this same issue.
Do you Googlers have some common way to let everybody else in the company know not to make the same mistake?
You are also in the business of shipping "libraries", don't you realize you need to test your packages with code built with previous versions of the compiler?

Greetings folks, and thanks for the heads up.   When something does break for you - we love it when folks file issues, and we try to get to them in a timely fashion.
In terms of "making the same mistake" - we generally snap to the latest available version of TypeScript for our libraries.  Due to the way the TypeScript compiler makes backwards
incompatible changes in semver minor releases.  With this particular change - the code emitted by 3.7 is backwards compatible with 3.6, but not 3.5 🤦♂
This puts us in a position where we have no way to know when it's acceptable to accept a new version of the compiler.  I see a few options, and I'm curious where folks stand:

We make semver minor updates to the TypeScript compiler a semver major change in the module.  This is very heavy handed, but feels like the only way we could guarantee updates won't break downstream users.   It's unfortunate because it would increase the number of semver major releases, when there are likely no runtime changes.

We institute a "latest version only" policy of the TypeScript compiler, and document it.  This is essentially where we are today, and does come with the risk of breaking people when the TypeScript compiler changes.  But at least then we wrote it down, and y'all know what to expect.

I am hoping @bcoe or @alexander-fenster have other ideas 😆
Regardless of where we go here - we need to have a strategy, write it down, and make sure folks know where we're headed.
On this note:

You are also in the business of shipping "libraries", don't you realize you need to test your packages with code built with previous versions of the compiler?

I can understand that you're frustrated, but we're all humans here.  I'd appreciate a little more assumption of best intent. I'm happy to have a discussion about the policies of how we support older versions of the TypeScript compiler, or how we test it - but please let's try to do so in a kind way.

Listen, I think you need to show some patience in embracing the latest typescript version. Start with using tests compiled with previous versions of typescript (ie what we do) against your libraries that are compiled with whatever version of TS you want, and document what is the earliest version of TS you support because of issues like this. But you need to give developers 6-12 months to move and when you hit issues like that you need to back out before we point it out to you.
I also want to be at the latest TS but here are my constraints. I currently work on a project that has both back end and front end in typescript. Front end uses angular and there is some shared code between front end and back end, and since we are full stack developers and try to keep our sanity, the TS version supported by angular is the LCD. We just switched to angular 8 that supports "typescript": "~3.5.3"; angular 9 is in RC with "typescript": "~3.6.4",. We will move angular 9 when we feel it is stable and we get an upgrade window.
Is Microsoft aware of the issue they introduced with this incompatibility?

@jshoemaker this issue should have been addressed by https://github.com/googleapis/google-auth-library-nodejs/pull/845.
We have opted to pin TypeScript for the time being across the ~80 libraries we manage, until we can figure out a better resolution for the upstream TypeScript issue can be found.

@bcoe I confirm that I removed the workarounds in our pakckage.json files and we do not see the issue any more, thanks to you and @JustinBeckwith for the quick resolution.


Correction for raw affiliation National Institute for Medical Research, Tanga Medical Research Centre, Tanga, Tanzania.

Correction needed for raw affiliation National Institute for Medical Research, Tanga Medical Research Centre, Tanga, Tanzania.
raw_affiliation_name: National Institute for Medical Research, Tanga Medical Research Centre, Tanga, Tanzania.
new_rors: 05fjs7w98
previous_rors: 04tnbqb63
works_examples: W2123263812;W2045093293;W2117047676
contact: 2265cebd54336d07bfd2a067b4eccab9:137408e09542aa66c6f3e3cdba6b2fe35730d008 @ crick.ac.uk

This issue was accepted and ingested by the OpenAlex team on 2024-10-10. The new affiliations should be visible within the next 7 days.


Update related-data.md

The object variable 'Blogs' was split thus making it unreadable.

Thanks @OOberoi!

Always a pleasure Diego 😊
Obi Oberoi – (M.Sc.)
Cell:<PHONE_NUMBER>

On Mar 13, 2019, at 5:08 PM, Diego Vega<EMAIL_ADDRESS>wrote:
Thanks @OOberoi!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.


fix: inputField style fixes

Closes #
📝 Description
fixed the css following figma such as background color from #fff to transparent and the border color

Add a brief description

Screenshots

Please provide screenshots for any visual changes

Merge checklist

[ ] Added/updated tests
[ ] Added changeset

Could you also address this issue with the changes to Textfield here?
https://github.com/project44/manifest/issues/412


Bmap file integrity check

Checks if the bmap hash is correct for the current bmap file.
Bmap file checksum is calculated having that field as all 0s.
Closes: #50
Signed-off-by: Rafael Garcia Ruiz<EMAIL_ADDRESS>

Bmap integrity check bmap_integrity added into the remote copying function copy_remote_input


feat: adds facilities table & admin dashboard backend

Adds facilities table and backend for the admin dashboard. Commented out PATCH on handler (UpdateFacilities) due to errors but will revisit later as it was not needed right at this moment.

I am getting this all fixed up and I'll have it merged with all my changes by monday


what's the stage mean in rate limit

(optional, integer) Refers to the stage set in the filter. The rate limit configuration only applies to filters with the same stage number. The default stage number is 0.

i have find this in the envoy doc,but what's the stage mean？what is the different of state 0 or state 10?

It's a mechanism to have multiple rate limits in the filter chain. For example:
pre-auth rate limit -> auth -> post-auth rate limit

thanks

@mattklein123 @du2016
Any idea how to use it? I'm wondering if I can have 2 different rate limiting services and point few workloads to rateLimitService1 and few workloads to rateLimitService2  - not sure if it's possible though.


Add support for SpeechStarted via vad_events feature

A new feature to the Deepgram API allows for a user to better determine when speech has started in an audio live stream. We want to add support for this into the .NET SDK.
See Docs for more details: https://developers.deepgram.com/docs/start-of-speech-detection

Merged https://github.com/deepgram/deepgram-dotnet-sdk/pull/253


fix: fix Dell EMC Powerswitch n parser

solves https://github.com/splunk/splunk-connect-for-syslog/issues/2180
This Pull Request introduces a breaking change to the codebase that addresses an issue related to parsing logs from Dell EMC PowerSwitch N devices. Previously, the logs were parsed based on message content using the syslog parser located at package/etc/conf.d/conflib/syslog/app-syslog-dell_switch_n.conf.
Background
In issue #2180, it was reported that the existing parser had a bug and incorrectly classified events from various devices such as VMware vSphere, ISC BIND, Cisco IOS, and Aruba ClearPass. The root cause of the issue was identified as a flawed design of the parser, which did not rely on unique message characteristics of Dell PowerSwitch N devices. Instead, it improperly classified events based on the hyphen in the hostname, whenever the program name started with an uppercase letter.
Breaking Change Details
To rectify this issue and improve the accuracy of log parsing, a breaking change was introduced. The syslog parser package/etc/conf.d/conflib/syslog/app-syslog-dell_switch_n.conf has been replaced with a new netsource parser located at package/etc/conf.d/conflib/netsource/app-netsource-dell_switch_n.conf.
Impact
This breaking change will affect any existing functionality or configurations that relied on the previous syslog parser for Dell PowerSwitch N logs.

:tada: This PR is included in version 3.4.6 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


⚠ Bofrost.si has degraded performance

In eb053d9, Bofrost.si (https://www.bofrost.si) experienced degraded performance:

HTTP code: 200
Response time: 3857 ms

Resolved: Bofrost.si performance has improved in 5ace4f9.


Whether to support proxy

Hello, I think this is great, but does it support sending requests through a proxy?

Sorry, not supported at this time.


pipe:1 for aiff leaving file corrupt

Hi
I am trying to convert a wav to an aiff and via memory streams (using npm package: memorystream).  This works for converting wav to mp3, but when I do it for aiff, the file is corrupted.  If I instead write to file, it only works if I add a second output of 'tmp.mp3' and the aiff is not corrupted anymore.
Then command that gets generated when I use the memory stream is:
ffmpeg -i ./inputwav -y -f aiff -id3v2_version 3 -write_id3v2 1 -metadata "title=My Track Title" pipe:1
Any ideas why aiff may be corrupted?
Thanks
Josh

Looks like an issue with ffmpeg, not fluent-ffmpeg. Please try the same thing in command line first.

Hi
Yes, it seems that ffmpeg pipe to the stdout when piped to a file does not write out the header properly (particularly for wavs and aiffs) - tried doing this directly with ffmpeg and piped to the file and the same issue occured.
Thanks for the reply.
Josh

Maybe there's an option to force writing the header? Have a look at the ffmpeg doc.


[Event Request] Codeunit 1006 "Copy Job"- OnBeforeCopyJob

Dear ALAppExtensions team,
through this issue we would like to request adding event publisher OnBeforeCopyJob to Codeunit 1006 Copy Job with the following signature:
[IntegrationEvent(true, false)]
local procedure OnBeforeCopyJob(var SourceJob: Record Job; TargetJobNo: Code[20]; TargetJobDescription: Text[100]; TargetJobBillToCustomer: Code[20]; CopyDimensions: Boolean; CopyPrices: Boolean; var IsHandled: Boolean)
begin
end;

which would be called as follows in CopyJob:
procedure CopyJob(SourceJob: Record Job; TargetJobNo: Code[20]; TargetJobDescription: Text[100]; TargetJobBillToCustomer: Code[20])
var
    TargetJob: Record Job;
    // >>>> New >>>>>>>>>>>>>>>>
    IsHandled: Boolean;
    // <<<< New <<<<<<<<<<<<<<<<
begin
    // >>>> New >>>>>>>>>>>>>>>>
    IsHandled := false;
    OnBeforeCopyJob(SourceJob, TargetJobNo, TargetJobDescription, TargetJobBillToCustomer, CopyDimensions, CopyPrices, IsHandled);
    if IsHandled then
        exit;
    // <<<< New <<<<<<<<<<<<<<<<

    TargetJob."No." := TargetJobNo;
    TargetJob.TransferFields(SourceJob, false);
    TargetJob.Insert(true);
    if TargetJobDescription <> '' then
        TargetJob.Validate(Description, TargetJobDescription);
    if TargetJobBillToCustomer <> '' then
        TargetJob.Validate("Bill-to Customer No.", TargetJobBillToCustomer);
    TargetJob.Validate(Status, TargetJob.Status::Planning);
    if CopyDimensions then
        CopyJobDimensions(SourceJob, TargetJob);
    CopyJobTasks(SourceJob, TargetJob);

    if CopyPrices then
        OnBeforeCopyJobPrices(SourceJob, TargetJob);

    OnAfterCopyJob(TargetJob, SourceJob);
    TargetJob.Modify();
end;

Thanks in advance!

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


Revert "Bugfix: Fixes cluster-proxy addon agent image rendering"

--agent-image-name should be honored

the github revert doesnt add sign-off information to the commits, deleting


4.5a5 will likely not be startable because location of start-tor-browser changed

./start-tor-browser will be moved to Browser/start-tor-browser. I know this, because I looked into 4.5a5. Related changelog. Quote https://blog.torproject.org/blog/tor-browser-45a5-released:

We're very excited about the usability and security improvements in this release. On the usability front, we've created a FreeDesktop-compatible launcher wrapper for Linux that can be invoked from either the GUI or the shell, and we also provide Windows users with the ability to add optional Start Menu and Desktop shortcuts.

Related IRC log:
<Patrick> is it considered sane to start TBB/Browser/start-tor-browser ? @ GeKo
<Patrick> for start of TBB from terminal
<arma> patrick: that's how i do it. seems to work for me.
<Patrick> i see
<Patrick> i hope that script will stay in that place, because moving the file around breaks torbrowser-launcher and tb-updater
<arma> patrick: yeah, i have no idea why they moved it
<arma> i wonder if there's a ticket for moving it
<arma> or if they even know they did
<Patrick> will report a bug against torbrowser-launcher
<arma> patrick: https://trac.torproject.org/projects/tor/ticket/13375 looks related
-zwiebelbot/#tor- tor#13375: Tor Browser Script can't be launched from the Linux desktop - https://bugs.torproject.org/13375

<GeKo> Patrick: as long as you are not removing it it is staying but the new alpha does not have it anymore due to #13775
-zwiebelbot/#tor- tor#13775: Tor Browser won't open with OpenVPN - https://bugs.torproject.org/13775
<Patrick> GeKo:  So where will it be moved? Or how to start TBB from terminal by then?
<GeKo> ./start-tor-browser.desktop

I think it might be better for torbrowser-launcher to use ./Browser/start-tor-browser (that script has not moved, although the symlink with the same name that sat above it, i.e., next to the Browser directory, is gone).

Why is that?
Do you think ./start-tor-browser.desktop won't last for long either?

You might ask other developers for their opinion, but since Browser/start-tor-browser is the script that really starts the browser and because it is something that advanced users may modify, I think the Tor Browser team is less likely to move it in the future.  That is just a "gut feeling" on my part though. An argument can also be made that the .desktop file is at the top level and therefore more users may know about it, which means renaming or moving it would be more disruptive.

I see. I am in favor of ./start-tor-browser.desktop to prevent subtle browser fingerprint issues vs being a subset that just uses Browser/start-tor-browser. The "do as most others" credo. But that could just be FUD.

Sorry about being flaky, I've been traveling and just realizing this is a serious issue!
I also prefer the idea of running ./start-tor-browser.desktop, except that if you choose to allow opening links from external programs with Tor Browser (basically if you want to set it as your default browser) TBL passes custom -allow-remote into Browser/start-tor-browser. So to keep this functionality, TBL must call the bash script. I'll go ahead and do that for now, but maybe change this in the future.

Actually, it looks like the -allow-remote trick stopped working. After manually testing, it looks like opening URLs in Tor Browser doesn't work anymore with the new Browser/start-tor-browser script (which looks like it has changed a bunch). You can open Tor Browser with a URL the first time it's open, but if you have an already open window you can't open new tabs by calling it again.
That's a shame, but I'll go ahead and remove the default browser feature.

Wow, executing .desktop files turns out to be nontrivial. https://askubuntu.com/questions/5172/running-a-desktop-file-in-the-terminal

./start-tor-browser.desktop
works for me.

@adrelanos that's only if you're in the same directory. Try going to your home directory and running ~/.local/share/torbrowser/tbb/x86_64/tor-browser_en-US/start-tor-browser.desktop. This is what happens for me, in a couple of different platforms:
micah@ubuntu-dev:~$ ~/.local/share/torbrowser/tbb/x86_64/tor-browser_en-US/start-tor-browser.desktop
/usr/bin/env: ./Browser/execdesktop: No such file or directory

Could be a bug in start-tor-browser.desktop or general issue with .desktop files.
Anyhow... What works...
Why not cd into that folder before running ./start-tor-browser.desktop? This is what tb-starter does. That works.

Good idea, looks like you can pass cwd into subprocess.call: https://github.com/micahflee/torbrowser-launcher/commit/5f833d73290bd3623bf22caffaed599381d454d9

For what it's worth, these two commands worked for me with Tor Browser 4.5 on Ubuntu 14.04 (the second one opens a new tab in the already running first browser):
./Browser/start-tor-browser -allow-remote &
./Browser/start-tor-browser -allow-remote http://torproject.org/
If -allow-remote is not working for you, please open a Tor Browser trac ticket via https://trac.torproject.org/projects/tor/newticket


Allow Custom OIDC Scopes to be Passed to the Authenticator

Expected Behavior
I can choose what OIDC scopes are passed as part of the authentication request.
Actual Behavior
Only the hardcoded "openid" scope is defined. See here. This also prevents OAuth support.
Enhancements
Allows custom scopes to be defined as per OIDC v1.0 Scopes

Implemented in https://github.com/aerogear/aerogear-android-sdk/pull/155


Need a popup to confirm when a selected submission is to be removed

Should be possible show a popup asking the user to confirm that [s]he is removing a submission?
I've experienced that when I select a submission from mydspace  and want to delete it, on pressing the remove button there is no message shown asking for confirming. In case of erroneous selection it could be helpful...

will be reopened if a volunteer is found to implement it


CSV Imports - Duplicate import_documents are created

Somehow import CSV rows are being added to import_documents twice, which can really lengthen the import time for adding many records at a time.

Closing. I cannot replicate with vanilla GBL Admin.
I think the duplication captured above was due to BTAA Geoportal development work quirk.


FracDiff with different order d_j for each time series

issue moved here https://github.com/ulf1/sklearn-fracdiff/issues/1


Be able to mouse-over and view monomer structure in Canvas

Fixed in 2016-09-12 version

Confirmed fixed. Close.


Custom JSON validation formats for manifest

Right now, some fields are not validated, any fields that reference these types just accept any string:

match-pattern
glob-pattern
content-security-policy
mime-type
permission

Here's the schema for V3: https://json.schemastore.org/chrome-manifest

They should perform actual validation checks, not just checking if they're a string.
Here's where we're setting these formats to accept any string.
https://github.com/aklinker1/vite-plugin-web-extension/blob/b2ca582c426132ae4ef5b9600e047b94c13fd8c4/packages/vite-plugin-web-extension/src/manifest-validation.ts#L23-L28

https://json.schemastore.org/chrome-manifest

Yeah. For example, the validation wouldn't catch if you passed asdf as a permission.

If we comment out any of those lines, we get an error like this:

I see, yeah. Might be worth fixing it in the source repo. I'll dig in a bit deeper.

Yeah. Ideally the format would be defined in the  schema itself, somehow. I'm not too well versed in JSON schemas, so I don't even know if you can define custom formats inside a schema.

So from what I'm gathering, these formats might be there as placeholders, since they're not defined anywhere else in the schema and are even flagged as unknown in the schema-validation file.
Now, you can define custom formats, but I don't quite see why you would want to in this case, since most of it can be fixed by using patterns or enums.
I already updated the permissions to behave apropiately so it should bounce off bogus keywords or improper match_patterns.
Removing these redundant formats, along with the permissions update would solve most of these errors. I'm still investigating the content_security_policy validation and the glob_pattern, the latter being apparently just a string as there's not really a way to 'clamp' it inside a regex.
However:
Checking the webextension manifest and its docs, there seem to be a few permission keywords that are not contained in Chrome's enum.
Do you think it's best if we compare against each manifest depending on the target build and trim the unwanted bits behind the scenes, or just stick to the Chrome one and just do the casting entirely within the plugin?
I'm not familiar yet with how you're handling the validations internally as I've mostly been digging in the schemastore repo, but the multi-schema sounds like the most orderly way of doing it. I'd hope it doesn't explode into complexity though 😂.

Do you think it's best if we compare against each manifest depending on the target build and trim the unwanted bits behind the scenes, or just stick to the Chrome one and just do the casting entirely within the plugin?

The build target isn't necessarily going to be chrome, firefox, or safari. For example, one of my extensions includes an ios target. We wouldn't know which validation format to use for that target.
Right now, I'm just using the chrome schema, and I provide the option to skip validation.
All the validation logic is in the file liked in the issue description.

I'm going to close this issue, there doesn't appear to be any solution, event after 2 years.


Fixes a bug with cacheFirst handler + maxAgeSeconds + CORS request

R: @addyosmani @gauntface
CC: @pbakaus
Fixes #691
This fixes a bug that would prevent a response used in a cache-first handler from properly triggering maxAgeSeconds-based expiration iff that response lacked a Date: header. A CORS-response without the Date: header specifically whitelisted via Access-Control-Expose-Headers could trigger this scenario, as @pbakaus encountered.
This also changes the method signature of the cacheWillMatch lifecycle callback to be async (i.e. return a Promise), since we now want to wait for it to complete before returning a cached response to the client (to ensure that any expiration that's necessary gets performed). That should (arguably) be considered a breaking change, since cacheWillMatch is part of the public interface.

Actually, as an alternative to changing cacheWillMatch to be async, I could keep things as-is without affecting the real-world behavior for most scenarios. The downside is that it could introduce some flakiness into the new test and require longer timeouts to reduce the risk of that flakiness. That might be an acceptable trade-off, though.

PTAL.

Smallest nit in the world. LGTM otherwise.


Fix #2551

Description of the pull request:
This pull request fixes #2551. As I said here, using a copy of attr instead of an empty array ensures all redundant classes are removed.
Fixes the following issues:
#2551
Is breaking:
It shouldn't break anything.

:+1:


Resource Landing Page: Consider Changing "Manage Access" Icon

Submitted by @ChristinaB:

I created a new resource, but it took too long to figure out how to share the resource with the group. Either I need a spend time asking someone how to do it, or it's not obvious, but working with the impatient busy user timeframe of 30-60 sec, I suggest it needs to be more obvious. I think the Collaborate page could use a 'Share my Resources' button that takes me back to the start of the workflow. This may be redundent, since I could use the dashboard, but if you keep the lock as the workflow to sharing, you may need a more obvious pathway via the Collaborate page.

Eventually I searched through each of the icons from my resource page and found the lock, which led to the Groups radio button. I think the lock for user access control is not as intuitive. I expected to share with the group with the arrow escaping the box icon (which is publish HydroShare, but is typically used to share). I suggest this be reconsidered.

@horsburgh Can this be closed?

The icon has been changed, and we are no longer using a radio button on the manage access modal window, but rather using a toggle between users and groups that is more obvious.  I'm going to close this one as I think it's consistent to manage all access to resource through this one interface. We may eventually want to enable managing access to multiple resources at once, but that is a separate issue (and I think may have already been added to the issue tracker. Closing.


No Tests were found

Could I be doing something wrong?

Did you try non-regression tests ?

I found the tests, but none of them passed.  See output:


Add rejection sampling method

Summary
Added sampler structs to implement different sampling methods, including rejection sampling, Closes #15
A sampler object for the method specified in the yaml file is created when it is parsed Closes #14
Rationale
Allows different sampling methods to be used to produce output from simulations. Including frugal rejection sampling and empirical supremum rejection sampling.
Implementation Details
Additional notes
Check before merging:

[ ] All discussions are resolved
[ ] New code is covered by appropriate tests
[ ] Tests are passing locally and on CI
[ ] The documentation is consistent with changes
[ ] Any code that was copied from other sources has the paper/url in a comment and is compatible with the MIT licence
[ ] Notebooks/examples not covered by unittests have been tested and updated as required
[ ] The feature branch is up-to-date with the master branch (rebase if behind)
[ ] Incremented the version string in Project.toml file

Codecov Report

Merging #21 (a26d061) into master (a1ac3ac) will decrease coverage by 1.06%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #21      +/-   ##
==========================================
- Coverage   89.07%   88.01%   -1.07%
==========================================
  Files           5        6       +1
  Lines         293      367      +74
==========================================
+ Hits          261      323      +62
- Misses         32       44      +12

Impacted Files
Coverage Δ

src/execution.jl
96.33% <100.00%> (-1.73%)
:arrow_down:

src/mpi_execution.jl
80.35% <100.00%> (-17.02%)
:arrow_down:

src/parameters.jl
100.00% <100.00%> (ø)

src/sampling.jl
100.00% <100.00%> (ø)

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 a1ac3ac...a26d061. Read the comment docs.


[WIP] Use rayon-cond for using multiple threads conditionally

This PR uses rayon-cond to conditionally use rayon threads (if the job is big enough to warrant the overhead).
Before this PR, code blocks are duplicated manually for serial and parallel code paths.
Implements issue #448

[x] Use rayon-cond for betweenness centrality
[x] Use rayon-cond in the remaining places where code was duplicated by hand

I don't see an obvious way to use CondIterator here
https://github.com/Qiskit/retworkx/blob/747a4f6dad37e1e0495a7425e133dcc54b6cd6b7/src/shortest_path/floyd_warshall.rs#L132
since it doesn't seem to cover this functionality.

Perhaps adding a threshold in some other places might be beneficial. Such as,
https://github.com/Qiskit/retworkx/blob/747a4f6dad37e1e0495a7425e133dcc54b6cd6b7/src/shortest_path/all_pairs_dijkstra.rs#L171-L211

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

42 of 42 (100.0%)  changed or added relevant lines in 4 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.01%) to 97.518%

Totals

Change from base Build<PHONE_NUMBER>:
-0.01%

Covered Lines:
10135

Relevant Lines:
10393

💛  - Coveralls

@mtreinish What do you think of merging this PR as it is? That is, it replaces previous uses of rayon with rayon-cond. But, it does not add any new uses of rayon/rayon-cond as suggested in https://github.com/Qiskit/retworkx/pull/450#issuecomment-919513145 . Those could be treated in a separate PR.

@mtreinish What do you think of merging this PR as it is? That is, it replaces previous uses of rayon with rayon-cond. But, it does not add any new uses of rayon/rayon-cond as suggested in #450 (comment) . Those could be treated in a separate PR.

Yeah I think this is fine as scoping for merging this PR. We can look at adding more uses in a follow-up PR, I think that makes sense because there will be some benchmarking needed to find the threshold values for running in multiple threads by default.

want to update the betweenness centrality function to use rayon-cond

Oh yeah. I missed that some how. I'll do that.


In log filter hook, bash substitution returning blank string

Using the following variables in an env_file in docker:
VALHEIM_LOG_FILTER_CONTAINS_Connected=Got connection SteamID
ON_VALHEIM_LOG_FILTER_CONTAINS_Connected='{read l; l=${l//*SteamID /}; msg="$l logged on"; curl...}'
the $l ends up being a blank string, so $msg only returns " logged on".
After troubleshooting, I found that read l does bring in the correctly populated string at first, but it's after the bash substitution expression l=${l//*SteamID /}; that the string becomes empty.
When I run bash on the docker image, I'm able to perform the same substitution successfully, resulting in $l containing only the numerical SteamID, but it appears to fail when being executed by the log hook.

Little more troubleshooting.
Whereas the env_file reads:
ON_VALHEIM_LOG_FILTER_CONTAINS_Connected=read l; id=${l//*SteamID /};...
Running bash on the docker image and using printenv shows the variable completely loses the substitution string:
ON_VALHEIM_LOG_FILTER_CONTAINS_Connected=read l; id='';...
So something does not like the ${l//*SteamID / reference even when passing the variable to the docker image in the first place. I've tried using escape characters, double quotes, and single quotes on that substitution expression, but nothing works.

I've figured it out. When using the env_file to pass in the variables, the substitution expression appears to get evaluated by the host machine before getting passed into the docker container.
My solution was to not use an env_file, rather define everything directly in the docker-compose.yaml. This requires some tweaking.
env_file version:
ON_VALHEIM_LOG_FILTER_CONTAINS_Connected=read l; id=${l//*SteamID /};...
docker-compose.yaml version:
- 'ON_VALHEIM_LOG_FILTER_CONTAINS_Connected=read l; id=$${l//*SteamID /};...'
Note the entire string must be surrounded by single quotes, and $ must be switched to $$.
@lloesche - I imagine this is the root cause to the handful of similar issues that are reported, such as #455 and $296. Since you were able to use the substitution expression in an env_file, might this be distro-dependent?

Just wanted to add, I have been using Ubuntu 22.04 if it does indeed turn out to be distro related

Same distro here.


[GH-679] ssl

@deviantony PR updated

@deviantony Could you indicate when this feature will become available? I will update the portainer doc now.

If the tests are OK, this will be integrated in the next release (1.12.5, should probably be released next week).

I made some tests, when using a self-signed certificate I've got a few errors in the Portainer logs:
2017/04/14 15:32:49 http: TLS handshake error from <IP_ADDRESS>:56570: tls: first record does not look like a TLS handshake
2017/04/14 15:32:50 http: TLS handshake error from <IP_ADDRESS>:56572: tls: first record does not look like a TLS handshake
2017/04/14 15:32:54 http: TLS handshake error from <IP_ADDRESS>:56576: tls: first record does not look like a TLS handshake

I've also tried to use a valid certificate/key pair generated from Letsencrypt and there is no error when using these.
I'm still investigating the issues related to self-signed certs.

@deviantony I'm able to reproduce that issue when SSL is enabled and I try to connect with http, not https - with both letsencrypt and self-signed certs

@adrianfalleiro Did you follow these instructions?

@030 I used these instructions to generate the SSL files and start Portainer with SSL support.
@adrianfalleiro yes, I searched a bit about these error messages and all that I found is that this is logged when using HTTP instead of HTTPS. Looks like my browser is somehow sending HTTP requests as I've got this error logs when I access https://my-ip:9000.

@deviantony Should something be fixed?

@030 Sorry I'm currently focused on another feature. I think that it's OK but I'd like to expend my tests a bit, I'll do that soon.

Thanks @030 :trophy: