Provisioning USB devices

Please add that USB devices can not be provisioned from the Teams Admin Center.
Also, could you make BTOE and make it work better than BTOB? BTOB is currently bad and needs improvements.
With BTOE, the direct connection would be from the PC port on the phone and network traffic will ALWAYS pass through the phone when wired connection is present.

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

ID: 344ac314-e98e-ab21-ef47-fb0da80ec884
Version Independent ID: 8f3d2fe8-5d96-4298-f875-fb3e64688afc
Content: Remote provisioning and sign in for Teams Android devices - Microsoft Teams
Content Source: Teams/devices/remote-provision-remote-login.md
Service: msteams
GitHub Login: @dstrome
Microsoft Alias: dstrome

@bteams1221 thank you for reaching out and helping to improve Microsoft Docs. Please have a look at this article and let me know if it helps. https://docs.microsoft.com/en-us/microsoftteams/devices/usb-devices. Please can I ask where you found information mentioning the above regarding USB devices?

@tiburd please can you help with this and confirm if the information is correct regarding USB devices.

@lindspea
Apologies...I thought I had sent email to the author about this, but I cannot find it so that I can follow-up on it, so I sent email today.

Hi @tiburd Hope all is well. Wanted to see if there is an update here? Thanks!

Supported devices are clearly outlined in the article.


Patch spring port

Configure Docker+Spring Boot to use port 80

@jdubois interesting, so Spring too needs to expose port 80. I thought it was doing a clever port mapping that Quarkus couldn't do.

Yes I'm having the same bug as you, but it's not finished yet, seems I have a second bug....

In fact I was wrong, I have another bug!!! So @agoncal it's working fine with Spring out of the box!


Poll

Adding a "PollDaemon" to the already existing "NoopDaemon".

Both can be used singly or simultaneously or not at all.
The Noop Daemon only sends commands, on the control connection, if a control connections is connected.
The Poll Daemon only "invokes" socket.Poll operations on the control conections and the data connections, if such a connection is connected.
The intervals can be configured independently.
The existing "Poll" mechanism is superseded, still works but can be removed soon, (if not right away?).

While developing and testing this, some needed improvements to the existing Noop daemon appeared:

Cancellation of the Deamon via Token
Subtle timing changes or oder of execution changes to better handle edge cases - this invariably involves locking/semaphore operation to handle the cases where the daemon might interfere with normal command handling.

Some "todo"s for seldom to be seen edge cases remain. I will address them in the near future.
One big caveat: Those who want to use VS debug mode with breakpoints are well advised to disable the daemons, because they derive their action triggers from the timing of "last actions" on the socket connections - if you sedately step through your FTP app, these will seem to misbehave timing-wise.

Closing this - I am going to add some stuff before pulling this entirely

Timeout and continue, for Daemon Termination
Timeout and continue, for Daemon Initialization (because this can fail on certain .NET versions.

This will be back asap as another PR

What does Polling do? Can u help me understand it so I can document it?


Cookie banner > add commonly used utilities to the banner API

Both iframe embedding (based on replacing a div with data attributes), and Google Tag Manager snippets are used in every implementation of the cookie banner in our projects.
We should consider adding the snippets to the banner module?

@sarah-storm @Nick-StormID @CatVine Before I take this any further, what do you think about this implementation? Is it any better than just having the iframe rendering and GA snippets in each project?
Adding these utils functions to the state Object that is passed to each of the functions executed based on cookie preferences
import cookieBanner from '@stormid/cookie-banner';

cookieBanner({
    ...lots of other config
    type: {
        ads: [
            state => state.utils.renderIframe(),
            state => state.utils.gaSnippet('UA-12345-6789')
        ]
    }
});

Note that due to the bundler config required to support older projects that need commonjs or umd we cannot have a default export and a named export. So this is not possible:
In the cookie banner module
export const renderIframe = () => ...

In a project index.js
import cookieBanner, { renderIframe, gaSnippet } from '@stormid/cookie-banner';

cookieBanner({
    ...lots of other config
    type: {
        ads: [
            renderIframe
            () => gaSnippet ('UA-12345-6789')
        ]
    }
});

hence the slightly more unusual implementation above.

Hello!  Yes, I think it's still worthwhile standardising the functions... still a reasonably manual process to enable them, but at least there's much less code being copy-pasted around in case of an update.  Looks good to me!


DM Migration error for Oracle 19c

Describe the bug
DM Migration error for Oracle 19c
To Reproduce
Steps to reproduce the behavior:

configure JPA persistence pointing to Oracle 19c database
start server

Expected behavior
Server should be able to start pointing to Oracle 19c database

HAPI FHIR Version
v6.4.4

Fixed by: https://github.com/hapifhir/hapi-fhir/pull/4916


[gpu] clean-up of sources.list and keyring file assertion

I found a couple of things I wanted to update in order to improve performance

/gcbrun

/gcbrun

/gcbrun


JWT Bearer Authentication Parameters for Graph 2.0 endpoint token

Question: Is it possible to use the token obtained by Msal.UserAgentApplication.acquireTokenSilent() method to post as a bearer authorization header to authenticate against a dotnet core Web API? If so, what should I use as JwtBearerOptions in app.UseJwtBearerAuthentication() method?
I tried the standard options used by one of my other apps that uses Azure Active Directory. But getting the following error:
IDX10503: Signature validation failed. Keys tried: 'Microsoft.IdentityModel.Tokens.X509SecurityKey , KeyId:

This worked for me in case of AD B2C:
app.UseJwtBearerAuthentication(new JwtBearerOptions()
{
   MetadataAddress = string.Format("https://login.microsoftonline.com/{0}/v2.0/.well-known/openid-configuration?p={1}",
   Configuration["AAD:TenantId"], Configuration["AAD:Policy"]),
   AuthenticationScheme = Configuration["AAD:Policy"],
   Audience = Configuration["AAD:AppId"],
   AutomaticAuthenticate = true,
   AutomaticChallenge = true,
});

TenantId is the GUID of your AD tenant.
AppId is the GUID of your App.
Policy is the name of the sign-in or sign-up policy that you have configured in B2C.

I don't have a B2C implementation, I have registered my app on https://apps.dev.microsoft.com/ as per instructions from here. There is no notion of AAD:Policy AFAIK.
The only difference in my case is that my web API is dotnet core app so there is no UseOAuthBearerAuthentication and my front-end is my own implementation of angular2 service that uses MSAL JS.

I ended up scrapping the idea of directly validating the graph token. Instead, I ended up validating the id token as usual and sent graph token as a custom header to my requests to the api.


Installation - ERROR: Process exited with code 25

I tried to install the adapter and get this error:
NPM version: 6.14.15
npm install<EMAIL_ADDRESS>--loglevel error --prefix "/opt/iobroker" (System call)
npm ERR! code E404
npm ERR! 404 Not Found - GET https://codeload.github.com/homeinstalator/mikronode-ng/tar.gz/v1.0.11npm ERR! 404 npm ERR! 404 'mikronode-ng@https://github.com/homeinstalator/mikronode-ng/archive/v1.0.11.tar.gz' is not in the npm registry.npm ERR! 404 You should bug the author to publish it (or use the name yourself!)npm ERR! 404 It was specified as a dependency of 'iobroker.mikrotik'npm ERR! 404 npm ERR! 404 Note that you can also install from anpm ERR! 404 tarball, folder, http url, or git url.
npm ERR! A complete log of this run can be found in:npm ERR! /home/iobroker/.npm/_logs/2021-11-24T14_31_56_189Z-debug.log
host.SmartHomeBck Cannot install<EMAIL_ADDRESS>1
ERROR: Process exited with code 25
Log:
21 verbose stack Error: 404 Not Found - GET https://codeload.github.com/homeinstalator/mikronode-ng/tar.gz/v1.0.11
22 verbose stack     at /usr/lib/node_modules/npm/node_modules/npm-registry-fetch/check-response.js:117:15
22 verbose stack     at processTicksAndRejections (internal/process/task_queues.js:95:5)
23 verbose statusCode 404
24 verbose pkgid mikronode-ng@https://github.com/homeinstalator/mikronode-ng/archive/v1.0.11.tar.gz
25 verbose cwd /opt/iobroker
26 verbose Linux 5.10.63-v7l+
27 verbose argv "/usr/bin/node" "/usr/bin/npm" "install"<EMAIL_ADDRESS>"--loglevel" "error" "--prefix" "/opt/iobroker"
28 verbose node v14.18.1
29 verbose npm  v6.14.15
30 error code E404
31 error 404 Not Found - GET https://codeload.github.com/homeinstalator/mikronode-ng/tar.gz/v1.0.11
32 error 404

Same Error here. Seems like mikronode-ng link is not working anymore.
Any alternative to get this adapter working?

Is the GitHub version here working?

Is the GitHub version here working?

I have a running Version 1.0.16, but a new installation does not work ...

Installation via "install from github" at the adapter window doesnt work.
Is there any way to get the dependency that seems missing?
Another instance on a different iObroker is still running since month but a new installation is not possible.

Looks like the project has been abandoned by the original author. What are the steps necessary to install from an cloned git repo?

I hope this helps
mikronode-ng.zip

Problem with installation still exist. Also no success with provided mikronode-ng.zip by using local webserver.
Is there any description available, how to install with current version of ioBroker ?

looks like this is outdated


Issue #110, D3.js

#110 NOTE:

Please fill out the template below

Did you read the instructions in the README?

Y

Have you read the instructions in CONTRIBUTING?

Y

Have you written this article by yourself? Have you taken inspiration from anywhere and then written it in your words?

I've written it myself after taking inspiration from online resources!

As always, on top! @pbiswas101
Great going!
@the-ethan-hunt : Reviewed.


mockup loader?

in https://github.com/sbcgua/mockup_loader/blob/master/src/zcl_mockup_loader.clas.abap
I cannot find methods class_set_source and get_instance? are you using a different loader?
    zcl_mockup_loader=>class_set_source(
      i_type = 'MIME'
      i_path = 'ZMONSTER_TEST_DATA' ).

    TRY.
        DATA(mockup_loader) = zcl_mockup_loader=>get_instance( ).

I downloaded the latest version of the project and the way you create an instance has been simplified - two methods calls have been reduced down to one, which is much better. I have updated my code to match,

cool, 👍
https://github.com/hardyp/ABAPToTheFuture04/commit/c79815cb54c42b38922285e766d599651ce1a94c


[Extension Authoring] TreeDataProvider update doesn't cause update of collapsibleState of TreeItems

VSCode Version: 1.25.0
OS Version: Win10

Steps to Reproduce:

Create TreeDataProvider
Put a TreeItemCollapsibleState.Collapsed TreeItem there and save a ref to it
Fire TreeDataProvider#onDidChangeTreeData
Note: as expected now there is a collapsed TreeItem in the TreeDataProvider
Change collapsibleState of the TreeItem to the TreeItemCollapsibleState.Expanded via the stored ref
Fire TreeDataProvider#onDidChangeTreeData

Expected result: There is an expanded TreeItem in the TreeDataProvider
Actual result:   There is a collapsed TreeItem in the TreeDataProvider
Note 1: It worked correctly in VSCode 1.24.0 but not in 1.25.0 for me
Note 2: changing collapsibleState in the UI still works.
Note 3: changing collapsibleState from TreeItemCollapsibleState.Expanded/Collapsed to TreeItemCollapsibleState.None works fine.

Duplicate of #30918

@sandy081, are you sure this is the same issue?
One I reported is appeared after update from 1.24.0 to 1.25.0
And it has another description

@rugpanov There was a similar issue before which is a dup of #30918.
Since you are mentioning it is working in previous release, I will check it.

I'm also having this problem.
I want to add a collapse/expand button to the navigation bar, but the only ways that I've found for actually collapsing/expanding the tree are:

Clearing it first, then rebuilding it collapsed
Change the labels by appending a random number of whitespace characters to them

The obvious solution is just setting TreeItem.collapsibleState to something, which doesn't work.

This is another issue related to shouldAutoexpand api from the tree which shares the same root cause of #30918.

If you want a node to be expanded or collapsed programatically, may be the right approach is to have an API to expand or collapse instead of causing a data change?

@sandy081 Why not both an API and listening for a mutation of the collapsibleState property? The "problem" with the API is that we would have to keep references to the TreeItems around.

It used to work with collapsibleState property and some extension authors used it. So from this perspective it would be better to return this way. In any case - with separate API or with previous approach, now it doesn't work and for me this is a problem. Please could you provide a possibility to expand/collapse a collapsible tree item in the nearest release.

@rugpanov It only works consistently if you give the state for the first time and was not working completely. See #30918

@sandy081 Now I see. So are there any plans about adding such a functionality? It would be really useful for an extension authoring.

There are plans to add an API to expand/collapse - https://github.com/Microsoft/vscode/issues/55879

.collapse was never added on the view, so it's currently impossible to collapse a single item!  .reveal({expand:false}) does not work either.
For example, try to implement toggle-expansion-on-select behavior to mimic the built-in explorer.  Can track the real state using onDid(Expand|Collapse)Element, but can only set a new state of expanded, using .reveal({expand:true}) - impossible to set collapsed.  Any workarounds appreciated. : )
As mentioned earlier in this bug, updating an existing TreeItem's collapsibleState has no effect.
Current stable (1.31) and insiders (1.32).
Thanks!

duplicate of https://github.com/microsoft/vscode/issues/78970


APP crashing when device loses internet connection [Android]

Hi All,
This is happening on a real device, when the device loses internet connect, then recover it crashes the app. fabric.io is showing these logs
MusicModule.java line 102 com.guichaguri.trackplayer.module.MusicModule.waitForConnection
Fatal Exception: java.lang.IllegalStateException: Not allowed to start service Intent { cmp=/com.guichaguri.trackplayer.service.MusicService }: app is in background uid UidRecord{4df9b02 u0a156 CAC  bg:+1m6s332ms idle change:cached procs:1 seq(0,0,0)}        at android.app.ContextImpl.startServiceCommon(ContextImpl.java:1522)        at android.app.ContextImpl.startService(ContextImpl.java:1478)        at android.content.ContextWrapper.startService(ContextWrapper.java:650)        at android.content.ContextWrapper.startService(ContextWrapper.java:650)        at com.guichaguri.trackplayer.module.MusicModule.waitForConnection(MusicModule.java:102)        at com.guichaguri.trackplayer.module.MusicModule.stop(MusicModule.java:322)        at java.lang.reflect.Method.invoke(Method.java)        at com.facebook.react.bridge.JavaMethodWrapper.invoke(JavaMethodWrapper.java:372)        at com.facebook.react.bridge.JavaModuleWrapper.invoke(JavaModuleWrapper.java:158)        at com.facebook.react.bridge.queue.NativeRunnable.run(NativeRunnable.java)        at android.os.Handler.handleCallback(Handler.java:790)        at android.os.Handler.dispatchMessage(Handler.java:99)        at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(MessageQueueThreadHandler.java:29)        at android.os.Looper.loop(Looper.java:164)        at com.facebook.react.bridge.queue.MessageQueueThreadImpl$4.run(MessageQueueThreadImpl.java:232)        at java.lang.Thread.run(Thread.java:764)
version: 1.1.4

@ntk860 Are you saying you've been able to reproduce this?
We have been trying to track down the cause in #473

Oh that would be nice if it is the cause of the crash thanks a lot for that @ntk860 !
@dcvz what do you think of it?

@ntk860 What exactly is the circumstance that causes this for you?
Are you saying:

start playing a track
disable connection
track reaches end of buffer
enable connection
the error happens?

In the case I described, I just get a playback-error.

@curiousdustin, when I go to a zone where the device loses internet connection, and then I get back to a good zone and the device reestablish the connection it crash the app and throw the exception. I run ads on my app (using react-native-video). It usually happens when the audio from (react-native-audio-player) ends, then a ad comes on (react-native-video), if the device loses connection while the content on (react-native-video) is playing, when the ads end and I try to go to the next track, thats where the app crash.

I'm getting a similar crash happening only on Android 9. See crash log below:

@The0racle Same issue

@Saehanseul no

I've deployed an app using this library and have around 500 users like now, and this crash is my top Crashlytics report right now (about 10-20 reports so far). although upgrading React-Native to 0.60+ reduced number of reports considerably. Unfortunately since my users does not have any significance computer knowledge it's hard to asses why this happens and get a decent scenario from them.

@Guichaguri @curiousdustin I'm also experiencing this crash

We are using this with a pretty substantial userbase and this is our most frequent issue by a wide margin.

+1

We are using this with a pretty substantial userbase and this is our most frequent issue by a wide margin.

I am quite sure it is not related to loss of internet

I'm getting a similar crash happening only on Android 9. See crash log below:

Same issue here. Is very annoying

+1

+1


Support Go modules

It might be time to start considering support for Go modules. Suggestions and support are welcome.

Ok, the chief problem with supporting go modules is that, even with vendoring enabled, non-Go files and non-Go package dependencies are not included in the vendored code (we can see this from @rsc's disappointing response in https://github.com/golang/go/issues/26366#issuecomment-405683150). The solution here will be to add another "include" implementation that searches through checked out, unmodified modules to find protobuf files and their on-disk locations to the include path.
It looks like we can do this using the following command:
go mod download -json

The above will output json records in this format:
{
	"Path": "k8s.io/utils",
	"Version": "v0.0.0-20190607212802-c55fbcfc754a",
	"Info"<EMAIL_ADDRESS>	"GoMod"<EMAIL_ADDRESS>	"Zip"<EMAIL_ADDRESS>	"Dir"<EMAIL_ADDRESS>	"Sum": "h1:2jUDc9gJja832Ftp+QbDV0tVhQHMISFn01els+2ZAcw=",
	"GoModSum": "h1:sZAwmy6armz5eXlNoLmJcl4F1QuKu7sr+mFQ0byX7Ew="
}

This solves the problem of where these files will be on disk but it doesn't solve the issue of mapping proto imports to Go package names, which is the key benefit from protobuild.
It seems like we'd also have to make temporary set of links with the go module paths that link out to the expanded version names to setup the correct import paths. For the example above (which doesn't have protobufs, so its contrived) would create a directory k8s.io/utils with a link back to<EMAIL_ADDRESS>We'd then manufacture this include path with links during compilation time and pass that to the protobuf compiler.
This doesn't seem like a hack and may actually be a decent improvement if we can make it work out of tree.

#29 only made it compatible with go get using go modules. We still need a solution that works with using only modules.


S3 bucket name validation

Added ability to add entries to dictionaries in patch code of CodeGenerator
Added regex pattern validation for s3 bucket name.

Bucket names can have lowercase letters, numbers or hyphen
Bucket names can only start and end with a lowercase letter or number
Originally bucket names could include periods but these don't work with s3 virtual addressing so I am not allowing these here.

The user will get a more useful error now instead of the SSL unableToValidateCertificate error you get if you use a bucket name containing a period which is not informative at all. See #173

Originally bucket names could include periods but these don't work with s3 virtual addressing so I am not allowing these here.

I'm running into this exact issue. According to this, periods in s3 virtual addressing is fine but gives ssl trouble. However, a simple solution could be to use this form https://s3.amazonaws.com/{bucket.with.periods}/{key}. StackOverFlow

@aymanbagabas Amazon are phasing out that form of addressing s3 buckets in 2020.

@Yasumoto I’m wondering if we can’t support both versions of s3 bucket url. Maybe pass a flag to the middleware somehow. I noticed the aws js sdk does this.

This has now been reverted in #198. If a bucket has a period in its name we don’t apply virtual addressing.


quic protocol cause caddy exit unexpectedly with POST request

1. What version of Caddy are you running (caddy -version)?
Caddy 0.9.5
2. What are you trying to do?
POST in quic protocol
3. What is your entire Caddyfile?
https://saki.everpcpc.com {
    header / Server  "{host}"
    root /home/everpcpc/www/
}

4.  Please paste any relevant HTTP request(s) here.
POST https://saki.everpcpc.com
6. What did you expect to see?
response header
date: xxxx
last-modified: xxxx
server: saki.everpcpc.com
etag: W/"xxxxxxxx-x"
content-type: text/html; charset=utf-8
status: 200
accept-ranges: bytes
content-length: 7

response content
さき

7. What did you see instead (give full error messages and/or log)?
response header
last-modified: xxxxxx
server: saki.everpcpc.com
etag: W/"xxxxxxxx-x"
content-type: text/html; charset=utf-8
status: 200
content-length: 7
accept-ranges: bytes
alt-svc: quic=":443"; ma=2592000; v="36,35,34"
alternate-protocol: 443:quic

response content is empty

error log
caddy[107761]: panic: interface conversion: io.ReadCloser is struct { io.Reader; io.Closer }, not *h2quic.requestBody
caddy[107761]: goroutine 74 [running]:
caddy[107761]: panic(0x9ca1c0, 0xc420296a00)
caddy[107761]: #011/usr/local/go/src/runtime/panic.go:500 +0x1a1
caddy[107761]: github.com/lucas-clemente/quic-go/h2quic.(*Server).handleRequest.func1(0xc420287680, 0xc4201004b0, 0xc4200b40f0, 0x0, 0xd1e3a0, 0xc42039a1a0)
caddy[107761]: #011/home/caddy/go/src/github.com/lucas-clemente/quic-go/h2quic/server.go:193 +0x17c
caddy[107761]: created by github.com/lucas-clemente/quic-go/h2quic.(*Server).handleRequest
caddy[107761]: #011/home/caddy/go/src/github.com/lucas-clemente/quic-go/h2quic/server.go:202 +0x628

8. How can someone who is starting from scratch reproduce the bug as minimally as possible?
The config above is already the minimal case.
I created the POST request with request maker extension in Chrome 56.0.2924.87 (Official Build) (64-bit).

Hi @everpcpc - thank you for filing a bug report. I have good news, this has already been reported in numerous issues such as #1519 and fixed. It will be released in less than two weeks!


Glossary of Terms

I think something that we should have is a glossary of terms that people can refer to easily
Please contribute to things we should define: (currently not ordered but this defs should be order alphabetically or something)
Also I know this is gonna be a lot of fighting on what accurate definitions are, so I apologise for any insane arguments that happen through this lol >.< Probably also best to have a note in the documentation that this is our understanding of it or something like that

Individuals

Named Individuals
Anonymouse Individuals

Classes
Object Properties
Annotation Properties
Data Properties
Anonymous Ancestor
Materialised
Nodes and Edges
Knowledge Graph (comparing with ontology)
Controlled Vocabulary (comparing with ontology)
Data Model (compared to the above)
Triple Store
Endpoint

I think it's a great idea to have a glossary for OBO Academy. I think a vocabulary specifically for OBO Academy would be best, as we may want to include terms that aren't relevant to OAK.
Could we just copy and paste what is in OAK into OBO Academy and extend it?
@shawntanzk I like the idea of a disclaimer too :)
@shawntanzk, I would be happy to help too.

I am not worried about duplication and its fine to have two glossaries. I agree we need one here, for sure

Sounds good! Will make a start on it soon (I say soon, but I'm on holiday next week so... lol). @nicolevasilevsky I would love help :) I think starting with a copy and paste of whats in OAK is a good place (@cmungall - is it alright if we flagrantly plagiarise your document?)

And while I think separate voices are good, OAK-OBOOK consistency is important
One of my bugbears is one community to use a term like "ancestor" to mean one thing (e.g. OWL community => subClassOf ancestor) and another community to use it another thing (everyone else => ancestor = transitive closure of relation graph)

Maybe more general terms can migrate to the OBOOK glossary which is likely to have a much larger scope.. and the OAK glossary can focus on specific terms required to understand the data models and otherwise link to the OBOOK GLOSSARY?

plagiarize all you want, don't worry about attribution or anything like
that, but rather than copypasta, consider each term individually and try
and speak with one obo academy voice, which may be different from the OAK
voice
it may also be tempting to copypaste from e.g. W3 docs but consider if this
is really doing our community a service, it's better to go for internal
cohesion and consistency (but by all means provide links to external
resources)
On Wed, Jul 20, 2022 at 9:09 AM Shawn Tan @.***> wrote:

Sounds good! Will make a start on it soon (I say soon, but I'm on holiday
next week so... lol). @nicolevasilevsky
https://github.com/nicolevasilevsky I would love help :) I think
starting with a copy and paste of whats in OAK is a good place @.***
https://github.com/cmungall - is it alright if we flagrantly plagiarise
your document?)
—
Reply to this email directly, view it on GitHub
https://github.com/OBOAcademy/obook/issues/210#issuecomment-1190474427,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAMMOILRYARNOYZNIGNSX3VVAQBXANCNFSM54DBUNHQ
.
You are receiving this because you were mentioned.Message ID:
@.***>


Can't view "Preview" on comments on pull requests

Gitea version (or commit ref): f6eb669
Can you reproduce the bug at https://try.gitea.io:

[x] Yes: https://try.gitea.io/go-gitea/chardet/pulls/1/files

Description
If I try to click on the "Preview" tab at the comment at line container nothing happens. If I do the same thing via a reply button everything works like expected.
Screenshots

[+] Button

"Reply" Button

I can confirm it, I have the same problem...
Gitea version: 6e03390

@xxxtonixxx are you able to use a more recent version on master branch?

I can confirm it happens on 552d8d3 too (latest commit) and I'm digging on JS and I'm found this:

The value of write textarea is not being getted.
I see it's because $tabMenu.data('write') output "write976219", but the .tab.segment element, where it's the textarea, has a data-tab value of "write976219976219", as you can see here:

And, If I set a static value to render in preview (test) it doesn't show, preview tab doesn't open
And, I have noticed that this pice of code:
$('pre code', $previewPanel[0]).each(function (i, block) {
  hljs.highlightBlock(block);
});

Laggy my browser, $previewPanel[0] is undefined and $('pre code', $previewPanel[0]) has a length of 1550, is it the expected behavior?


feat: add Datadog Logs output

What type of PR is this?
/kind feature
Any specific area of the project related to this PR?
/area outputs
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #1052
Special notes for your reviewer:

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: yohboy
Once this PR has been reviewed and has the lgtm label, please assign fjogeleit for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Issif, yohboy
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Issif]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: cf6fb7f10f163ef7bcb845f940d4efe078d06482

Thanks for your review ! 🚀


Test deconvolution methods: EPIC

Broken out of #126
This issue tracks exploring usage of EPIC for bulk cell type deconvolution. Sources:

Paper: https://doi.org/10.7554/eLife.26476.001
Package: https://github.com/GfellerLab/EPIC/

I have run EPIC through a single bulk sample (SCPCS000001) only as proof-of-concept to confirm we can run it. Run time is essentially negligible for this method.
Here is the notebook I created for this initial exploration.
epic.nb.html.zip
EPIC has two built-in references with different sets of cells with some overlap (bolded, and both have an other category:

TRef reference:

Bcells
CAFs  (cancer-associated fibroblasts)
CD4_Tcells
CD8_Tcells
Endothelial
Macrophages
NKcells
otherCells

BRef reference:

Bcells
CD4_Tcells
CD8_Tcells
Monocytes
Neutrophils
NKcells
otherCells

EPIC also allows for a custom reference, for which I tried using the quanTIseq reference but I don't think this was very successful, due to some pretty salient differences between how methods treat references! My sense is that we'd want to use a built-in one, but note that there are fewer cell types these built-in references compared to the quanTIseq built-in reference (see #128).


Re-establish cronjob for database fetching

Re-establish cronjob for database fetching

oh the cronjob is still running, just looked:
0 0 * * 0 sh /var/www/webroot/cronjob.sh > /dev/null 2>&1

meaning every midnight sunday, run the cronjob script which is
cd ~/ROOT
wget -O SIMPLE.db https://raw.githubusercontent.com/SIMPLE-AstroDB/SIMPLE-binary/main/SIMPLE.db
git pull

and shove the text output into nothingness


Ad/issues/459

What this PR does / why we need it:

Fixes #
#fixes oke

Fixes #459 (just to link it)
Thanks @wahyuarif! We'll give this a look. On initial inspection, my only feedback is we may want to use our KUDO client logging package for the new client side log line.

Thanks for the PR... unfortunately it is dated and review of current master shows this was resolved in another way.   Thanks again!!


Fix isolated network for hypervisor and management VM

Summary and Scope

Fixes: Isolated network added in #345 and #342

Issue Type

Bugfix Pull Request

type="network" was missing from the <interface> definition in domain.xml
wicked was rejecting DHCP leases on the link-local network, had to switch to something else (using Class C, private network)

Minor edits:

Switched to prefix instead of netmask in isolated.xml because it's more human-readable.
Updated localhypervisor entry in /etc/hosts for new IP range
Reordered <devices> in domain.xml so the <interface> is on the bottom

Prerequisites

[ ] I have included documentation in my PR (or it is not required)
[ ] I have tested this by building an image using this branch HEAD, or this is does not pertain to the node-images pipeline.
[x] I tested this on internal system or this pertains to the node-images pipeline (if yes and not build related, please include results or a description of the test)
[ ] I tested this on a vshasta system or this pertains to the node-images pipeline (if yes and not build related, please include results or a description of the test)

Idempotency

Risks and Mitigations

/backport lts/csm-1.5


SSI- add RegisterWalletChallenge and RegisterWallet

https://github.com/knox-networks/ssi/issues/135
Currently the Camera scan of the QR will call user mgmt grpc directly for association of wallet.  SSI should expose this as well.

Make it possible to do registration with user mgmt through FFI


Build pipeline: Build a managed solution

[Enter feedback here]
Build pipeline: Build a managed solution
==> this pipeline seems to be wrong.  You are importing a unmanaged solution and exporting the solution again without publishing the customizations.  This can cause unexpected behaviour in the managed solution that is being created.

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

ID: e2d7f63d-dcde-f057-555a-3fffce0f229c
Version Independent ID: e4bba5f7-ae53-260f-269b-c8ad002ef696
Content: Build tool tasks - Power Platform
Content Source: power-platform/alm/devops-build-tool-tasks.md
Service: powerapps
GitHub Login: @mikkelsen2000
Microsoft Alias: pemikkel

@jef3003 If you are still having this problem, please file a new issue.


client/network: Rename DebugInfoBehaviour to InfoBehaviour

I would like to use the protocol_version reported via the DebugInfoBehaviour to only add peers to the DHT that are of the same protocol (e.g. Kusama). See https://github.com/paritytech/substrate/issues/5825 for details.
https://github.com/paritytech/substrate/blob/ec2ab7978a54e7f20af2f9ac12bde7719bb744fb/client/network/src/debug_info.rs#L41-L43
This would elevate the DebugInfoBehaviour from previously only being used for debugging to now being used as a core building block. Thus I would like to rename DebugInfoBehaviour to InfoBehaviour.
Objections? Alternative naming suggestions?
//CC @romanb @tomaka

PeerInfoBehaviour?

:+1: for the name change


Remove broken MPS build

All M1 CI jobs have been broken for more than a week with the errors mentioned in https://github.com/pytorch/vision/issues/8456. It seems that MPS build is the issue. We're temporarily deactivating MPS builds for the CI to be back.

Labelling as bug in case this doesn't get fixed before the release, we'll need to announce it in the release notes.


Tuweni provides an SLF4J implementation

I had to exclude it from our dependency tree in this PR since it conflicted with log4j2. It's no big deal, but perhaps there is a way to make it a provided-scope dependency instead?

Currently those dependencies are provided with a runtime dependency. I'll go read more on provided vs runtime.


Install fails (stops prematurely) when intellij is already installed.

On the new CLIF image, intellij is already installed, which causes workstation-setup to stop-prematurely when brew cask discovers that intellij is already installed.

Also RubyMine.app

Rachel, please tell me more about the CLIF image. I just installed with the Pivotal 10.11 workstation image and upgraded to macOS Sierra.
I do not see intellij installed in Applications, but the script does fail at the intellij step.

I forwarded you a standup email from a couple months ago with information on the CLIF image.

The New York office recently observed this happening. It appears that on some machines Intellij and RubyMine are already installed. Buwahahahahahahaaha!

It appears that brew cask install rubymine and brew cask install intellij-idea throw an Error when the applications are already manually installed. They are fine with if the brew cask had previously installed the application.
Perhaps a solution is to modify the brew cask to look to see if the application is already installed.

Maybe try brew install --force

I've also noticed that in New York the jetbrain products on the images are also not up to date. Perhaps there is some check we can do to in the script to override the existing version always.

I believe that we have finally solved this issue. Thanks everyone for all your help!


Local image paths?

Is it possible to send images located on my local drive to the API? I tried doing so through a base64 string but that doesn't seem to work.

not at the moment @nikitalokhmachev-ai
we are planning to do soon


cue/def: running def on the output creates increasingly nested results

What version of CUE are you using (cue version)?

$ cue version
cue version v0.5.0-beta.5

go version go1.19.3
       -compiler gc
       -trimpath true
     CGO_ENABLED 0
          GOARCH amd64
            GOOS linux
         GOAMD64 v1

What did you do?
exec cue def 1.cue --outfile 2.cue
exec cue def 2.cue --outfile 3.cue
exec cue def 3.cue
cmp 3.cue golden.output

-- 1.cue --
package main

import "hof.io/repro/foo"

foo.#Foo

a: "A"

-- foo/foo.cue --
package foo

#Foo: {
	a: string
}

-- cue.mod/module.cue --
module: "hof.io/repro"

-- golden.output --
package main

import "hof.io/repro/foo"

foo.#Foo
a: "A"

What did you expect to see?
the final output is the same as the original
What did you see instead?
package main

import "hof.io/repro/foo"

_#def
_#def: {
        _#def
        foo.#Foo
        foo.#Foo
        _#def: {
                _#def
                _#def: {
                        foo.#Foo
                        a: "A"
                }
        }
        a: "A"
}

Does this happen with v0.4.3? That's what the section about "latest release" in the bug template is for.

With v0.4.3
package main

import "hof.io/repro/foo"

_#def
_#def: {
        _#def
        _#def: {
                _#def
                _#def: {
                        foo.#Foo
                        a: "A"
                }
        }
}

I would still consider this undesirable output

@verdverm - just to confirm, is the intent behind embedding foo.#Foo into package main, to enforce that package main should then satisfy foo.#Foo?
If so, this gets close to needing what we want in #575 (or similar): a mechanism by which we can enforce that a package value satisfies a given schema. Because the problem with embedding (as in this case) is that closedness is relaxed during the embedding... which is almost certainly not what was intended.
The current behaviour of def is to apply some sort of heuristic that guesses what the user was trying to do. If we implement something like must() (bike shedding on name and semantics) that heuristic can go away entirely.


Apple Notice of End of Push Binary Support

This notice was received today:
"The HTTP/2‑based Apple Push Notification service (APNs) provider API lets you take advantage of great features, such as authentication with a JSON Web Token, improved error messaging, and per‑notification feedback. If you still send push notifications with the legacy binary protocol, make sure to upgrade to the APNs provider API as soon as possible. APNs will no longer support the legacy binary protocol after March 31, 2021. "
It is unclear if PushD already uses the more modern HTTP/2 protocols or not.  Can this please be confirmed?  I see this uses the APN library which does support HTTP/2 in its most modern implementation but unclear if PushD has been adapted to use the latest versions of that library.

Hello, i would like to ask you?
Can we still using this Push D discharging Apple resource?

but unclear if PushD has been adapted to use the latest versions of that library.

My interpretation is: NO. But it is not hard to migrate.
Some more detail:
pushd uses "apn" (apn), which is supposed to be compatible with HTTP/2. From what I see, the code is made for version 1.7 of that library, but I'm not sure if that version is compatible with HTTP/2. A migration is probably in order (it would be safe anyway). See What's new in v2.0 on what needs to be changed.

Is this something you can work on?  I reviewed the fork for mdholloway and it has been re-written in JS instead of Coffee which would require a larger migration as we have 120 deployment settings.

I will look in to it. It depends a bit on the used OS though. It is likely that the new lib requires some other changes.

Done. See my fork.
The mdholloway fork did not support the latest version of the apns lib.
Changes:

made HTTP/2 APNS possible via @parse/node-apn (most others do not seem maintained anymore)
added support for badges under Android
added explanation on support for the 2 different apns authentication methods: certificate or token
adapted the doc a bit
included all the other the work from mdholloway.

Sorry. Have not been able to keep it under coffeescript, as the apn module threw a syntax error. Now I'm not a node expert, so I took the easy way out by building upon mdholloway's fork.
I have tested it under node v11.15.0. Lower versions may very well have problems.
You will need gcc 4.9 or more when installing. If your OS does not have it,you may find it under backports.
NOT DONE YET (at the time of writing):

work on the root cert. See the related issue on parse-community/node-apn

Thanks!  As for the root cert, it sounds like this just needs to be run using Node v12.13.0+ and .  It is not clear if there is anything else required.  We've never bundled a root cert with this project and simply uses PEM files for Apple and API keys for Google.
NOTE:  I have Node 12.16.3 installed and getting this error on your fork on npm install:

<EMAIL_ADDRESS>install /Users/jamescahall/Downloads/pushd-master_hb020/node_modules/hiredis
node-gyp rebuild

CC(target) Release/obj.target/hiredis-c/deps/hiredis/sds.o
CC(target) Release/obj.target/hiredis-c/deps/hiredis/read.o
LIBTOOL-STATIC Release/hiredis-c.a
CXX(target) Release/obj.target/hiredis/src/hiredis.o
CXX(target) Release/obj.target/hiredis/src/reader.o
../src/reader.cc:21:17: warning: 'Set' is deprecated: Use maybe version
[-Wdeprecated-declarations]
larray->Set(task->idx,v);
^
/Users/jamescahall/Library/Caches/node-gyp/12.16.3/include/node/v8.h:3507:3: note:
'Set' has been explicitly marked deprecated here
V8_DEPRECATED("Use maybe version",
^
/Users/jamescahall/Library/Caches/node-gyp/12.16.3/include/node/v8config.h:328:29: note:
expanded from macro 'V8_DEPRECATED'
declarator attribute((deprecated(message)))
^
../src/reader.cc:55:33: error: no matching member function for call to
'ToString'
v = Exception::Error(v->ToString());
~^~~~~~
/Users/jamescahall/Library/Caches/node-gyp/12.16.3/include/node/v8.h:2668:44: note:
candidate function not viable: requires single argument 'context', but no
arguments were provided
V8_WARN_UNUSED_RESULT MaybeLocal ToString(
^
/Users/jamescahall/Library/Caches/node-gyp/12.16.3/include/node/v8.h:2684:31: note:
candidate function not viable: requires single argument 'isolate', but no
arguments were provided
Local ToString(Isolate* isolate) const);
^
1 warning and 1 error generated.
make: *** [Release/obj.target/hiredis/src/reader.o] Error 1
gyp ERR! build error
gyp ERR! stack Error: make failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/Users/jamescahall/.nodebrew/node/v12.16.3/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:194:23)
gyp ERR! stack     at ChildProcess.emit (events.js:310:20)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:275:12)
gyp ERR! System Darwin 20.3.0
gyp ERR! command "/Users/jamescahall/.nodebrew/node/v12.16.3/bin/node" "/Users/jamescahall/.nodebrew/node/v12.16.3/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /Users/jamescahall/Downloads/pushd-master_hb020/node_modules/hiredis
gyp ERR! node -v v12.16.3
gyp ERR! node-gyp -v v5.1.0
gyp ERR! not ok
npm WARN<EMAIL_ADDRESS>No license field.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR!      /Users/jamescahall/.npm/_logs/2021-03-07T00_50_57_278Z-debug.log

Sorry, in my case I cannot go above node 11, and when on 11, I do not have that error. Of course, best would be to go all the way up to the latest node and package versions, but not everybody can do that.


Do not fail GCP auth when GOOGLE_APPLICATION_CREDENTIALS is not found

Auth could have been set up using the Google Cloud CLI:

gcloud init
gcloud auth application-default login

Got this error when not setting the google application credentials.
Also would be good to add this to the docs as an alternative way to configure the cloud for this scenario
2024-10-07 13:54:51,605 [INFO] Starting node_stop_start_scenario injection
2024-10-07 13:54:51,605 [INFO] stop scenario
2024-10-07 13:54:51,605 [INFO] Starting node_stop_scenario injection
2024-10-07 13:54:51,606 [ERROR] Failed to stop node instance. Encountered following exception: 'GCP' object has no attribute 'project'. Test Failed

Got this error when not setting the google application credentials.

cc: @pablomh

I've changed the status to DRAFT while I figure out how to avoid @paigerube14 problem. The reason I didn't spot it is because I've been testing this code using the google.auth Python API which sets project using:
credentials, project = google.auth.default()

Will close in favor of https://github.com/krkn-chaos/krkn/pull/723.


Include AoT section / crosslinks in Blazor WASM Perf

Possible crosslink to https://docs.microsoft.com/aspnet/core/blazor/host-and-deploy/webassembly?view=aspnetcore-6.0#ahead-of-time-aot-compilation. Or perhaps a mini section detailing the perf benefits (ie. for compute intensive apps).
cc/ @guardrex thoughts?

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

ID: a29eb861-e8eb-e54c-b441-e1f14d7e6a7f
Version Independent ID: 40361d5d-c806-9c9b-c7f7-ad317a06bb4f
Content: ASP.NET Core Blazor performance best practices
Content Source: aspnetcore/blazor/performance.md
Product: aspnet-core
Technology: aspnetcore-blazor
GitHub Login: @pranavkm
Microsoft Alias: riande

I'm just going through that docs page and there's a bench of perf related best practices that may be helpful (AoT, relinking, compression). While we can include a link in the additional resources section at the bottom, I wonder if this may warrant a more explicit call-out?


Shared folders

I am trying to view the changes of a folder that has been shared with me. I have added it to my OneDrive so it shows up as a normal folder in the website and my PC.
Looking at the metadata, the shared folder has an undocumented facet called remoteItem. It seems that I can use its content to make the item work like a normal folder (view.delta works fine with the id provided in the facet).
Can I rely on it ? Is this facet going to be documented ?

It looks like the documentation has caught up to the code! Have a read over https://github.com/OneDrive/onedrive-api-docs/blob/master/facets/remoteitem_facet.md and hopefully it'll confirm whatever you derived from the responses. To answer your first question, yes you can rely on it.

Thank you


Update Pretzel.csproj

needed reference for UrlDecode

Also belongs with the fix for #125

Nice one, but please next time could you make just one PR? :wink:

I'll try to figure out how to do that next time :)


[Question] Want some help in implementing sampling with masking for Box spaces?

Question
I am willing to contribute to implementing masking in sampling for gymnasium.spaces.Box and was curious if this is something on the roadmap. Also, would very much appreciate any help/advice on how to tackle this.

No one is currently working on it,
please mention the motivation for adding this feature, and describe how you want it to work

There were some discussions in the past about extending the space.sample() functionality, either here or back in Gym, but the general conclusion was that this is not something we're planning to add. It's not necessarily a definitive decision, but it would need a very solid argumentation and discussion, so closing this for now, and feel free to reopen/create a new issue if you strongly believe this should be added (and ideally find the old discussions on the topic)

The problem we discussed is that it is not obvious how to mask sampling for a uniform distribution (Box) compared to a discrete distribution of all the other spaces.
If there an easy to use and efficient masking for uniform sampling then we could consider it


Backend Implementation: User Connections and Real-Time Webcam Feature with Socket.IO and IP Handshaking

Feature Request: Backend Development for User Connections and Webcam Integration
Is your feature request related to a problem? Please describe.
The project cannot currently connect users and enable real-time webcam functionality. This is a key feature necessary for creating an interactive platform where users can allocate and use webcams seamlessly.
Describe the solution you'd like

Develop a backend system using Socket.IO for real-time communication.
Implement IP handshaking to establish direct connections between users for optimized video streaming.
Enable users to initiate and maintain webcam sessions securely through the backend.
Ensure a robust connection mechanism to handle user disconnects, reconnections, and connection drops gracefully.

Describe alternatives you've considered

Using WebRTC for peer-to-peer video connections; however, this would require additional signaling mechanisms and may add unnecessary complexity at this stage.
Leveraging third-party APIs like Twilio, which may simplify implementation but reduce control over the system.

Additional context

Backend technologies: Node.js with Socket.IO for communication.
Video streaming implementation should emphasize minimal latency and high-quality visuals.
Security considerations: Implement mechanisms to validate IP handshakes and prevent unauthorized access.
Future scalability: Design the system to allow for group connections or potential screen sharing in later updates.

The project dosen't seem ready sadly it's not connecting when i open 2 tabs even when i tried https://allocam.vercel.app/chat

The project dosen't seem ready sadly it's not connecting when i open 2 tabs even when i tried https://allocam.vercel.app/chat

Yeah, the project isn't ready for Production it's still in the development phase and I'm working on it but due to my busy schedule it's being delayed 😔. That's why I'm looking for collaboration and it may have many bugs.

I wish i'm a programmer to help you this project looks super cool and i'm planning to launch a website with it when it's finished i a;ready got a domain

Yeah sure. I look forward for your contribution on my project 😀


Export to CSV functionality

Great job!
It would be desirable to have the ability to export to csv at least, and to pdf and xslx perhaps, all data on the datatable as the jQuery DataTables plugin.

Hi,
Exporting all data (or the filtered data) to CSV should be possible and not to hard to implement so I will probably give it a try.
Exporting to PDF / XLS(X) without a third party library may be harder to do, I'll see if something is available.


Clearer rule severity for React Compiler eslint plugin

What is this PR?
Updates the eslint-plugin-react-compiler docs to use severity of "error" rather than severity of 2
Why is this PR?
Using "off", "warn", "error" for eslint rule severity has been supported for many years now - I think this helps improve the readability :)
I completely forgot what rule: 2 meant - had to look it up!
https://eslint.org/docs/latest/use/configure/rules

Signed the CLA - not sure how long that takes to update :(

thanks!


Issues when translating from TType to TNumber and parameterized types within methods.

Many of the Java TF Ops use parameterized types for either TType, TNumber or both. Sometimes an Op uses <T extends TType> and sometimes another Op is using <T extends TNumber>. When writing a method that uses two different Ops that declare  <T> differently, the compiler complains that T cannot be converted to the other type. It is interesting that TNumber is a subclass of TType. I have searched "Professor Google", but have not found an answer to this kind of problem.
TType to TNumber conversion is very common, especially if you are creating a base class with a common method signature across many similar objects. Sometimes, the subclass calls for a TType, sometimes a TNumber. The real problem, is when you have a common method such as public <T extends TType> Operand<T> call (Operand<T> input).
As a work around, let's say that you cast a TType to a TNumber (where <U extends TNumber>) as in:
@SuppressWarnings("unchecked")
Operand<U> uInput = (Operand<U>)input;

Now when you call something like tf.math.greater(uInput,  otherValue);, the compiler complains:
no instance of type variables(s) exists so that T conforms to TNumber. That is because tf.math.greater uses <T extends TNumber> while other ops, like tf.nn.relu defines <T extends TType>.
Another way around this is to force erasure as in (Operand)value.
At a minimum, it would be nice if there were a convention like <T extends TType> and <U extends TNumber> consistently, but this may not solve all these kind of issues, as I have seen <U extends TType, T extends TType>, and <V extends TType, T extends TType, U extends TType>
The main issue that contributes to this problem is that the Ops require a mixture of types, so a higher level user is artificially juggling the situation by casting like above, or by forcing an erasure of the type.
IMO this situation is going to be confusing to the API user. I still haven't figured out a clean way to get around the issue when two method signatures use the same generic parameter in different ways.
Perhaps there is a better way. My gut feel is this is going to become a larger headache down the line.
The specific example I am running into at this time this problem is:
@Override
    public Operand<T> call(Operand<T> input) {
        @SuppressWarnings("unchecked")
        Operand<U> uInput = (Operand<U>)input;
....
        Operand<U> greater = tf.dtypes.cast(
                    tf.math.greater(uInput,
                            tf.dtypes.cast(tf.constant(threshold),
                            input.asTensor().dataType())), input.asTensor().dataType());
         uInput = tf.math.mul(uInput, greater);
         input = (Operand<T>)uInput;
...

I'd be amazed and disappointed if the Java compiler conflated type variables of the same name across different scopes, such as if "tf.math.greater uses <T extends TNumber> while other ops, like tf.nn.relu defines <T extends TType>", and if the problem is addressed by changing T to U in one of the scopes. Can you create a branch that isolates this problem?
I expect the main solution here is to be ruthlessly consistent in the specificity of our type constraints. I think we need to divide the parameters of our ops and framework methods into a few broad type categories, where both the compilation and the runtime support arbitrary mix and match within a category. To the extent at all possible, we need the compiler to complain if and only if an expression would fail at runtime.
It's a major ergonomics loss when a compiler complaint can be resolved by a simple language-level cast like (Operand<TNumber>) x. This means our typing is inconsistent with our runtime semantics. But it's a major ergonomics win when the compiler complains about a situation that indeed requires runtime changes.
It would also be a major ergonomics loss if we had lots of categories of parameters with different runtime and compile-time behavior. Perhaps we could limit the number of distinct, commonly used categories to something like 3. E.g. TFloating, TNumber, and TType? Then, I think we'd want to be pretty aggressive (especially at the framework level) in supporting the broadest category feasible for a particular parameter.

Right now, the generated wrappers parametrize an operation to accept an TType or TNumber operand based on the information that is defined in the kernel definition of that op, for example here. If all the types listed for a given attribute is member of this group, then it is bound to TNumber in Java. In the same file you'll find other groups that classifies types in a certain logic. The classification in Java (what we call "family") should reflect this as well to make sure that compile time and runtime validations are in sync.
Now note that I've already saw in the past cases where some types were wrong in the kernel definition (can't remember if it was that unsupported types were listed or if it was accepting all possible values while it should have been more restrictive). But basically, that is our source of truth.
In your example @JimClarke5 , if the method call invokes unconditionally tf.math.greater, then the signature of that method should only accept TNumber operands as well and that would resolve the compiler complaints. The problem is that is you have some conditional logic, you might need to explicitly cast it, like this:
Operand<T> input = ...;
...
if (input.asOutput().dataType() == TFloat32.DTYPE) {
    tf.math.greater((Operand<TFloat32>)input, tf.constant(10.0f));
}

which is not bad in this case but if your condition applies to more than one type, it you need to go more generic:
if (input.asOutput().dataType() == TFloat32.DTYPE || input.asOutput().dataType() == TInt32.DTYPE) {
    tf.math.greater((Operand<? extends TNumber>)input, tf.constant(10.0f));
}

I think this complexity could be partially resolved by the work in #92 again but it might not cover all cases yet, it is more focusing on tensors than any type of operands.

I actually resolved this one by forcing everything to TNumber in the upcoming PR for losses.
The issue mainly comes from TBool which is usually TF cast to a TNumber like TInt32 later in the method. However, sometimes the input might be a TNumber  but still but still has to be passed as a TType in the method signature. This gets tricky when calling another method with .

This gets tricky when calling another method with .

Can you share an example? Normally if you call a method that accepts and returns T extends TType, and you pass a T extends TNumber operand, you should get back a T extends Number as well.

The signature for tf.math.abs() has <T extends TNumber>
If I do this with <T extends TType> to support  TBool:
public static <T extends TType> Operand<T> handle(Ops tf, Operand<T> input) {

        DataType<T> dataType = input.asOutput().dataType();

        Operand<? extends TNumber> tInput;
        if(dataType.isBoolean()) {
            tInput = tf.dtypes.cast(input, TInt32.DTYPE);
        }else {
            @SuppressWarnings("unchecked")
            tInput = (Operand<? extends TNumber>)input;
        }

        return tf.math.abs(tInput);
    }

This produces errors on :

@SupressWarnings("unchecked") - Annotations are not allowed here
return tf.math.abs(tInput); - Incompatible types. Found: 'org.tensorflow.op.math.Abs<capture<? extends org.tensorflow.types.family.TNumber>>' required: 'org.tensorflow.Operand`

If I try this, which is what I would like to do:
public static <T extends TType> Operand<T> handle(Ops tf, Operand<T> input) {

     DataType<T> dataType = input.asOutput().dataType();

     if(dataType.isBoolean()) {
         input = tf.dtypes.cast(input, TInt32.DTYPE);
     }

     return tf.math.abs(input);
 }

Errors with:

Incompatible types. Found: 'org.tensorflow.op.dtypes.Cast<org.tensorflow.types.TInt32>', required: 'org.tensorflow.Operand<T>'
'abs(org.tensorflow.Operand<T>)' in 'org.tensorflow.op.MathOps' cannot be applied to '(org.tensorflow.Operand<T>)'

Here's my understanding of this situation. I haven't tried running my handle2, but IntelliJ is happy with it syntactically.
  // T is an unknown subclass of TType. It could be a TString, a TBool, or a TNumber.
  public static <T extends TType> Operand<T> handle(Ops tf, Operand<T> input) {

    DataType<T> dataType = input.asOutput().dataType();

    if(dataType.isBoolean()) {
      // Since input is an Operand<T> and T may not be TInt32, this doesn't compile.
      input = tf.dtypes.cast(input, TInt32.DTYPE);
    }

    // Since abs requires a TNumber and input could be something else, this doesn't compile.
    return tf.math.abs(input);
  }

  // That didn't compile. Let's see what will:

  @SuppressWarnings("unchecked")
  public static <T extends TType> Operand<T> handle2(Ops tf, Operand<T> input) {

    DataType<T> inputType = input.asOutput().dataType();

    final Operand<? extends TNumber> x =
        inputType.isBoolean()
            ? tf.dtypes.cast(input, TInt32.DTYPE)
            : inputType.isString()
                ? tf.strings.toNumber((Operand<TString>) input)
                : (Operand<? extends TNumber>) input;

    // At this point, we know x is a TNumber, but we don't know its exact type at compile
    // time. We also don't know the exact type of T at compile time, so it's not trivial
    // to sort things out on the way back.

    // Not all hope is lost, because the runtime value of input gave us the desired
    // runtime DataType.

    final Operand<? extends TNumber> a = tf.math.abs(x);

    DataType<? extends TNumber> outputType = a.asOutput().dataType();
    if (outputType == inputType) {
      return (Operand<T>) a;
    } else if (inputType.isString()) {
      return (Operand<T>) tf.dtypes.asString(a);
    } else {
      return tf.dtypes.cast(a, inputType);
    }
  }

Your example will result in untyped casts warnings.

It does depend on the @SuppressWarnings("unchecked") at the top of the method, or is that not the thrust of your comment?

If we take the #139 route, many things around type handling will be different. But for this particular discussion here, it looks like everything works fine as expected so far so if you agree @JimClarke5 , I suggest that we close it and open a new one of problematic cases arise again?


CK new year wishes - feel free to add your own!

Hi all,
I started collecting different CK wishes for 2019 here:

start preparing different "How to guides": "how to create a module", "how to create a software detection plugin", "how to create different types of packages (code, data sets, models)", "how to create a program workflow", etc.
update CK contributor guide
start standardizing all APIs of shared modules: http://cKnowledge.org/shared-modules.html
add continuous testing of shared CK packages across different compilers, platforms and sub-dependencies: http://cKnowledge.org/shared-packages.html
add continuous testing of all program workflows: http://cKnowledge.org/shared-programs.html
improve soft/package modules and meta descriptions (make them simpler and move different functionality from OS-dependent scripts to Python)
improve support for spack and easybuild
improve automatic generation of reproducible articles based on http://cKnowledge.org/rpi-crowd-tuning
improve CK workflows to crowd-source AI/ML/SW/HW autotuning and co-design: https://github.com/ctuning/ck-mlperf , http://cKnowledge.org/request and http://cknowledge.org/android-apps.html

Please feel free to add your own wishes with some ideas about to achieve them! Also please indicate if you can help yourself or provide resources - as a non-profit community project, we have limited resources and rely on your help!
Looking forward to further collaboration to improve our open R&D platform in 2019!

Improve high-level overview of CK capabilities and program workflows: http://cknowledge.org/high-level-overview.pdf - feedback is welcome!

After the 1st Quantum Machine Learning hackathon in Paris, we got a feedback to provide a simpler installer: https://github.com/ctuning/ck/issues/98

For automatic testing, it would be handy to check out a particular revision of a repository or branch e.g.:
$ ck pull repo:ck-tensorflow --git_hash=655a20f99af32926cbf6d8fab092506ddd70e49c

or:
$ ck pull repo:ck-tensorflow --git_branch=object-detection-tflite

Another handy feature would be to search preprocessing/postprocessing scripts by tags, so, for example, instead of hard-coding:
        "pre_process_via_ck": {
          "data_uoa":       "b98ee24399ef4c3a",
          "module_uoa":     "script",
          "script_name":    "preprocess"
        },

one could use:
        "pre_process_via_ck": {
          "tags": "image-classification,imagenet,tf",
          "module_uoa":     "script",
          "script_name":    "preprocess"
        },

We already addressed some of these issues and together with OctoML we started adding support for the ONNX runtime.
I close this ticket and move some ideas to https://github.com/ctuning/ck/issues/150 .


🚀 feat dark-mode toggle

Added dark mode toggle

Looks Great @akshitarora921. It is ready to be merged from my side. The code is also awesome.

Kudos to the work, works really smooth


forceSetTimeOut broken in 2.4

Example: http://codepen.io/anon/pen/epJdbo?editors=101
When using forceSetTimeOut the game basically runs in slow motion, like the 1000ms tween in the example taking ~3000ms for me in Chrome. In Firefox it jerks around and takes ~1500ms.
When going back in versions it still worked fine in 2.3.0.

True - fixed in dev.


Removed multiple CI version

Hi, as of now we are running CI for 16 various Ruby versions. shall we remove each specific version and test with only the latest stable release?
rvm:
  2.0
  2.1
  2.2
  rbx-2
  jruby-head
  ruby-head

This will ensure only the latest patch as well we can help travis by reducing the CI count....
If there is a specific reason then kindly Ignore this PR...
This is one of my suggestion...

@ferdinandrosario thanks for the PR, we want to ensure that there is no regression whatsoever with every minor version of major series. Furthermore, there have been few intermittent failtures on specific minor versions occured in the past.

Ok :+1:


Mat/Pat - Undo the 4 week email feature that is causing Review task list order to be messed up

We need to Stop sending the email Sent to applicant's alternate email 6 weeks before end of leave (last date of maternity and/or parental leave). This is causing the application task to be updated everyday, messing the order of tasks on the Review and Process tab.
AC

[ ] Stop sending the email Sent to applicant's alternate email sent 6 weeks before end of leave (last date of maternity and/or parental leave).
[ ] The list of tasks in the review and process tab is in the right oder - Last created to first created

Added solution to keep this workflow in #1398 ticket, It is in QA.

the submission order issue has been fixed, so no need to do this


@jsx React.DOM pragma has been deprecated as of React 0.12

As per: https://facebook.github.io/react/blog/2014/10/16/react-v0.12-rc1.html
I'm receiving this error message when incorporating simpletabls in an atomify project on React 0.13.3

I was able to fix it by deleting the JSX pragma and use strict statement from line 66 of react-simpletabs.js and also the JSX pragma from line 216 of that same file.

There is a pull request for React 0.14 support, is this project dead or is anyone still looking after it (pretty apt given todays Twitter blow up about delayed pull requests and releases).


update yunjun's blog post url link

The link for yunjun's blog post is wrong, update it to the right one.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Overriding an associated key still creates a new instance in the database

Hey there, firstly awesome revival of this package, it's made E2E testing our systems so much smoother than previous approached! But we've recently run into a bug/issue with creating instances:
In the create method of the Factory class, the method first gets the default attributes and resolves the associations before taking into account associated keys manually passed in the overrides field. This lands up creating undesired entries in the DB as you'd expect it to just link to the provided foreign key, but instead it lands up linking the provided key and creating an loose hanging entry in the table as well.
I feel the desired behaviour would be to merge the default attributes and overrides and only afterwards resolve the associations. We noticed this because we have unique constraints on some of our tables and tests were failing because sometimes the factory would happen to create a new entry with the same unique fields and the suite would error out.
Happy to try make a PR for the desired change if this project is still being maintained!

Hello @dkpoult , thanks for the enthusiasm and for reporting the bug :)
PRs are more than welcome, for sure! I haven't had much time lately to work on it due to my full-time job, but I certainly want to improve it further :)

@thiagomini we're using Sequelize+Sequelize-Typescript with a Postgres database.
I've created PR #36 to address the issue with a new test case for it, hope it's satisfactory! :)

Hey @dkpoult , thanks for the contribution, I'll review it as soon as possible and merge if everything looks good!

Super, thank you 🥳 glad I could help


Too many classes in --main-dex-list, main dex capacity exceeded

Previously used as follows
Classpath 'com.android.tools.build:gradle:3.0.1'
Classpath 'com.jakewharton:butterknife-gradle-plugin:8.5.1'

After the upgrade version for 9.0.0 appear a mistake as below
Classpath 'com.android.tools.build:gradle:3.1.3'
Classpath 'com.jakewharton:butterknife-gradle-plugin:9.0.0'

ERROR:
com.android.build.api.transform.TransformException:
com.android.ide.common.process.ProcessException:
java.util.concurrent.ExecutionException:com.android.dex.DexException:
Too many classes in --main -dex-list, main dex capacity exceeded

Added an exception when compatibility with min sdk=16, and changed to 21 version for normal use, but this does not work properly. At the same time, I tried to upgrade the gradle plugin and it can't be used normally. What is the difference between 8.0-9.0? Why is there a subcontracting exception in the upgrade? Thank you.

maindex will keep all the classes whose fields, methods or themselves are  annotated.
you can apply this closure in your app/build.gradle
android {
  dexOptions {
     keepRuntimeAnnotatedClasses false
  }
}

But this will remove all the previously mentioned classes, you can try thinAnnotation to remove target class


pkg/build: add build command for starnix

After this, syz-ci can build Starnix and run syz-manager with a manager config with "type": "starnix".

Hi!! Sorry about that, you still show up as an auto-assigned reviewer even though you're emeritus, and I thought I'd managed to take you off the notification list. I think we'll need help from the syzkaller admins to change the default list of reviewers.

No problem. :) I did read it tho! :)


feat(haystack): V2 Support

Fixes #640

[x] I have added tests that cover my changes.
[ ] If adding a new instrumentation or changing an existing one, I've added screenshots from some observability platform showing the change.
[x] PR name follows conventional commits format: feat(instrumentation): ... or fix(instrumentation): ....
[ ] (If applicable) I have updated the documentation accordingly.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@mayankagarwals can you update the sample app as well and share a screenshot showing this working?

Sorry @mayankagarwals I missed that 🤦
I don't have one, but it should look like the other samples - you can just use the test you've created and turn it into a working program. This is how the screenshot should look like - https://github.com/traceloop/openllmetry/pull/706

Attaching Traceloop Screenshot with haystack V2

@nirga Can you help me with the lint command for the repo?

Why does the OpenAI span appear twice? 🤔

I think that's because I see an OpenAI client specific instrumentation with same name : https://github.com/traceloop/openllmetry/blob/9f6048089c4de70cf6e43d19992fc088464ac8fe/packages/opentelemetry-instrumentation-openai/opentelemetry/instrumentation/openai/shared/chat_wrappers.py#L34
We can potentially change the span name to haystack.openai.chat?

Why does the OpenAI span appear twice? 🤔

I think that's because I see an OpenAI client specific instrumentation with same name :
https://github.com/traceloop/openllmetry/blob/9f6048089c4de70cf6e43d19992fc088464ac8fe/packages/opentelemetry-instrumentation-openai/opentelemetry/instrumentation/openai/shared/chat_wrappers.py#L34
We can potentially change the span name to haystack.openai.chat? Let me know if you have any other naming ideas

Yep, that sounds good!

Updated screenshot after changing name


Native: PrimeExceptionHandler not finding error pages

In Native mode PrimeExceptionHandler does not parse the pages out of web.xml

I fixed it in MyFaces: https://issues.apache.org/jira/browse/MYFACES-4573


dummy change

/build-native

/native

/native again

/native with push ?

not a trigger comment

/native !

🎉 This issue has been resolved in <IP_ADDRESS> (Release Notes)


Add pagination and timeout to commitments and ack queries

Closes: #4101
Description

PR author checklist:

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

Reviewer checklist:

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

Applied the suggestions in this commit https://github.com/informalsystems/hermes/pull/4110/commits/d048aff17f65636cd1861a840770b34f1c2e6d47.
And opened this issue to follow-up on the paginate method abstraction https://github.com/informalsystems/hermes/issues/4135


Site-wide topbar for navigation and links

Is your feature request related to a problem? Please describe.
It'd be nice to have an option for adding a header to the docs.
It can be used to organize navigation in a different way - for example, for having links which are not related directly to the documentation content, important links to related projects, etc. Sometimes it is also a better place for branding (depends on design).
Describe the solution you'd like
Optional header block.
Describe alternatives you've considered

Reusing announcement block (hack)
overriding page.html template to add a header (good to have something standard, out-of-the-box).

Thinking out loud and making notes for a future me... There's basically 2 reasons for someone to want a topbar in documentation:

For linking to other resources/projects
For splitting the same project's documentation into multiple sections (tutorials, reference, etc.)

I'm actually inclined to create a new theme that derives from Furo, that's making a few different design choices (like no announcements, different navigation handling, logo going into the header instead of sidebar). That can be biased toward larger/multi-project documentation sets; which is also where I imagine that something like this would be more appealing. This would also cleanly separate the code and different behavior, which is good -- it limits the user-facing configuration that Furo has to have (fewer the number of knobs, the easier it is to use).


Marked cpuid functions pure

Never mind. Doing this would require inlining all of the initializaiton functions in the static constructor.

Yeah, it would require quite some code shuffling, still a correct change.


The client_id specified does not have access to the api product

Hi,
I get this error when I try to login:
{ "developerMessage":"The client_id specified does not have access to the api product","userMessage":"","errorCode":"AUTH-001","more info":"http://developer.api.autodesk.com/documentation/v1/errors/AUTH-001"}
I am on Windows 10, using Chrome 55 64 bit.

fixed using Node.js command prompt

I have the same problem, what did you do to fix it?

Use Node.js' s command prompt as stated in the installation guide. Don't use Windows CMD or any other shell.

The sample expect to find NODE_ENV, FORGE_CLIENT_ID and FORGE_CLIENT_SECRET as environment variables. On Windows you can use user variables, did you do that on your local machine?


Add Azure provisioner for inlets-operator app

Enables the Azure provisioner for inlets-operator app.
Signed-off-by: Ze Chen<EMAIL_ADDRESS>
Description
This is to enable the Azure provisioner for inlets-operator in arkade.
Motivation and Context

The following up changes in arkade for #47

[x] I have raised an issue to propose this change (required)

How Has This Been Tested?

Install inlets-operator with provider as Azure
arkade install inlets-operator --provider azure --region eastus --token-file ~/client_credentials.json --subscription-id 4d6ffffe-64ee-4a11-e329-c973629efcdb
Using kubeconfig: <User>/.config/k3d/k3s-default/kubeconfig.yaml
Node architecture: "amd64"
Client: "x86_64", "Darwin"
2020/10/17 16:57:18 User dir established as: <User>/.arkade/
"inlets" has been added to your repositories

VALUES values.yaml
Command: <User>/.arkade/bin/helm [upgrade --install inlets-operator inlets/inlets-operator --namespace default --values /var/folders/pf/yb76r0855d7297p2dhq066980000gn/T/charts/inlets-operator/values.yaml --set provider=azure --set subscriptionID=4d6ffffe-64ee-4a11-e329-c973629efcdb --set region=eastus]
Release "inlets-operator" does not exist. Installing it now.
NAME: inlets-operator
LAST DEPLOYED: Sat Oct 17 16:57:23 2020
NAMESPACE: default
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
1. Find the inlets-operator logs:

kubectl logs -n default deploy/inlets-operator
=======================================================================
= inlets-operator has been installed.                                  =
=======================================================================

# The default configuration is for DigitalOcean and your secret is
# stored as "inlets-access-key" in the "default" namespace or the namespace
# you gave if installing with helm3

# To get your first Public IP run the following:

# K8s 1.17
kubectl run nginx-1 --image=nginx --port=80 --restart=Always

# K8s 1.18 and higher:

kubectl apply -f \
 https://raw.githubusercontent.com/inlets/inlets-operator/master/contrib/nginx-sample-deployment.yaml

# Then expose the Deployment as a LoadBalancer:

kubectl expose deployment nginx-1 --port=80 --type=LoadBalancer

# Find your IP in the "EXTERNAL-IP" field, watch for "<pending>" to
# change to an IP

kubectl get svc -w

# When you're done, remove the tunnel by deleting the service
kubectl delete svc/nginx-1

# Check the logs
kubectl logs deploy/inlets-operator -f

# Find out more at:
# https://github.com/inlets/inlets-operator

Thanks for using arkade!

Install Nginx and expose to public using inlets with provider as Azure
➜  ~ kubectl apply -f \
 https://raw.githubusercontent.com/inlets/inlets-operator/master/contrib/nginx-sample-deployment.yaml
deployment.apps/nginx-1 created

➜  ~ kubectl expose deployment nginx-1 --port=80 --type=LoadBalancer
service/nginx-1 exposed

➜  ~ kubectl get svc -w

NAME         TYPE           CLUSTER-IP      EXTERNAL-IP                 PORT(S)        AGE
kubernetes   ClusterIP      <IP_ADDRESS>       <none>                      443/TCP        7m33s
nginx-1      LoadBalancer   <IP_ADDRESS>   <IP_ADDRESS>,<IP_ADDRESS>   80:31085/TCP   2m19s

➜  ~ curl <IP_ADDRESS>|grep title
<title>Welcome to nginx!</title>

Logs inlets-operator
➜  ~ kubectl logs deploy/inlets-operator
2020/10/17 08:57:35 Inlets client: inlets/inlets:2.7.4
W1017 08:57:35.155339       1 client_config.go:552] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
I1017 08:57:35.156548       1 controller.go:123] Setting up event handlers
I1017 08:57:35.156636       1 controller.go:245] Starting Tunnel controller
I1017 08:57:35.156662       1 controller.go:248] Waiting for informer caches to sync
I1017 08:57:35.258107       1 controller.go:253] Starting workers
I1017 08:57:35.258187       1 controller.go:259] Started workers
2020/10/17 08:58:14 Creating tunnel for nginx-1-tunnel.default
I1017 08:58:14.149961       1 controller.go:317] Successfully synced 'default/nginx-1'
2020/10/17 08:58:14 Provisioning started with provider:azure host:nginx-1-tunnel
2020/10/17 08:58:14 Provisioning host with Azure
2020/10/17 08:58:14 Creating resource group inlets-nginx-1-tunnel
2020/10/17 08:58:20 Resource group created inlets-nginx-1-tunnel
2020/10/17 08:58:20 Creating deployment deployment-03beffb7-64d6-41ae-953e-4e11b20e896d
2020/10/17 08:58:27 Provisioning call took: 13.127465s
2020/10/17 08:58:27 Status (nginx-1): provisioning, ID: inlets-nginx-1-tunnel|deployment-03beffb7-64d6-41ae-953e-4e11b20e896d, IP:
I1017 08:58:27.287917       1 controller.go:317] Successfully synced 'default/nginx-1-tunnel'
I1017 08:58:28.880479       1 controller.go:317] Successfully synced 'default/nginx-1-tunnel'
I1017 08:58:36.651687       1 controller.go:317] Successfully synced 'default/nginx-1-tunnel'
I1017 08:59:13.411495       1 controller.go:317] Successfully synced 'default/nginx-1-tunnel'
I1017 08:59:38.606001       1 controller.go:317] Successfully synced 'default/nginx-1-tunnel'
2020/10/17 09:00:07 Status (nginx-1): active, ID: inlets-nginx-1-tunnel|deployment-03beffb7-64d6-41ae-953e-4e11b20e896d, IP: <IP_ADDRESS>

Delete exposed service
➜  ~ kubectl delete svc/nginx-1

service "nginx-1" deleted

➜  ~ kubectl logs deploy/inlets-operator
2020/10/17 09:16:58 Delete event: nginx-1-tunnel default [{v1 Service nginx-1 38f6a815-1b2a-4ee1-bb2a-efdc6a7a4db9 0xc000885f3b 0xc000885f3a}]
2020/10/17 09:16:58 Deleting exit-node for nginx-1: inlets-nginx-1-tunnel|deployment-03beffb7-64d6-41ae-953e-4e11b20e896d, ip: <IP_ADDRESS>

➜  ~ kubectl get svc -w

NAME         TYPE        CLUSTER-IP   EXTERNAL-IP   PORT(S)   AGE
kubernetes   ClusterIP   <IP_ADDRESS>    <none>        443/TCP   24m

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I've read the CONTRIBUTION guide
[x] I have signed-off my commits with git commit -s
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

[ ] I have tested this on arm, or have added code to prevent deployment

Thank you for the PR 👍🙂

Thank you for the review.


TypeError

It throws the following error while running predict_image
TypeError: depthwise_conv2d() got an unexpected keyword argument 'data_format'

Could you provide the entire debug log ?

okay thank you. I have fixed it by updating it to the latest version of keras

I have the same problem even after I upgraded keras


ARROW-16683: [C++] Add missing dependency to bundled gflags target

Rebased to hopefully fix AppVeyor build.


Add Dockerfile

add Dockerfile
add requirements.txt
add pre-built libwally-core and gdk from master and psetv2 branch
add README instructions to build and run the container

Merged with some changes, thanks!


Getting BrowserslistError: Unknown browser query dead

Just forked the project and trying to run gatsby develop which is giving me BrowserslistError: Unknown browser query dead.

@siwalikm you probably has  gatsby-cli v 2.4.1 installed globally.
This is a starter for Gatsby v1, it seems that it has problem with gatsby-cli v2. The workaround the issue is to use local gatsby-cli
The convenient way is to update package.json
  "scripts": {
    "build": "./node_modules/.bin/gatsby build",
    "develop": "./node_modules/.bin/gatsby develop",
   ...

and instead gatsby develop and gatsby build use yarn develop and yarn build

Hi Greg, Thanks a lot, this solved the issue for me. Shall I add a note to the readme.md ?

@siwalikm
Sure. Thank you

Hi Greg,
Tried above. when I excuted command gatsby build it results in same error
success delete html and css files from previous builds — 0.043 s
success open and validate gatsby-config — 0.025 s
info One or more of your plugins have changed since the last time you ran Gatsby. As
a precaution, we're deleting your site's cache to ensure there's not any stale
data
success copy gatsby files — 0.056 s
success onPreBootstrap — 8.508 s
success source and transform nodes — 1.717 s
success building schema — 0.899 s
success createLayouts — 0.010 s
success createPages — 0.121 s
success createPagesStatefully — 0.023 s
success onPreExtractQueries — 0.009 s
success update schema — 0.142 s
success extract queries from components — 0.205 s
success run graphql queries — 3.630 s
success write out page data — 0.008 s
success write out redirect data — 0.006 s
success onPostBootstrap — 0.002 s
info bootstrap finished - 29.591 s
error Generating CSS failed
BrowserslistError: Unknown browser query dead

index.js:37 error
[blog]/[browserslist]/index.js:37:11

thanks,
Suhas

@suhaschitade https://github.com/gatsbyjs/gatsby/issues/8575#issuecomment-425018353


mods.toml for 1.18 somehow ended up in 1.17 asking for all the wrong dependency versions including forge

occultism for 1.17.1 wont launch due to asking for 1.18 versions of forge and dependency mods:
https://github.com/klikli-dev/occultism/blob/version/1.17/src/main/resources/META-INF/mods.toml
was gonna fix it myself, but unsure which minimum versions of the mods you want haha

Closed in 474cfb42330e22388fbccfb9ac0a3b48ab512a66


Compile time error on Linkage.swift on 2.12.0

Getting a compile time error on Linkage.swift defaultLinkage property.
  Linkage.swift:12:9: note: add missing case: '.xcFramework'
        switch type {
        ^

Fixed in 2.13.0

Thanks for getting it sorted so quickly 👏


Update packages gating message

Issue #, if available: https://github.com/aws/eks-anywhere-packages/issues/340
Description of changes: Update packages gating message
Testing (if applicable):
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/cherrypick release-0.11


The node connected to the wallet is not displayed in the delegation destination when setting the delegation harvest

Same issue as for https://github.com/nemgrouplimited/symbol-desktop-wallet/issues/1106
INFO: Remember to check if the current node is a peer node.

#165 Will solve this issue collaterally


"CollapseClauseToAssert" lint/suggestion

Inspired by the following code on luau-lang.org:
https://luau-lang.org/2023/03/31/luau-recap-march-2023.html#:~:text=if not x then error('first argument is nil') end
master
Adds the CollapseClauseToAssert lint, which triggers in the following code:
-- `if`-clause can be collapsed to an `assert`
if X then
    error("SomeErrorMessage")
end

Any number of conditions for the if
No else block
error cannot be given a level argument (change in behavior as assert does not have a level parameter)
Error string must be constant (no string interpolation/concatenation) to avoid slowdowns:

AstExpr* errmsg = call->args.data[0];

// The `if`-clause allows the VM to occasionally (and, in this case, almost always)
// avoid resolving any string operations, but `assert` (like all functions)
// forces it to resolve it's arguments every time they are called, regardless
// of if the condition actually fails.
// https://devforum.roblox.com/t/1289175
// Don't give the suggestion in this case, we don't want to slow people's code down.
if (!errmsg->is<AstExprConstantString>())
    return true;

Body must only be an error call

For some reason, the string formatting wasn't working. I would have liked to have the message substitute the condition and error strings into the lint warning, but it's not too important.
Passed all tests w/ 0 errors, 0 skips (assuming I ran the tests correctly...)
Am I doing this right?

😨Shocked, I was, when I saw... 2 OF 7 CHECKS FAILED ⛈⛈⚡⚡⚡, this being the first time I've failed a Unit Test (or actually done any Unit Tests at all), and... only on Mac OS? Oh no... this is bad... an Operating System-specific compile error?!?!
I furtively middle-clicked macos and macos-arm, and waited in fearful anticipation as GitHub scrolled to the bottom of the compile logs, and- and... and...
Analysis/src/Linter.cpp:2661:36: error: unused variable 'string' [-Werror,-Wunused-variable]
            AstExprConstantString* string = errmsg->as<AstExprConstantString>();
                                   ^

Why does only Mac have -Wunused-variable?

Accidently closed this. Oh well. I don't know if there's any point re-opening it because I would assume the new type solver is the main focus right now.

The role of the linter is to detect patterns of code that are obviously incorrect, rather than to point out equivalency, and this seemed to be the latter. Automated code fixes would be able to give you the option to switch between assert or error versions, with no code warnings since there aren't any bugs in either version.

@alexmccord I actually deleted the fork 3 weeks ago (it's listed as the last event before my message today), I don't think anyone reviewed it, but thanks for the clarification on the role of the Linter :)


Create test infrastructure

Create test infrastructure in repository

We found that using the proptest crate allows for easy arbitrary testing and finding odd cases.
proptest


Not showing?

The winbar with the path doesn't show up for me. I have nvim-treesitter installed and :script shows that the after/ftplugin/json.lua file has loaded.
How else can I troubleshoot this?

Did you include the below snippet in after/ftplugin/json.lua?
if vim.fn.exists("+winbar") == 1 then
  vim.opt_local.winbar = "%{%v:lua.require'jsonpath'.get()%}"
end

This might be confusing, but the plugin does not change the winbar out of the box, it just exposes a function. I'm guessing this may be the problem.

Thanks, but I just can't get it working, which is a pity, as I was hoping this could help me understand jq better.
I even tried using vim-greprtpscr to see if it was loading and it appears that it is. Cheers.

Sorry for this bad experience. Don't know exactly what's going on. Maybe try the oneliner below?
autocmd FileType json setlocal winbar=%{luaeval('require\"jsonpath\".get()')}

Thanks, but that didn't work. I guess I am finally experiencing the consequences of having a complicated setup, as it's proving difficult to debug this.


[WIP] Vessel of the Dragon

Issues

Sync issue when loading world
XP contained gets reset to 0 when receiving mechanical power

Could this have the rendering performance problem of the Cooking Pot (mentioned line 463 and at issue #102 ) ? At the time I think BeetoGuy wanted to move it out in a separate block, but it's always a painful operation (to avoid breaking worlds).

Yeah, I think the conclusion was that the block would be created when the Vessel of the Dragon was added, then move the crucible and cauldron over to that one and removing the rotation state from the old block. And yeah, I think it would be more readable if those facing variables used EnumFacing instead.

So, should I close this and work on a cooking pot overhaul instead?

There is now a vessel of the dragon in the game, although nonfunctional. if you want to implement on that go for it


Swift 360 Video Player

simple360player - Free & ad-free 360 VR Video Player. Flat or Stereoscopic. In Swift 2.

@Aralekk this goes to Video Section.
Do you wanna do the PR, or I can do it for you?

@lfarah Yes sure, do it :)


more syntax problems not caught by Circle CI CLI

@rgardler,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


Don't include null or empty fields in serialized JSON

What is this PR trying to achieve?
Ensure our JSON responses only include fields with interesting values. Resolves #241.
Who is this change for?
Anybody who reads our JSON.
Have the following been considered/are they needed?

[x] Tests – added
[x] Docs – n/a
[x] Spoken to the right people?

That JSON debate... 😁
I'll be writing an article on this at some point.


fix(sync_file): return error to handlerFailureNoLock

ref: https://github.com/longhorn/longhorn/issues/4852, https://github.com/harvester/harvester/issues/3123
Test Step

Install LH and set the default-backing-image-manager-image setting to this branch.
Create a BackingImage with a invalid checksum. We can see the state of the BackingImage will get into failed.

Can the below modification for this fix this issue?
	defer func() {
		err = sf.finishProcessing(err)
	}()

I used another branch to test this modification, but it doesn't work. The root cause is that we update state in handleFailureNoLock function, so we need to give a correct error to it.
https://github.com/FrankYang0529/backing-image-manager/commit/a4a5f9081e6a56c390848fc056eb689c40c367a0

OK, I see.
In my previous suggestion code, the defer function defer sf.handleFailureNoLock inside finishProcessingNoLock does not get a correct error input. If the returned error of finishProcessingNoLock is named finalErr, then the defer function should be defer sf.handleFailureNoLock(finalErr).
If you prefer the current modification, it looks good as well but with one minor suggestion: finishProcessingNoLock does not need to receive an error input. Instead, the error can be handled in the caller part.

Hi @shuo-wu, thanks for the suggestion. After reading https://trstringer.com/golang-deferred-function-error-handling/, I updated Fetch, DownloadFromURL, IdleTimeoutCopyToFile, and Receive to handle errors in the sf.finishProcessing function.


sdk-introduction

Please use the form below, leaving the prefilled data to help us. Thank you.
Page link: sdk-introduction
Document link: sdk-intro.md
My Issue/Suggestion
If you image it, there is probably a way to do it via these SDKs. > If you can imagine it, there is probably a way to do it via these SDKs.
(In case the current sentence is already correct, I don't understand it.)

Hi Michiel,
Thanks for bringing this to our attention.
I've reviewed the document and this sentence doesn't seem to add anything and seems to have been accidentally published while half-written. I have therefore removed it and done a quick review of the rest of the document as well.
Thanks for taking the trouble to report this - we rely on our readers to draw our attention to errors like this and make the documentation better for everyone.
Yours
Mark van Ments