Make rm_r able to delete read-only files on Windows

Previously seen in https://github.com/crystal-lang/crystal/pull/9348/files#diff-18f2fae0553160612c39c958c497aa76df5716785471f9b69e93d3b05f709e1eR67

Since this PR attempts to address "Recursive Deletions of Non-Writeable/Read-Only Files+Folders", I believe it can also address tempfiles(https://github.com/crystal-lang/crystal/pull/13178#issue-1619875940) too.

The pending tempfile spec for nonwritable folder is still a TODO.


Make new release for oauth2client 2.0.0 compatibility?

@nathanielmanistaatgoogle

:+1:

+1 the oauth2 change is breaking things for us too.

FYI I am working on this, releasing this project is no easy task.

Closed by #189


Signing Devices - Health Check and details screen

Task Description

This is very different to the health check of the Wallets backup.
Every 90 days from the last verification or usage (used for signing) of a particular SD, the user will get a message for them to check on that particular SD
The user can also do that independently by going to the details screen of a particular signing device (similar to Keepers/ Recovery Key in Hexa)
On the SD details screen they see the history of the SD setup, confirmation, usage for signing etc. The CTAs are "Health Check" like Confirm on Hexa, Change, (may have more in the future).
There is also settings and Learn More.
The Helth Check has triggered automatically if the user has come from the user message as we know that they are there to check the health of the SD. Else the user can initiate it manually.
On triggering Health Check, the user is prompted to either touch the device (if NFC enabled) or scan a QR (if QR based). Same as scanning NFC-enabled TapSigner.
The user can also say "I have it for sure" which means they don't want to scan but are sure they have it and it is working. A warning message comes and the user can even say OK on that. If so, the clock is reset to 90 days.

Task

[x] #685
[x] #686
[x] #687
[x] #688

Dependencies
Any dependencies for the task

For dev env the time should be in days to make it testable

For dev env the time should be in days to make it testable

@pratyakxx
For dev env the time should be in days to make it testable

Verified this issue on keeper app v 1.1.8(266)


Offer Tracking for Stacked Offers

I was testing out the stacked offer tracking that will be included in v1.6 and came across what may be a problem. It looks like the LineOfferConsumer class might be tracking the applied offers incorrectly.
As an example, in the basket app when  AbstractLine.consume() runs it should mark a line as consumed using LineOfferConsumer.consume() and passing the applicable offer. I think it should be storing the offer that consumed the items regardless of if the offer was exclusive or not. However, if the offer is exclusive it doesn't store the offer that consumed the line items.
This is for a test basket with an offer that should be applied to all three items in the line:
class Line(AbstractLine):

    def consume(self, quantity, offer=None):
        super(Line, self).consume(quantity, offer)
        print "offer------------------------->", offer
        print "exclusive--------------------->", offer.exclusive
        print "has_discount------------------>", self.has_discount
        print "quantity_with_discount-------->", self.quantity_with_discount
        print "has_offer_discount------------>", self.has_offer_discount(offer)
        print "quantity_with_offer_discount-->", self.quantity_with_offer_discount(offer)

Output:
offer-------------------------> Discount 123456
exclusive---------------------> True
has_discount------------------> True
quantity_with_discount--------> 3
has_offer_discount------------> False
quantity_with_offer_discount--> 0

If the offer is set to non-exclusive then the behavior is as expected:
offer-------------------------> Discount 123456
exclusive---------------------> False
has_discount------------------> True
quantity_with_discount--------> 3
has_offer_discount------------> True
quantity_with_offer_discount--> 3

I don't actually need stacked offers per se, I just need to know what offer was applied to the line as a whole. Maybe this is stored somewhere else when a whole line is consumed by the same offer?

I'll take a look at this asap.
The LineOfferConsumer interface could do with more extensive tests.


Upgrade npm dependencies

Upgrade webpack to v4
Upgrade axios to v0.18
Upgrade mocha to v5
Upgrade mocha-webpack v2 (beta)
Now using unminified-webpack-plugin to generate two different files (minified and non-minified)
All npm scripts should work as before
This PR does not include dist

Thanks @ankurk91 I'll merge this soon

@ankurk91 I'm not sure why this is failing CI. Can you take a look?

I was able to fix the travis ci by -
rm -rf node_modules
rm package-lock.json
npm install

This was the only way.
One more thing to notice that the package-lock.json file contained a malicious package<EMAIL_ADDRESS>This package was installed when i updated the webpack to v4.
The package has been updated. You can check it by running npm audit
Please also enable the GitHub inbuilt security alerts on repo. See how


JS type checking: recognize globalThis.vars set in functions

In Settings, enable JS/TS: Check JS
Create app.js

globalThis.uti = {}

function init() {
    globalThis.gigel = 1
}

function plugin(options) {

    console.log('ready on port', process.env.PORT)

    console.log(uti) // this works

    console.log(gigel) // Error: cannot find name

}

init()
plugin()

gigel should be recognized as a global variable, even though it was set in a function.

This kind of issue should be reported in TS repo.
Most likely same as https://github.com/Microsoft/TypeScript/issues/9998

Ok, thanks!


Failure with tonic when a proto file has only service definitions

If there is a proto file that has only service definitions like that ,
syntax = "proto3";

package b.a;

import "common.proto";

service BService {
  rpc Create(b.common.Request)
    returns (b.common.Response);

  rpc Get(b.common.Request)
    returns (b.common.Response);
}

the compilation will fail with this message .
b.a.rs: Tried to insert into file that doesn't exist.
A workaround is to add a type like that in the file.
enum TestEnum {
  ZERO = 0;
  ONE = 1;
  TWO = 2;
}

What happen I think is Prost doesn’t generate b.rs because it is empty so tonic cannot add its b.tonic.rs include to it.
Maybe it is related to issue #59.

We got this issue too, and similar found the walkaround by defining a test message. It will be great if we don't have to do that.
I also tried adding --include-imports in the buf generate command but still got the same error.

Hi, get my upvote.
The plugins are now unusable with buf when such a situation arises, because you cannot use the "single protoc invocation" trick mentioned in the readme. And using the no_imports flag of the tonic plugin is a nogo especially when using prost-crate.
So please make the plugins output insertion points in prost-crate's include file to have actual imports of the tonic generated files.

Hi. I have the some problem. Any idea when this could be resolved?

Hey @neoeinstein do you have some guidelines on this? Maybe a WIP branch somewhere?

FYI this fixes it https://github.com/neoeinstein/protoc-gen-prost/pull/58

Seems to work. :)


Deploy contract with customer version cause load assembly exception

Description
If user build contract with version number, then deploy contract to node it will throw load error.
Contract build command:
dotnet publish /p:Version=1.0.123 --configuration Release -o ~/Downloads/aelf

Error Message
[2018-12-15 09:13:48.291 - Error - Miner][40]: Mining failed with exception. System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.IO.FileNotFoundException: Could not load file or assembly 'AElf.Common, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null'. The system cannot find the file specified.
 ---> System.IO.FileNotFoundException: Could not load the specified file.
   at System.Runtime.Loader.AssemblyLoadContext.ResolveUsingEvent(AssemblyName assemblyName)
   at System.Runtime.Loader.AssemblyLoadContext.ResolveUsingResolvingEvent(IntPtr gchManagedAssemblyLoadContext, AssemblyName assemblyName)
   --- End of inner exception stack trace ---
   --- End of inner exception stack trace ---
   at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean wrapExceptions, Boolean& canBeCached, RuntimeMethodHandleInternal& ctor)
   at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean wrapExceptions, Boolean skipCheckThis, Boolean fillCache)
   at AElf.Runtime.CSharp.SmartContractRunner.RunAsync(SmartContractRegistration reg) in /home/ubuntu/workspace/AElfProject/AElf/AElf.Runtime.CSharp/SmartContractRunner.cs:line 75
   at AElf.SmartContract.SmartContractService.GetExecutiveAsync(Address contractAddress, Hash chainId) in /home/ubuntu/workspace/AElfProject/AElf/AElf.SmartContract/SmartContractService.cs:line 90
   at AElf.Execution.Execution.SimpleExecutingService.ExecuteOneAsync(Int32 depth, Transaction transaction, Hash chainId, IChainContext chainContext, Dictionary`2 stateCache, CancellationToken cancellationToken) in /home/ubuntu/workspace/AElfProject/AElf/AElf.Execution/Execution/SimpleExecutingService.cs:line 102
   at AElf.Execution.Execution.SimpleExecutingService.ExecuteAsync(List`1 transactions, Hash chainId, CancellationToken cancellationToken, Hash disambiguationHash, TransactionType transactionType) in /home/ubuntu/workspace/AElfProject/AElf/AElf.Execution/Execution/SimpleExecutingService.cs:line 41
   at AElf.Miner.Miner.Miner.ExecuteTransactions(List`1 txs, Boolean noTimeout, TransactionType transactionType) in /home/ubuntu/workspace/AElfProject/AElf/AElf.Miner/Miner/Miner.cs:line 216
   at AElf.Miner.Miner.Miner.Mine() in /home/ubuntu/workspace/AElfProject/AElf/AElf.Miner/Miner/Miner.cs:line 149
[2018-12-15 09:13:48.295 - Trace - BlockExecutor][40]: Current Event: MiningEnd ,IsLimitExecutionTime: True

Discuss with the team and think that this is an incorrect way to use version, so close it.


Convert README.txt to README.md files

Markdown is formatted nicer on GitHub.
Lets fix up all our README files to be markdown.

All of them? I'm not a fan of this. I primarily view the repo for local use, not github. In that case they are nicer as .txt files

Thanks to @unixb0y , the conversion has been done, but now they need a bit of clean up on the formatting. I think they should be formatted this way;

# CLBnFFMUX Fuzzer

## Purpose

Document nFFMUX family of CLB muxes

## Algorithm

## Outcome

```
CLB.SLICE_X0.AFFMUX.B0 30_00
CLB.SLICE_X0.AFFMUX.B0 30_00
CLB.SLICE_X0.AFFMUX.B0 30_00
... more lines ...
```

From manual O6 testing ;

```
X0 AOUTMUX O6
X0 BOUTMUX O6
```

which will then render like this;

CLBnFFMUX Fuzzer
Purpose
Document nFFMUX family of CLB muxes
Algorithm
Outcome
CLB.SLICE_X0.AFFMUX.B0 30_00
CLB.SLICE_X0.AFFMUX.B0 30_00
CLB.SLICE_X0.AFFMUX.B0 30_00
... more lines ...

From manual O6 testing ;
X0 AOUTMUX O6
X0 BOUTMUX O6

Ok @mithro if you want I’ll do that the next days. Didn’t know that was needed but it’s not a problem!
Sent with GitHawk

Btw, this can be closed now.

I think the bullet points still need to be fixed.

Oh right, I remember.

Btw @unixb0y are you student at Uni?

Yeah I am 😃

Pull Request is open 😊

It is likely that both the TimVideos and FOSSi Foundation will definately consider projects related to SymbiFlow for Google Summer of Code.

Oh, thanks for the hint! I've heard of "Google Summer of Code" but didn't think of participating myself, especially with this project.
Might have a look at it after my exams 😉


compilation fails

Hi,
Is is possible to prebuild c++ file without node present? That is - to have my working c++ project, and just to include nbind/nbind.h like in examples, and then just compile using g++ or windows studio and have a working exec? I'm trying to do this with visual studio 2015, but
NBIND_GLOBAL() { //explicit type is missing error
	function(sayHello); //identifier NBIND_FUNCTION is undefined error
}

there is also error with callback function...
I'm interested in doing it this way, since I plan to use node in embedded enviroment, and it complicated to cross compile.
Maybe I'm just missing something trivial?

Did I understand correctly that you want to compile an executable which does not use Node.js, and include nbind.h and an NBIND_GLOBAL block but not have them do anything?
In that case just put #ifdef NBIND_GLOBAL around the NBIND_GLOBAL block so the preprocessor will remove it. Then make sure BUILDING_NODE_EXTENSION is not defined in the Makefile or Visual Studio project. Normally node-gyp will add it.
If instead you're trying to cross-compile a Node.js addon without the Node.js headers installed, the addon won't work.

Sorry for I was not clear. I'm indeed trying to compile c++ executable that is going to be used by node. But, I must compile separately. I do not know what node version will it be.
Also, exec must be able to run even if node is down. That is - exec will be started by system, and node will be or may not be started at all.
The way it is now is - I have exec listening low level perifery, then map key stuff to mqtt, and then - node (if running) is listening mqtt. I was just wandering if this way (with nbind) is with a bit less overhead, and also - it would give me more flexibility. If my idea of using it is correct.
However - I'm not able to compile ANY of your examples (as of today). I do see errors I described, looking like there is no library, but my #include path is there and no problem with it. I can post screenshot if that would help.

nbind is currently meant for Node.js addons which are actually libraries loaded with dlopen or similar. It's designed to also allow code using nbind to be linked into an executable. In that case, however, it won't do anything. It's important to use #ifdef NBIND_GLOBAL and #ifdef NBIND_CLASS around such blocks, because they will be undefined when compiling a normal executable.
There's simply no standard mechanism for your executable to communicate with Node.
I'm interested in adding a new communication channel that would work by sending binary message in a standard format between C++ and JavaScript, and would somewhat fit your case. However, it's still in planning and unimplemented. Also, I was still planning the C++ code to run in the same process as Node.js. Your case sounds like it would involve some sort of inter-process communication. That's not entirely out of scope of nbind in the future, but in the near term there's nothing like that implemented.

If you have time and interest, I can help you extend nbind in the necessary ways, with the goal of adding the new code in the official repo. However, expect it to take several weeks of full-time work.

well, to be honest, I will use some other solution or approach, but I will send you my contact now, to see if I can help you in some way.

Thanks! I'll close this for now, then. A better solution will probably appear some day, but unfortunately not any time soon.


Escape key does not exit immediately

By pressing Ctrl+G, hh exits immediately but by pressing Esc it exits with ~1s delay.

Actually this is not a bug - when you hit Esc, terminal waits (for a while) for a next key to be pressed. Please hit Esc twice to exit hh immediately.


Update README URLs based on HTTP redirects

Created with https://github.com/dkhamsing/frankenstein
GitHub Corrected URLs

Was
Now

https://github.com/nosami/OmniSharpServer
https://github.com/OmniSharp/omnisharp-server

https://github.com/nosami/OmniSharpServer/wiki
https://github.com/OmniSharp/omnisharp-server/wiki

HTTPS Corrected URLs

Was
Now

http://tuxproject.de/projects/vim/
https://tuxproject.de/projects/vim/

http://www.python.org/download/releases/2.7.8/
https://www.python.org/download/releases/2.7.8/

Thanks :smiley:

:tada:


strange behavior router.go() or component ready() function

I have 2 components. Component A on route '/a' and component B on route '/b'. In comp B I have the code :
ready(){
   this.$route.router.go('/a') ;
}

Now in browser If I try to go from route '/a' to route '/b' I see both components A and B but in address line there is '/a'.
If code will be :
ready(){
   sleepTimeout(()=>{this.$route.router.go('/a') ;},0);
}

Everything will be ok and if I try to go from route '/a' to route '/b' I see only component A again on route '/a'.

I'm experiencing this in a component for catching an auth token from an OAUTH 2 redirect. the timeout solution works for now, but I'd rather not rely on window.setTimeout hacks all over.

This should work, but before it's fixed, the more proper way to do redirects is calling transition.redirect inside route hooks instead of ready.

Thanks for the quick response and the pointer!

@LuckyBlade Is this issue occurred when the url '/b' is directly accessed (not clicking v-link)?
I found the router._rendered flag here https://github.com/vuejs/vue-router/blob/dev/src/pipeline.js#L186 is still false at an initial route redirection in ready by default.
The transitionOnLoad would be nice option when you want to make transition successfully before all renderings are done.
const router = new VueRouter({
  history: true,
  saveScrollPosition: true,
  transitionOnLoad: true
})

@tejitak  Yes, it's occurred when directly accessed.
After setting "transitionOnLoad: true" in config everything works fine. Thank you.


Error occured during initiating recorder

Loaded up the example project from this repo, ran "yarn install", then hit an error, ran "pod install" in the ios folder to get past it, ran "yarn ios" to build and load up the sample app in the simulator.
Hitting record showed a popup asking for microphone permission.  I clicked OK, then the app threw the error below.  It created a file, but the file it created is only 28 bytes

LOG  Running "RNAudioRecorderPlayer" with {"rootTag":1,"initialProps":{}}
LOG  audioSet {"AVEncoderAudioQualityKeyIOS": 96, "AVFormatIDKeyIOS": "aac", "AVNumberOfChannelsKeyIOS": 2, "AudioEncoderAndroid": 3, "AudioSourceAndroid": 1}
WARN  Possible Unhandled Promise Rejection (id: 0):
Error: Error occured during initiating recorder

Version of react-native-audio-recorder-player
RNAudioRecorderPlayer (3.1.2)
Version of React Native
sorry buddy, I'm too much of a noob to know how to get this.. my podfile.lock file says this though:

React (0.64.1):

React-Core (= 0.64.1)

Platforms you faced the error (IOS or Android or both?)
ios
Expected behavior
Audio would be recorded into the file
Actual behavior
The file is empty
Steps to reproduce the behavior
Reprod in example project to eliminate as much PEBKAC as possible
errorLog.txt
Podfile.lock.zip

I tried a couple of different filenames.  The default cache path file is created and just 28 bytes.  I also tried passing in the documents directory and "test.m4a", this file was created as well but was only 28 bytes.  I hamfistedly tracked the error message down to here, FWIW:  https://github.com/hyochan/react-native-audio-recorder-player/blob/master/ios/RNAudioRecorderPlayer.swift#L222

Turns out I ran afoul of this old bug:  https://developer.apple.com/forums/thread/650741
Updating Xcode fixed it for me

@Debuggernaut ran into the same issue and the swift file that you pointed at helped me to solve the problem.
if you scroll to line 37 you'll see how the fileURL is determined:
func setAudioFileURL(path: String) {         if (path == "DEFAULT") {             let cachesDirectory = FileManager.default.urls(for: .cachesDirectory, in: .userDomainMask).first!             audioFileURL = cachesDirectory.appendingPathComponent("sound.m4a")         } else if (path.hasPrefix("http://") || path.hasPrefix("https://") || path.hasPrefix("file://")) {             audioFileURL = URL(string: path)         } else {             let cachesDirectory = FileManager.default.urls(for: .cachesDirectory, in: .userDomainMask).first!             audioFileURL = cachesDirectory.appendingPathComponent(path)         }     }
from that we can determine that a full file path must have the prefix of file:// , or alternatively if you wish to use the default cache directory with a custom file name you simply pass in the string of the file name (without directory).
the following two examples are working for me:
audioRecorderPlayer.startRecorder('customName.m4a')
audioRecorderPlayer.startRecorder(file://${RNFS.CachesDirectoryPath}/customName.m4a

I am still getting this issue with latest library version. what was the resolution for this issue? @hyochan

Also getting the same error in example https://github.com/hyochan/react-native-audio-recorder-player/tree/master/Example
@hyochan
simulator os: iOS 14.1
xcode version: Version 12.1

Hey @mdtechcs , there were a few problems I ran into:

I was using the wrong file path
Audio was misconfigured in my simulator
I coincidentally downloaded the simulator during a brief time when there was a bug that broke audio in it
Audio was screwed up on my whole desktop computer by an outdated audio plugin I had installed

I figured out most of these problems by getting a plain iOS Swift audio recording "Hello, World!" app running.  Once it was working, I was able to fix the react native audio library in my project pretty quickly

@mdtechcs Was your problem resolved?
I'm also facing the same issue despite following all the instructions and also trying to implement all the available solutions in previous issues


use provider with OSS installation?

So far I haven't found a way to specify the url of the oss installation that should be used.
Is this even possible or is this provider only for the cloud instances?

works fine for us. You can take a look at the terraform grafana-provider configuration and just put that in the secret with the connection details.
The secrets content could look like this:
 {
            "auth": "admin:<supersecret>",
            "url": "https://grafana.your.domain.org"
          }

Ah I thought it should go into the provider config directly, which confused me since it's not in the CRD spec for that.
Maybe it would help others to document this in the readme?

Now I understand, so I'm leaving a record.
First, we deploy provider-grafana.
# provider.yaml
apiVersion: pkg.crossplane.io/v1
kind: Provider
metadata:
  name: provider-grafana
spec:
  package: xpkg.upbound.io/grafana/provider-grafana:v0.6.0

kubectl apply -f provider.yaml

Now, create a JSON file in the format mentioned in the above conversation.
# grafana-secret.json
{
    "auth": "admin:a234!56gsd@deW",
    "url": "http://grafana.default.svc.cluster.local:8880"
}

Turn this JSON into a k8s secret.
kubectl create secret generic grafana-secret -n upbound-system --from-file=auth=grafana-secret.json

Make a ProviderConfig that uses this secret.
# providerConfig.yaml
apiVersion: grafana.crossplane.io/v1beta1
kind: ProviderConfig
metadata:
  name: grafana-config
spec:
  credentials:
    secretRef:
      key: auth
      name: grafana-secret
      namespace: upbound-system
    source: Secret

Now you can use it to create resources.
Thank you both for giving me hints to solve the problem.

Hey, I cannot seem to get it to work. Our GF instance resides under https://grafana.<domain>.com, I set up the PC like so:
---
apiVersion: v1
kind: Secret
metadata:
  name: grafana.cloud.token
  namespace: crossplane-system
type: Opaque
stringData:
  credentials: |
    {
      "cloud_api_key": "<token>",
      "url": "https://grafana.<domain>.com"
    }
---
apiVersion: grafana.crossplane.io/v1beta1
kind: ProviderConfig
metadata:
  name: grafana.cloud
spec:
  credentials:
    source: Secret
    secretRef:
      name: grafana.cloud.token
      namespace: crossplane-system
      key: credentials

And the dashboard:
---
apiVersion: oss.grafana.crossplane.io/v1alpha1
kind: Dashboard
metadata:
  name: test-dashboard
spec:
  forProvider:
    folderRef:
      name: test-folder
    configJson: |
      {
        "title": "Crossplane Test!",
        "uid": "crossplane"
      }
  providerConfigRef:
    name: grafana.cloud

But the provider still seem to hit the public GF instance:
$ k logs -n crossplane-system provider-grafana-<id> -f --tail=60
2024/03/28 15:18:05 [TRACE] Waiting 10s before next try
2024/03/28 15:18:15 [DEBUG] POST https://grafana.com/api/instances
2024/03/28 15:18:15 [DEBUG] GET https://grafana.com/api/instances/tomtom
2024/03/28 15:18:25 [TRACE] Waiting 10s before next try
2024/03/28 15:18:27 [WARN] WaitForState timeout after 2m0s
2024/03/28 15:18:27 [WARN] WaitForState starting 30s refresh grace period
2024/03/28 15:18:28 [DEBUG] Waiting for state to become: [success]
2024/03/28 15:18:28 [DEBUG] POST https://grafana.com/api/instances
2024/03/28 15:18:28 [DEBUG] GET https://grafana.com/api/instances/tomtom
2024/03/28 15:18:38 [TRACE] Waiting 500ms before next try
2024/03/28 15:18:38 [DEBUG] POST https://grafana.com/api/instances
2024/03/28 15:18:38 [DEBUG] GET https://grafana.com/api/instances/tomtom
2024/03/28 15:18:48 [TRACE] Waiting 1s before next try
2024/03/28 15:18:49 [DEBUG] POST https://grafana.com/api/instances
2024/03/28 15:18:49 [DEBUG] GET https://grafana.com/api/instances/tomtom
2024/03/28 15:18:59 [TRACE] Waiting 2s before next try
2024/03/28 15:19:01 [DEBUG] POST https://grafana.com/api/instances
2024/03/28 15:19:02 [DEBUG] GET https://grafana.com/api/instances/tomtom
2024/03/28 15:19:12 [TRACE] Waiting 4s before next try
2024/03/28 15:19:16 [DEBUG] POST https://grafana.com/api/instances
2024/03/28 15:19:16 [DEBUG] GET https://grafana.com/api/instances/tomtom
2024/03/28 15:19:26 [TRACE] Waiting 8s before next try
2024/03/28 15:19:34 [DEBUG] POST https://grafana.com/api/instances
2024/03/28 15:19:34 [DEBUG] GET https://grafana.com/api/instances/tomtom
2024/03/28 15:19:44 [TRACE] Waiting 10s before next try
2024/03/28 15:19:54 [DEBUG] POST https://grafana.com/api/instances
2024/03/28 15:19:54 [DEBUG] GET https://grafana.com/api/instances/tomtom
2024/03/28 15:20:04 [TRACE] Waiting 10s before next try
2024/03/28 15:20:14 [DEBUG] POST https://grafana.com/api/instances
2024/03/28 15:20:14 [DEBUG] GET https://grafana.com/api/instances/tomtom
2024/03/28 15:20:24 [TRACE] Waiting 10s before next try
2024/03/28 15:20:28 [WARN] WaitForState timeout after 2m0s
2024/03/28 15:20:28 [WARN] WaitForState starting 30s refresh grace period
2024/03/28 15:20:28 [DEBUG] Waiting for state to become: [success]
2024/03/28 15:20:28 [DEBUG] POST https://grafana.com/api/instances
2024/03/28 15:20:28 [DEBUG] GET https://grafana.com/api/instances/tomtom
2024/03/28 15:20:38 [TRACE] Waiting 500ms before next try

How do I configure it correctly?

I added an example here: https://github.com/grafana/crossplane-provider-grafana/blob/main/examples/oss.yaml


Fixed typo

Fixes Or Enhances N/A.
Make sure that you've checked the boxes below before you submit PR:

[x] Tests exist or have been written that cover this particular change.

Change Details:

Minor typo fix.

@go-playground/admins

Coverage remained the same at 100.0% when pulling 9f6c1cdebf290c5304ab9c9ef0f7103bde6dc823 on tobiassjosten:patch-1 into 884d31b8cad6a1ec877f2400d555924cea03bbea on go-playground:v9.


nixos/tailscale: make extraUpFlags work without authKeyFile

Description of changes
services.tailscale.extraUpFlags is valid only when services.tailscale.authKeyFile is set.
This change makes extraUpFlags work without authKeyFile.
extraUpFlags can be used to configure tailscale daemon and authKey is not an required option.
Fix https://github.com/nixos/nixpkgs/issues/276912

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/3897

@misuzu I'm sorry to bother you but is there a way to get this reviewed?


No support for dropping files?

Describe the bug
I'm in the process of porting a webapp into Tauri, and I need to drop files into a text editor (it's a CodeMirror instance). This worked without issue in the browser or in Electron, but Tauri does not trigger anything when a file is dropped. Even an ondrop on the topmost div does nothing.
To Reproduce

Implement an ondrop event on a Tauri app.
Try to drop a file from the filesystem onto the app
See it doesn't trigger anything

Expected behavior
The ondrop event should trigger.
Screenshots
n/a
Platform and Versions (required):

Operating System - Windows, version 10.0.19042 X64
Webview2 - 94.0.992.50

Node.js environment
  Node.js - 16.0.0
  @tauri-apps/cli - 1.0.0-beta.10
  @tauri-apps/api - 1.0.0-beta.8

Global packages
  npm - 7.10.0
  yarn - Not installed

Rust environment
  rustc - 1.55.0
  cargo - 1.55.0

App directory structure
/.git
/.history
/.vscode
/dist
/node_modules
/public
/src
/src-tauri

App
  tauri.rs - 1.0.0-beta.8
  build-type - bundle
  CSP - default-src blob: data: filesystem: ws: wss: http: https: tauri: 'unsafe-eval' 'unsafe-inline' 'self' img-src: 'self'
  distDir - ../dist
  devPath - http://localhost:3000
  framework - Vue.js

Did you get this to work eventually? My app won't receive any file drop on windows. The cursor simply turned into a disabled state.

@shenghan97 this works for me:
import { listen } from '@tauri-apps/api/event'

listen('tauri://file-drop', event => {
  console.log(event)
})

on Ubuntu 22 Tauri Dev mode latest with fileDropEnabled disabled so far I can run native dragEnter, dragOver, dragLeave and onDrop events perfectly in basic ReactJS app.. will try Tauri production and Windows later and post back here if they don't work.

I need to drag and drop the file into the webview to get the parseable file content, I am using the fs system works with the URL in the event callback now, does Tauri provide an existing API to achieve the same effect？

Does this support multiple files being drag and dropped onto the web view? And we'd get the full filepaths of each dropped file?

yes, the tauri://file-drop event shown above returns an array with all file paths.

If anyone stumble into this lost on why your dropzone input isn't working, just disable the fileDropEnabled in the windows section.

If anyone want to set it in rust code, just read this:
let window = tauri::WindowBuilder::from_config(
                    app,
                    WindowConfig {
                        label: "main".to_string(),
                        url: tauri::WindowUrl::App("index.html".into()),
                        file_drop_enabled: false, // notice this
                        ..Default::default()
                    },
                )
                .build()
                .unwrap();

Can confirm on OSX: disabling the fileDropEnabled in the tauri.config lets the window successfully process the file drag and drop instead.

Update for those who're using v2:
As in https://v2.tauri.app/reference/javascript/api/namespaceevent/
import { listen } from "@tauri-apps/api/event";

listen('tauri://drag-drop', event => {
  console.log(event)
})

in v2 you can set it in your tauri.conf.json by setting app.windows[0].dragDropEnabled to false


Collect expert 'question - expected answer' pairs for component development and testing

To develop, fine-tune, test and validate the NLQ component a set of "prompt scenarios", or defined pairs of questions with expected answers (including reference to sources that need to have been used/mentioned) is needed. Such a datasets also helps to clarify what is expected from the component, including e.g. context to be used and style of writing in the generated responses.

We have suggested Fenny/Thaisa to start collecting such scenarios in the upcoming months. Will monitor progress for that.


Add support for tslint 6.x

Currently the peer dependency of tslint: ^5.0.0 means you get this warning when using tslint 6.x

npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.

Can support for 6.x be added?

I just ran into this as well, when updating to Angular 10.

I just ran into this as well, when updating to Angular 10.

Same with me, I've encountered this when running v11 upgrade:
$> ng update @angular/core @angular/cli

have you tried to force (--force) and ignore the peer dependency warning? Would there be issues?

Same with me, I've encountered this when running v11 upgrade:
$> ng update @angular/core @angular/cli

have you tried to force (--force) and ignore the peer dependency warning? Would there be issues?

@rooby Yep, I'm currently doing that and haven't had any issues.

I got the same issue. Because of this issue, I am unable to update the angular version from 10 to 11. Is there any solution to fix this?


[5.1] Limit the supported ciphers and check key length

// cc @ibrasho, @ircmaxell, @paragonie-scott for review. :)

Pass '8bit' to mb_strlen()

@paragonie-scott Good catch. Thank you. :)

Can you add the check for openssl_encrypt() failure?

@ibrasho is right, openssl_decrypt() will return false on failure.

Can you add the check for openssl_encrypt() failure?

@ibrasho is right, openssl_decrypt() will return false on failure.

Yes, of course. I'll get that sorted in a second PR.


Renamed pre/postTask to pre/postScripts + load scripts inside the engine

Renaming pre/postTask to pre/postScript to make it easier to understand what it does. And making sure the CLI and API handles it the same way (fixes https://github.com/sitespeedio/sitespeed.io/pull/966)

In engine.js we should rename taskData to scriptData, and update the video scripts and test sample scripts accordingly.

I'm not 100% sure about loading scripts from disk in engine.js. The initial idea was for all setup like that (e.g. parsing and transforming cli args) to happen outside of the engine to keep the core classes from growing. Forcing the scripts to be a file on disk limits the flexibility of the engine as well. E.g. it can't be used in a web server where you post the data for the engine run. That's why I've eslint config for lib/core explicitly forbids use of the node 'fs' module. Using require to load and parse files sneaks under the radar…
That said, it's a good change over all. Update taskData to scriptData and we'll merge. Then we can revisit the loadPrePostScripts decision before cutting the next alpha release.

We can add a parsing module in front, we need to change the API to make it cleaner though, so that you don't have to massage the options before you use it? We have that kind of behaviour today for other scripts if I remember correctly. Maybe we can come up with a solution that fixes them both.

sooo should we merge this first and then change the name of input parameters as we discussed? or should we fix it all in a new PR?

Let's get this in first.

Hi,
I'm working on a new project and need your opinion on some issues, please take a look here http://thilotrathu.highspeedi.net/xycbcju
Good wishes<EMAIL_ADDRESS>


make sure 2 letter code list is in properties available for symbolizer for IAPP PMTile layer

we need to be able to reference:
         name = `IAPP Site - ${feature.props.site_id}: ${feature.props.species_on_site}`;
and not just
         name = `IAPP Site - ${feature.props.site_id}: ${feature.props.species}`;

can you also fix the zoom


Aave calculation methodology v1.0.0

Used as example only. Will manage the changes here https://github.com/ken-m-1/subgraphs/tree/master/subgraphs


fix(types): map uinteger to correct type

As part of investigating https://github.com/ibis-project/ibis/pull/6650 I noticed this mapping looked incorrect.

Thanks!


feat(): mysql

Adding mysql tutorial which includes: how to open mysql with 1.terminal, 2.browser, 3.workbench

Hi Paul


Update terragrunt.hcl

Ran Plan for project: main dir: . workspace: default
Show Output
time=2024-10-25T23:02:27Z level=warning msg=No double-slash (//) found in source URL /atlantis-data/repos/italorafaeltavares/Atlantis/25/default/module. Relative paths in downloaded Terraform code may not work.

Initializing the backend...

Initializing provider plugins...
- Finding latest version of hashicorp/null...
- Installing hashicorp/null v3.2.3...
- Installed hashicorp/null v3.2.3 (signed by HashiCorp)

Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # null_resource.example will be created
  + resource "null_resource" "example" {
      + id = (known after apply)
    }

  # null_resource.path will be created
  + resource "null_resource" "path" {
      + id = (known after apply)
    }

Plan: 2 to add, 0 to change, 0 to destroy.

─────────────────────────────────────────────────────────────────────────────

Note: You didn't use the -out option to save this plan, so Terraform can't
guarantee to take exactly these actions if you run "terraform apply" now.

:arrow_forward: To apply this plan, comment:atlantis apply -p main

:put_litter_in_its_place: To delete this plan and lock, click here
:repeat: To plan this project again, comment:atlantis plan -p main

Plan: 2 to add, 0 to change, 0 to destroy.

:fast_forward: To apply all unapplied plans from this Pull Request, comment:atlantis apply

:put_litter_in_its_place: To delete all plans and locks from this Pull Request, comment:atlantis unlock

atlantis apply

Ran Apply for 0 projects:

Locks and plans deleted for the projects and workspaces modified in this pull request:

dir: . workspace: default


picard-tools: 2.18.7 -> 2.18.9

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/picard-tools/versions.
These checks were done:

built on NixOS
Warning: no invocation of /nix/store/ah3v1x61gmj9lan8a3qvy3824lqvjdgi-picard-tools-2.18.9/bin/picard had a zero exit code or showed the expected version
0 of 1 passed binary check by having a zero exit code.
0 of 1 passed binary check by having the new version present in output.
found 2.18.9 with grep in /nix/store/ah3v1x61gmj9lan8a3qvy3824lqvjdgi-picard-tools-2.18.9
directory tree listing: https://gist.github.com/0972acdc51fe8a1cde470e4ab5e87993
du listing: https://gist.github.com/6a66b6723ce4887cd108678369b87360

meta.description for picard-tools is: '"Tools for high-throughput sequencing (HTS) data and formats such as SAM/BAM/CRAM and VCF."'.
cc @jbedo for testing.
This build is cached with Cachix. To use the cache follow these instructions:
One time setup in nixpkgs Git checkout:
cachix use r-ryantm
git remote add r-ryantm https://github.com/r-ryantm/nixpkgs.git

Test this build:
git fetch r-ryantm && git checkout 5ddbced87f793e986599f9c0bd64c571f6a79867 && nix-shell --pure -I nixpkgs=. -p picard-tools

Success on x86_64-darwin (full log)
Attempted: picard-tools
Partial log (click to expand)
building '/nix/store/95z6f052mijj7bzh3fj1yn5vnpbkp7cq-picard.jar.drv'...

trying https://github.com/broadinstitute/picard/releases/download/2.18.9/picard.jar
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   600    0   600    0     0   1149      0 --:--:-- --:--:-- --:--:--  1149
100 14.6M  100 14.6M    0     0  5050k      0  0:00:02  0:00:02 --:--:-- 6492k
building '/nix/store/m64v2dgp6x12phz9v0yqf1zmkzaj2c6i-picard-tools-2.18.9.drv'...
installing
/nix/store/kcvy6znsl7jhs6kk78vjvhw4i7w3lwhw-picard-tools-2.18.9

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: picard-tools
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnfree = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnfree = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Attempted: picard-tools
Partial log (click to expand)
building '/nix/store/imw99gbrwlx9a02xmzy8yngshf7kdjs1-picard.jar.drv'...

trying https://github.com/broadinstitute/picard/releases/download/2.18.9/picard.jar
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   600    0   600    0     0   1167      0 --:--:-- --:--:-- --:--:--  1165
100 14.6M  100 14.6M    0     0  2766k      0  0:00:05  0:00:05 --:--:-- 3496k
building '/nix/store/ypymhrsysid1wqp5fns6cgiy4i0s7271-picard-tools-2.18.9.drv'...
installing
/nix/store/ah3v1x61gmj9lan8a3qvy3824lqvjdgi-picard-tools-2.18.9


remove usages of codecov pypi version

Collecting pytest-github-actions-annotate-failures==0.1.8
Using cached pytest_github_actions_annotate_failures-0.1.8-py2.py3-none-any.whl (5.1 kB)
ERROR: Ignored the following versions that require a different python version: 3.0.0 Requires-Python >=3.8; 3.0.1 Requires-Python >=3.8; 3.0.2 Requires-Python >=3.8; 3.0.3 Requires-Python >=3.8; 3.0.4 Requires-Python >=3.8; 3.1.0 Requires-Python >=3.8; 3.1.1 Requires-Python >=3.8; 3.2.0 Requires-Python >=3.8; 3.2.1 Requires-Python >=3.8; 3.2.2 Requires-Python >=3.8; 6.0.0 Requires-Python >=3.8.1
ERROR: Could not find a version that satisfies the requirement codecov==2.1.12 (from versions: 2.1.13)
ERROR: No matching distribution found for codecov==2.1.12

This package doesn't seem to depend on codecov so you may looking at a different dependency

I fixed the hidden one which was causing this. thanks


Adding view transitions to the Starlight site

Hi @onrirr, this is the PR I offered on Discord.
Is it working for you?
I'm happy to help if you're still facing issues!

this appears to work, wonder what went wrong with mine. Thanks!


Merge conflict text decorations not getting properly cleared

Steps to reproduce:

Find a merge conflict

Press backspace twice on the line containing ======

Undo the changes

Repeat 2-3 a couple times

The text decorations will stack as shown below.

Also once the text decorations are stacked you can spread the text decoration to multiple lines like so.

Duplicate of #66


Feature/urllib python2 and 3

@rolando-ebi I know this was a pretty old PR. I was trying to see if I could bring it up to date and merge . The tests are not passing for python 2 so I won't merge. Do we need this?

@rolando-ebi I know this was a pretty old PR. I was trying to see if I could bring it up to date and merge . The tests are not passing for python 2 so I won't merge. Do we need this?

@rolando-ebi I know this was a pretty old PR. I was trying to see if I could bring it up to date and merge . The tests are not passing for python 2 so I won't merge. Do we need this?

I dont think we need this branch, pretty outdated at this stage


DATAJDBC-491 - Correctly combine schema- and table name

We now correctly combine schema and table name using separate SqlIdentifier objects instead of leaving the schema name as part of the table name. Previously, the concatenated name failed to resolve with quoted identifiers.

Related ticket: DATAJDBC-491.

That's merged.


FEAT: Updating python pdf download in template file for consistency

for julia, at present it is a disabled button

thanks @AakashGfude -- @arnavs @jlperla we will enable the Julia complete pdf download once we have compiled a Julia pdf file.


Deep Well has no "refilling" transition

https://kazetsukai.github.io/onetech/#663/Deep-Well
Lets take a look. Deep Well refills one charge every 5 minutes. There is transition that I believe is responsible for this behaviour - "-1_663.txt", but your parser have not parsed it for some reason.
Even tho it successfully parsed "-1_30.txt" - wild berry bush regrowing one berry every ten minutes, which looks the same to me.

Good spotting. We currently don't have "reverse one use" style transitions implemented and parsed. We hide transitions that come from and go to the same object. What you are seeing on the berry bush is a specific transition -1_279_LT.txt which goes from empty berry bush to berry bush. There is no transition from dry well to well, which is why that doesn't show up.

Thanks for reporting. Seems I went to far attempting to remove the junk transitions.

I'm not sure adding them straight back in is the right answer. Or rather, I want a large "+1" on the target in any "reverseUseTarget" transitions, so it is more obvious that what is happening is one "use" being recharged.

Alright, I'll reopen this to make those transitions clearer.

https://github.com/Kazetsukai/onetech/issues/46

Haha, closing this again since we have issue #46 now.


Refs #32191 -- Added Signer.sign_object()/unsign_object().

@apollo13 Thanks for checking edits :+1:

@apollo13 Thanks for checking edits :+1:


Session resume broken switching contexts

When an SSL's context is swtiched from a ticket-enabled context to
a ticket-disabled context in the servername callback, no session-id
is generated, so the session can't be resumed.
If a servername callback changes the SSL_OP_NO_TICKET option, check
to see if it's changed to disable, and whether a session ticket is
expected (i.e. the client indicated ticket support and the SSL had
tickets enabled at the time), and whether we already have a previous
session (i.e. s->hit is set).
In this case, clear the ticket-expected flag and create a new session
that has a session-id associated with it.
If the SSL hit (resumed) and switched to a ticket-disabled context,
assume that the resumption was via session-id, and don't bother to
create a new session.
Before this fix, the updated unit-tests in 06-sni-ticket.conf would
fail test #4 (server1 = SNI, server2 = no SNI).

(drive-by) Haven't though about the gist of it yet, but this needs a test.

Unit tests added.

ping?

According to GitHub, this PR needs a rebase.

Conflicting files
ssl/t1_lib.c
test/handshake_helper.h
test/ssl-tests/06-sni-ticket.conf.in
test/ssl_test_ctx.h

Rebased.

ping?

Rebased.

ping @openssl/cmo

@mattcaswell are you ok with this now?

Rebased.

ping @mattcaswell ?

ping @mattcaswell @openssl/omc ?

Ping @openssl/committers ?

Thank you!

Merged and closed.


Request

Thank you for creating this.  Could you include the Requester name in the area with the details so it can be copied.  I use it to cross reference my completed hits and am unable to highlight and copy from the main entry.  I know I can copy to clipboard, but that creates a lot of effort to acquire the requester name in my paste.  See sample below:
Requester:  Insert this line
Description: ---
Time allotted: ---
If you can't, that's OK, but it would be very helpful.
Thanks

Sure that sounds very doable. I wasn't even aware it's not possible to highlight requester's names, thanks for letting me know! I'll include this with the next minor release, which should be within the next few days.

Thanks, I appreciate it.

Added in 1.4.2: https://github.com/Anveio/mturk-engine/releases/tag/1.4.2 although I'd like to get requester names highlightable ASAP.

That will help very much, thanks!


OpenCV4 GAPI not being built when ADE is enabled

Describe the bug
Installing opencv4[ade] should lead to the OpenCV4 GAPI being built, but currently the cmake configuration step is disabling it from being built by passing "-DBUILD_WITH_GAPI=" instead of "-DBUILD_WITH_GAPI=ON".
The problem lies in the portfile.cmake. The cmake variable BUILD_opencv_gapi is being set correctly but where it should be getting used, we're instead using the variable DBUILD_opencv_gapi which is empty. See:
https://github.com/microsoft/vcpkg/blob/414bec05f2a97cfc0ddb8e22fd4635dfe2a20ab8/ports/opencv4/portfile.cmake#L378
Correcting the typo (to -DBUILD_opencv_gapi=${BUILD_opencv_gapi}) fixes the bug.
Environment

OS: Windows
Compiler: VS 16.9.4

To Reproduce
Steps to reproduce the behavior:

./vcpkg install opencv4[ade]:x64-windows
Check vcpkg/buildtree/opencv4/x64-windows-*/modules you should see that there is no gapi directory. Also you can check the vcpkg/buildtree/opencv4/config-x64-windows-out.log and see that the cmake configure command has "-DBUILD_opencv_gapi=".

Expected behavior
The modules directory should have a gapi directory. Furthermore the cmake configure command should have "-DBUILD_opencv_gapi=ON".

Hi @l90lpa
Thanks for reposting this issue.
This should be a mistake. I'll fix this soon.


Topiary reports a parsing error on a valid OCaml file

Bug Description
Topiary reports parsing errors on OCaml files manipulating first-class modules, even when they are valid OCaml files. The error does not seem to come from the OCaml tree-sitter grammar that parses such constructions just fine.
Expected Behaviour
Considering that tree-sitter parses such constructions correctly, I would expect Topiary to succeed in parsing, potentially failing elsewhere. As a user, I would expect that running Topiary on my file either succeeds (even if it leads to an odd formatting) or reports an error that does not have to do with parsing. For instance, something about an unsupported construct in the query file?
Environment

NixOS unstable with nixpkgs at commit 6060f12.
OCaml and tree-sitter from aforementioned nixpkgs.
Topiary on main as of December 1st, 2022, at commit 534b3d0.
tree-sitter-ocaml at commit cc26b1e.

Reproduction
My protocol is to create a file using first-class modules and to run OCaml, Topiary and tree-sitter on it, to show that both OCaml and tree-sitter agree that the file is syntactically correct while Topiary reports a syntax error. Each invocation of nix run github:nixos/nixpkgs/6060f12#<command> -- (or nix run <flake>#<command> -- in general) can be replaced by a direct invocation of <command> if you have it on your machine.

Create an ML file named issue106.ml with the following content:
module type FOO = sig val foo : string end
let create foo : (module FOO) = (module struct let foo = foo end)
module Foo = (val create "Issue #106")

Confirm that it is a valid OCaml file by running OCaml on it and not getting an error:
$ nix run github:nixos/nixpkgs/6060f12#ocaml -- issue106.ml

Run Topiary as of commit 534b3d0 on it. For instance, I would run:
$ commit=534b3d0
$ wget https://raw.githubusercontent.com/tweag/topiary/$commit/languages/ocaml.scm --output-document=ocaml.scm
$ nix run github:tweag/topiary/$commit -- --query ocaml.scm --input-file issue106.ml

Confirm that you get a parsing error, eg.:
Error: Parsing error between line 1, column 19 and line 1, column 30

Note that, as of 534b3d0, Topiary relies on tree-sitter/tree-sitter-ocaml as of commit cc26b1e:
https://github.com/tweag/topiary/blob/534b3d0ada72388e1fee50092c8fe83fc9dc649c/Cargo.lock#L687

Setup tree-sitter with this version of OCaml's grammar. For instance, I did the following:

Create an initial configuration for tree-sitter:$ nix run github:nixos/nixpkgs/6060f12#tree-sitter -- init-config
Saved initial configuration to ~/.config/tree-sitter/config.json

Check which directories tree-sitter uses for languages:$ cat ~/.config/tree-sitter/config.json
{
  "parser-directories": [
    "~/github",
    "~/src",
    "~/source"
  ],
  "theme": {
      ...

Create one of those directories, get in it and get the OCaml grammar:$ mkdir ~/source
$ cd ~/source
$ wget -qO- https://github.com/tree-sitter/tree-sitter-ocaml/archive/cc26b1e.tar.gz | tar xz

Check that tree-sitter sees the grammar in question:$ nix run github:nixos/nixpkgs/6060f12#tree-sitter -- dump-languages
scope: source.ocaml
parser: "~/source/tree-sitter-ocaml-cc26b1ef111100f26a137bcbcd39fd4e35be9a59/ocaml"
highlights: None
file_types: ["ml"]
content_regex: None
injection_regex: Some(^(ocaml|ml)$)

scope: source.ocaml.interface
parser: "~/source/tree-sitter-ocaml-cc26b1ef111100f26a137bcbcd39fd4e35be9a59/interface"
highlights: None
file_types: ["mli"]
content_regex: None
injection_regex: Some(^ocaml_interface$)

Run tree-sitter with this version of OCaml's grammar on the previous file:
$ nix run github:nixos/nixpkgs/6060f12#tree-sitter -- parse issue106.ml
(compilation_unit [0, 0] - [3, 0]
  (module_type_definition [0, 0] - [0, 42]
    name: (module_type_name [0, 12] - [0, 15])
    ...

In particular, note that the return code is 0 and that there is no error printed at the end of parsing.

Optionally, add an obvious OCaml error to issue106.ml and check that both OCaml (step 2.) and tree-sitter (step 7.) find it. For instance:
$ echo BONJOUR >> issue106.ml
$ nix run github:nixos/nixpkgs/6060f12#ocaml -- issue106.ml
File "./issue106.ml", line 4, characters 0-7:
4 | BONJOUR
    ^^^^^^^
Error: Syntax error
$ nix run github:nixos/nixpkgs/6060f12#tree-sitter -- parse issue106.ml
(compilation_unit [0, 0] - [3, 0]
  (module_type_definition [0, 0] - [0, 42]
    name: (module_type_name [0, 12] - [0, 15])
    ...
  (ERROR [3, 0] - [3, 7]))
issue106.ml	0 ms	(ERROR [3, 0] - [3, 7])

@GuillaumeGen suggested that I add a test case corresponding to this example file to see if we could reproduce the bug above. This is done in branch niols/issue106 at commit b78d9fe. Funnily enough, on this branch, cargo test does not exhibit the same behaviour as above, but rather:
failures:

---- input_output_tester stdout ----
thread 'input_output_tester' panicked at 'assertion failed: `(left == right)`

Diff < left / right > :
<module type FOO = sig val foo : string end
<let create foo : (module FOO) = (module struct let foo = foo end)
<module Foo = (val create "Issue #106")
>module type FOO = sigvalfoo : string
<

Apart from the fact that the diff looks a bit broken, it shows that there is no parse error! There might be a difference in the way Topiary calls the OCaml tree-sitter grammar during tests and with nix run ....

Good catch!
$ nix run github:tweag/topiary/$commit -- --query ocaml.scm --input-file issue106.ml --skip-idempotence
module type FOO = sigvalfoo : string

I guess this becomes more an issue of error reporting in Topiary. In that case, I think it should report a problem of idempotence (potentially a very severe one if the first pass yield unparseable results) and not a parse error.

Yes, the first pass of Topiary leads to an invalid Ocaml program.
The reason for this is that end is a keyword triggering an "end of indentation". Since neither val nor sig opened an indentation, the line module type FOO = sig val foo : string end lead to an "end of indentation" right before the end and made Topiary stop. The program after it is then invalid, both because sigval is not a keyword and because the end is missing. That's precisely the problems #110 solve.

Ideally, the error reporting should be improved here as well, like @Niols suggests. So if the second run causes a parse error, but not the first, then it isn't really a parse error, but a formatting error.


Error Encountered When Running ./scripts/code.sh on Mac

Description:
I'm encountering an issue while trying to develop the PearAI App on my Mac. After executing the command ./scripts/code.sh, I receive the following error:
Error: Request https://walrus-backup-app-sgqep.ondigitalocean.app/pearai-backup-server-api/gallery/publishers/ms-vscode/vsextensions/js-debug-companion/1.1.2/vspackage failed with status code: 500
When I attempt to access the URL directly through a browser, it returns:
{
"message": "An unexpected error occurred."
}
It seems likely that there is an issue with the resource URL. Could it be possible that the extensionsGallery service URL needs to be updated?
Environment:
macOS
Node.js v20.16.0
Yarn 1.22.22
Steps to Reproduce:
Clone the PearAI repository.
Execute the command ./scripts/code.sh on a Mac environment with the specified versions of Node.js and Yarn.
Observe the error message.
I would appreciate any guidance or updates on this issue. Thank you for your assistance.

I tried to remove the extensionsGallery configuration to allow the system to use the default official marketplace.
This solved my problem, but I am not sure if there might be any other impacts from this setting.


Implement commands for listing per-cluster CT/SNAT maps

Please see individual commits for more details.
Implement commands for listing per-cluster CT/SNAT maps

/test

/test

/test

Reflected on Nate's comment. And sorry, I added a commit that implements the missing flag string for from_tunnel (c.f. https://github.com/cilium/cilium/pull/24212#discussion_r1158217756).

Smoke test: https://github.com/cilium/cilium/issues/23812

/conformance-test

/test

/conformance-test-ipv6

/test

/test

/ci-datapath

Cilium Datapath is broken by cilium-cli change (https://github.com/cilium/cilium-cli/pull/1498) and now fixed by https://github.com/cilium/cilium/commit/0a984a71975d63228abfe23fd546f7798b834ef1. I think we don't have to re-run datapath test as it is not related to this change.

Rebasing on the master and re-running the CI.

/test

ConformanceK8sKind: https://github.com/cilium/cilium/issues/24622

/ipv4


Corporate Author Field

EBSCO Discovery Service API 18.7: Release Notes
EDS API supports the retrieval of the Corporate Author field in catalogs.
Please Note: The Corporate Author field functionality is only available upon request.

Done.


Status Bar Integration

I would like to contribute a Status Bar under SWOC'24.

It helps the user to know how much form is left for the last question.
Rainbow coloring effects.

Screenshot

@Aryainguz please assign this task to me under SWOC'24

assign this issue to me


Remove Flow interface with a Flow struct?

Flow interface started out small and seemed good, however, now that the project has progressed, it seems that hte interface could actually be removed and instead use a Flow struct?
Needs some thinking about...

There is now a Struct used instead
That struct now has a Payload channel
Payload is a interface with GetPayload() []Byte
and SetPayload([]byte)
Flow struct has a channel for ingress/egress.


Kyiv not a Kiev

Correct name of timezone for Kyiv is Europe/Kyiv, not a Europe/Kiev

Fixed in version 0.1.2


Unable to initialize contents from storage

This is a cool editor if the heroku app example is to be believed.
However, it doesn't work. I can't get it to render document contents from my store. I've tried replicating what you have in your example, and I've tried using other people's examples. After a couple of days, I think what I really need is for someone to update the documentation and clearly indicate

What sort of type needs to go into the value props. Neither the example, nor the source is using PropType validation so all I have are best guesses, which is clearly not good enough.
How to get from whatever you're storing in your DB, in very clear terms, to what the Wysiwyg editor component expects.

I cannot adequately express how disheartening it is to run across an impressive library like this only to run into an inability to use it because of documentation problems.
Please address this or give me some help.
Thanks very much for your time.

BK's stuff is cool. Last year we evaluated a few draft-js editors which seemed like good starting points. Ended up going with this one and successfully built a great custom editor inside WordPress with it. https://github.com/globocom/megadraft have a look if you haven't seen it yet.

Yeah, using the above editor instead. Thanks!


Syntax Error in Helper

When deploying to Heroku, this error comes up.
Important part:
def pdfjs_viewer(style:, pdf_url: nil, title: nil)

Full error:
/app/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.1/lib/active_support/dependencies.rb:274:in `require': /app/vendor/bundle/ruby/2.0.0/gems/pdfjs_viewer-rails-0.0.6/lib/pdfjs_viewer-rails/helpers.rb:4: syntax error, unexpected ',' (SyntaxError)
2015-11-17T19:29:45.025205+00:00 app[web.1]:       def pdfjs_viewer(style:, pdf_url: nil, title: nil)

remove the : at the end of style.
def pdfjs_viewer(style, pdf_url: nil, title: nil)

I had the same problem. The issue is that in my case I cannot easily modify the file provided by the gem since I have an automatic deployment in AWS: machine starts, git pull, bundle install, then rails runner something and it crashes because of this bug.

@Patrax this library requires at least Ruby 2.1


bfs algorithm implement

Implement on bfs algorithm

@himanisuthar  I want to work on this issue assing it to me


Allow subgraphs to be coiped/shared between indexers

At first glance, this feature would operate similarly to graphman copy but subgraphs could be sent to a foreign cluster.
The motivation behind this encompasses both:

mutual aid while indexing a given subgraph, and
marketplace dynamics with indexed data

Alternatively, an import/export pattern similar to pg_dump would also fit those needs.

I think @lutter has looked at the mechanics of copying a given subgraph previously, and if I recall correctly there were some potential challenges.
@chriswessels there are certainly those considerations, but I think the scope of this issue should focus on how such a transfer might be implemented in Graph Node, to transfer to a foreign db - those other things warrant discussion in a GIP / in the forum, and have cascading impact on other components (e.g. indexer components)

The main headache with import/export is defining a good format for transferring the data; it would be desirable to make that format usable for both dump/restore and for substreams. That format should be db agnostic, and live at the level of the subgraph schema, not the current db schema.
In my mind, the first order of business for this though is to address the network concerns around import/export; that might be as simple as "we don't care from the network side, we'll just treat this the same as people sharing SQL dumps" or more involved.

Bumping this. There is value to an operation like this although I understand it creates a shortcut for doing and verifying the sync work. I need this functionality to migrate very large subgraphs to a new database and integrate them correctly into the new primary shard. Below is the content of the feature request I was going to post before finding this existing request.
Context:
I asked this question on Discord:
I am building a new stack, and I want to at least copy the very largest subs I already have into a new database because they would take months to sync again. What is the most effective way to do this. Main restriction is the old database must die, it's nearly 4 years old and I am starting new. Dunno if its relevant but old database didn't have the right locale, whereas the new one does.
This is a pretty common use case we have discussed a few times on Indexer Office Hours. Vincent from Data Nexus has outlined how you would manually achieve the above - interested to have a feature in graphman that extend a copy operation to achieve this if folks think it is useful to a wider audience and if it's a realistic ask:
Unfortunately that will require some DB surgery. If you're going to do a sharded DB, you should be able to create a new shard with the correct locale, copy the data to the new shard using graphman copy, then you'll have to input the new shard config into the new stack graph node config, manually insert deployment details into the primary, and then set the counter in the primary to one higher than your largest sgd number. We really need a graphman command for dumping subgraph data so it can be imported into another disconnected DB...


What Can I do about Deathlog?

Anytime I Try To Open The Mod It Always Says " An Error Startup Prevented Minecraft From Starting" What Caused It Was Deathlog. I Have Been Trying To Play For A Week Now And Nothing. Any Help?

Without a crash report I can't really help you here - this could be caused by literally anything
Cheers

Have you since made any new discoveries about this issue?


[DO-NOT-MERGE] Increase the number of retries

What changes were proposed in this pull request?
See if it makes the situation better.
Why are the changes needed?
Does this PR introduce any user-facing change?
How was this patch tested?

Test build #137054 has started for PR 32086 at commit 1deb43a.

Test build #137057 has started for PR 32086 at commit d274e25.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/41631/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/41631/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/41631/

Kubernetes integration test unable to build dist.
exiting with code: 1
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/41635/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/41635/

Test build #137059 has started for PR 32086 at commit 805ce30.

Test build #137054 has finished for PR 32086 at commit 1deb43a.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test build #137063 has started for PR 32086 at commit 254d758.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/137054/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/41637/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/41637/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/41637/

Kubernetes integration test unable to build dist.
exiting with code: 1
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/41641/

Test build #137057 has finished for PR 32086 at commit d274e25.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/41641/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/137057/

Test build #137059 has finished for PR 32086 at commit 805ce30.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/137059/

Test build #137063 has finished for PR 32086 at commit 254d758.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/137063/

Test build #137109 has started for PR 32086 at commit 0a3d717.

Test build #137111 has started for PR 32086 at commit 2649705.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/41687/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/41687/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/41687/

Test build #137112 has started for PR 32086 at commit c60c354.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/41689/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/41689/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/41689/

Kubernetes integration test unable to build dist.
exiting with code: 1
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/41690/

Test build #137109 has finished for PR 32086 at commit 0a3d717.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/137109/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/41690/

I'll take a look in my own repo. This seems not specific to Apache Spark anyway.

Test build #137111 has finished for PR 32086 at commit 2649705.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/137111/

Test build #137112 has finished for PR 32086 at commit c60c354.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/137112/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/41691/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/41691/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/41691/


Autosubmit-GUI standalone documentation

In GitLab by @manuel-g-castro on Aug 18, 2022, 12:22
I was trying to configure ReadTheDocs of the autosubmit-gui, which we had agreed it deserved its own documentation. Unfortunatelly, ReadTheDocs requires the project to be public in order to see the repo.

In GitLab by @manuel-g-castro on Aug 25, 2022, 13:08
I created a new repo with the documentation of the GUI that was under autosubmit's main repo. Along side with it, a new branch add-documentation was created here with the configuration of the documentation as a submodule.
The docs can be seen here. Images were not pushed to the repo, that is why no image can be seen at the pages. I am still working on how make ReadTheDocs fetch images.


RuntimeError: Jacobian mismatch for output 0 with respect to input 0

When I run check_gradient_dconv( ), it will return this RuntimeError message. When I looked into the def gradcheck( ), I found that the output of analytical and numerical is different. Can you give me any advice to solve this Problem?
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
error in deformable_col2im_cuda: too many resources requested for launch
Traceback (most recent call last):
File "/home/wanghanzhang/PycharmProjects/HANZHANG_WANG_LAB2/ls.py", line 661, in
check_gradient_dconv()
File "/home/wanghanzhang/PycharmProjects/HANZHANG_WANG_LAB2/ls.py", line 437, in check_gradient_dconv
eps=1e-6, atol=1e-5, rtol=1e-3, raise_exception=True))
File "/usr/local/lib/python2.7/dist-packages/torch/autograd/gradcheck.py", line 205, in gradcheck
'numerical:%s\nanalytical:%s\n' % (i, j, n, a))
File "/usr/local/lib/python2.7/dist-packages/torch/autograd/gradcheck.py", line 185, in fail_test
raise RuntimeError(msg)
RuntimeError: Jacobian mismatch for output 0 with respect to input 0,
numerical:tensor([[ 0.0713,  0.0000,  0.0000,  ...,  0.0000,  0.0000,  0.0000],
[ 0.0000,  0.0000,  0.1671,  ...,  0.0000,  0.0000,  0.0000],
[ 0.0000,  0.3468,  0.0345,  ...,  0.0000,  0.0000,  0.0000],
...,
[ 0.0000,  0.0000,  0.0000,  ...,  0.0000, -0.2030, -0.2692],
[ 0.0000,  0.0000,  0.0000,  ...,  0.0000, -0.1620, -0.4735],
[ 0.0000,  0.0000,  0.0000,  ...,  0.0000,  0.0000, -0.1104]],
dtype=torch.float64)
analytical:tensor([[0., 0., 0.,  ..., 0., 0., 0.],
[0., 0., 0.,  ..., 0., 0., 0.],
[0., 0., 0.,  ..., 0., 0., 0.],
...,
[0., 0., 0.,  ..., 0., 0., 0.],
[0., 0., 0.,  ..., 0., 0., 0.],
[0., 0., 0.,  ..., 0., 0., 0.]], dtype=torch.float64)

I have the same issue as well.

me too,how to slove the problem?

Sorry for the late reply.
error in deformable_col2im_cuda: too many resources requested for launch could be solved by https://github.com/chengdazhi/Deformable-Convolution-V2-PyTorch/issues/15#issuecomment-473521698
This error caused the operator failed so the gradient check won't pass.


How the component events the mouse wheel zoom

"A webpage has a k-line chart on it, which can support mouse wheel zooming. How is it implemented? Is it a function that comes with Windows webview2 or a function that comes with the" webview_flutter "component? I would like to know about its implementation.". thank you

The mouse wheel event works well on this W3CSchools test page.
But please make sure you have already CLICKed on the webview before using mouse wheel event.
Before you click the webview, the focus is owned by flutter, so the webview won't receive any keyboard / mouse events .

I wonder if webview2 for Windows supports zooming

Hmm... webview2 can set zoom factor
but not support zooming by ctrl+wheel
and because this package is not integrated into flutter view hierarachy,
so you cannot listen key/mouse event in dart (but possible in js code),
so it's not possible to listen wheel event and set zoom factor.

ok Thanks

Sorry, I'm now correcting my anwser:
webview2 support ctrl+wheel to zooming (you should CLICK webview2 first)
and it also support developer to set zoom factor (even though official webview_flutter package not support this API)

Okay, let me take a look at the official API for webview2. Thank you


Locksmith file - shortcut (.lnk)

Description of the new feature / enhancement
With a shortcut, open the locksmith window to the source file of shortcut when we click on "What using this file ?" of the locksmith feature. In example : With the shortcut "Minercraft.exe.lnk" the locksmith windows open to "Minecraft.exe" (the source file)

Scenario when this would be used?

If a already used file is in our shortcut
When a application (Minecraft) is always used even if it is closed (bug) and the only way to open it is to end task.

Supporting information
No response

Can you explain a bit more how you get into the state of Minecraft is locking a file but this tool can't detect it?  The tool isn't aimed to replace Task manager.
the LNK file could be in use which is when you'd want this tool as you'd want to terminate what ever app has a lock on the shortcut.

/needinfo

FeedBack:
https://user-images.githubusercontent.com/54465233/203761409-12bd74f3-76ed-4b40-b0dd-e8b7ef2366df.mp4
This is a example of how locksmith can not understand shortcut .

come on i provided new activity. please review!!!!!


Add the Azure Boards badge to the README

Add the Azure Boards badge for the board used to track the work for this repository. Fixes AB#2. See the status badge configuration documentation for more information.

Push origin merge

Jump button


Next and Prev Slide Image Preview

I want To show next slider image preview and with it there should be next and prev buttons. when i hover on prev button previous images should take place on that next image preview. then when i hover out next image shouuld return.

Do you want to ask a question? Are you looking for support? The Swiper forum and Stack Overflow are the best places for getting support

Please, don't use GitHub issues for questions


"Error" in ( Responsive Web Design: Learn CSS by building a set of Colored Markers in Italian Language)

Describe the Issue
I was doin' the Responsive Web Design: Learn CSS by building a set of Colored Markers (with Italian translation) and I realized that there is a "error" about the Steps.. Im actually in Step 27 but there's wrote Step 37.
I dont know if this is the right way to "report" a bug/issue... then first of all sorry for the disturb..
and I hope u a nice day!
Affected Page
https://www.freecodecamp.org/italian/learn/2022/responsive-web-design/learn-css-colors-by-building-a-set-of-colored-markers/step-27
Your code
Step 37
Now that you have the primary RGB colors, it's time to combine them.

Per la funzione rgb nella regola .container, imposta rosso, verde e blu al valore massimo di 255.

Expected behavior
Step 27
Now that you have the primary RGB colors, it's time to combine them.
Per la funzione rgb nella regola .container, imposta rosso, verde e blu al valore massimo di 255.
Screenshots
No response
System

Device: [e.g. iPhone 6, Laptop]
OS: [e.g. iOS 14, Windows 10, Ubuntu 20.04]
Browser: [e.g. Chrome, Safari]
Version: [e.g. 22]

Additional context
No response

Thanks to you for your availability!
Have a nice day

The string in crowdin has been changed, then it will go through the usual pipeline. Thank you for reporting this, you can also use the translation-discussion channel in Discord if you find other translation mistakes, or if you want to partecipate in the tranlsation.


Affecting one picker from another

Not an 'issue' but a cry for help.. How to seed one picker from another?
var endDate = $('.end-date .datepicker').pickadate({
    formatSubmit: 'yyyy-mm-dd'
})

// Would like date from startDate copied over to endDate on change
var startDate = $('.start-date .datepicker').pickadate({
    formatSubmit: 'yyyy-mm-dd',
    onSet: function(endDate) {
        console.log('Want to set endDate to - ' + this.get('select', 'yyyy/mm/dd'));
        endDate.set('select', this.get('select')); // This line is wrong :-(
    }
})

Hi there.
Does this.get('select').obj help? It normally returns a Date object so it should be a valid input fot setting select.

Sorted! Thanks! I used that tip and also added this line..
 var picker_end_date = endDate.pickadate('picker');

Working looks like this...
// End date
var endDate = $('.end-date .datepicker').pickadate({
    formatSubmit: 'yyyy-mm-dd'
});
var picker_end_date = endDate.pickadate('picker');

// Start date, onset change enddate
var startDate = $('.start-date .datepicker').pickadate({
    formatSubmit: 'yyyy-mm-dd',
    onSet: function(endDate) {
        //console.log('Want to set endDate to - ' + this.get('select', 'yyyy/mm/dd'));
        picker_end_date.set('select', this.get('select').obj);
    }
})


ddclient: 3.8.3 -> 3.9.0

Motivation for this change
This release fixes cloudflare protocol usage by switching to a new api
version. See release notes: https://sourceforge.net/p/ddclient/news/2018/08/ddclient-390-released.
Partially fixes #26691.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Yes, the old version was failing to update cloudflare without JSONAny. So I added build input as suggested in the linked issue, but then I got an error regarding usage of an old API. After upgrade, I tried to remove JSONAny and it worked without any issues. Here is the exact packageOverride I have in my configuration:
      nixpkgs.config.packageOverrides = super: let self = super.pkgs; in {
        ddclient = super.ddclient.overrideAttrs (
          oldAttrs: rec {
            name = "ddclient-${version}";
            version = "3.9.0";
            src = super.fetchurl {
              url = "mirror://sourceforge/ddclient/${name}.tar.gz";
              sha256 = "0fwyhab8yga2yi1kdfkbqxa83wxhwpagmj1w1mwkg2iffh1fjjlw";
            };
            patches = [];
            buildInputs = oldAttrs.buildInputs ++ (with super.perlPackages; [ DataValidateIP ]);
          }
        );
      };

@c0bw3b according to ddclient changelog, they are switch from JSON::Any to JSON:PP in the new release. This explains why it works without having JSONAny package in buildInputs.

Ah! Nice catch. I guess we should add JSONPP to the build inputs list of Perl packages then?

For some reason, cloudflare updates work for me without this dependency, but since it's clearly listed in README file, I added it to build inputs as well.

@GrahamcOfBorg build ddclient

Would this be a candidate for a backport to 18.09?


[BUG] Azure Cosmos SDK for Java - Closing GlobalEndpointManager does not actually stop the scheduler from running scheduled tasks

Describe the bug
After calling close() on the CosmosClient, the thread associated with the GlobalEndpointManager continues running for over an hour. This leads to resource leaks, as the thread persists and executes tasks when it should have been terminated and garbage collected long after the client was closed.
Observed Behavior:

Logs from RxDocumentClientImpl confirm the close() method was called.
Logs indicate GlobalEndpointManager was closed in that process(Closing Global Endpoint Manager logged).
GlobalEndpointManager.close() also called scheduler.dispose() which should release all resources and reject any new tasks from being executed
Despite the closure process, the thread continues executing tasks from startRefreshLocationTimerAsync() for more than an hour after the close() method is called.

Impact:
This behavior results in lingering threads consuming resources unnecessarily, potentially leading to resource exhaustion or unexpected behavior in applications managing multiple CosmosClient instances.
Exception or Stack Trace
See attached logs in CSVcosmos_sdk_global_endpoint_manager_not_closing.csv
To Reproduce

Initialize CosmosClient
Replicate some FeedRanges either from continuationToken or from beginning, probably doesn't matter
call client.close()
Observe GlobalEndpointManager does not get closed right away.

Code Snippet
Add the code snippet that causes the issue.
See RxDocumentClientImpl.close() and GlobalEndpointManager.close() and GlobalEndpointManager.startRefreshLocationTimerAsync()
Expected behavior
GlobalEndpointManager and its scheduler closes properly and stop utilizing any thread or resources as soon as the client has been closed.
Screenshots
Setup (please complete the following information):

OS: [e.g. iOS] MacOS 14.6.1
IDE: [e.g. IntelliJ] IntelliJ
Library/Libraries: com.azure:azure-cosmos:4.64.0
Java version: [e.g. 8] openjdk 17.0.7
App Server/Environment: N/A
Frameworks: N/A

If you suspect a dependency version mismatch (e.g. you see NoClassDefFoundError, NoSuchMethodError or similar), please check out Troubleshoot dependency version conflict article first. If it doesn't provide solution for the problem, please provide:

verbose dependency tree (mvn dependency:tree -Dverbose)
exception message, full stack trace, and any available logs

Additional context
Add any other context about the problem here.
Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

[x ] Bug Description Added
[x ] Repro Steps Added
[x ] Setup information Added

cc: @xinlian12 @kushagraThapar

@tvaron3 / @jeet1995 please take a look at this issue, thanks!

Hi team, I realize the holidays are almost upon us. Can someone provide a quick timeline on whether this has been accepted as a bug and when we might expect it to be resolved?
From our end, this is a major blocker that is preventing us from migrating our Cosmos service to a multi-tenant environment due to this thread not being properly closed and leading to resource leak.

@fivetran-kevinzhao apologies, but we have been running short on resources and actively investigating other high priority issues. We will pick this up soon Kevin and will provide an update to you!

@fivetran-kevinzhao - we have some ideas on what the fix should be. The change being targeted shouldn't take upwards of a week but will update with a release schedule on Monday (12/16/2024).

@jeet1995 thank you all for the update!


Removed creation of offer instances by player

This PR changes offers to stop the creation of offer instances by player, and instead uses offer version instances, which are only one per offer version.

Coverage increased (+0.6%) to 89.476% when pulling b57380a7e1f4e4bad2914f3f466a6f7781b7f94a on feature/offerVersions into d3e51a9031bd731728308beb3f3af581650766b7 on master.