Authentication error

This request is not authorized to perform this operation.
This storage account's 'Firewalls & virtual networks' settings may be blocking access to storage services. Try adding your client IP address to the firewall exceptions, or by allowing access from 'all networks' instead of 'selected networks'. To learn more about Azure Storage firewalls and virtual networks, visit http://go.microsoft.com/fwlink/?LinkId=845443.
Error Details:
{
"name": "RestError",
"code": "AuthorizationFailure",
"statusCode": 403,
"request": {
"streamResponseStatusCodes": {},
"url": "https://pttgcshare.blob.core.windows.net/?comp=list&include=metadata",
"method": "GET",
"headers": {
"_headersMap": {
"x-ms-version": {
"name": "x-ms-version",
"value": "2023-01-03"
},
"accept": {
"name": "Accept",
"value": "application/xml"
},
"user-agent": {
"name": "User-Agent",
"value": "Microsoft Azure Storage Explorer/1.35.0 (win32) azsdk-js-storageblob/12.15.0 (NODE-VERSION v20.14.0; Windows_NT 10.0.22631)"
},
"x-ms-client-request-id": {
"name": "x-ms-client-request-id",
"value": "07b35077-4132-4b76-a3e3-a067bfb7a051"
},
"authorization": {
"name": "authorization",
"value": "Bearer JSON Web Token Redacted"
}
}
},
"withCredentials": false,
"timeout": 0,
"keepAlive": true,
"decompressResponse": false,
"requestId": "07b35077-4132-4b76-a3e3-a067bfb7a051"
},
"response": {
"request": {
"streamResponseStatusCodes": {},
"url": "https://pttgcshare.blob.core.windows.net/?comp=list&include=metadata",
"method": "GET",
"headers": {
"_headersMap": {
"x-ms-version": {
"name": "x-ms-version",
"value": "2023-01-03"
},
"accept": {
"name": "Accept",
"value": "application/xml"
},
"user-agent": {
"name": "User-Agent",
"value": "Microsoft Azure Storage Explorer/1.35.0 (win32) azsdk-js-storageblob/12.15.0 (NODE-VERSION v20.14.0; Windows_NT 10.0.22631)"
},
"x-ms-client-request-id": {
"name": "x-ms-client-request-id",
"value": "07b35077-4132-4b76-a3e3-a067bfb7a051"
},
"authorization": {
"name": "authorization",
"value": "Bearer JSON Web Token Redacted"
}
}
},
"withCredentials": false,
"timeout": 0,
"keepAlive": true,
"decompressResponse": false,
"requestId": "07b35077-4132-4b76-a3e3-a067bfb7a051"
},
"status": 403,
"headers": {
"_headersMap": {
"content-type": {
"name": "content-type",
"value": "application/xml"
},
"server": {
"name": "server",
"value": "Microsoft-HTTPAPI/2.0"
},
"x-ms-request-id": {
"name": "x-ms-request-id",
"value": "3c7c31c9-801e-003e-5ad7-0581bd000000"
},
"x-ms-client-request-id": {
"name": "x-ms-client-request-id",
"value": "07b35077-4132-4b76-a3e3-a067bfb7a051"
},
"x-ms-error-code": {
"name": "x-ms-error-code",
"value": "AuthorizationFailure"
},
"date": {
"name": "date",
"value": "Fri, 13 Sep 2024 12:18:28 GMT"
},
"content-length": {
"name": "content-length",
"value": "246"
}
}
},
"bodyAsText": "AuthorizationFailureThis request is not authorized to perform this operation.\nRequestId:3c7c31c9-801e-003e-5ad7-0581bd000000\nTime:2024-09-13T12:18:29.0835032Z",
"parsedBody": {
"message": "This request is not authorized to perform this operation.\nRequestId:3c7c31c9-801e-003e-5ad7-0581bd000000\nTime:2024-09-13T12:18:29.0835032Z",
"code": "AuthorizationFailure"
},
"parsedHeaders": {
"errorCode": "AuthorizationFailure",
"content-type": "application/xml",
"server": "Microsoft-HTTPAPI/2.0",
"x-ms-request-id": "3c7c31c9-801e-003e-5ad7-0581bd000000",
"x-ms-client-request-id": "07b35077-4132-4b76-a3e3-a067bfb7a051",
"date": "Fri, 13 Sep 2024 12:18:28 GMT",
"content-length": "246"
}
},
"details": {
"errorCode": "AuthorizationFailure",
"content-type": "application/xml",
"server": "Microsoft-HTTPAPI/2.0",
"x-ms-request-id": "3c7c31c9-801e-003e-5ad7-0581bd000000",
"x-ms-client-request-id": "07b35077-4132-4b76-a3e3-a067bfb7a051",
"date": "Fri, 13 Sep 2024 12:18:28 GMT",
"content-length": "246",
"message": "This request is not authorized to perform this operation.\nRequestId:3c7c31c9-801e-003e-5ad7-0581bd000000\nTime:2024-09-13T12:18:29.0835032Z",
"code": "AuthorizationFailure"
}
}

The storage account you are trying to connect to may have certain network security settings that restrict traffic. Review your storage account's network settings or contact your admin for help.
If you are unable to resolve your issue, please provide additional information as outlined by our bug template.

@craxal, I believe I've hit the same/similar issue. I'm using my Entra ID account in the Azure Portal and in the Azure Storage Explorer. In the Azure Portal I can view the storage account and its blob containers without issue.
Here are the network settings for that storage account:

The only thing that looks suspicious is the "Microsoft network routing" option. Is it possible that the explorer can't deal with accounts configured this way? I'm running the explorer from a machine connected to corpnet, if that helps in any way.
Here's the error I'm seeing:
This request is not authorized to perform this operation.

This storage account's 'Firewalls & virtual networks' settings may be blocking access to storage services. Try adding your client IP address to the firewall exceptions, or by allowing access from 'all networks' instead of 'selected networks'. To learn more about Azure Storage firewalls and virtual networks, visit http://go.microsoft.com/fwlink/?LinkId=845443.

Error Details:
{
  "name": "RestError",
  "code": "AuthenticationFailed",
  "statusCode": 403,
  "request": {
    "streamResponseStatusCodes": {},
    "url": "https://azurelinuxtmpsrc.blob.core.windows.net/?comp=list&include=metadata",
    "method": "GET",
    "headers": {
      "_headersMap": {
        "x-ms-version": {
          "name": "x-ms-version",
          "value": "2017-04-17"
        },
        "accept": {
          "name": "Accept",
          "value": "application/xml"
        },
        "user-agent": {
          "name": "User-Agent",
          "value": "Microsoft Azure Storage Explorer/1.35.0 (win32) azsdk-js-storageblob/12.15.0 (NODE-VERSION v20.14.0; Windows_NT 10.0.19045)"
        },
        "x-ms-client-request-id": {
          "name": "x-ms-client-request-id",
          "value": "e2beaf5e-4603-4a40-b92d-1a0d8326b8fd"
        },
        "authorization": {
          "name": "authorization",
          "value": "Bearer JSON Web Token Redacted"
        }
      }
    },
    "withCredentials": false,
    "timeout": 0,
    "keepAlive": true,
    "decompressResponse": false,
    "requestId": "e2beaf5e-4603-4a40-b92d-1a0d8326b8fd"
  },
  "response": {
    "request": {
      "streamResponseStatusCodes": {},
      "url": "https://azurelinuxtmpsrc.blob.core.windows.net/?comp=list&include=metadata",
      "method": "GET",
      "headers": {
        "_headersMap": {
          "x-ms-version": {
            "name": "x-ms-version",
            "value": "2017-04-17"
          },
          "accept": {
            "name": "Accept",
            "value": "application/xml"
          },
          "user-agent": {
            "name": "User-Agent",
            "value": "Microsoft Azure Storage Explorer/1.35.0 (win32) azsdk-js-storageblob/12.15.0 (NODE-VERSION v20.14.0; Windows_NT 10.0.19045)"
          },
          "x-ms-client-request-id": {
            "name": "x-ms-client-request-id",
            "value": "e2beaf5e-4603-4a40-b92d-1a0d8326b8fd"
          },
          "authorization": {
            "name": "authorization",
            "value": "Bearer JSON Web Token Redacted"
          }
        }
      },
      "withCredentials": false,
      "timeout": 0,
      "keepAlive": true,
      "decompressResponse": false,
      "requestId": "e2beaf5e-4603-4a40-b92d-1a0d8326b8fd"
    },
    "status": 403,
    "headers": {
      "_headersMap": {
        "content-length": {
          "name": "content-length",
          "value": "438"
        },
        "content-type": {
          "name": "content-type",
          "value": "application/xml"
        },
        "date": {
          "name": "date",
          "value": "Thu, 10 Oct 2024 20:45:06 GMT"
        },
        "server": {
          "name": "server",
          "value": "Windows-Azure-Blob/1.0 Microsoft-HTTPAPI/2.0"
        },
        "x-ms-request-id": {
          "name": "x-ms-request-id",
          "value": "b699ece3-501e-0099-6955-1b0e60000000"
        }
      }
    },
    "bodyAsText": "<?xml version=\"1.0\" encoding=\"utf-8\"?>\n<Error>AuthenticationFailed<Message>Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature.\nRequestId:b699ece3-501e-0099-6955-1b0e60000000\nTime:2024-10-10T20:45:07.0989931Z</Message><AuthenticationErrorDetail>Authentication scheme Bearer is not supported in this version.</AuthenticationErrorDetail></Error>",
    "parsedBody": {
      "message": "Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature.\nRequestId:b699ece3-501e-0099-6955-1b0e60000000\nTime:2024-10-10T20:45:07.0989931Z",
      "code": "AuthenticationFailed",
      "AuthenticationErrorDetail": "Authentication scheme Bearer is not supported in this version."
    },
    "parsedHeaders": {
      "content-length": "438",
      "content-type": "application/xml",
      "date": "Thu, 10 Oct 2024 20:45:06 GMT",
      "server": "Windows-Azure-Blob/1.0 Microsoft-HTTPAPI/2.0",
      "x-ms-request-id": "b699ece3-501e-0099-6955-1b0e60000000"
    }
  },
  "details": {
    "content-length": "438",
    "content-type": "application/xml",
    "date": "Thu, 10 Oct 2024 20:45:06 GMT",
    "server": "Windows-Azure-Blob/1.0 Microsoft-HTTPAPI/2.0",
    "x-ms-request-id": "b699ece3-501e-0099-6955-1b0e60000000",
    "message": "Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature.\nRequestId:b699ece3-501e-0099-6955-1b0e60000000\nTime:2024-10-10T20:45:07.0989931Z",
    "code": "AuthenticationFailed",
    "AuthenticationErrorDetail": "Authentication scheme Bearer is not supported in this version."
  }
}

The only thing that looks suspicious is the "Microsoft network routing" option. Is it possible that the explorer can't deal with accounts configured this way? I'm running the explorer from a machine connected to corpnet, if that helps in any way.

Definitely not the problem. That's what's configured by default, and we work and test storage accounts with this configuration all the time.
What if you sign out completely and sign back in? Does the problem persist? What if you sign out and uninstall completely then reinstall and sign in?

It's good to know that "Microsoft network routing" is not the problem, since we definitely need that on.
Here's the results of the suggested steps:

Signing out and back in: didn't help, same error.
Signing our, uninstalling, reinstalling and signing back in: didn't help, same error.

For the second step I've also removed the C:\Users\<user>\AppData\Local\Programs\Microsoft Azure Storage Explorer folder after the uninstall to make sure there are no lingering configs. Having said that, the explorer still remembered my quick access settings, so I'm guessing uninstalling and removing the folder hasn't purged everything.
I am on version 1.35.0 of the explorer btw.

Just to reiterate, can you edit your first comment so that it shows the information we ask for in our bug template?
Can you also tell me which tenant you are attempting to sign in to?
Try removing the %APPDATA%\StorageExplorer folder. If you're still having problems, feel free to reach out to us on Teams.

I've updated the message but I think I also found a workaround. Deep in the "Activities" log there was a message saying that the explorer is using "Azure Stack APIs" and that this may cause some issues. I've switch to using the other option form "Edit" and it seems like now things work. Or at least I was able to view the blob storage I was struggling with.


Created Calender Application

I've created a calender application using HTML, CSS and JavaScript.

There is no conflict, looks fine. Thank you for submitting.


Extending response_fields syntax to allow rejecting/adding individual fields relative to the default

I think a potentially useful piece of syntax that we are missing is the ability to specify response_fields relative to the default response for that implementation.
Typically you run into this when you require e.g., one extra field but would still like to access all the provider data, for example, for the OQMD, you need to manually request species, but don't want to have to list the other 50+ fields served by the API. You can also imagine a case where you want everything but cartesian_site_positions, which maybe prohibitively large, which would also require listing many many fields.
I propose we add the following syntax (following sort) to handle these two cases:

?response_fields=+species

Return all default fields, but also include species if not already present.

?response_fields=-cartesian_site_positions

Return all default fields, but exclude cartesian_site_positions if present.

?response_fields=+species,-cartesian-site_positions

Hopefully obvious.

?response_fields=+species,lattice_vectors

Any mixed syntax like the above should probably just strip any fields with the - or + syntax and return those without the prefix.

Is this something we think would be generally useful and readily implementable?
A natural extension could then be to request whole namespaces as includes/excludes, like:
?response_fields=+_biomol (since _biomol on its own is not a valid field name) or perhaps with some wildcard syntax: ?response_fields=-_biomol_* to make it more obvious.

This could be useful, especially when people query the database manually and they do not want to have to type the entire list of properties that need to be returned.
Should we also add a list of which properties are shared by default to info endpoint? Now you can only determine which fields are shared by default, by first sending a dummy query, and seeing which fields are returned.

~Should we also add a list of which properties are returned by default to info endpoint? Now you can only determine which fields are shared by default, by first sending a dummy query, and seeing which fields are returned.~ (If I read section 5.3 of the OPTIMADE standard correctly, it is already determined by the standard which properties are returned by default. Although not all database providers seem to adhere to this.)

I think only id, type and last_modified are strictly required (REQUIRED) in the default response, which most implementations seem to do fine with. Everything else is optional (which I think is fine).
I guess the only concern here is that the default fields returned by an implementation can change whenever they want, so queries using this syntax might not be perfectly repeatable.

I had interpreted REQUIRED as also containing all the MUST and SHOULD properties. But it seems you are right and only the properties explicitly marked as REQUIRED should be returned.
In the OPTIMADE standard it says: "Properties not marked as REQUIRED in any case, MUST be included only if explicitly requested in the query parameter response_fields. Otherwise they SHOULD NOT be included."
Many of the Optimade properties are not "REQUIRED". They are instead labelled as MUST or SHOULD be supported.
So basically every OPTIMADE server does not adhere to the standard when it automatically returns fields like cartesian_site_positions or elements.
I am not saying that this is a bad behaviour, but we should adjust the standard.

In the OPTIMADE standard it says: "Properties not marked as REQUIRED in any case, MUST be included only if explicitly requested in the query parameter response_fields. Otherwise they SHOULD NOT be included."
Many of the Optimade properties are not "REQUIRED". They are instead labelled as MUST or SHOULD be supported. So basically every OPTIMADE server does not adhere to the standard when it automatically returns fields like cartesian_site_positions or elements. I am not saying that this is a bad behaviour, but we should adjust the standard.

I think in context, this part is trying to say that when someone asks for response_fields=cartesian_site_positions, you should not include, say,  elements (which leads to the issue above). It is not making any point about what fields are returned when response_fields is not present.
Perhaps this could be clearer in the spec though.

As you mentioned in" Add ASE-based visualisation usnistgov/nmrr-optimade-demo#4" not all the databases now offer all the MUST and SHOULD fields of the structures.
So I think we should indeed write it more clearly in the spec.

I think I'm still keen on this functionality (both syntactically and logically) (though have just stumbled across #181 where @merkys and @rartino already hashed out pretty much the same idea)!


Use currently loaded model for chat title generation

Is your feature request related to a problem? Please describe.
Yes. I have an ollama's llama3.1:70b-instruct-q4_K_S model imported and set as the default for my user account, as well as under Admin>Users>Manage Models>Default Model and Admin>Interface>Set Task Model. Under Workspace, I edit the model to set some custom parameters (e.g. num_gpu, num_predict, etc), including Context Length=16384. I open a new chat and send a message, the model gets loaded and generates the reply.
A few seconds later, the model gets unloaded, only to get reloaded again but with n_ctx=2048 in order to generate the title for the chat. As a result, when it's done and I send a new message, another unload+load happens with the parameters I've set. If instead of sending a new message I edit my original or request a re-generation, then the cycle happens yet another time!
Describe the solution you'd like
It would be cool if the chat renaming function used the already loaded model as is, especially since it is the exact same model and the only thing that's different is the "Advanced Params" section.
Describe alternatives you've considered
Not sure what a viable alternative would be.
Additional context

Version: v0.3.20
Ollama: 0.3.10

# first request sent, loading model:

ollama  | time=2024-09-09T17:53:14.229Z level=INFO source=server.go:391 msg="starting llama server" cmd="/tmp/ollama349776158/runners/cuda_v12/ollama_llama_server --model /root/.ollama/models/blobs/sha256-7e1ca97e0d39109ebd4c253ce3f60fb886a7abf328f34e4c99b834874b16b9b6 --ctx-size 16384 --batch-size 512 --embedding --log-disable --n-gpu-layers 81 --threads 1 --flash-attn --no-mmap --mlock --parallel 1 --tensor-split 39,39 --port 33159"
...
ollama  | llm_load_tensors:  CUDA_Host buffer size =   563.62 MiB
ollama  | llm_load_tensors:      CUDA0 buffer size = 19142.57 MiB
ollama  | llm_load_tensors:      CUDA1 buffer size = 18764.43 MiB
ollama  | llama_new_context_with_model: n_ctx      = 16384
ollama  | llama_new_context_with_model: n_batch    = 512
ollama  | llama_new_context_with_model: n_ubatch   = 512
ollama  | llama_new_context_with_model: flash_attn = 1
ollama  | llama_new_context_with_model: freq_base  = 500000.0
ollama  | llama_new_context_with_model: freq_scale = 1
ollama  | llama_kv_cache_init:      CUDA0 KV buffer size =  2624.00 MiB
ollama  | llama_kv_cache_init:      CUDA1 KV buffer size =  2496.00 MiB
ollama  | llama_new_context_with_model: KV self size  = 5120.00 MiB, K (f16): 2560.00 MiB, V (f16): 2560.00 MiB
ollama  | llama_new_context_with_model:  CUDA_Host  output buffer size =     0.52 MiB
ollama  | llama_new_context_with_model: pipeline parallelism enabled (n_copies=4)
ollama  | llama_new_context_with_model:      CUDA0 compute buffer size =   368.01 MiB
ollama  | llama_new_context_with_model:      CUDA1 compute buffer size =   394.52 MiB
ollama  | llama_new_context_with_model:  CUDA_Host compute buffer size =   144.02 MiB
ollama  | llama_new_context_with_model: graph nodes  = 2247
ollama  | llama_new_context_with_model: graph splits = 3
ollama  | INFO [main] model loaded | tid="139687063945216" timestamp=1725904401
ollama  | time=2024-09-09T17:53:21.239Z level=INFO source=server.go:629 msg="llama runner started in 7.00 seconds"
ollama  | [GIN] 2024/09/09 - 17:53:30 | 200 | 18.169522003s |    <IP_ADDRESS> | POST     "/api/chat"

# first request done, loading model again (notice: it's the same file)

ollama  | time=2024-09-09T17:53:32.849Z level=INFO source=sched.go:731 msg="new model will fit in available VRAM, loading" model=/root/.ollama/models/blobs/sha256-7e1ca97e0d39109ebd4c253ce3f60fb886a7abf328f34e4c99b834874b16b9b6 library=cuda parallel=1 required="41.7 GiB"
ollama  | time=2024-09-09T17:53:32.849Z level=INFO source=server.go:101 msg="system memory" total="124.9 GiB" free="109.8 GiB" free_swap="0 B"
ollama  | time=2024-09-09T17:53:32.850Z level=INFO source=memory.go:326 msg="offload to cuda" layers.requested=-1 layers.model=81 layers.offload=81 layers.split=41,40 memory.available="[23.3 GiB 23.3 GiB]" memory.gpu_overhead="0 B" memory.required.full="41.7 GiB" memory.required.partial="41.7 GiB" memory.required.kv="640.0 MiB" memory.required.allocations="[21.2 GiB 20.4 GiB]" memory.weights.total="36.8 GiB" memory.weights.repeating="36.0 GiB" memory.weights.nonrepeating="822.0 MiB" memory.graph.full="1.1 GiB" memory.graph.partial="1.1 GiB"
ollama  | time=2024-09-09T17:53:32.853Z level=INFO source=server.go:391 msg="starting llama server" cmd="/tmp/ollama349776158/runners/cuda_v12/ollama_llama_server --model /root/.ollama/models/blobs/sha256-7e1ca97e0d39109ebd4c253ce3f60fb886a7abf328f34e4c99b834874b16b9b6 --ctx-size 2048 --batch-size 512 --embedding --log-disable --n-gpu-layers 81 --flash-attn --parallel 1 --tensor-split 41,40 --port 35271"
...
ollama  | llm_load_tensors:        CPU buffer size =   563.62 MiB
ollama  | llm_load_tensors:      CUDA0 buffer size = 19142.57 MiB
ollama  | llm_load_tensors:      CUDA1 buffer size = 18764.43 MiB
ollama  | llama_new_context_with_model: n_ctx      = 2048

Came here to report the same issue. Looks like the title generation doesn't take into account advanced parameters when sending in the request, which with context size causes model reloading.

Should be fixed on dev, testing wanted here!

Tested both dev and main and can confirm my issue was fixed! Thanks!

I've only tested release (v0.3.28), but the problem is still there for me. Also happens with tool use, which makes things very slow.
I have the context size set via Settings -> General -> Advanced parameters though, so it applies to all models for my user.


Working with SQLite database

Brief Summary:
Describe the what, why, and how of your content idea in 2-5 sentences.
SQLite is a relational database management system (RDBMS) contained in a C library. In contrast to many other database management systems, SQLite is not a client–server database engine. Rather, it is embedded into the end program. In this article, we will learn what SQLite database is, how to work with it, and demonstrate all the operations by building a simple project.
Key Takeaways:
What are the 3-5 most important things the reader should understand or be able to do after reading this article?

The reader will understand what SQLite database is, and how to work with it
The reader will build a simple project to understand better

References:
Please list links to any published content/research that you intend to use to support/guide this article. (If none, please indicate 'N/A'.)

https://en.wikipedia.org/wiki/SQLite
https://www.sqlite.org/index.html

closing while other article is worked through

closing while other article is worked through

Hey @ninjaginja/@hectorkambow,
My other article is in final review. Can I start working on this?
Requesting for your approval.
Thank you.

@srishilesh 👋
I'd hold off on submitting a PR - just in case the last one requires any final edits 🚀

gtg 👍

@srishilesh just wanted to follow up - in case I missed the PR for this tipic

@srishilesh just wanted to follow up - in case I missed the PR for this tipic

@hectorkambow
This article is in progress, will raise a PR soon by this weekend.

👋  @srishilesh
Just pinging you on this topic form - as Im trying to make some room in the topic queue.
No rush if you're still working on this one - if you need more time we can always re-open at a later date.

@hectorkambow
Yeah sure.
I'll close this PR now. Will reopen once I complete it.
Thanks.


Large posts must be streamed

Blog posts above a certain size fail to leave the HttpClient. The solution is to add streaming to the post method of that class. The modification has been performed, but not yet committed.

Large posts, in fact, all posts are now streamed.


Errors while building Chapter 10

While building the code in Chapter 10 using grunt, I have errors regarding Data.Monoid.Additive module : "Unknown type Semiring" (line 48 and 51)

You've got two options:

Put older versions of the libraries in your bower/package file. You might have to spend sometime trying to work out which version of which library plays nicely with each other though!
Update to the latest purescript, which includes Semiring in the prelude. You may have to remove .psci_modules in your folder to you get the latest code as well.

Thanks for the reply. I should have closed this issue ^^ I updated my version of Purescript, it was the easiest solution I found :)


Renaming NconBuilder and related

We should consider renaming the methods around NconBuilder.
Current changes proposed:
NconBuilder -> ContractionBuilder
tn.contract -> tn.contract_edge
tn.finalize -> tn.contract

#869

Well, I think it's a good idea. I personally think I would prefer this API in my own work, which is admittedly fairly MPS-centric.
I also like the opportunity it gives to abstract contractions so they can be manipulated and so on independently of the concrete tensors. I wonder if we can invent convenient functions to generate e.g. reflections of contractions:
given
|----
A-B-
|----
return
--|
-B-A
--|

Ok well I can't get the bottom one to come out right but hopefully you get the idea. Not sure if it's feasible.

tn.conj?

I would stick to conj and transpose for that.

Sorry, what I mean is that the function would be transpose, not the output tensor

I don't understand what you mean.

Well that's cause the idea is a bit half-baked:
-eventually we could use Contraction/NconBuilder to create "Contraction"
objects which do the specified ncon call
-having done that one could also imagine functions acting on the
tn.Contraction before it is actually used. For example, reflecting the
specified tensor network about an axis, permuting the output, removing one
of the tensors or adding a new one.
On Tue, Nov 3, 2020 at 12:27 PM Chase Roberts<EMAIL_ADDRESS>wrote:

I don't understand what you mean.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/google/TensorNetwork/issues/871#issuecomment-721270676,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAINHBUIOJUV7PCEMMRSFPTSOA4PRANCNFSM4THWZZ5A
.

I really like this idea. We could use NconBuilder as a "shell" tensor network class that Glen was proposing a few months back. The NconBuilder could for example store metadata about contraction orders and the like. In that case it would be useful to be able to replace the current tensors in the builder with new ones. For complicated algorithms, reusing the network structure with different tensors is sometimes useful.
In a way, this would be similar to the early TensorNetwork object we had, but easier to build.

You could not live with your own failed OO design. And where did that bring you? Back to me.

-- The TensorNetwork class

And I like all these ideas. My only request is that the NconBuilder remains functional. (Immutable, functions have no side effects)

absolutely agree

You could not live with your own failed OO design. And where did that bring you? Back to me.

-- The TensorNetwork class

lol


Test failure in test_batch_renormalization

The discrepancy is beyond what can be soved by adjusting tolerances.
assert_allclose failed:
  shape: () ()
  dtype: float64 float64
  i: (0,)
  x[i]: 0.89111328125
  y[i]: 0.2871745824813843
  err[i]: 0.6039386987686157
x: 0.89111328125
y: 0.2871745824813843
F
======================================================================
FAIL: test_backward_cpu (test_batch_renormalization.transplant_class.<locals>.C)  parameter: {'dtype': <class 'numpy.float16'>, 'ndim': 2, 'test': False}
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/data/work/w/repos/chainer/chainer/testing/condition.py", line 74, in wrapper
    fail()
  File "/data/work/w/repos/chainer/chainer/testing/condition.py", line 51, in fail
    instance.fail(msg)
AssertionError:
Fail: 1, Success: 77

The first error message:
Traceback (most recent call last):
  File "/data/work/w/repos/chainer/chainer/testing/condition.py", line 60, in <lambda>
    lambda: f(ins, *args[1:], **kwargs),
  File "/data/work/w/repos/chainer/tests/chainer_tests/links_tests/normalization_tests/test_batch_renormalization.py", line 135, in test_backward_cpu
    self.check_backward(self.x, self.gy)
  File "/data/work/w/repos/chainer/tests/chainer_tests/links_tests/normalization_tests/test_batch_renormalization.py", line 129, in check_backward
    eps=1e-2, **self.check_backward_options)
  File "/data/work/w/repos/chainer/chainer/gradient_check.py", line 341, in check_backward
    testing.assert_allclose(gx, gx_accum, atol=atol, rtol=rtol)
  File "/data/work/w/repos/chainer/chainer/testing/array.py", line 25, in assert_allclose
    x, y, atol=atol, rtol=rtol, verbose=verbose)
  File "/home/niboshi/anaconda/anaconda3/lib/python3.6/site-packages/numpy/testing/utils.py", line 1395, in assert_allclose
    verbose=verbose, header=header, equal_nan=equal_nan)
  File "/home/niboshi/anaconda/anaconda3/lib/python3.6/site-packages/numpy/testing/utils.py", line 778, in assert_array_compare
    raise AssertionError(msg)
AssertionError:
Not equal to tolerance rtol=0.1, atol=0.5

(mismatch 100.0%)
 x: array(0.89111328125)
 y: array(0.2871745824813843)

This seems to be fixed, or at least, I cannot reproduce this failure. Can we close this ticket?

This is still occasionally happening in our CI server.

Yes, I just confirmed it still happens in the current master(e7dcc12a114cb6ed26523a53b1f5d866accb0f33) after 64044 iterations.
E   AssertionError:
E   Fail: 1, Success: 64043


Following the license change, modify the boilerplates in crypto/chacha/

Merged.
03d770d935b93417334c0a93c58409b5587c7c8c Following the license change, modify the boilerplates in crypto/chacha/


Don't retry function upload on 4xx

WIP
Don't retry function upload on 4xx. A 4xx response

Something I would suggest we had is a property (a boolean flag of some sort) that we can use to enable this new behaviour and that way feature flag it on Buildbot's side.

I added this to the options struct, but am also open to passing it in as a parameter. I started adding it in Buildbot here, but it's not set up quite right yet and I haven't set up the flag in DevCycle yet.

This is ready for review. We set skipRetry to false by default if no value is received for the feature flag. The accompanying change is also ready for review, but depends on this change going out first because this is where options is defined.


Allow for setting numeric state.scrollTarget

@matthewspencer @rossluebe
Update Util.getScrollTarget() to allow for setting a numeric scroll target. The intended use case is for an infinite scroll transition where the scroll position should remain the same. In that case, setting window.history.state.scrollTarget to be the same as the current .scrollPos.

@rossluebe Sure thing, but should I keep the version update in the /dist file?

@douglas-johnson You can revert that as well. The version number in the dist is dynamically updated from the package.json. It looks like it wasn't updated at 0.1.5, but we'll get it this time.

@rossluebe Done!


[Chi-Hung] FIERpy updates

Hi Kel,
This is Chi-Hung. I have added some functions to the current FIERpy:

unrot_eof: To perform conventional non-rotated EOF analysis.
sig_eof_test: To perform significant test which help decide the number of EOF modes retained for rotation (for REOF). Currently I have implemented the Monte Carlo test.
find_hydro_mode: Identify water-related EOF/REOF modes based on Spearman's correlation between RTPC/TPC with hydrological data.
wrap_streamflow: Allow users to enter a list for latitude and longitude at multiple river reaches. This is for users that are interested in using multiple reaches of data as input.

I also slightly modified some existing functions:

reof: I have added few lines which calculate and sort the explained variance fraction after rotation.
get_streamflow: Now also return GEOGloWS reach ID.

All checks out for this PR. There have been some changes to the xarray api that will need to be updated to I will fix those and release an update to this package shortly.


Fix loss of performance in TwoPassWindowSum

Added

check for the (likely very rare) case in which the timing fit results in an undetermined timing slope,
new section in image extractors docs page with 1st pass image example for this extractor

Preview
Nevermind the requirement, it doesn't have the same units...
This PR

Current master (0.9.0)

ctapipe 0.8.0

With the removal of the option to set the window width, this is now a breaking change


Need to pause Orchid ORM for a while

I'm having a hard time looking for a job and, for a while, I need to fully focus on this.
Bug reports are still welcome, I'll do fixings, but new features will have to wait.
Orchid ORM is and will remain my beloved project, there are tons of features to implement and I'll work on it with pleasure, but later.
Sorry, I hope you don't depend on it too much, and it's risky to depend on one guy's hobby project anyway.
Please suggest me if your company is looking for a remote dev. I'm good at TS, node.js, databases, and React, working usually as a full-stack. Applying for Middle and Senior positions. I live in Poland, but open to work in any timezone.

Good luck with your job search!

Good luck and thanks for all your efforts so far. Orchid ORM is an amazing amount of work for one person.


[Suggestion] The ability to make in-game GUIs?

Like the hunger mod for tconfig.

It's planned in the future, it's the 'support for interface' part in the forums thread

Ohk.


[FIX PERMISSION]

No one could be able to modify a watchlist that doesn't belong to him

@vseguin @wfortin I can't assign you to this PR.
So in case you guys don't receive a notification about this PR, I tag you there.

LGTM but I don't think this will work on the unsecure mode, since you're relying on the user.id
We can merge that but we'll need to have a way to make it work with unsecure also.
@vseguin what do you think?

I think it needs to work with unsecure before merging.

@mapy69003 can you handle that?

I'll see

Done with unsecure @wfortin @vseguin

Don't merge, there is an error

Thanks @mapy69003 this will deploy shortly.


force world copy does not work with volumes

    environment:
      WORLD: /worlds/world
      FORCE_WORLD_COPY: "TRUE"

    volumes:
      - ./lobby1/worlds:/worlds:ro

lobby1_1  | mv: can't rename '/data/world/DIM1': Directory not empty
lobby1_1  | mv: can't rename '/data/world/DIM1': Directory not empty
lobby1_1  | mv: can't rename '/data/world/DIM1': Directory not empty

should we add a -f flag to mv command?

Your suggestion might be correct. Can you re-run that with
  DEBUG: "true"

orchestration_lobby1_1 exited with code 1
lobby1_1  | + build=571
lobby1_1  | + case $? in
lobby1_1  | + '[' 0 '!=' 0 ']'
lobby1_1  | ++ curl -fsSL https://papermc.io/api/v2/projects/paper/versions/1.16.5/builds/571 -H 'accept: application/json'
lobby1_1  | ++ jq -r .downloads.application.name
lobby1_1  | + export SERVER=paper-1.16.5-571.jar
lobby1_1  | + SERVER=paper-1.16.5-571.jar
lobby1_1  | + '[' 0 '!=' 0 ']'
lobby1_1  | + '[' -f paper-1.16.5-571.jar ']'
lobby1_1  | + zarg=(-z "$SERVER")
lobby1_1  | + log 'Removing old PaperMC versions ...'
lobby1_1  | + echo '[init] Removing old PaperMC versions ...'
lobby1_1  | [init] Removing old PaperMC versions ...
lobby1_1  | + shopt -s nullglob
lobby1_1  | + for f in paper-*.jar
lobby1_1  | + [[ paper-1.16.5-571.jar != paper-1.16.5-571.jar ]]
lobby1_1  | + log 'Downloading PaperMC 1.16.5 (build 571) ...'
lobby1_1  | + echo '[init] Downloading PaperMC 1.16.5 (build 571) ...'
lobby1_1  | [init] Downloading PaperMC 1.16.5 (build 571) ...
lobby1_1  | + curl -fsSL -o paper-1.16.5-571.jar -z paper-1.16.5-571.jar https://papermc.io/api/v2/projects/paper/versions/1.16.5/builds/571/downloads/paper-1.16.5-571.jar -H 'accept: application/java-archive'
proxy_1   | Replacing RCON_PORT with 25575 ...
lobby1_1  | + '[' 0 '!=' 0 ']'
lobby1_1  | + export TYPE=SPIGOT
lobby1_1  | + TYPE=SPIGOT
lobby1_1  | + export SKIP_LOG4J_CONFIG=true
lobby1_1  | + SKIP_LOG4J_CONFIG=true
lobby1_1  | + exec /start-spiget --noconsole
lobby1_1  | + extraCurlArgs=(-v)
lobby1_1  | + :
lobby1_1  | + [[ -n '' ]]
lobby1_1  | + exec /start-finalSetupWorld --noconsole
lobby1_1  | + : world
lobby1_1  | + export LEVEL
lobby1_1  | + '[' SPIGOT = FEED-THE-BEAST ']'
lobby1_1  | + worldDest=/data/world
lobby1_1  | + [[ -n /worlds/world ]]
lobby1_1  | + isTrue TRUE
lobby1_1  | + local value=true
lobby1_1  | + result=
lobby1_1  | + case ${value} in
lobby1_1  | + result=0
lobby1_1  | + return 0
lobby1_1  | + isURL /worlds/world
lobby1_1  | + local value=/worlds/world
lobby1_1  | + [[ /worlds/ == \h\t\t\p\s\:\/\/ ]]
lobby1_1  | + [[ /worlds == \h\t\t\p\:\/\/ ]]
lobby1_1  | + return 1
lobby1_1  | + [[ /worlds/world =~ .*\.zip ]]
lobby1_1  | + [[ -n '' ]]
lobby1_1  | + log 'Cloning world directory from /worlds/world ...'
lobby1_1  | + echo '[init] Cloning world directory from /worlds/world ...'
lobby1_1  | [init] Cloning world directory from /worlds/world ...
lobby1_1  | + rsync --recursive --delete /worlds/world/ /data/world
lobby1_1  | + '[' SPIGOT = SPIGOT ']'
lobby1_1  | + log 'Moving End and Nether maps to Spigot location'
lobby1_1  | + echo '[init] Moving End and Nether maps to Spigot location'
lobby1_1  | [init] Moving End and Nether maps to Spigot location
lobby1_1  | + '[' -d /data/world/DIM1 ']'
lobby1_1  | + mv -f /data/world/DIM1 /data/world_the_end
lobby1_1  | mv: can't rename '/data/world/DIM1': Directory not empty

mv will refuse to rename a directory to another directory if the target directory contains files. looking at the script, FORCE_WORLD_COPY does not remove the original files so caused this conflict. not a force related issue

Can you test out with itzg/minecraft-server:test-issue-814 and see if that works better? I took your suggestion and have it remove existing world data directories when FORCE_WORLD_COPY is true.

Tested and it is working great.


Program Overview

Program Needs

Call for presentations
Encouraging interesting speakers to submit
Setting up the talk submission system
Review of the submissions
Working out a great schedule
Communication with speakers
Coordination with scholarship team
Canceling, changing, rearranging talks
Keynote speakers
Plan social events (space, catering, music)

For context, this is the sheet we mainly worked in after exporting from Sessionize: https://docs.google.com/spreadsheets/d/1d8ePmc3a-dhJWqmXtW4A4Ni5togV_4s3Y-iwPO-Pbt0/edit#gid=1344315386
Here is last year's Sessionize project: https://sessionize.com/app/organizer/event/1541

Key Milestones (suggested)
CFP Open - April 1 (7 months out)
CFP Close  - June 15 (4.5 months out)
Announce keynotes - July 15 (3.5 months out)
Announce program - August 1 (3 months out)


Return non-zero exit code on err

Returning a non-zero exit code when errors are discovered would allow chaining like: cargo-wsgl && cargo run where it only runs the program if the shaders are good. This would help when purely working in the terminal or on an editor other than vscode.

Oh, that's great, I definitely want to support this workflow. Thank you for suggestion, I will look into that, it should be easy to add

Done in 0.0.6 release, thank you!


Revert "Improve normalize_chunks calculation for "auto" setting"

Reverts dask/dask#11354
Just one possible quick fix for https://github.com/dask/dask/issues/11383
cc @phofl @hendrikmakait for thoughts. Definitely open to other options.

Sounds good -- I'll merge after CI is done (looks like this is a clean revert)


Crash when receiving reward

Version: 1.0.3-1.20.1
The server that I am an admin experienced a crash when a player received a reward from a crate.
The crates have been used for a while now and this is the first time it has crashed.
The player received the reward even though the server crashed.
The config with the reward in question

The log output of the moment of the crash

Looks like there's an extra comma after your last command, can you see if removing that resolves the issue?

You're absolutely right, that fixed the crash. Thank you!


Add nullable option to communityGet, configGet, pointerGet and profileGet methods

Add nullable option to communityGet, configGet, pointerGet and profileGet methods. Related to issue number 49.
This pull request was created for https://app.gib.work/bounties/05ac2c3c-bc58-4594-8596-5575e126620f in an attempt to solve a bounty #49 . Payment for the bounty is immediately sent to the contributor after merge.

Hey there - thanks for this PR! You're the first one who made the tests pass! 🥳
I'm currently traveling, I'll review it as soon as I get back to my place!

Thanks for your contribution @DogukanGun 🥳


fix scrolling: it needs to go through the overall Update path -- instead is driving redraw directly and that causes many issues

Resizing or F5 refresh fixes it -- not a permanent damage..
The Window level UpdtRegs etc all look fine.
Seems like Drawer is in a bad state. Made stuff visible to GoGiEditor but didn't see anything yet..

to reproduce: examples/views scrolling quickly on right panel gets display all fragged
or scroll anything in an emergent sim while it is running and updating..
The culprit is in gi/layout.go:338:
	sc.SliderSig.ConnectOnly(ly.This(), func(recv, send ki.Ki, sig int64, data interface{}) {
		if sig != int64(SliderValueChanged) {
			return
		}
		li, _ := KiToNode2D(recv)
		ls := li.AsLayout2D()
		// if ls.IsUpdating() {
		// 	fmt.Printf("Layout: %v scroll signal while still in update\n", ly.Path())
		// }
		wupdt := ls.TopUpdateStart()
		win := ls.ParentWindow()
		win.ResetUpdateRegions()
		ls.Move2DTree()
		ls.ViewportSafe().ReRender2DNode(li)
		ls.TopUpdateEnd(wupdt)
	})

this is all kinds of bad: the direct call to ResetUpdateRegions, direct ReRender instead of an Update call.

just doing regular UpdateSig on the widget, and not calling ResetUpdateRegions, seems to work just fine -- not sure why it wasn't written that way originally!


Is it an error to reference a nonexistent property of a parameter of type object?

Consider this parameter:

name: my_param
type: object
default:
a: false
b: false
c: false

Is it an error to check for a nonexistent object property d:
${{ parameters.my_param.d }}

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

ID: 790318bb-8220-3241-4ca7-73351074492f
Version Independent ID: db1da9db-3694-779b-17aa-1ed67fcecf86
Content: Use runtime and type-safe parameters - Azure Pipelines
Content Source: docs/pipelines/process/runtime-parameters.md
Service: azure-devops-pipelines
Sub-service: azure-devops-pipelines-process
GitHub Login: @juliakm
Microsoft Alias: jukullam

@ed-randall-blk -- Ed, thank you for your question.  I'm not sure, and I don't currently have the environment to test it.  Please try that statement and let me know the results.

It seems OK.
The pipeline will blow up if I try to reference a non-existent top-level parameter, ie.
${{ parameters.nonexistant }}
but for my specific case it's fine to reference
${{ parameters.m_param.nonexistant }}
and the value just comes back empty.
parameters:
  - name: param4
    type: object
    default:
      aaa: true
      bbb: false
      ccc: 333
      ddd: 'text'

stages:
  - stage: StageA
    displayName: Stage one
    jobs:
      - job: JobA_1
        steps:
          - checkout: none
          - bash: |
              set -x
              p4a='${{ parameters.param4.aaa }}'
              p4b='${{ parameters.param4.bbb }}'
              p4c='${{ parameters.param4.ccc }}'
              p4d='${{ parameters.param4.ddd }}'
              p4e='${{ parameters.param4.eee }}'
              echo "p4a = [${p4a}]"
              echo "p4b = [${p4b}]"
              echo "p4c = [${p4c}]"
              echo "p4d = [${p4d}]"
              echo "p4e = [${p4e}]"
            displayName: 'Test object param4'

works fine, output:
p4a = [True]
p4b = [False]
p4c = [333]
p4d = [text]
p4e = []
+ p4a=True
+ p4b=False
+ p4c=333
+ p4d=text
+ p4e=
+ echo 'p4a = [True]'
+ echo 'p4b = [False]'
+ echo 'p4c = [333]'
+ echo 'p4d = [text]'
+ echo 'p4e = []'

Even if I blank-out all the attributes aaa, bbb, ccc, ddd at run/launch it still works fine, they are just blanked as expected:
p4a = []
p4b = []
p4c = []
p4d = []
p4e = []

@ed-randall-blk -- Ed, thank you for your well-researched followup.
@juliakm -- Julia, please look into this issue.

I'm happy that it works correctly and unsurprisingly right now.
I only raised as it appears to be a small gap in the documentation.  Thanks!


Reset button added to make counter 0, save button to save the number. (08-Number Counter)

closes:https://github.com/swapnilsparsh/30DaysOfJavaScript/issues/22

i have made the change, i hope it is fine now

I am not really good in css, so if you could accept this pull request and assign the responsive issue to someone else it would be great

I am not really good in css, so if you could accept this pull request and assign the responsive issue to someone else it would be great

Sure.

@zaidm124  Thank you for your contribution. Looking forward to more such amazing contributions 🥂


Minor fix in the readme file

Fix in the readme.
@ustinov @srinivas-kandula

Thanks @yogeshprasad for fixing this, please make sure to bump the minor version


Language link modified to direct link on the browser

Thank you for contributing! To help the review process, please provide the following:
Proposal
Provide a short description of the change you are proposing and the reasons for it.
Related
Provide links to any associated pull requests or issues. You can use #123 to link to a PR or issue in this repository, or user/repo#123 to link to other repositories.
Checklist

[ ] I have read the code of conduct and contributing guide
[ ] I have made this pull request to the master branch
[ ] I have run all of the automated validation using npm run ship
[ ] I have added myself to the "contributors" list in the package.json (or do not want to)

It is a useful solution. Thank you for your contribution

It is a useful solution. Thank you for your contribution


Added emojis introduced in Unicode 9.0

I didn't want to add these all by hand, so I used Jsoup and extracted them from http://blog.emojipedia.org/new-unicode-9-emojis/. Just look over the aliases and add new ones if the current ones are not perfect. :)

Coverage decreased (-0.4%) to 92.203% when pulling d2a2e84e42d8ed4b6a51822771e8c594da55213a on Sheigutn:unicode-9 into 261dc28475cd289ec738c8ad33babd3560fbcc9a on vdurmont:master.

I just added over 400 new emoticons that were missing and verified almost all their aliases. Maybe my list is more complete than yours? :joy: https://1drv.ms/x/s!ArQt_o2-63zph4RM_gJWdKGRKeRGYw

All the tests pass and the additions seem legit. I'll merge this for now. @searchy2, would you mind rebasing your PR on this one?


hit enter to get results

Closes https://github.com/Sifatul/find-profile/issues/5

@nsourov thank you for your first PR


speak.save_to_file() function not appending data but overwriting it

Hello
I am trying to use the pyttsx3 and pyttsx4 to save a pdf to an mp3 file.  what I have encountered is the function works in creating the mp3 but if you have say 20 page pdf your mp3 file will not append the data to the mp3 but will over write it.  As a result the mp3 will only have the last block of data saved to it.
I run windows 10 with all the updates installed.  I have installed Pyttsx3 and Pyttsx4 along with PyPDF2.
-->
Describe the bug
<the Mp3 or wav file are not including all the data sent to them but just the last block of data. it no appending the data but over writing it.
Expected behavior
<I should have an mp3 that grows to include the first page of converted data to the last but its not doing that at all.
To Reproduce
< I was able to reproduce the issue on my Centos 9 stream pc with the same results. I also got the same behavior with a windows 10 pc both events did the same thing.
My Platform

Additional context
<I do not think this is a new issue but I would like to have someone tell me if this is a bug or bad code.

Hi, this issue tracker is for issues with the codebase behind https://pypi.org itself, not the projects hosted on PyPI.
You should report this issue to the tracker for the project in question instead.


Displayplacer

Description

This is primarily a quality-of-life update. I've added a new command that acts like a wizard to help new users with all the steps they need for this extension to work properly. This also adds more feedback instead of failing silently when the "Load Preset by #x" commands don't do anything (e.g. the preset or utility is missing)
Screencast

Checklist

[X] I read the extension guidelines
[X] I read the documentation about publishing
[X] I ran npm run build and tested this distribution build in Raycast
[X] I checked that files in the assets folder are used by the extension itself
[X] I checked that assets used by the README are placed outside of the metadata folder

I spoke with @eluce2 about this in our community, awaiting a push to verify

Sorry I’m really new with this, could you give me a step by step way to put this into a keyboard shortcut please 🙏

@pernielsentikaer I've added an image to help illustrate this, but it's not loading properly. Am I doing something incorrectly?

Awesome, thanks @eluce2 🔥


npm install on ubuntu 14.04 within virutalbox

Installing on a plain new ubuntu 14.04 and node v0.12.7 (NO nvm !!) within virutalbox the usb fallback-to-build by node-pre-gyp doesn't work also after sudo apt-get install gyp node-pre-gyp
dan@dan-VirtualBox:~/T2$ cd t2-cli/
dan@dan-VirtualBox:~/T2/t2-cli$ npm install
npm WARN installMany async was bundled with<EMAIL_ADDRESS>but bundled package wasn't found in unpacked tree
npm WARN installMany colony-compiler was bundled with<EMAIL_ADDRESS>but bundled package wasn't found in unpacked tree
npm WARN installMany colors was bundled with<EMAIL_ADDRESS>but bundled package wasn't found in unpacked tree
npm WARN installMany colorsafeconsole was bundled with<EMAIL_ADDRESS>but bundled package wasn't found in unpacked tree
npm WARN installMany debug was bundled with<EMAIL_ADDRESS>but bundled package wasn't found in unpacked tree
npm WARN installMany effess was bundled with<EMAIL_ADDRESS>but bundled package wasn't found in unpacked tree
npm WARN installMany fstream was bundled with<EMAIL_ADDRESS>but bundled package wasn't found in unpacked tree
npm WARN installMany hardware-resolve was bundled with<EMAIL_ADDRESS>but bundled package wasn't found in unpacked tree
npm WARN installMany humanize was bundled with<EMAIL_ADDRESS>but bundled package wasn't found in unpacked tree
npm WARN installMany mkdirp was bundled with<EMAIL_ADDRESS>but bundled package wasn't found in unpacked tree
npm WARN installMany my-local-ip was bundled with<EMAIL_ADDRESS>but bundled package wasn't found in unpacked tree
npm WARN installMany nomnom was bundled with<EMAIL_ADDRESS>but bundled package wasn't found in unpacked tree
npm WARN installMany request was bundled with<EMAIL_ADDRESS>but bundled package wasn't found in unpacked tree
npm WARN installMany semver was bundled with<EMAIL_ADDRESS>but bundled package wasn't found in unpacked tree
npm WARN installMany structured-clone was bundled with<EMAIL_ADDRESS>but bundled package wasn't found in unpacked tree
npm WARN installMany tar was bundled with<EMAIL_ADDRESS>but bundled package wasn't found in unpacked tree
npm WARN installMany temp was bundled with<EMAIL_ADDRESS>but bundled package wasn't found in unpacked tree
npm WARN installMany usb was bundled with<EMAIL_ADDRESS>but bundled package wasn't found in unpacked tree
npm WARN prefer global<EMAIL_ADDRESS>should be installed with -g

><EMAIL_ADDRESS>postinstall /home/dan/T2/t2-cli/node_modules/tessel
> tessel install-drivers || true; tessel trademark || true

module.js:338
    throw err;
          ^
Error: Cannot find module 'node-pre-gyp'
    at Function.Module._resolveFilename (module.js:336:15)
    at Function.Module._load (module.js:278:25)
    at Module.require (module.js:365:17)
    at require (module.js:384:17)
    at Object.<anonymous> (/home/dan/T2/t2-cli/node_modules/usb/usb.js:1:76)
    at Module._compile (module.js:460:26)
    at Object.Module._extensions..js (module.js:478:10)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Module.require (module.js:365:17)
TESSEL™ by TECHNICAL MACHINE™
-
><EMAIL_ADDRESS>install /home/dan/T2/t2-cli/node_modules/usb
> node-pre-gyp install --fallback-to-build

make: Entering directory `/home/dan/T2/t2-cli/node_modules/usb/build'
  CC(target) Release/obj.target/libusb/libusb/libusb/core.o
  CC(target) Release/obj.target/libusb/libusb/libusb/descriptor.o
  CC(target) Release/obj.target/libusb/libusb/libusb/hotplug.o
  CC(target) Release/obj.target/libusb/libusb/libusb/io.o
  CC(target) Release/obj.target/libusb/libusb/libusb/strerror.o
  CC(target) Release/obj.target/libusb/libusb/libusb/sync.o
  CC(target) Release/obj.target/libusb/libusb/libusb/os/poll_posix.o
  CC(target) Release/obj.target/libusb/libusb/libusb/os/threads_posix.o
../libusb/libusb/os/threads_posix.c:24:0: warning: "_GNU_SOURCE" redefined [enabled by default]
 #  define _GNU_SOURCE
 ^
<command-line>:0:0: note: this is the location of the previous definition
  CC(target) Release/obj.target/libusb/libusb/libusb/os/linux_usbfs.o
  CC(target) Release/obj.target/libusb/libusb/libusb/os/linux_udev.o
../libusb/libusb/os/linux_udev.c:40:21: fatal error: libudev.h: No such file or directory
 #include <libudev.h>
                     ^
compilation terminated.
make: *** [Release/obj.target/libusb/libusb/libusb/os/linux_udev.o] Error 1
make: Leaving directory `/home/dan/T2/t2-cli/node_modules/usb/build'
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/home/dan/T2/t2-cli/node_modules/npm/node_modules/node-gyp/lib/build.js:269:23)
gyp ERR! stack     at ChildProcess.emit (events.js:110:17)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (child_process.js:1074:12)
gyp ERR! System Linux 3.16.0-30-generic
gyp ERR! command "/usr/bin/nodejs" "/home/dan/T2/t2-cli/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "build" "--fallback-to-build" "--module=/home/dan/T2/t2-cli/node_modules/usb/src/binding/usb_bindings.node" "--module_name=usb_bindings" "--module_path=/home/dan/T2/t2-cli/node_modules/usb/src/binding"
gyp ERR! cwd /home/dan/T2/t2-cli/node_modules/usb
gyp ERR! node -v v0.12.7
gyp ERR! node-gyp -v v2.0.2
gyp ERR! not ok
node-pre-gyp ERR! build error
node-pre-gyp ERR! stack Error: Failed to execute '/usr/bin/nodejs /home/dan/T2/t2-cli/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --module=/home/dan/T2/t2-cli/node_modules/usb/src/binding/usb_bindings.node --module_name=usb_bindings --module_path=/home/dan/T2/t2-cli/node_modules/usb/src/binding' (1)
node-pre-gyp ERR! stack     at ChildProcess.<anonymous> (/home/dan/T2/t2-cli/node_modules/usb/node_modules/node-pre-gyp/lib/util/compile.js:83:29)
node-pre-gyp ERR! stack     at ChildProcess.emit (events.js:110:17)
node-pre-gyp ERR! stack     at maybeClose (child_process.js:1015:16)
node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (child_process.js:1087:5)
node-pre-gyp ERR! System Linux 3.16.0-30-generic
node-pre-gyp ERR! command "node" "/home/dan/T2/t2-cli/node_modules/usb/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build"
node-pre-gyp ERR! cwd /home/dan/T2/t2-cli/node_modules/usb
node-pre-gyp ERR! node -v v0.12.7
node-pre-gyp ERR! node-pre-gyp -v v0.6.4
node-pre-gyp ERR! not ok
Failed to execute '/usr/bin/nodejs /home/dan/T2/t2-cli/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --module=/home/dan/T2/t2-cli/node_modules/usb/src/binding/usb_bindings.node --module_name=usb_bindings --module_path=/home/dan/T2/t2-cli/node_modules/usb/src/binding' (1)
npm ERR! Linux 3.16.0-30-generic
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "install"
npm ERR! node v0.12.7
npm ERR! npm  v2.11.3
npm ERR! code ELIFECYCLE

npm ERR<EMAIL_ADDRESS>install: `node-pre-gyp install --fallback-to-build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'node-pre-gyp install --fallback-to-build'.
npm ERR! This is most likely a problem with the usb package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-pre-gyp install --fallback-to-build
npm ERR! You can get their info via:
npm ERR!     npm owner ls usb
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/dan/T2/t2-cli/npm-debug.log
dan@dan-VirtualBox:~/T2/t2-cli$

sudo apt-get install build-essential libudev-dev usb put me to the next step... but is is an error anyway :cry:
dan@dan-VirtualBox:~/T2/t2-cli$ npm install
npm ERR! Linux 3.16.0-30-generic
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "install"
npm ERR! node v0.12.7
npm ERR! npm  v2.11.3
npm ERR! path /home/dan/T2/t2-cli/node_modules/tessel/node_modules/.bin/colony-compiler
npm ERR! code EACCES
npm ERR! errno -13

npm ERR! Error: EACCES, unlink '/home/dan/T2/t2-cli/node_modules/tessel/node_modules/.bin/colony-compiler'
npm ERR!     at Error (native)
npm ERR!  { [Error: EACCES, unlink '/home/dan/T2/t2-cli/node_modules/tessel/node_modules/.bin/colony-compiler']
npm ERR!   errno: -13,
npm ERR!   code: 'EACCES',
npm ERR!   path: '/home/dan/T2/t2-cli/node_modules/tessel/node_modules/.bin/colony-compiler' }
npm ERR!
npm ERR!  Please include the following file with any support request:
npm ERR!     /home/dan/T2/t2-cli/npm-debug.log
dan@dan-VirtualBox:~/T2/t2-cli$

sudo npm install -g --save-dev one more step ...
dan@dan-VirtualBox:~/T2/t2-cli$ sudo npm install -g --save-dev
npm WARN installMany async was bundled with<EMAIL_ADDRESS>but bundled package wasn't found in unpacked tree
npm WARN installMany colony-compiler was bundled with<EMAIL_ADDRESS>but bundled package wasn't found in unpacked tree
npm WARN installMany colors was bundled with<EMAIL_ADDRESS>but bundled package wasn't found in unpacked tree
npm WARN installMany colorsafeconsole was bundled with<EMAIL_ADDRESS>but bundled package wasn't found in unpacked tree
npm WARN installMany debug was bundled with<EMAIL_ADDRESS>but bundled package wasn't found in unpacked tree
npm WARN installMany effess was bundled with<EMAIL_ADDRESS>but bundled package wasn't found in unpacked tree
npm WARN installMany fstream was bundled with<EMAIL_ADDRESS>but bundled package wasn't found in unpacked tree
npm WARN installMany hardware-resolve was bundled with<EMAIL_ADDRESS>but bundled package wasn't found in unpacked tree
npm WARN installMany humanize was bundled with<EMAIL_ADDRESS>but bundled package wasn't found in unpacked tree
npm WARN installMany mkdirp was bundled with<EMAIL_ADDRESS>but bundled package wasn't found in unpacked tree
npm WARN installMany my-local-ip was bundled with<EMAIL_ADDRESS>but bundled package wasn't found in unpacked tree
npm WARN installMany nomnom was bundled with<EMAIL_ADDRESS>but bundled package wasn't found in unpacked tree
npm WARN installMany request was bundled with<EMAIL_ADDRESS>but bundled package wasn't found in unpacked tree
npm WARN installMany semver was bundled with<EMAIL_ADDRESS>but bundled package wasn't found in unpacked tree
npm WARN installMany structured-clone was bundled with<EMAIL_ADDRESS>but bundled package wasn't found in unpacked tree
npm WARN installMany tar was bundled with<EMAIL_ADDRESS>but bundled package wasn't found in unpacked tree
npm WARN installMany temp was bundled with<EMAIL_ADDRESS>but bundled package wasn't found in unpacked tree
npm WARN installMany usb was bundled with<EMAIL_ADDRESS>but bundled package wasn't found in unpacked tree
-
><EMAIL_ADDRESS>postinstall /usr/lib/node_modules/t2-cli/node_modules/tessel
> tessel install-drivers || true; tessel trademark || true

/usr/lib/node_modules/t2-cli/node_modules/usb/node_modules/node-pre-gyp/node_modules/npmlog/log.js:21
});
 ^
SyntaxError: Unexpected token )
    at exports.runInThisContext (vm.js:73:16)
    at Module._compile (module.js:443:25)
    at Object.Module._extensions..js (module.js:478:10)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Module.require (module.js:365:17)
    at require (module.js:384:17)
    at Object.<anonymous> (/usr/lib/node_modules/t2-cli/node_modules/usb/node_modules/node-pre-gyp/lib/node-pre-gyp.js:15:11)
    at Module._compile (module.js:460:26)
    at Object.Module._extensions..js (module.js:478:10)
TESSEL™ by TECHNICAL MACHINE™
-
><EMAIL_ADDRESS>install /usr/lib/node_modules/t2-cli/node_modules/usb
> node-pre-gyp install --fallback-to-build

make: Entering directory `/usr/lib/node_modules/t2-cli/node_modules/usb/build'
  CC(target) Release/obj.target/libusb/libusb/libusb/core.o
  CC(target) Release/obj.target/libusb/libusb/libusb/descriptor.o
  CC(target) Release/obj.target/libusb/libusb/libusb/hotplug.o
  CC(target) Release/obj.target/libusb/libusb/libusb/io.o
  CC(target) Release/obj.target/libusb/libusb/libusb/strerror.o
  CC(target) Release/obj.target/libusb/libusb/libusb/sync.o
  CC(target) Release/obj.target/libusb/libusb/libusb/os/poll_posix.o
  CC(target) Release/obj.target/libusb/libusb/libusb/os/threads_posix.o
../libusb/libusb/os/threads_posix.c:24:0: warning: "_GNU_SOURCE" redefined [enabled by default]
 #  define _GNU_SOURCE
 ^
<command-line>:0:0: note: this is the location of the previous definition
  CC(target) Release/obj.target/libusb/libusb/libusb/os/linux_usbfs.o
  CC(target) Release/obj.target/libusb/libusb/libusb/os/linux_udev.o
  AR(target) Release/obj.target/usb.a
  COPY Release/usb.a
  CXX(target) Release/obj.target/usb_bindings/src/node_usb.o
  CXX(target) Release/obj.target/usb_bindings/src/device.o
  CXX(target) Release/obj.target/usb_bindings/src/transfer.o
  SOLINK_MODULE(target) Release/obj.target/usb_bindings.node
  COPY Release/usb_bindings.node
  COPY /usr/lib/node_modules/t2-cli/node_modules/usb/src/binding/usb_bindings.node
  TOUCH Release/obj.target/action_after_build.stamp
make: Leaving directory `/usr/lib/node_modules/t2-cli/node_modules/usb/build'
/usr/bin/t2 -> /usr/lib/node_modules/t2-cli/bin/tessel-2.js
<EMAIL_ADDRESS>/usr/lib/node_modules/t2-cli
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS><EMAIL_ADDRESS>dan@dan-VirtualBox:~/T2/t2-cli$

But ....
dan@dan-VirtualBox:~/T2/t2-cli$ t2
module.js:338
    throw err;
          ^
Error: Cannot find module 'debug'
    at Function.Module._resolveFilename (module.js:336:15)
    at Function.Module._load (module.js:278:25)
    at Module.require (module.js:365:17)
    at require (module.js:384:17)
    at Object.<anonymous> (/usr/lib/node_modules/t2-cli/lib/usb_connection.js:6:11)
    at Module._compile (module.js:460:26)
    at Object.Module._extensions..js (module.js:478:10)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Module.require (module.js:365:17)
    at require (module.js:384:17)
    at Object.<anonymous> (/usr/lib/node_modules/t2-cli/lib/discover.js:1:73)
    at Module._compile (module.js:460:26)
    at Object.Module._extensions..js (module.js:478:10)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
dan@dan-VirtualBox:~/T2/t2-cli$

sudo npm install -g debug solves the issue
@johnnyman727 close it after dependencies are managed well.
1.) No superuser requirements!
2.) test it with nvm !

Thanks @Student007! Closing in favor of #239.


When a query is applied in a node and also referenced in other analsys, if you clear that query, it only does it over the first one

cc @ramiroaznar

It is not happening anymore, but fixed a problem when a compound analysis is removed (https://github.com/CartoDB/cartodb/pull/10557/commits/14959913f6b63cc0eaf2035ffc556f92d7bd5d16).


Possibly not needed functionlity

Generally I think that a library should provide only one way of doing something. Also more functionality means more tests, more maintenance effort, more bugs, etc. So I will list methods that I think you can safely remove from this library (they can always be re-added later):

GreaterThan, GreaterThanEQ, LessThan, LessThanEQ, Equals - Cmp should be enough
Binomial, Fib, MulRange, Jacobi.  This probably should be in another package or just use big.Int. And FizzBuzz too! ;)
Hypot, Log, Log10. This probably should be in another package or just use big.Float
MarshalJSON, UnmarshalJSON. MarshalText/UnmarshalText are already used by encoding/json
BitLen. Probably not needed, the documentation is confusing. What are the use cases?
Bytes, SetBytes Probably not needed. How is it different from GobEncode/GobDecode?
Ilog10. Why round before taking log10? What is the use case for this method?
What is the difference between Rem and Mod? Maybe just documentation issue
sql.Scanner and driver.Value implementations are probably not needed. Storing decimals in databases is database specific.

Cmp and friends

Fair enough.

Binomial, Fib, MulRange, Jacobi

I like these functions/methods -- I think they could be in their own package but they'd need more support. Perhaps if I added trig functions like sin, cos, tan, etc?

Hypot, Log, Log10

Similar to the above, I think they could be useful. Perhaps if I had a package with various math functions I'd add them...

JSON

Gone since encoding/json calls MarshalText if the type implements it. I think those methods were artifacts from when I originally forked this library (and then gutted 99% of it).

Bytes

Similar to math/big.Int's Bytes and SetBytes methods.

Ilog10 rounded

Ilog10 is the number of digits in the Decimal -- that's all it is. It's basically a faster ceil(log10(z)) It's fairly useful internally, and I could see it having some use if people need to figure out the length of a decimal (for, say creating a buffer to store it) before actually converting it into a string or something. I know I've had to do it in the past (not with decimals, but for other reasons).

sql.Scanner and driver.Value

I suppose. Originally I created this so I could use decimal types with lib/pq :smile:
Right now it just uses the String method, which could be stored as text, varchar, or whatever. I dunno. I'm a little on the fence about this one.

The main reason I think methods like Binomial or Hypot shouldn't be provided is because Decimal has very limited use case. Mostly accounting calculations. I suspect 99.9% of users of you library won't use these methods. If you need to calculate Binomial it is better to use big.Int (and probably faster). If you need to calculate Sin, Cos, Hypot, etc it is better to use float64 (much faster) or big.Float (probably faster too).
In the end it is up to you if you want to keep them or not. I just think it will be easier to maintain the library with more focused functionality ;)
Of course you should keep FizzBuzz as it is the main selling point of this package! ;)

BitLen and Bytes

The meaning and purpose of these types is clear for big.Int, however less clear for Decimal (what about non-integer numbers?). Besides it is always possible to use d.Unscaled().BitLen() (BTW, it looks like Unscaled method is missing as well). I would remove these methods.

Ilog10 rounded

Length of decimal is called precision and there is method Prec() to get it. I would unexport this method (it can always be added later).

sql.Scanner and driver.Value

I don't know enough about database/sql/driver to recommend anything to be honest. Most databases support decimal types with precision specified in the schema so there is no reason to use a varchar column to store decimal numbers. As far as I know there is no single on-wire representation of decimal type in different databases. You just need to make sure that implementing sql.Scanner and Value won't make this class incompatible with different databases and drivers.

Length of decimal is called precision and there is method Prec() to get
it. I would unexport this method (it can always be added later).

I assumed precision was the # of digits after the radix.
I should've read the entire decimal spec before I decided to name things 😉

SQL

Makes sense!

various methods

I noticed GCC reimplemented the float library for decimal. Hmmm...
So much code I can write now! 😁
On Thu, Jan 14, 2016 at 7:08 PM kostya-sh<EMAIL_ADDRESS>wrote:

The main reason I think methods like Binomial or Hypot shouldn't be
provided is because Decimal has very limited use case. Mostly accounting
calculations. I suspect 99.9% of users of you library won't use these
methods. If you need to calculate Binomial it is better to use big.Int (and
probably faster). If you need to calculate Sin, Cos, Hypot, etc it is
better to use float64 (much faster) or big.Float (probably faster too).
In the end it is up to you if you want to keep them or not. I just think
it will be easier to maintain the library with more focused functionality ;)
Of course you should keep FizzBuzz as it is the main selling point of this
package! ;)
BitLen and Bytes
The meaning and purpose of these types is clear for big.Int, however less
clear for Decimal (what about non-integer numbers?). Besides it is always
possible to use d.Unscaled().BitLen() (BTW, it looks like Unscaled method
is missing as well). I would remove these methods.
Ilog10 rounded
Length of decimal is called precision and there is method Prec() to get
it. I would unexport this method (it can always be added later).
sql.Scanner and driver.Value
I don't know enough about database/sql/driver to recommend anything to be
honest. Most databases support decimal types with precision specified in
the schema so there is no reason to use a varchar column to store decimal
numbers. As far as I know there is no single on-wire representation of
decimal type in different databases. You just need to make sure that
implementing sql.Scanner and Value won't make this class incompatible with
different databases and drivers.
—
Reply to this email directly or view it on GitHub
https://github.com/EricLagergren/decimal/issues/3#issuecomment-171856691
.

I assumed precision was the # of digits after the radix.

I should admit that this is how I understood it as well before reading the spec ;)

Ha! I'll make it my weekend reading to grok the entire spec.
On Thu, Jan 14, 2016 at 8:39 PM kostya-sh<EMAIL_ADDRESS>wrote:

I assumed precision was the # of digits after the radix.
I should admit that this is how I understood it as well before reading the
spec ;)
—
Reply to this email directly or view it on GitHub
https://github.com/EricLagergren/decimal/issues/3#issuecomment-171869977
.

The math/ subpackage now exists!


Update form #26

This is a simple fix to update single files.

+1

+++1

Nice!

Is this going to be merged any time soon?

I haven't had time to test, but I merged and released. Use at your own risk.

Thank you!

Is this only for forms type='update/insert', excluding Meteor methods?


[BUG] Fix wifi configuration on raspberrypi

Description
The packages in meta-common-configs do not yet suffice to have a working wifi on the raspberrypi.
Observed on
Current HEAD of dunfell.
How to reproduce
Boot a raspi flashed with the full-image and check network ip link show.
Ideas for fixing
None.

Fixed by #33 - only on kirkstone branch and only tested for raspberrypi.


Cover all the examples in the Threader paper

Threader is a verification tool from Andrey and co based on Horn clauses. We should cover all the examples in their CAV paper in Starling (or understand why we can't)
Threader CAV paper
Examples:

[ ] Spin2003 (standard model-checking example)
[ ] Dekker
[x] Peterson
[ ] Szymanski
[ ] Reader-writer (from Calvin model checker)
[ ] Time-varying mutex (from Calvin model checker)
[ ] NaiveBakery / Bakery
[ ] Lamport (unclear what this is?)
[ ] QRCU (the Linux RCU algorithm - verified with a fixed numbers of threads)
[ ] Mozilla-fix-vulnerab (a stock example from Mozilla CVS)
[ ] See-saw (don't know what this is)
[ ] Scull (a Linux character driver)

One observation is that Threader is limited to verifying RCU for a bounded no. of threads. We might be able to do this for unbounded threads using iterated views.

@septract is this still in scope for CAV?  Presumably not, as we have GRASShopper now…

I think this is now out of scope. We need to make sure our benchmarks look
okay but not cover all these examples.
On Wednesday, 11 January 2017, Matt Windsor<EMAIL_ADDRESS>wrote:

@septract https://github.com/septract is this still in scope for CAV?
Presumably not, as we have GRASShopper now…
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/septract/starling-tool/issues/88#issuecomment-271839816,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AANd9qKy_nedfenSqPCvGknehs4JKKm5ks5rRLXwgaJpZM4K4GZR
.

--
http://www-users.cs.york.ac.uk/~miked/


groupby() with arbitrary Series in by list raises an error

This is a follow-up on #1770, for the more complex case where the Series is not just an untouched Series from the DataFrame.
import pandas as pd
import modin.pandas as mpd

data = {
    "a": [1, 1, 2],
    "b": [11, 11, 22],
    "c": [111, 111, 222]
}

df = pd.DataFrame(data)
df = pd.concat([df])
ref = df.groupby(["a", "b", df["c"] + 1]).size()
print(ref)

df = mpd.DataFrame(data)
df = mpd.concat([df])
exp = df.groupby(["a", "b", df["c"] + 1]).size()
print(exp)

(The specific error raised will be different once https://github.com/modin-project/modin/pull/1842 is merged, but it errors out both before and after that PR.)
Originally reported by @ienkovich.

Will see if I can figure out this one too.

I've gotten size() working, but... it seems like there's more broad need for code, e.g. __iter__ breaks. So will move on to that and see what else is broken too.


Make complex integration test to test all editor features in sequence

Editor is no longer being worked on, and has been removed from the repo. Closing.


minify variable declarations

@fogleman sorry about this mess, I used the web client by mistake

I think the way it was previously is more readable.


Bumped version number to 3.3.2.

@dtaylor113 and @jeff-phillips-18 please review?

:+1:

@dtaylor113 can you review this one? Want to push this to patternfly.org next. Thanks!

LGTM


Update resource-manager-rest-api.md

Fixed a couple of typos.

Hi @alexandair, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
We will now validate the agreement and then real humans will evaluate your PR.
TTYL, AZPRBOT;


Expose dynamically setting the topLevelNavbarItems in v4

Is your feature request related to a problem? Please describe.
In v3, you could alter the navbar items by filtering what was passed to its props, such that you could dynamically change the navbar based on the path (the old turbo.build page used to do this). In v4, the navbar retrieves the items internally through a hook, preventing feeding it the modified list of items.
Describe the solution you'd like A clear and concise description of what you
want to happen.
Want to be able to modify the navbar items.
Describe alternatives you've considered A clear and concise description of
any alternative solutions or features you've considered.
Not sure what other workarounds are possible here. I want to be able to modify that list since that list also goes into the mobile navbar etc.
Additional context Add any other context or screenshots about the feature
request here.

Trying to come up with a solution in the referenced PR above. It's not working though, so if anyone can spot the issue or suggest a better way, or if there's a workaround, I'm all ears.

I think I had a similar problem when I did a migration of graphql.org
https://github.com/graphql/graphql.github.io/blob/f7bfbd177f1f7a13109bb370ad401151428444e8/src/globals.css#L78-L82
maybe we can add the possibility to set className in _meta files?

Would this also add new links? Not just hide existing ones?

Would this also add new links? Not just hide existing ones?

of course not

the navbar retrieves the items internally through a hook, preventing feeding it the modified list of items.

we cannot pass functions in server components to client components

Not sure what other workarounds are possible here. I want to be able to modify that list since that list also goes into the mobile navbar etc.

show me an example with screenshots of what you want to achieve

we cannot pass functions from server components into client components

Yes, I understand that, but the config.tsx in nextra-theme-docs is a client component that uses a zustand store that lives on the client? I'm not familiar with zustand but I reckon there must be a way to manipulate the store (scoped to the relevant field) and expose that in a hook?

show me an example with screenshots of what you want to achieve

I can do better, I can show you a live example, using nextra v3. Based on the URL, the navbar has items added based on route.
Root page:

More specific page (notice Guides and Reference added to the route):

You can see it here https://sphil.xyz

The problem with your PR is that even if you make work the setTopLevelNavbarItems function, it will not work as you expected.
When you will visit the root page you'll get a flash of Guide and Reference nav links present on initial loading, and after they will be removed.
I am not interested and not convinced in this feature for now

Ok, fair enough. I'll just have to get creative then :) thank you for your time and attention! Feel free to close this issue.

Thank you 🙏 let’s keep it open if anybody wants to have a similar feature or has an idea of proof of concept that could be easily integrated into Nextra


[FLINK-13293][state-processor-api][build] Add state processor api to opt/ directory in flink-dist

What is the purpose of the change
Similarly to flinks other libraries (cep, gelly, etc) the state processor api should be bundled in the opt directory of flink dist
Verifying this change
(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage. Manually verified.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented? not applicable

@tzulitai I think this should be backported to the 1.9 release branch

+1, merging ...


File generated with "resize: true" seems malformed

I tried to use the resize option with a single png source file and I noticed that Chrome (at least) can't read the resulting file. I also noticed that https://realfavicongenerator.net/ says that my favicon.ico is "ill-formed". I then used https://www.icoconverter.com/ to compare and .ico generated there work. That said, Preview (on my Mac) can read it properly.

Could you provide the original image?

Any image would do but here is an example

Interestingly enough I had more luck with https://www.npmjs.com/package/png-to-ico

I think it has to do in which order the sizes are created. The biggest one needs to be first.

@jraoult, could you try installing from master and see if it works? It rendered fine in Chrome for me.

@kevva fix verified it in Chrome. Cool.
Now, my actual goal was to fix https://www.npmjs.com/package/favicons.  So if I understand your fix properly it is a matter of ordering the given files by width here https://github.com/evilebottnawi/favicons/blob/d5d997f43bd4a50f7cbe511b644fabee4949e837/index.js#L46, right?

@jraoult, yup, that should do it. I'll probably add the sorting in here later on too.

I've checked further and I feel there is something more than the order of the bitmaps going on. I can't quite yet figure it out but I've generated a .ico on https://realfavicongenerator.net/ that works and the same with to-ico and the second one doesn't work.

Hmm, I think I found it: https://github.com/kevva/to-ico/blob/master/index.js#L27. You probably wanted to write (following that: http://www.blitzbasic.com/Community/post.php?topic=75770&post=847533):
data.width === 256 ? 0 : data.width;

instead of
data.width <= 256 ? 0 : data.width;

Am I right?

@jraoult, could you try it?

@kevva I did and it seems that the ordering was no the problem actually but these erroneous width and height info were. Do you want a PR?

@jraoult, yup, you're right. Sorry, I've already pushed out a fix, but thanks a lot for investigating and coming up with a fix!

Glad it helped :) I'll create a PR to https://github.com/haydenbleasel/favicons to require the 1.1.2


Apache v2.0 is the Perfect license

Last November, we gambled when we introduced Perfect to the world. As the first freely available server-side Swift web server and development toolkit, our timing was pinned to the hope Apple would follow through on an earlier pledge to open source their Swift programming language. Thankfully, they did 10 days later. Shortly afterward, thousands of developers expressed their interest in Perfect. Despite their enthusiasm, though, many voiced their unhappiness about the General Public License (GPL) we chose for it. After much internal discussion and contemplation, we have decided to change the Perfect license from the Affero General Public License (AGPL) to Apache immediately.
Our initial research led us to believe that a GPL-flavoured license would strengthen the Perfect community by requiring people to share any improvements they made to it. Our intent was simple: the likelihood of someone changing Perfect for internal or personal use only was low unless they were a large corporation looking to do things at scale. If a small developer were using Perfect, they wouldn't change it, so they would never have issues using it. If a large organization was to use it and made it "their own", our view is they should give back to the community or purchase an enterprise license from us. The AGPL, we thought, would reduce any perceived threats to our small team, and the growing Perfect community who have worked hard to make Perfect a reality.
We realize now this is an outdated perspective.
Over the last couple of months, we have taken the time to consult informally developers, academics and computer programming instructors, and business leaders at Apple, Facebook, LinkedIn, Pivotal, Realm, and more. Those discussions convinced us it was necessary to make this switch.
Linus Torvalds said it best: "There is no upside to pushing freeloaders away.” Certainly, value is created by community contributions – but also if more people are running Perfect in the wild. The more people who stress-test it, no matter how large or small, the faster and better the product will evolve organically.
We additionally believed, given our reading of the AGPL, that it suited us well since Perfect is server-based. It would ensure that a single corporate entity wouldn't push us aside without making a contribution of some sort. Our lawyers stroked their chins, clucked their tongues, and wholeheartedly agreed. At that time, an AGPL made sense.
You know the proverb about “good intentions.” Clearly, most developers that read the AGPL were confused by our intent. They thought (and possibly correctly so) that their projects might become restrictively entangled. This confusion has come up in conversations, in tweets, in emails, on phone calls. Given this reaction by so many developers, one fact is clear: there are multiple readings of the AGPL, and the stricter one’s reading, the further away from our original vision and goals we found ourselves. Defining the lines of our intent proved to be a challenging issue and a distraction.
The deeper we thought about it, the more confusing it became. I have countless explanations attempting to justify the AGPL in my inbox, but it was not enough to make it easy to use. My favourite remark was from one of our writers who said: "much of the criticism we’re facing will not be quelled by any amount of flowery prose."
The eureka moment, however, came when I was sitting in a small office with Bob Young, the founder of Red Hat, discussing how we could explain the importance of the GPL in our context. His advice was simple and powerful. To paraphrase: "make sure the license isn't a roadblock. If developers are confused by it in the slightest, it's getting in the way.”
The simplicity of GitHub's pull request has killed the GPL. We want people to play with Perfect, screw with it, and recommend improvements so we can strengthen and enhance it. Plus, Swift is licensed under Apache, and Perfect is Swift. It's a no-brainer.
We appreciate the contributions everyone has made to date. We hope developers will take note that we have heard them, acted upon their recommendations and that they will continue to consider using Perfect for their future projects.
I am especially grateful to all of the developers who contacted us directly to share their thoughts on this matter. Their aim was to help us without being difficult or mean-spirited.
We aren't perfect.
If you haven't starred and watched us above, please consider doing do!
Onwards!
Sean Stephens
CEO
PerfectlySoft Inc.

Great!
Next step may be to join Apache Software Foundation. This will ensure exposure and more contributors.

Thank you very much! I'd been dying to get into Perfect but I didn't because of the license.


dist-zip should always make the workspace group writeable

Describe the Enhancement
Some applications that we package using dist-zip can sometimes try and create some locks, unzipped JSPs, and some other small files.
Unfortunately, some stacks distinguish build time and runtime users / UID; so it has already happened that an application built with dist-zip, Apache ActiveMQ for example, can be prevented to create temporary and local files in the default workspace folder.
Possible Solution
The solution suggested here is to unconditionally make the workspace folder group writeable; because if the users can be different between build and runtime, they always belong to the same group.
BTW, this is what BP_LIVE_RELOAD_ENABLED does already.
Motivation
Let's take the example of an image built with dist-zip :
> pack build -e BP_APPLICATION_SCRIPT=apache-activemq-dist/bin/activemq -p apache-activemq-dist.zip  hello
> docker exec -it ac51ad787091 bash
cnb@ac51ad787091:/workspace$ ls -al
total 20
drwxr-xr-x 1 cnb  cnb  4096 Jan  1  1980 .
drwxr-xr-x 1 root root 4096 May  2 03:17 ..
drwxr-xr-x 1 cnb  cnb  4096 Jan  1  1980 apache-activemq-dist

If we change it to:
drwxrwxr-x 1 cnb  cnb  4096 Jan  1  1980 apache-activemq-dist

It will allow the app to create its tmp folder and other data
Performance
Of course it's not great to let container write files in their layerfs, but for small files the convenience is worth it.

Some questions:

Do we have a feel for how frequently this is an issue? I know that live-reload does this, but that is really a development feature. Deploying a dist zip app would be for production deployments, so we should strive to make it as secure as possible out of the box. Anyway, I'm asking because this seems like something we put behind a config flag that is default off, so by default you get no write access but if you enable this then it will change the permissions.

Can you change where the application is trying to write these files? It sounds like they are writing temp files, so maybe there is a disconnect between the app and where it's trying to write temp files? If it can write to /tmp, that would be best.

Some additional context:

We're hitting this with folks that were using the distribution zip format to deploy to Cloud Foundry and wanted to maintain the same patterns when moving to Korifi. I have 4 different applications at present that would benefit from this on Jammy (not an issue with Bionic's ClusterStack).

Some of the applications expose environment variables for writing to alternate locations, but others would require a refactor/rewrite to make it possible. With ActiveMQ, for example, you can redefine ACTIVEMQ_TMP and ACTIVEMQ_DATA, but the same situation isn't always available.

With BP_LIVE_RELOAD_ENABLED set to true, the following situation exists:

It is possible to write to sub-directories as the cnb user
Contents of dist-zip's bin/ directory are not updated with execute permissions for user cnb

This mandates setting the process: block in the manifest.yml, which can be somewhat cumbersome if the start script is referring to another binary within the bin/ directory that also does not have group execute permissions
For applications with advanced start scripts, this requires calling a shell first and then the command that the script is calling. The BP_APPLICATION_SCRIPT is then only used to get the build detection phase to pass, and not actually used to launch the first process (web).

An example "simple" manifest to work around the issue:
---
applications:
- name: foo
  path: target/foo.zip
  env:
    BP_APPLICATION_SCRIPT: foo/bin/start
    BP_LIVE_RELOAD_ENABLED: true
  process:
  - type: web
    command: >
      bash /workspace/foo/bin/foo --baz=bah

This becomes even more difficult when the start script is calling another script that calls the actual process. For example, if we have a startup script (bin/start) that calls bin/setup.sh that sets required application runtime variables and calls bin/somepath/foo via bash -c "$@", we have a situation where we now need to add bash as part of the command string. The manifest quickly becomes something like the following:
---
applications:
- name: foo
  path: target/foo.zip
  env:
    BP_APPLICATION_SCRIPT: foo/bin/start
    BP_LIVE_RELOAD_ENABLED: true
  process:
  - type: web
    command: >
      bash /workspace/foo/bin/setup.sh "bash somepath/foo"

Some of the scripts aren't location aware as well, so there are ugly hacks that the maintainers did to run the script from the appropriate directory (e.g. pushd / cd to the appropriate directories first`).

I have a provided a PR introducing a new flag BP_APP_PATH_GROUP_WRITABLE , please have a look!
Thanks!

That PR syntactically looked good by abstracting the permission management into markFolderAsReadWrite, and redacting the portions of BP_LIVE_RELOAD_ENABLED that we do not need, but this won't bring back the behavior that we have on Bionic where we can execute the scripts as the cnb user. Your tests even check those directories here, but with UID=1001 ownership, we still won't be able to call the scripts to start the application.
The issue title is specific to making directories writable, so perhaps that would be tracked in a separate bug. What do you think @anthonydahanne?

Hello @conzetti ! I suggest we move the execution part of the discussion to another issue?
Thanks

hello all!
If that's okay with you (react with a 👍 ) I'll this issue in favor of the chmod-buildpack RFC and POC.


Improve Readme

Old readme wasn't clear enough. Created new readme and added documentation of Profile class.

Thanks to @lionking6792 for translate.


Add express style routers

I think it would be nice to be able to construct routers, this would be an OO style route declaration, that would provide the basis for more simpler grouping, and separation of concerns.

This would look something like:
use Humming-Bird::Core;

my $router = Router.new(root => '/foo');

# This will register a route at /foo/bar
$router.get('/bar', -> $request, $response { $response.write('Foo bar!') });

# This will register this middleware for all routes in this router
$router.middleware(&middleware-logger);

# This will register this advice for all routes in this router
$router.advice(&advice-logger);


Modify Pedersen to use a 4-bit window

Closing, as there's no efficiency gain to be has (lookup is no longer free in a 4-bit window)


[scripts] Prompt minor fix.

Running cti --master will start an experiment directly.
It should be cti --master --help

Motivation
(Write your motivation for proposed changes here.)
Have you read the Contributing Guidelines on pull requests?
(Write your answer here.)
Test Plan
(Share your test plan here. If you changed code, please provide us with clear instructions for verifying that your changes work.)
Related PRs
(If this PR adds or changes functionality, please take some time to update or suggest changes to the docs at https://developers.diem.com, and link to your PR here.)
If targeting a release branch, please fill the below out as well

Justification and breaking nature (who does it affect? validators, full nodes, tooling, operators, AOS, etc.)
Comprehensive test results that demonstrate the fix working and not breaking existing workflows.
Why we must have it for V1 launch.
What workarounds and alternative we have if we do not push the PR.

It seems this PR has conflicts with the latest version. I just rebased it.

/land

:lock: Merge Conflict

/land

:broken_heart: Test Failed - ci-test

/land

/land

@zihaoccc :bulb: This PR is already queued for landing

:broken_heart: Test Failed - ci-test

/land

hit a bug in workflow, will fix ASAP. Do re-try to merge this PR first


add support for streaming xls / xlsx files

Many scientific datasets use XLS or XLSX to store their data.
These file formats are not easy to interpret by non-specialized tools (e.g., text editors).
Suggest to support a way to stream the contents of xls/xlsx files similar to #165 and #148 .

A first pass at adding streaming support for xls -
preston track "https://github.com/jhpoelen/msw3/raw/main/data-raw/03%20Monotremata%20final%20MSW3%20database.xls"\
 | preston excel-stream\
 | head -n2\
 | jq .

{
  "http://www.w3.org/ns/prov#wasDerivedFrom": "hash://sha256/7fec83b9202dae1b4ac91d6fd6e1cdf448c7167484a04b31c6f9a7c031496641",
  "http://purl.org/dc/elements/1.1/format": "application/vnd.ms-excel",
  "ORDER": "MONOTREMATA",
  "SUBORDER": "",
  "INFRAORDER": "",
  "SUPERFAMILY": "",
  "FAMILY": "",
  "SUBFAMILY": "",
  "TRIBE": "",
  "GENUS": "",
  "SUBGENUS": "",
  "SPECIES": "",
  "SUBSPECIES": "",
  "TAXON LEVEL": "ORDER",
  "ORIGINAL NAME": "",
  "VALID NAME (YES OR NO)": "YES",
  "AUTHOR": "Bonaparte",
  "( )?": "",
  "DATE": "",
  "ACTUAL DATE?": "",
  "CITATION": "",
  "VOLUME": "",
  "ISSUE": "",
  "PAGES": "",
  "CITATION TYPE": "",
  "TYPE SPECIES": "",
  "COMMON NAME": "",
  "TYPE LOCALITY": "",
  "DISTRIBUTION": "",
  "STATUS": "",
  "SYNONYMS": "",
  "COMMENTS": "Reviewed by Griffiths (1978). The order is the sole extant representative of the Subclass Prototheria (all other living mammals belong to subclass Theria). McKenna and Bell (1997) divided the order into two (Platypoda and Tachyglossa); the date of divergence of the two living families is unknown, and conservatively they are retained here in a single order. ",
  "": ""
}
{
  "http://www.w3.org/ns/prov#wasDerivedFrom": "hash://sha256/7fec83b9202dae1b4ac91d6fd6e1cdf448c7167484a04b31c6f9a7c031496641",
  "http://purl.org/dc/elements/1.1/format": "application/vnd.ms-excel",
  "ORDER": "MONOTREMATA",
  "SUBORDER": "Tachyglossidae",
  "INFRAORDER": "",
  "SUPERFAMILY": "",
  "FAMILY": "",
  "SUBFAMILY": "",
  "TRIBE": "",
  "GENUS": "",
  "SUBGENUS": "FAMILY",
  "SPECIES": "",
  "SUBSPECIES": "YES",
  "TAXON LEVEL": "Gill",
  "ORIGINAL NAME": "",
  "VALID NAME (YES OR NO)": "",
  "AUTHOR": "",
  "( )?": "Smithson. Misc. Coll.",
  "DATE": "",
  "ACTUAL DATE?": "",
  "CITATION": ""
}

xlsx/xls streaming support has been added in Preston v0.4.6