"No translate routes data found. next-translate-routes plugin is probably missing from next.config.js"

I keep getting this error although I followed all the basic steps. I can even see the debug log in the terminal with all the redirects and rewrites created by the plugin, but somehow I'm still getting this error.
What I did:

Wrap you next config with the next-translate-routes plugin

// next.config.js
const { i18n } = require("./next-i18next.config");
const withTranslateRoutes = require("next-translate-routes/plugin")

module.exports = withTranslateRoutes({
  pageExtensions: ["page.tsx", "page.ts", "page.jsx", "page.js"],
  reactStrictMode: true,
  eslint: {
    ignoreDuringBuilds: true,
  },
  esModule: true,
  images: {
    domains: [
      //...
    ],
  },
  i18n,
  translateRoutes: {
    debug: true,
  },
});

Define your routes

// _routes.json
{
  "/": {
    "en": "hi",
    "es": "hola",
    "pt-BR": "oi"
  }
}

Wrap you _app component with the withTranslateRoutes hoc

import { appWithTranslation } from "next-i18next";
import { wrapper } from "../redux";
import { withTranslateRoutes } from "next-translate-routes";

function MyApp({ Component, pageProps }: AppProps) {
  /**/
  return (
    <>
      <Component {...pageProps} />
    </>
  );
}

export default withTranslateRoutes(
  appWithTranslation(wrapper.withRedux(MyApp))
);

What I get in terminal:
[next-translate-routes] - Redirects: [
  {
    source: '/pt-BR/(hi|hola)/downloads/',
    destination: '/oi/downloads/',
    locale: false,
    permanent: false
  },
  {
    source: '/en/(oi|hola)/downloads/',
    destination: '/en/hi/downloads/',
    locale: false,
    permanent: false
  },
...
]
[next-translate-routes] - Rewrites: [
  {
    source: '/(oi|hi|hola)/downloads/',
    destination: '/downloads/'
  },
  {
    source: '/(oi|hi|hola)/about/',
    destination: '/about/'
  },
...
]

And eventually:
Error: [next-translate-routes] - No translate routes data found. next-translate-routes plugin is probably
missing from next.config.js
    at withTranslateRoutes (\node_modules\next-translate-routes\react\withTranslateRoutes.js:63:15)
    at eval (webpack-internal:///./src/pages/_app.page.tsx:71:140)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)

I have searched for other issues here and in Google, but haven't find anything similar. What am I missing?

I had the same issue. After many unsuccessful tries to fix this, I installed v.1.7.2 instead of the latest release and now it's working fine. I'm on Nextjs version 11.1.2 with Preact 10.5.14.

Just upped the version incrementally and it seems like v. 1.8.0-1 is the latest version that still works for me.
So 1.8.0-2 seems to be the issue in my case, or the following commit:
https://github.com/hozana/next-translate-routes/commit/8bfee0f14f05e0b35e1e705711ff980e5e3e551d
any idea @cvolant ?

Thank you both for reporting the issue. Having identified the precise version that introduced the bug is a great help. I will look at it as soon as I can.

Hi, I have the same issue, but my problem is little difference, because I use NX monorepo, and if I want to work next-translate in this monorepo I must add env variable NEXT_TRANSLATE_PATH=apps/projectName I think there is similar problem for me. Is there any variable where I can set up this? My error is Error: [next-translate-routes] - No pages folder found.

Currently working on this issue...
@yzmp, @simonhenke, ...

Are you on Windows?
Could you give me the path to you _app file? Something like /pages/_app.js...

@krystianjj your problem is different: what you are looking for is probably the pageDirectory config.
In next.config.js:
translateRoutes: {
  pageDirectory: 'apps/projetName',
}

See the configuration section in the docs.

@krystianjj your problem is different: what you are looking for is probably the pageDirectory config. In next.config.js:
translateRoutes: {
  pageDirectory: 'apps/projetName',
}

See the configuration section in the docs.

@cvolant
Unfortunately this did not solve the problem.
I want to use your packege with this framework -> https://nx.dev/

@yzmp I suspect that it comes from slashes in paths: \ on Window and / on Linux.
I released<EMAIL_ADDRESS>yesterday, and it includes an attempt to fix this issue: could you try it and tell me if it works?

@cvolant I'm also on Windows and the path is /pages/_app.page.tsx.
I'm excited to try out the new version (probably tomorrow), I'll let you know if it helped :) Thanks!

@cvolant On 1.9.0-3, when I start the app, I now get the following error:
TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string or an instance of Buffer or URL. Received undefined
    at Object.readdirSync (fs.js:1038:10)
    at getAllRoutesFiles (C:\Users\...\node_modules\next-translate-routes\plugin\routesFiles.js:46:39)

@cvolant I'm still getting the same error (ERR_INVALID_ARG_TYPE). In our project we currently have a branch on which we updated to Next12. I'll test the latest version of this lib there as well, maybe that works.

@cvolant Seems to work on Next12, nice! :)


Out of memory when the meta optimizer updates parameters

Hello, I find your code very helpful, but too much memory is consumed when the meta optimizer updates parameters of the model. On my computer, it always raises an error 'out of memory' when executes Line 140 of meta_optimizer.py.
I think it could consume less memory if the MetaModel class holds a flat version of parameters instead of wrapping a model. In this way, the MetaModel reshapes the parameters and computes result through nn.functional.conv/linear, so that the meta optimizer can directly use this flat version of parameters, without allocating extra memory for flatted parameters.

Nevermind that was not the problem, the problem was certainly version change in pytorch and so the operation: flat_params = self.f * flat_params - self.i * Variable(flat_grads) produce a 25450*25450 matrix (not support by my computer). I change to:
        flat_params = torch.t(self.f) * flat_params - torch.t(self.i) * Variable(flat_grads)
        flat_params = flat_params.view(-1)

and it works

Sorry, I didn't have enough time recently to fix problems with this code.
Could you submit a PR with this fix?


Extension naming simplification?

Our naming convention for extensions is namespace-element name-extension, for example, shr-base-TopicCode-extension.  This seems out of step with the way other extensions (defined by FHIR and other work groups) are named; they seem to just use a readable name. Could we simplify our naming to "TopicCode" for the purposes of the IG?  We don't have to change the unique URL.
Note that the full URL for the extension is included in the instance data, so in practice, this shouldn't cause a name collision.

I'll take a look at this to see what we can do.  It seems to be a reasonable request, but I need to see where the IG documentation generator is pulling the name from -- and if that is required to be unique.  One potential issue is that we have some things that have both a profile representation and an extension representation -- and their identifiers need to be unique.

Unfortunately, when an extension is used in a profile, the snapshot view in the IG displays the extension's id rather than name or title.  In the example above, the id is shr-base-TopicCode-extension.
The problem with simplifying the id is two-fold:

the id must be unique in the IG
the id must match the last part of the identifying uri

If we simplify something like my-namespace-MyElement-extension to just MyElement, there are two potential ways we could end up w/ duplicate ids:

If we need to represent MyElement as both a profile and an extension, then they'd both have the same simplified id.  You could disambiguate by adding -extension, which is what I did.
If there was a MyElement in two different namespaces, then they'd both have the same simplified id.  You could disambiguate by adding the namespace, which is what I did.

We could dynamically determine if either of these name clashes happen and only disambiguate if necessary, but then there is a possibility that if we add elements in a future version that cause an ambiguity, we'd change the already published id -- which is not a good thing.

Interesting discussion, perhaps relevant to modularization. Copied remarks into the wiki https://github.com/standardhealth/shr_spec/wiki/Modularity-and-Packaging


RHEL-08-010740 PATCH Task fails if home directory is set to /dev/null

Describe the Issue
On el8 baselines, the tss user’s home directory appears to be set to /dev/null. This causes the Task to fail as /dev/null is a not a directory.
Expected Behavior
Task should gracefully handle a situation where a user’s "home directory” is not actually a directory.
Actual Behavior
Execution of the RHEL-08-010740 PATCH logic fails if a local user’s home directory (as defined in /etc/passwd) is not actually a directory due to the Task’s inclusion of “state: directory”. I acknowledge the intent behind this (why would a home directory not be a home directory?), but in the case of the tss user on el8 baselines, the home directory is not actually a directory.
Control(s) Affected
RHEL-08-010740
Environment (please complete the following information):

branch being used: the latest release (STIG V1R12 April release)
Ansible Version: 8.3.0
Host Python Version: 3.11.5
Ansible Server Python Version: 3.11.5
Additional Details: N/A

Additional Notes

https://access.redhat.com/solutions/6625061
https://access.redhat.com/solutions/6996195

Possible Solution
Either remove the “state: directory” definition or add a conditional that excludes an item if its path is /dev/null (ex. item.dir != '/dev/null') or filter based on shell (ex. item.shell != '/sbin/nologin'). Not sure how you guys would prefer to handle this situation, so I don’t want to assume the proper resolution. Also unsure how likely this is to surface with a non-directory defined as a home directory that isn’t /dev/null.

Looks like the logic introduced with the resolution of https://github.com/ansible-lockdown/RHEL8-STIG/issues/251 impacted both RHEL-08-010740 as well as RHEL-08-010741. The latter logic attempts to access transient paths under /proc that may have existed during initial query but not during attempted “resolution".

Also, with https://github.com/ansible-lockdown/RHEL8-STIG/commit/2f81776ecc07b7b8a717077c4de0e69d2a353965#diff-35cfe8756c71552d3b6700a13f666c527fb0611caa46588369338d2d95f1eb49 we seem to be parsing all of /etc/passwd but arbitrarily filtering out the root, halt, sync, and shutdown users. At a minimum, I would add the nss user (for resolving the /dev/null problem with RHEL-08-010740) and then the dbus, nobody, and system-coredump users (for resolving the /proc/self problem with RHEL-08-010741). Unsure if these are the only accounts that cause this issue with RHEL-08-010741.. Need more testing.

This issue is still present in the latest (3.3.0 // V1R13) release.

hi @SeanathanVT
Thank you for the detailed information. I can see this has been attempted to be addressed a few times and so as to utilise different data to ensure its matching as expected.
Apologies for not picking this up sooner.
Running locally in testing this appears to be addressed? Can you confirm if you are still seeing issues with these control listed?
Many thanks
uk-bolly


UI polish

Fixes ooni/probe#1098

Merging, but documenting the things which are not fixed in a dedicated issue.

https://github.com/ooni/probe/issues/1113


Can O' Spam: Watch carsofl.com

Can O' Spam requests the watch of the watch_keyword carsofl\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

carsofl\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.


ssl-redirect only when incoming port is 80 ?

I have a situation where I have 2 https listen-ports defined and I want ssl redirect to 443 when the incoming request is http:80 .
I have the following annotations:
    alb.ingress.kubernetes.io/actions.redirect: '{"Type": "redirect", "RedirectConfig": { "Protocol": "HTTPS", "Port": "443", "StatusCode": "HTTP_301"}}'
    alb.ingress.kubernetes.io/listen-ports: '[{"HTTP": 80}, {"HTTPS": 443}, {"HTTPS": 8443} ]'

And the first rule is:
  rules:
  - http:
      paths:
      - backend:
          serviceName: redirect
          servicePort: use-annotation
        path: /*

I do NOT want the redirect action when the incoming port is 8443, but it is currently being added to that listener. Is there a way I can modify the actions.redirect annotation to only add the redirect rule on the http:80 listener and not the https:8443 listener ?

hi, it's not supported for now since we cannot specify rules per listener port.
it will be supported after we added support for "ingress group"


Update previewTemplate.html

change toobarElement for Export and Open in browser, because these unicode is not compatible for HTML standard cymbols

Looks good. Thanks for the contribution.


Add env var to --help output for flags and args

Fixes #270

@alecthomas Any chance you have a few minutes to review this again? I would like this feature as well :-)


[BUG] tokio-runtime-worker' panicked at 'called `Option::unwrap()

Describe the bug
When passing the tool a large list from STDIN:
cat URLs |grep -v SOMEURL| /usr/bin/feroxbuster --stdin -r --auto-tune -k --silent -o bigCDrun
I get the error:
thread 'tokio-runtime-worker' panicked at 'called Option::unwrap()on aNone value', src/scanner/requester.rs:131:14
Any thoughts?

hmmm, has something to do with --auto-tune.
I'll try to reproduce, but in the interim, just removing that option should allow you to get back to what you were doing. Below is a snippet from the docs and is what you're losing out on without that particular option.
Also, if you're willing to accept some unsolicited advice, you may be leaving a lot on the table by not using --extract-links, which does the following

parses Allow/Disallow from robots.txt
parses a:href, img:src, form:action, script:src, iframe:src, div:src, frame:src, embed:src tag attributes from html
applies linkfinder regex to any found asset, i.e. catch inline JS from html as well as from *.js files found
detect directory listing and parse the links found therein

Even though that sounds like a lot, the performance hit is negligible, especially for the amount of stuff it finds. I assume you're doing all of this one way or another, but it can all be done in one-shot with -e.
---- auto-tune docs snippet ----
The --auto-tune policy enforces a rate limit on individual directory scans when one of the criteria below is met.

number of general errors (timeouts, etc) is higher than half the number of threads (or at least 25 if threads are lower) (per directory scanned)
90% of responses are 403|Forbidden (per directory scanned)
30% of requests are 429|Too Many Requests (per directory scanned)

The rate limit self-adjusts every (timeout / 2) seconds. If the number of errors have increased during that time, the allowed rate of requests is lowered. On the other hand, if the number of errors hasn’t moved, the allowed rate of requests is increased. If no additional errors are found after a certain number of checks, the rate limit will be removed completely.

follow up:
I'm not able to reproduce this. Can you reliably reproduce with your list of urls?
How many urls are in your list (after the grep)?
The item that .unwrap()'d to None is the object that controls the leaky bucket algorithm used for rate limiting. I'm trying to figure out how one of them could missed being instantiated (doesn't look like that should ever happen, but obviously it can... lol)

this was fixed in 2.7.1, just forgot to close it out


tcpconnect: The header line is printed multiple times

Description
The header line is printed multiple times when running tcpconnect gadget.
Reproduced only when deploying the IG with the option --tools-mode=standard.
Impact
It does not look good and impact the UX.
Environment and steps to reproduce

Set-up: Reproduced in kubeadm and AKS underlay clusters.
Task: Run tcpconnect gadget
Action(s):
a. Deploy IG with --tools-mode=standard
b. Run tcpconnect
Error:$ ./kubectl-gadget tcpconnect -A
Tracing connect ...

Hi.
This bug is sadly tricker than I expected, adding this simple patch:
diff --git a/gadget-container/gadgets/bcck8s/bcc-wrapper.sh b/gadget-container/gadgets/bcck8s/bcc-wrapper.sh
index 1a9cfda..bcc999c 100755
--- a/gadget-container/gadgets/bcck8s/bcc-wrapper.sh
+++ b/gadget-container/gadgets/bcck8s/bcc-wrapper.sh
@@ -136,6 +136,7 @@ if [ "$MANAGER" = "true" ] ; then
     MODE="--cgroupmap"
     MAPPATH=$BPFDIR/gadget/cgroupidset_$TRACERID
   fi
+  echo "Bug ($(hostname))"
   exec $GADGET $MODE $MAPPATH "$@"
 else
   exec $GADGET "$@"

Leads all the gadget to print their header several times (in my case two since I have two nodes):
$ ./kubectl-gadget mountsnoop -n test-ns
Bug (aks-nodepool1-20876740-vmss000001)
NODE             NAMESPACE        POD              CONTAINER        COMM             PID     TID     MNT_NS      CALL
NODE             NAMESPACE        POD              CONTAINER        COMM             PID     TID     MNT_NS      CALL

This leads me to suspect there is a race condition underneath but I am not sure where and how to solve it...
Best regards.

For strange reasons, the first outputted line is not printed.

This is by design. We only print the first line coming from the different nodes once, otherwise the header will be printed multiple times: https://github.com/kinvolk/inspektor-gadget/blob/7925af2181cb6788e2cccfdc998868b080a856ec/cmd/kubectl-gadget/utils/post-process.go#L44

In fact, all the gadgets which print something before the header (like "Hit Ctrl-C to end") are affected:

Yes, we're only skipping the first line (that's why Hit Ctrl-C... line is printed only once in those cases).
I tried to find a way to skip more than one line but it's not that easy to implement without having corner cases where this logic could fail. IMO the effort to fix this issue now is not worth it.

Oh sorry, I missed this option.
A "solution" would be to remove bcc printing "Hit Ctrl-C..." and to skip $n - 1$ first lines (n being the number of nodes).
But I agree with you this is not really worth it.


BCTools runs on wrong web pages.

BCTools runs on each page of www.bondageprojects.com, resulting in many console errors when playing college/poker.
Replacing matching links for content script and permissions with these should fix it:
    "https://www.bondageprojects.com/college/*/BondageClub/",
    "https://bondageprojects.com/college/*/BondageClub/",
    "https://www.bondageprojects.elementfx.com/*/BondageClub/",
    "https://bondageprojects.elementfx.com/*/BondageClub/",
    "http://www.bondageprojects.com/college/*/BondageClub/",
    "http://bondageprojects.com/college/*/BondageClub/",
    "http://www.bondageprojects.elementfx.com/*/BondageClub/",
    "http://bondageprojects.elementfx.com/*/BondageClub/"

The extension should check if it can find the game on the current page, and if not, should disable itself automatically. This was done to support beta and cheater versions, as "BondageClub" in the URL is replaced with a random number.
I see that it throws a lot of errors and keeps throwing "ChatRoomSpace is not defined" even after it couldn't find the ServerSocket variable. I'll look into making it a bit more elegant.

A new version has been published for review on the Chrome web store: v0.5.0. I've rewritten the way the game is detected and the extension should not longer attempt to run on any page other than the club itself.


Incorrect error message regrading loading of module

This line raises an exception when the V2 module, that was just installed, cannot be found in the venv. In that case the error message f"{python_package} does not contain a {namespace_package} module." is returned to the user. However, there are more reason why the path_for() would return None than this reason. This error message occurs for example when someone runs pytest against a V2 module that has a __init__.py file in the inmanta_plugins package. It would be better to explain what goes wrong instead of pointing to a potentially incorrect root cause. But we can for example hint to potential root causes.
The path_for is also implemented in a strange way. In some cases it returns None when the module cannot be loaded and in other cases it raises an InvalidModuleException with a concrete error message. Maybe we have to adjust this method to make it either return the requested path or raise an InvalidModuleException with a specific error message (i.e. not make it return None anymore)?

I'd have to check the code again but I would think that InvalidModuleException means that something was found that looks like a v1/v2 module but that has an invalid format, while None means nothing was found that resembles the requested module type.


No color on produced svg sprite.

Hi everyone. This post is more of a question than an issue. I am new to webpack so I am probably missing something trivial, but please bear with me.
So to give you some context. I am working on a Laravel project and i would like to experiment with svg sprites, to investigate the performance improvement (if any), on the load times and or total size of resources that need to be downloaded.
So my setup is the following:
-Node.js: v9.10.1
-Vue.js: 2.5.17
-svg-sprite-loader: "5.0.0
I appended the configuration using the laravel mix, because i am not yet comfortable enough with webpack itself and maybe that is where I goofed, so i will furthermore supply my webpack.mix.js file.
https://pastebin.com/7uDraWZT
Furthermore in my app.js (main js file) I require the files I want merged, like so:
 const svgFiles = require.context('../images/', true, /.*\.svg$/i) svgFiles.keys().forEach(file => file)
My "source" files are located in:
├── resources
│   ├── images
│   │   └── koromposFolder
│   │       ├── B.svg
│   │       └── W.svg
And after compilation i end up with:
├── public
│   ├── images
│   │   ├── B.svg
│   │   └── sprites
│   │       └── icons-sprite.svg
Which i guess is to be expected, so all well so far (I guess).
Now if i open the generated sprite in the browser i only see a blank page. The svg with the symbols is there with the respective fills but it just does not display.
This is the generated svg https://pastebin.com/pfD44jVH (maybe all works fine and i am missing something).
As a side note, and with that i will be closing the description, i tried the same thing with the files you provide in your examples, just to ensure that the problem is not caused by weird/incorrect formatting of my source SVG files.
Edit: If i try to just import in a vue component like so
import W from '../../../public/images/W.svg'
The watch enters an endless loop... I guess I really got something wrong.
Lastly i would greatly appreciate any input / articles / blogposts / or whatever, concerning the pros and cons of sprites vs separate SVG files vs inlining the svgs. In my search so far everything seems really vague and the most common replay is "Measure for yourself", which is acceptable enough as an answer, but i would also appreciate some more theoretical context.
Thank you for your time,
Best Regards

Well some time has passed and no answer has been given and since the svg displays normally when you reference it, i will be closing this and if someone has any input, just reopen. Thanks.


Update readme with first info and logo/visual scheme

needs to create branches with issue name and PDR prefix


4.04: Crash when using Dragon Ball FighterZ assets

The software seems to hard crash when trying to load the Dragon Ball FighterZ assets, specifically version 1.2 of base_files and full
Running the software from the BAT file reveals the following message:
Reload games
SmashGG characters file updated
Changed to game: dbfz
Loaded stock icons
Character Android 16 has 1 skins
Character Android 17 has 1 skins
Character Android 18 has 1 skins
Character Android 21 has 1 skins
Character Bardock has 1 skins
Character Beerus has 1 skins
Character Broly has 1 skins
Character Broly (DBS) has 1 skins
Character Captain Ginyu has 1 skins
Character Cell has 1 skins
Character Cooler has 1 skins
Character Frieza has 1 skins
Character Gogeta (SS4) has 1 skins
Character Gogeta (SSGSS) has 1 skins
Character Gohan (Adult) has 1 skins
Character Gohan (Teen) has 1 skins
Character Goku has 1 skins
Character Goku (GT) has 1 skins
Character Goku (SSGSS) has 1 skins
Character Goku (Super Saiyan) has 1 skins
Character Goku (Ultra Instinct) has 1 skins
Character Goku Black has 1 skins
Character Gotenks has 1 skins
Character Hit has 1 skins
Character Janemba has 1 skins
Character Jiren has 1 skins
Character Kefla has 1 skins
Character Kid Buu has 1 skins
Character Krillin has 1 skins
Character Majin Buu has 1 skins
Character Master Roshi has 1 skins
Character Nappa has 1 skins
Character Piccolo has 1 skins
Character Super Baby 2 has 1 skins
Character Tien has 1 skins
Character Trunks has 1 skins
Character Vegeta has 1 skins
Character Vegeta (SSGSS) has 1 skins
Character Vegeta (Super Saiyan) has 1 skins
Character Vegito (SSGSS) has 1 skins
Character Videl has 1 skins
Character Yamcha has 1 skins
Character Zamasu (Fused) has 1 skins
Character Android 21 (Lab Coat) has 1 skins
Traceback (most recent call last):
  File "C:\TournamentStreamHelper_Next\TournamentStreamHelper\src\TSHScoreboardStageWidget.py", line 307, in SetupOptions
    self.LoadRulesets()
  File "C:\TournamentStreamHelper_Next\TournamentStreamHelper\src\TSHScoreboardStageWidget.py", line 382, in LoadRulesets
    myRuleset.useDSR = ruleset.get("settings", {}).get(
AttributeError: 'list' object has no attribute 'get'

Fixed on 4.05


image upload mime_content_type check

In the recent 3.13.0 update a function has been added to upload-images.php and some variables to variables.php which should check the MimeType of an uploaded file using the mime_content_type check php functionality. The latter has been marked as deprecated and does not work on my Server with php 7.3.
In order to be able image upload with this version again, either the MimeType check has to be removed or the function has to be re-implemented using Fileinfo which is the successor of mime_content_type check.

Hi,this issue was solved.
Looks like the function mime_content_type is not deprecated.
https://www.php.net/manual/en/function.mime-content-type.php

Hi,this issue was solved.
Looks like the function mime_content_type is not deprecated.
https://www.php.net/manual/en/function.mime-content-type.php

when i upload a image in php5.6 or php7.0 , it will return 500 error .
the error is at upload-images.php:68 , may be it caused by the 'mime_content_type'

can you provide the logs ?

I just insert the 'ajaxResponse("xxx");' at the 68 , and it return 500 code  .
When inserted before line 68 it return 'ajaxResponse("xxx");'

do you have access to the server logs ? called php_error.log ? because I would like to know what happen in the server side

[24-Jul-2020 09:00:52 Asia/Shanghai] PHP Fatal error:  Uncaught Error: Call to undefined function mime_content_type() in C:\phpStudy\WWW\bl-kernel\helpers\filesystem.class.php:311
Stack trace:
#0 C:\phpStudy\WWW\bl-kernel\ajax\upload-images.php(69): Filesystem::mimeType('C:\Windows\php6...')
#1 C:\phpStudy\WWW\bl-kernel\boot\admin.php(50): include('C:\phpStudy\WWW...')
#2 C:\phpStudy\WWW\index.php(37): require('C:\phpStudy\WWW...')
#3 {main}
thrown in C:\phpStudy\WWW\bl-kernel\helpers\filesystem.class.php on line 311
[24-Jul-2020 09:00:57 Asia/Shanghai] PHP Fatal error:  Uncaught Error: Call to undefined function mime_content_type() in C:\phpStudy\WWW\bl-kernel\helpers\filesystem.class.php:311
Stack trace:
#0 C:\phpStudy\WWW\bl-kernel\ajax\upload-images.php(69): Filesystem::mimeType('C:\Windows\php7...')
#1 C:\phpStudy\WWW\bl-kernel\boot\admin.php(50): include('C:\phpStudy\WWW...')
#2 C:\phpStudy\WWW\index.php(37): require('C:\phpStudy\WWW...')
#3 {main}
thrown in C:\phpStudy\WWW\bl-kernel\helpers\filesystem.class.php on line 311
[24-Jul-2020 09:01:06 Asia/Shanghai] PHP Fatal error:  Uncaught Error: Call to undefined function mime_content_type() in C:\phpStudy\WWW\bl-kernel\helpers\filesystem.class.php:311
Stack trace:
#0 C:\phpStudy\WWW\bl-kernel\ajax\upload-images.php(69): Filesystem::mimeType('C:\Windows\php9...')
#1 C:\phpStudy\WWW\bl-kernel\boot\admin.php(50): include('C:\phpStudy\WWW...')
#2 C:\phpStudy\WWW\index.php(37): require('C:\phpStudy\WWW...')
#3 {main}
thrown in C:\phpStudy\WWW\bl-kernel\helpers\filesystem.class.php on line 311
use php5.6 and php7.0 in phpstudy 2016 will report this error .

Thank you, looks like this function is not installed by default in PHP. I will try to do some workaround.

The mime_content_type function is provided by the fileinfo PHP extension, which is (or should be) enabled per default. The function is also not deprecated, even if it was due to a mistake back on the good old PHP 5.3x times.
There is no other easy possibility to read out the mime type, since the only alternative file_info function depends on the mentioned extension as well.
The only possible way I found is to read out the magic number and evaluate them directly, which - of course - is not possible on plain/text files but should work on images, videos, sounds and also on PDFs. But maybe there is also another workaround.

I uploaded a workaround, this happen to a few users.
https://github.com/bludit/bludit/commit/86e0f69030440c82ae82e3b2f3bc11c1f54022f1

Hello, with the new version of Bludit v4.0 rc1, I would like to close the old Github issues. If you feel that your issue is not resolved in the latest version, create a new ticket.

Help and Support use the Forum https://forum.bludit.org
Bugs and new requests here in Github https://github.com/bludit/bludit/issues


Remove the last stop_bit computation from each binary-tree depth

In #487, I changed how we compute the prefix-sum. Determining whether we should accumulate the sibling_value only depends on the current_stop_bit. That means we skip the bottom stop bits at stop_bits[(num_rows - step_size + 1)..], which allows us to reduce 1 mult from each depth = log N mult reduction.

Removed push()


chore: remove dockerfile

cc @marcosnils as the last person to edit this file :eyes:
As far as I'm aware, this Dockerfile isn't actually used for anything? It's not used in our own internal/mage package, and it isn't referenced anywhere in our docs, I think this is legacy from before dagger was built in dagger? Also, since go 1.21, this dockerfile no longer even builds! (gotta love the best error message of all time invalid go version '1.21.5': must match format 1.23)
Additionally, the constants for go versions and alpine are out-of-date from the rest of the code.
Should also close #6349

Oh, I hadn't realized that was the context.
Could there still potentially be users using the old github action? I don't want to have a repeat of the issue from there - though I guess what's changed is that we have decided what to do with dagger-for-github now.

Could there still potentially be users using the old github action?

I doubt it. If that's still the case, since you pointed out, this Dockerfile doesn't work anymore so those users would have to change their pipelines anyways as they'd be broken.


Enhance aria-label for top 10 and 10 around me buttons

clearly state that clicking those buttons will update the leaderboard and note which one is currently selected
in addition enhance aria-labels for values in the cells

PR: https://github.com/NationalSecurityAgency/skills-service/pull/2280

:+1:


Error reverting/updating types from closed archive (#6424)

Describe the bug
Same as #6424 except with the revert and update actions. The source datatype archive is not being modified an does not need to be open for editing.
Environment (please complete the following information):

Ghidra Version: 11.1_DEV

Is this still an issue given that #6424 has been resolved?

Is this still an issue given that #6424 has been resolved?

Yes

The "revert" and "update" operations are not possible without the source archive being open since Ghidra must pull data from the original source type.
I did verify that the "revert" and "update" operations work properly without having the source archive open for edit, although the source archive must be open.

The "revert" and "update" operations are not possible without the source archive being open since Ghidra must pull data from the original source type.
I did verify that the "revert" and "update" operations work properly without having the source archive open for edit, although the source archive must be open.

I meant open for editing. You cannot open the archives provided with Ghidra for editing. Therefore if you attempt to rever the changes you have made to a data type provided in an archive that came with Ghidra it will result in an error 100% of the time.
Aha! Ok, so it only occurs when you use the action on the archive containing the modified datatype and does not occur when reverting it from the datatype.
I mostly blame my explanation here, communication is difficult.
application.log.txt

Thanks.  Much improved explanation and I was easily able to reproduce.  I will submit for fix.

Thanks.  Much improved explanation and I was easily able to reproduce.  I will submit for fix.

If I'm ever unclear or am not making sense, feel free to give me an earful about it. I often misunderstand and am misunderstood.
This just about sums it up.


possible this bug?

Noticing that the this object here is referencing the window object and not the expected instance of Superlogin.
Thinking it's because it may need this line to change from this:
			const _oauthInterval = setInterval(function () {

to this
			const _oauthInterval = setInterval(() => {

Or this line from this:
			}, 500);

to this
			}.bind(this), 500);

I noticed it when I click the "close" button on my oauth browser window.
Thoughts?

Good catch.
Could you send a PR with your first proposal.

@micky2be will do. Before I do, can you tell me the purpose of this.authComplete = true; It only appears to be set once - but never used? Am I missing something?


Allow greater control to disable DLRS globally or in specific cases

Changes

Allow DLRS to be disabled globally using new Custom Setting field
Allow DLRS to be disabled globally using new Apex API method: RollupService.bypassAll()
Allow individual Rollups to have a Custom Permission assigned that, when held by the user, will disable that rollup

Issues Closed
#1469
#786
#468

@octatau could I get another review on this one? We expanded the scope of the behavior toggles to background jobs.


Overwriting cs files in folder while folder is source of csproj in vs2017 RTM makes nuget restore fail on build

Hi,
I have two .net standard 1.6 class libraries in one solution, with the following contents:
AW.Model.csproj
<?xml version="1.0" encoding="utf-8"?>
<Project Sdk="Microsoft.NET.Sdk">
  <PropertyGroup>
    <TargetFramework>netstandard1.6</TargetFramework>
    <AssemblyName>AW.Model</AssemblyName>
    <RootNamespace>AW</RootNamespace>
  </PropertyGroup>
</Project>

<?xml version="1.0" encoding="utf-8"?>
<Project Sdk="Microsoft.NET.Sdk">
  <PropertyGroup>
    <TargetFramework>netstandard1.6</TargetFramework>
    <AssemblyName>AW.Persistence</AssemblyName>
    <RootNamespace>AW</RootNamespace>
  </PropertyGroup>
  <ItemGroup>
    <PackageReference Include="Microsoft.EntityFrameworkCore.SqlServer" Version="1.1.1" />
  </ItemGroup>
  <ItemGroup>
    <ProjectReference Include="..\Model\AW.Model.csproj" />
  </ItemGroup>
</Project>

They're in their own folders, Model for the first, Persistence for the second. Both folders contain .cs files, all being generated.
Now I re-generate the code files in the two folders while I have the two csproj files open in a solution (and no other projects) in vs2017 RTM. The csproj files are overwritten with the same contents (so are the other files).
When I now try to build, I get the error:
Error occurred while restoring NuGet packages: The operation failed as details for project AW.Persistence could not be loaded.
Log of MSBuild in vs2017 on rebuild with detail level 'normal'
Error occurred while restoring NuGet packages: The operation failed as details for project AW.Persistence could not be loaded.
1>------ Rebuild All started: Project: AW.Model, Configuration: Debug Any CPU ------
1>Build started 10-3-2017 10:51:46.
1>Target CoreClean:
1>  Deleting file "C:\Temp\generatortest\test1\Model\bin\Debug\netstandard1.6\AW.Model.deps.json".
1>  Deleting file "C:\Temp\generatortest\test1\Model\bin\Debug\netstandard1.6\AW.Model.dll".
1>  Deleting file "C:\Temp\generatortest\test1\Model\bin\Debug\netstandard1.6\AW.Model.pdb".
1>  Deleting file "C:\Temp\generatortest\test1\Model\obj\Debug\netstandard1.6\AW.Model.AssemblyInfo.cs".
1>  Deleting file "C:\Temp\generatortest\test1\Model\obj\Debug\netstandard1.6\AW.Model.dll".
1>  Deleting file "C:\Temp\generatortest\test1\Model\obj\Debug\netstandard1.6\AW.Model.pdb".
1>Target GenerateTargetFrameworkMonikerAttribute:
1>  Skipping target "GenerateTargetFrameworkMonikerAttribute" because all output files are up-to-date with respect to the input files.
1>Target CoreCompile:
1>  Using shared compilation with compiler from directory: C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\15.0\Bin\Roslyn
1>Target CopyFilesToOutputDirectory:
1>  Copying file from "obj\Debug\netstandard1.6\AW.Model.dll" to "bin\Debug\netstandard1.6\AW.Model.dll".
1>  AW.Model -> C:\Temp\generatortest\test1\Model\bin\Debug\netstandard1.6\AW.Model.dll
1>  Copying file from "obj\Debug\netstandard1.6\AW.Model.pdb" to "bin\Debug\netstandard1.6\AW.Model.pdb".
1>
1>Build succeeded.
1>
1>Time Elapsed 00:00:00.18
2>------ Rebuild All started: Project: AW.Persistence, Configuration: Debug Any CPU ------
2>Build started 10-3-2017 10:51:46.
2>Target CoreClean:
2>  Deleting file "C:\Temp\generatortest\test1\Persistence\bin\Debug\netstandard1.6\AW.Persistence.dll.config".
2>  Deleting file "C:\Temp\generatortest\test1\Persistence\bin\Debug\netstandard1.6\AW.Persistence.deps.json".
2>  Deleting file "C:\Temp\generatortest\test1\Persistence\bin\Debug\netstandard1.6\AW.Persistence.dll".
2>  Deleting file "C:\Temp\generatortest\test1\Persistence\bin\Debug\netstandard1.6\AW.Persistence.pdb".
2>  Deleting file "C:\Temp\generatortest\test1\Persistence\bin\Debug\netstandard1.6\AW.Model.dll".
2>  Deleting file "C:\Temp\generatortest\test1\Persistence\bin\Debug\netstandard1.6\AW.Model.pdb".
2>  Deleting file "C:\Temp\generatortest\test1\Persistence\obj\Debug\netstandard1.6\AW.Persistence.csprojResolveAssemblyReference.cache".
2>  Deleting file "C:\Temp\generatortest\test1\Persistence\obj\Debug\netstandard1.6\AW.Persistence.AssemblyInfo.cs".
2>  Deleting file "C:\Temp\generatortest\test1\Persistence\obj\Debug\netstandard1.6\AW.Persistence.dll".
2>  Deleting file "C:\Temp\generatortest\test1\Persistence\obj\Debug\netstandard1.6\AW.Persistence.pdb".
2>Target _GetProjectReferenceTargetFrameworkProperties:
2>Target ResolveProjectReferences:
2>Target GenerateTargetFrameworkMonikerAttribute:
2>  Skipping target "GenerateTargetFrameworkMonikerAttribute" because all output files are up-to-date with respect to the input files.
2>Target CoreCompile:
2>  Using shared compilation with compiler from directory: C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\15.0\Bin\Roslyn
2>Target _CopyFilesMarkedCopyLocal:
2>  Copying file from "C:\Temp\generatortest\test1\Model\bin\Debug\netstandard1.6\AW.Model.dll" to "bin\Debug\netstandard1.6\AW.Model.dll".
2>  Copying file from "C:\Temp\generatortest\test1\Model\bin\Debug\netstandard1.6\AW.Model.pdb" to "bin\Debug\netstandard1.6\AW.Model.pdb".
2>Target GetCopyToOutputDirectoryItems:
2>Target _CopyAppConfigFile:
2>  Copying file from "app.config" to "bin\Debug\netstandard1.6\AW.Persistence.dll.config".
2>Target CopyFilesToOutputDirectory:
2>  Copying file from "obj\Debug\netstandard1.6\AW.Persistence.dll" to "bin\Debug\netstandard1.6\AW.Persistence.dll".
2>  AW.Persistence -> C:\Temp\generatortest\test1\Persistence\bin\Debug\netstandard1.6\AW.Persistence.dll
2>  Copying file from "obj\Debug\netstandard1.6\AW.Persistence.pdb" to "bin\Debug\netstandard1.6\AW.Persistence.pdb".
2>
2>Build succeeded.
2>
2>Time Elapsed 00:00:00.47
========== Rebuild All: 2 succeeded, 0 failed, 0 skipped ==========

This is strange as the project is loaded properly, I can navigate the references in solution explorer as well and builds go fine. Closing / reopening VS2017 and reloading the solution file fixes the problem.

Additional info: once the sln is loaded from disk in a new vs2017 session, I can't reproduce the problem. So my guess is that this is related to some state being wrong when the sln is created (and saved), projects are added and then modified outside vs2017. Might be related to the issue I reported yesterday: #1725

This looks a lot like https://github.com/NuGet/Home/issues/4577. @emgarten @alpaix?

@FransBouma the message looks scary but you can ignore it, NuGet will retry when the project details are loaded and restore everything.
@davkean yes looks like the same issue, you can probably close this one out

@emgarten

the message looks scary but you can ignore it, NuGet will retry when the project details are loaded and restore everything.

But that never happens unless the sln is re-loaded. So although it might retry, it will never actually work: only reloading the solution works. I agree though that it looks like the same issue, which IMHO all come from a bug somewhere in the initialization of the internal datastructures, as the problems are gone when the sln is reloaded, but are present when the sln is created, saved but not reloaded.

So although it might retry, it will never actually work: only reloading the solution works

Even after waiting the project isn't restored?

Indeed, it stays this way. I tried numerous things for 5-10 minutes, nothing. Restarted vs2017 and reloaded the solution and that sorted it.
it's not an error that you see due to some data that's not available yet and will be gone in a few seconds or so, it's not solvable unless the solution is reloaded.

@FransBouma thanks for the details, sounds like you are hitting more than just the timing issues. If it does work to reload everything then the solution/projects are likely correct. It sounds like this is just an issue with restore.

Does right clicking on the solution and selecting restore help when you hit this?

I will try that tomorrow and see what the outcome is :)

I can't reproduce it now... very strange! And not very good of course, as it might pop up later. Anyway, let's chalk this up for the restore issue already known then. I have no other explanation.
Is issue #1717 also caused by the same issue?

This issue was moved to NuGet/Home#4846

We'll track this over in the NuGet repo.


add passthrough filter chain support for v1beta1 authorization policy

For #12394

Added e2e tests with v1beta1 authorization policy for the passthrough filter chain.
Tested manually in the cluster that the RBAC filter is inserted for the passthrough filter chain.

And to help us figure out who should review this PR, please
put an X in all the areas that this PR affects.

@yangminzhu: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

unit-tests_istio
8881a441abd8d638138ace333a9da90f28960d11
link
/test unit-tests_istio

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

@yangminzhu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

unit-tests_istio
8881a441abd8d638138ace333a9da90f28960d11
link
/test unit-tests_istio

pilot-multicluster-e2e_istio
8881a441abd8d638138ace333a9da90f28960d11
link
/test pilot-multicluster-e2e_istio

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

@yangminzhu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

unit-tests_istio
8881a441abd8d638138ace333a9da90f28960d11
link
/test unit-tests_istio

pilot-multicluster-e2e_istio
8881a441abd8d638138ace333a9da90f28960d11
link
/test pilot-multicluster-e2e_istio

lint_istio
8881a441abd8d638138ace333a9da90f28960d11
link
/test lint_istio

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

@yangminzhu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

unit-tests_istio
8881a441abd8d638138ace333a9da90f28960d11
link
/test unit-tests_istio

pilot-multicluster-e2e_istio
8881a441abd8d638138ace333a9da90f28960d11
link
/test pilot-multicluster-e2e_istio

lint_istio
8881a441abd8d638138ace333a9da90f28960d11
link
/test lint_istio

integ-galley-k8s-tests_istio
8881a441abd8d638138ace333a9da90f28960d11
link
/test integ-galley-k8s-tests_istio

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

@yangminzhu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

unit-tests_istio
8881a441abd8d638138ace333a9da90f28960d11
link
/test unit-tests_istio

pilot-multicluster-e2e_istio
8881a441abd8d638138ace333a9da90f28960d11
link
/test pilot-multicluster-e2e_istio

lint_istio
8881a441abd8d638138ace333a9da90f28960d11
link
/test lint_istio

integ-galley-k8s-tests_istio
8881a441abd8d638138ace333a9da90f28960d11
link
/test integ-galley-k8s-tests_istio

integ-new-install-k8s-tests_istio
8881a441abd8d638138ace333a9da90f28960d11
link
/test integ-new-install-k8s-tests_istio

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

@yangminzhu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

unit-tests_istio
8881a441abd8d638138ace333a9da90f28960d11
link
/test unit-tests_istio

pilot-multicluster-e2e_istio
8881a441abd8d638138ace333a9da90f28960d11
link
/test pilot-multicluster-e2e_istio

lint_istio
8881a441abd8d638138ace333a9da90f28960d11
link
/test lint_istio

integ-galley-k8s-tests_istio
8881a441abd8d638138ace333a9da90f28960d11
link
/test integ-galley-k8s-tests_istio

integ-new-install-k8s-tests_istio
8881a441abd8d638138ace333a9da90f28960d11
link
/test integ-new-install-k8s-tests_istio

integ-mixer-k8s-tests_istio
8881a441abd8d638138ace333a9da90f28960d11
link
/test integ-mixer-k8s-tests_istio

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

Right now don't we only call rbac/mixer code through the plug-in interface? directly calling rbac here seems like the wrong place since it breaks the plug-in abstraction

Switched to use plugin interface.
@lambdai Also added an e2e test.

@yangminzhu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

unit-tests_istio
8881a441abd8d638138ace333a9da90f28960d11
link
/test unit-tests_istio

pilot-multicluster-e2e_istio
8881a441abd8d638138ace333a9da90f28960d11
link
/test pilot-multicluster-e2e_istio

integ-galley-k8s-tests_istio
8881a441abd8d638138ace333a9da90f28960d11
link
/test integ-galley-k8s-tests_istio

integ-new-install-k8s-tests_istio
8881a441abd8d638138ace333a9da90f28960d11
link
/test integ-new-install-k8s-tests_istio

integ-mixer-k8s-tests_istio
8881a441abd8d638138ace333a9da90f28960d11
link
/test integ-mixer-k8s-tests_istio

lint_istio
4fa92c7947b5c3108493430b7e1a98d43289e7f8
link
/test lint_istio

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

@yangminzhu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

unit-tests_istio
8881a441abd8d638138ace333a9da90f28960d11
link
/test unit-tests_istio

integ-galley-k8s-tests_istio
8881a441abd8d638138ace333a9da90f28960d11
link
/test integ-galley-k8s-tests_istio

integ-new-install-k8s-tests_istio
8881a441abd8d638138ace333a9da90f28960d11
link
/test integ-new-install-k8s-tests_istio

integ-mixer-k8s-tests_istio
8881a441abd8d638138ace333a9da90f28960d11
link
/test integ-mixer-k8s-tests_istio

lint_istio
4fa92c7947b5c3108493430b7e1a98d43289e7f8
link
/test lint_istio

pilot-multicluster-e2e_istio
7ad9ead619874ca88cb39d8cf377fb6b8d08a0d4
link
/test pilot-multicluster-e2e_istio

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

@yangminzhu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

unit-tests_istio
8881a441abd8d638138ace333a9da90f28960d11
link
/test unit-tests_istio

integ-galley-k8s-tests_istio
8881a441abd8d638138ace333a9da90f28960d11
link
/test integ-galley-k8s-tests_istio

integ-new-install-k8s-tests_istio
8881a441abd8d638138ace333a9da90f28960d11
link
/test integ-new-install-k8s-tests_istio

integ-mixer-k8s-tests_istio
8881a441abd8d638138ace333a9da90f28960d11
link
/test integ-mixer-k8s-tests_istio

pilot-multicluster-e2e_istio
7ad9ead619874ca88cb39d8cf377fb6b8d08a0d4
link
/test pilot-multicluster-e2e_istio

lint_istio
7ad9ead619874ca88cb39d8cf377fb6b8d08a0d4
link
/test lint_istio

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

@yangminzhu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

pilot-multicluster-e2e_istio
7ad9ead619874ca88cb39d8cf377fb6b8d08a0d4
link
/test pilot-multicluster-e2e_istio

integ-new-install-k8s-tests_istio
9264ba1438ae6e5a42c43ef16c1cf4fe4e7c5982
link
/test integ-new-install-k8s-tests_istio

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

@yangminzhu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-new-install-k8s-tests_istio
9264ba1438ae6e5a42c43ef16c1cf4fe4e7c5982
link
/test integ-new-install-k8s-tests_istio

pilot-multicluster-e2e_istio
9264ba1438ae6e5a42c43ef16c1cf4fe4e7c5982
link
/test pilot-multicluster-e2e_istio

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

@yangminzhu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-new-install-k8s-tests_istio
9264ba1438ae6e5a42c43ef16c1cf4fe4e7c5982
link
/test integ-new-install-k8s-tests_istio

pilot-multicluster-e2e_istio
9264ba1438ae6e5a42c43ef16c1cf4fe4e7c5982
link
/test pilot-multicluster-e2e_istio

lint_istio
e707fd7a64429afb94ae45ff3b16da0b11203112
link
/test lint_istio

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

@yangminzhu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-new-install-k8s-tests_istio
9264ba1438ae6e5a42c43ef16c1cf4fe4e7c5982
link
/test integ-new-install-k8s-tests_istio

lint_istio
e707fd7a64429afb94ae45ff3b16da0b11203112
link
/test lint_istio

pilot-multicluster-e2e_istio
2164ca1460415bda5538f60e562d0599ec939848
link
/test pilot-multicluster-e2e_istio

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

@yangminzhu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-new-install-k8s-tests_istio
9264ba1438ae6e5a42c43ef16c1cf4fe4e7c5982
link
/test integ-new-install-k8s-tests_istio

pilot-multicluster-e2e_istio
2164ca1460415bda5538f60e562d0599ec939848
link
/test pilot-multicluster-e2e_istio

integ-mixer-k8s-tests_istio
2164ca1460415bda5538f60e562d0599ec939848
link
/test integ-mixer-k8s-tests_istio

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

@yangminzhu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

pilot-multicluster-e2e_istio
2164ca1460415bda5538f60e562d0599ec939848
link
/test pilot-multicluster-e2e_istio

integ-mixer-k8s-tests_istio
2164ca1460415bda5538f60e562d0599ec939848
link
/test integ-mixer-k8s-tests_istio

integ-new-install-k8s-tests_istio
2164ca1460415bda5538f60e562d0599ec939848
link
/test integ-new-install-k8s-tests_istio

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

@yangminzhu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

pilot-multicluster-e2e_istio
2164ca1460415bda5538f60e562d0599ec939848
link
/test pilot-multicluster-e2e_istio

integ-mixer-k8s-tests_istio
2164ca1460415bda5538f60e562d0599ec939848
link
/test integ-mixer-k8s-tests_istio

integ-new-install-k8s-tests_istio
66b7b82b61d2a50a03ef4f4a731b23da2062dddf
link
/test integ-new-install-k8s-tests_istio

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

@howardjohn @rshriram @lambdai Could you approve if there is no change needed? Thanks.

Generally LGTM
@yxue could you share some light on how tcp service is tested on default chain?
I didn't catch up all the progress. My impression was left at the age that echo client will always be sniffed as http since the traffic pattern at echo client is always Http-like.

integ-new-install-k8s-tests_istio is failing on the new test

/test integ-new-install-k8s-tests_istio

@yangminzhu: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-new-install-k8s-tests_istio
66b7b82b61d2a50a03ef4f4a731b23da2062dddf
link
/test integ-new-install-k8s-tests_istio

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

The test failed with timeout:
=== RUN   TestMirroring
2019-10-25T22:48:12.163262Z	info	pickfirstBalancer: HandleSubConnStateChange: 0xc00062bdd0, CONNECTING
2019-10-25T22:48:12.170807Z	info	pickfirstBalancer: HandleSubConnStateChange: 0xc00062bdd0, READY
2019-10-25T22:48:22.665491Z	info	transport: loopyWriter.run returning. connection error: desc = "transport is closing"
panic: test timed out after 30m0s

Let me rerun it one again /test integ-new-install-k8s-tests_istio

/test integ-new-install-k8s-tests_istio

@howardjohn The integ-new-install-k8s-tests_istio is now failing for time out on many different PRs: https://k8s-testgrid.appspot.com/istio_istio#integ-new-install-k8s-tests_istio&width=20, I suspect there is something else causing the timeout, can we merge this PR first?

@yangminzhu understood, that will need to be fixed. I am working on making the test required.
Your PR is introducing an additional failure though. So we can merge if that passes, but not add a new error

@howardjohn How do you know this PR is introducing new error for the test?
Also filed https://github.com/istio/istio/issues/18351 for the test failing.

Your PR adds TestV1beta1_PassThroughFilterChain which failed in https://prow.istio.io/view/gcs/istio-prow/pr-logs/pull/istio_istio/18207/integ-new-install-k8s-tests_istio/2282 and https://prow.istio.io/view/gcs/istio-prow/pr-logs/pull/istio_istio/18207/integ-new-install-k8s-tests_istio/2242, or is that just an old commit I was looking at maybe?

@yangminzhu: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-new-install-k8s-tests_istio
73e6d9aee98e2d76b9bf815f59f534068f41f7d1
link
/test integ-new-install-k8s-tests_istio

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

/test integ-new-install-k8s-tests_istio

Your PR adds TestV1beta1_PassThroughFilterChain which failed in https://prow.istio.io/view/gcs/istio-prow/pr-logs/pull/istio_istio/18207/integ-new-install-k8s-tests_istio/2282 and https://prow.istio.io/view/gcs/istio-prow/pr-logs/pull/istio_istio/18207/integ-new-install-k8s-tests_istio/2242, or is that just an old commit I was looking at maybe?

I suspect these are from some old commits, I tried to run make test.integration.new.installer with a small customization to the configmap to remove the applicationPorts to workaround the other issue, The TestV1beta1_PassThroughFilterChain is passing with it.

@yangminzhu: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-new-install-k8s-tests_istio
73e6d9aee98e2d76b9bf815f59f534068f41f7d1
link
/test integ-new-install-k8s-tests_istio

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

/retest

@howardjohn It seems istio-testing doesn't create the cherrypick to release-1.4 automatically for this PR, will create one manually.

/cherrypick release-1.4

@howardjohn: new pull request created: #18409

In response to this:

/cherrypick release-1.4

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


Check to make sure password is dirty before hashning

To prevent double-hashing on updates.

Thanks 😄


Tweak some tests that failed on Unity

let me know if you need me to also update the version # etc

let me know if you need me to also update the version # etc

I'm merging this as is.  But on #85 please update NEWS and DESCRIPTION as well.


fix(cdk/coercion): add the support for readonly array coercion

Fixes a type definition of coerceArray so that it accepts both mutable and
immutable arrays.
Fixes #18806

@crisbeto I updated the code according to your comment. Can you have a look?

LGTM

ci/angular merge status is still blocking while the tag was added. Am I missing something?


dyld: Symbol not found

I am adding the framework manually in my workspace with the source. The project builds successfully but when I try to run it on the simulator, I get the following error message, possibly due to a namespace collision with a tvOS framework:
dyld: Symbol not found: OBJC_CLASS$_BBAction
Referenced from: /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/Library/CoreSimulator/Profiles/Runtimes/iOS.simruntime/Contents/Resources/RuntimeRoot/System/Library/Frameworks/VideoSubscriberAccount.framework/VideoSubscriberAccount
Expected in: /Users/gargs/Library/Developer/Xcode/DerivedData/iPhoneApp-gsobcvjpesljtaakzbpampqecelj/Build/Products/Debug-iphonesimulator/BulletinBoard.framework/BulletinBoard
in /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/Library/CoreSimulator/Profiles/Runtimes/iOS.simruntime/Contents/Resources/RuntimeRoot/System/Library/Frameworks/VideoSubscriberAccount.framework/VideoSubscriberAccount
New Issue Checklist

[X] I updated BulletinBoard to the latest version.
[X] I read the Contribution Guidelines.
[X] I read the documentation.
[X] I searched for existing GitHub issues.

Issue Description
The issue occurs when the framework is manually added as a build dependency in a workspace. If I rename the product from 'BulletinBoard' to anything else, I am able to build and run on both device as well as the simulator. I am probably doing something wrong, but would really appreciate help on figuring out what exactly that is.

Environment

iOS Version: 11.2
Device(s): iPhone X Simulator

@gargs Hello! Did you solve this problem?

@gargs @artoymsd It appears that there is a conflict with a private framework Apple added on iOS 11.1 that's named ... BulletinBoard. The only way to get around this would be to rename the library. Working on a fix for the v2 release.

That’s what I did in my private branch.
Sent from my iPhone

On 23 Apr 2018, at 10:29 AM, Alexis Aubry<EMAIL_ADDRESS>wrote:
@gargs @artoymsd It appears that there is a conflict with a private framework Apple added on iOS 11.1 that's named ... BulletinBoard. The only way to get around this would be to rename the library. Working on a fix for the v2 release.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

I have fixed this on the v2 branch. All classes now have the BLTN prefix, and the module was renamed to BLTNBoard to avoid these conflicts. The fix will be available in the next beta release. Thanks for reporting this issue!


Feature request: error and latency logging

It would be nice if the LoggerFunc interface also had provided to it the outcome of the query, such as the number of rows returned, execution latency and the error. This could also be achieved by providing a middleware interceptor.

Agreed.

New SetQueryLogger function added to support this feature in Release 2.7.0  - wiki


Snippets for JS/TS

Hi!
I've noticed that snippets don't work when JS or TS language is enabled, would it be possible to fix it?
Thanks!

Hey, thank you for bringing it to my notice. I will try to fix it asap. I totally forgot the code. It might take a while for me to fix.
Thank you for using my extension :)


Make linked object a single array of all linked relations, regardless of type

Also:

Made model index lookup an object outside of exporter closure
Fixed instances of sending linked model ids as a number instead of a string

:+1:


Make install path problem

The make install instruction will place shared library into ${CMAKE_INSTALL_PREFIX} which on Ubuntu is  usr/local/lib.
I think the header files need to place in /usr/local/include so that the gcc #include can find these file properly without explicitly set argument -I (or in readme.md "> sudo make install (install the library and header files in /usr/local/lib and /usr/local/include" should be update). I found #223 discussed about this but in #89 said this is fine. Are there any other consideration about this?
Also, libmimalloc.so is used to link the shared library in compile time. However, when run the program(without any arguments like LD_LIBRARY_PATH or LD_PRELOAD), it will cause No such file or directory error in finding libmimalloc.so.{version}, which is the soname of shared library.
$ gcc myprogram.c -lmimalloc
$ ldd a.out
	linux-vdso.so.1 (0x00007fff45feb000)
	libmimalloc.so.2.0 => not found
	libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f849292c000)
	/lib64/ld-linux-x86-64.so.2 (0x00007f8492b45000)

This is because ld cannot search the path under usr/local/lib likes usr/local/lib/mimallc-2.0.
I think we can place libmimalloc.so.{major-version} in /usr/local/lib and add symbolic link to shared library.
Something like these:
/usr/local
├── include
│   ├── mimalloc-2.0
│   │   ├── mimalloc.h
│   │   ├── mimalloc-new-delete.h
│   │   └── mimalloc-override.h
├── lib
│   ├── libmimalloc.so -> libmimalloc.so.2 (symbolic link)
│   ├── libmimalloc.so.2 -> mimalloc-2.0/libmimalloc.so.2.0 (symbolic link)
│   ├── mimalloc-2.0
│   │   ├── cmake
│   │   │   ├── mimalloc.cmake
│   │   │   ├── mimalloc-config.cmake
│   │   │   ├── mimalloc-config-version.cmake
│   │   │   └── mimalloc-release.cmake
│   │   ├── include
│   │   │   ├── mimalloc.h
│   │   │   ├── mimalloc-new-delete.h
│   │   │   └── mimalloc-override.h
│   │   ├── libmimalloc.a
│   │   ├── libmimalloc.so -> libmimalloc.so.2.0
│   │   ├── libmimalloc.so.2.0
│   │   └── mimalloc.o

and then this all can be linked properly by ldconfig.

Yes I think you are right; when I first made the cmake rules I wanted to install everything in one directory instead of spread out; but I think now that was a mistake as it just doesn't fit with the way unix installs are set up (with lib, bin, and share etc).
I'll take a look if I can fix this.

Should be fixed now: the install looks like /
<prefix>
├── include
│   ├── mimalloc-2.0
│   │   ├── mimalloc.h
│   │   ├── mimalloc-new-delete.h
│   │   └── mimalloc-override.h
├── lib
│   ├── libmimalloc.so -> mimalloc-2.0/libmimalloc.so.2.0 (symbolic link)
│   ├── libmimalloc.so.2.0 -> mimalloc-2.0/libmimalloc.so.2.0 (symbolic link)
│   ├── mimalloc-2.0
│   │   ├── libmimalloc.a
│   │   ├── libmimalloc.so -> libmimalloc.so.2.0
│   │   ├── libmimalloc.so.2.0
│   │   └── mimalloc.o
├── share
│   ├── mimalloc-2.0
│   │   ├── cmake
│   │   │   ├── mimalloc.cmake
│   │   │   ├── mimalloc-config.cmake
│   │   │   ├── mimalloc-config-version.cmake
│   │   │   └── mimalloc-release.cmake

(and with MI_INSTALL_TOPLEVEL=ON the files go directtly to include, lib, and cmake.)


Limit world size?

Is there a way to limit the world size to like 64x64x64 or 128x64x128?

Hi, at the data level the world is (sorta) infinite, but you can define the world data to be empty beyond a certain size, or solid blocks beyond some boundary, in order to limit the player to a given area. Is that what you mean?

yes that's what i mean, i could make it transparent blocks outside so you can not move out, but wouldn't the blocks still show up as selected when you look at them?

that also wouldn't limit building outside of the area

check this https://github.com/moddio/box .
We are limiting the size of the map in world.js

yes that's what i mean, i could make it transparent blocks outside so you can not move out, but wouldn't the blocks still show up as selected when you look at them?

There's no built-in setting for area limits, but the engine should have all the tools you need to set whatever rules you want to happen.
For blocking player movement, the easiest thing will be solid transparent blocks, as I imagine you've already tried. To make those blocks not selectable, check the engine's default block-target highlight function. By default it just draws a highlight whenever the target block is solid, but if you set the skipDefaultHighlighting option then the engine won't do any highlighting, and you can add your own targetBlockChanged listener that draws highlights as you like (e.g. skipping the highlight if the target is your invisible barrier block).
As for building, the engine has no built-in behaviors for this. It has APIs for creating/destroying blocks, and it fires events when the player clicks the mouse, but how your game links those together is up to you. Here is the handler from the hello-world example where it creates blocks on mouse events, so you could use code like that but with added logic to disallow building outside certain regions, etc.

alright, thanks


Uploaded solution for problem number 83 of leetcode i.e Remove Duplicates from Sorted List

I am unable to send another PR . Whenever I am sending a second PR , it's
showing " view pull request " . I donno what to do. I am a beginner in open
source. Can you please kindly help
On Sun, 4 Oct, 2020, 10:43 PM Vishruth Subramanian, <
<EMAIL_ADDRESS>wrote:

@Vishruth-S commented on this pull request.
This has 54 file changes instead of 2.
Please fork the repo again and send another PR.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Vishruth-S/CompetitiveCode/pull/94#pullrequestreview-501641917,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOUQZZ5N272LPO3YTIAQSA3SJCUKBANCNFSM4SDXHD3A
.

@tanmoyee04  Will look into this issue and get back to you as soon as I can.

Already merged this in  #83
Closing this


✨ Zenith: Allow installing modules from private Git repositories.

What are you trying to do?
Currently you can only dagger mod install modules hosted in public Git repositories. While this is great for OSS, it's not ideal for Enterprises that use private Git repositories like Gitlab and Github Enterprise.
We require a way to somehow pass in/use authentication (GH PAT for example) when adding a module hosted in a private git repository.
Discord thread: https://discord.com/channels/707636530424053791/1171809848057401375
Why is this important to you?
As a company in a highly regulated industry, we cannot publish modules in the open. Git repositories hosted within our Github Enterprise instance requires authentication in order to access. This is a blocker for using dagger modules.
How are you currently working around this?
No known workaround so far which makes this a high priority request for us and any others using private Git repositories to host Dagger modules.

Bringing attention back to this issue now that modules have become the default. (I suppose, as the docs only mention the modules and previous cookbooks and guides have been removed). For us, this is the only obstacle preventing us from using Dagger modules at present.

If i want to add a private lib in go.mod the problem arise the same

Just adding to the Why is this important to you? section.
I would like to keep my personal projects private.
No need to summon "highly regulated industry". It is just basic privacy.

Would be a very nice feature, I'm interested in using this with modules hosted on our internal Bitbucket instance.

You could use git submodules as a temporal workaround.
Simple usage
git submodule add<EMAIL_ADDRESS>
dagger install your_dagger_module

This is under active development at this very moment
It is tightly linked to the implementation of https://github.com/dagger/dagger/issues/7218.
The first part is this PR: https://github.com/dagger/dagger/pull/7511, followed by another one for the directory refs, in which we unify the currently different way to reference directories and files on git remotes
This one has been unblocked recently by the Erik's work on the CA certificates that allows passing SSH sockets securely. A draft PR shall be available this week, on which feedback from the community is welcome 😁

@oblogic7
I followed the links posted by @grouville and found two PRs that haven't been merged

https://github.com/dagger/dagger/pull/7708
https://github.com/dagger/dagger/pull/7609

Thanks @oblogic7 for asking, and @LiHRaM for the answer 🙏
A few intermediary steps were necessary too:

https://github.com/dagger/dagger/pull/7742, as a base for authenticated calls with git subcommands
https://github.com/dagger/dagger/pull/7663, for the foundation of multi VCS testing (including with private modules)

Indeed these are the two main PRs for the implementation: with #7708 to be the first one to be merged. #7608 will be a followup.
As stated in a comment with Nipuna, the current implementation relies on SSH auth, but the design also needs to anticipate the other forms of auth.
I've got a rebase / improvement for #7742 + a comment incoming, to discuss all the design choices implied to make sure with the community that every use case is taken into account and that the path to full implementation is clear and all intermediary implementations

Update
Main PR for SSH support has been reviewed, and all the requested changes have been implemented. A bit more reviews are expected this week (yours is welcome too). This is probably going to be part of next release.
Your feedback is welcome, especially on the DX of this ref style, which you can see here
Once done, the http / https + PAT support is going to be my priority

Great progress so far!
Regarding DX on the ref style:

Gitlab, similar to Bitbucket, also uses the git user for SSH.
Looking at https://github.com/vito/dagger/blob/refs-v2/rfcs/001-refs-v2.md: On GitLab, it's very convenient to use the "Code > Clone with SSH/HTTPS > Copy URL" button on a project. It formats the address like this: git@gitlab.com:dagger-modules/private/test/more/dagger-test-modules-private.git. It would be great if this format is also supported.

Gitlab, similar to Bitbucket, also uses the git user for SSH.

Oh sorry, the git user is inferred for that example. If this behavior creates confusion, I can add a comment OR fail on that ?
Current PR ref format
[proto][user@]repo[.git][subpath][@version]
With proto:

git+ssh://
git+http://
git+https://

Empty proto is tansformed as git+https://
For private repos, the [.git] is recommended to declaratively say where the repo separates and where the path inside the repo starts. Which is useful for private GitLab
cc @aluzzardi what do you think about the implicit SSH refs: git@gitlab.com:dagger-modules/private/test/more/dagger-test-modules-private.git

Ah, sorry, got it. You've just omitted the git user for that test. I think that might be fine for a test, even though it's very unlikely in the real world. If the user is not defined, one would rely on the devs to set up their ~/.ssh/config accordingly. On the other hand, git has the same behaviour. So, not an issue, I guess. On a side note: Gitlab allows setting the git user on self-hosted instances, even though it seems very rare for people to change that.
Regarding the ref spec: You are right that both cases (using the Copy URL button or copying the URL from the browser's address bar) require manual editing the URL by the developer. Maybe it's just me, but when copying from the browser's address bar, I'm more prone to forgetting to add the .git suffix (which seems kind of mandatory for dagger to detect subpaths) or copying a tree path like https://gitlab.com/dagger-modules/private/test/more/dagger-test-modules-private/-/tree/main/mymodule?ref_type=heads instead of just https://gitlab.com/dagger-modules/private/test/more/dagger-test-modules-private, just because my browser selects the whole URL when clicking the address bar.  When copying from the browser's address bar, I would copy the URL, being careful as some browsers like Chrome add an https:// to the URL and require a second click to select the URL without the scheme, type git+ssh://, hit Cmd+v, move the cursor back, and remove the https:// if I accidentally copied it (looking at you, Chrome), type .git, and hit Enter. That's why I prefer to use the Copy URL button. On the other hand, I guess most module developers will write READMEs that include a copy-paste line. In CI, we use HTTPS anyway.

Thanks @skycaptain,
Your feedback helped reassessing the DX 🙏.
Following your comments, with @aluzzardi, we paused a bit and tried to think on a first-principal basis about:

Go-style refs -- github.com/aluzzardi/daggerverse
Git HTTPS (copy button with HTTP protocol on all providers GitHub / GitLab / BitBucket...) -- https://github.com/dagger/dagger.git
Git SCP-like (copy button with SSH protocol on all providers) -- git@github.com:dagger/dagger.git

The scope of the issue is to come up with the proper ref style, where DX is the most important. It needs to be intuitive / easy to read and not too verbose for users.
Context

The Go-ref style was introduced by Google to abstract the VCS AND the protocol from the ref. In which that the ref itself is its canonical representation. However, do we really need to apply these constraints to us ?
Most Git providers such as GitHub / GitLab ... all have a copy button to have an easy access to git https and git scp-like refs, and most developers are used to this DX, and more importantly, they seem to love copy-pasting these refs.

Lastly, the current effort with the very explicit ref style (the one with git+ssh://) was introduced to be computationally correct, at the expense of the DX. This format helps to have a unified ref for both modules AND dir / file passed as CLI arguments.
Now, after reflexion, Andrea came up with a series of postulates that could help scoping the ref style:

It is ok for Dagger to store modules only on Git - being VCS agnostic to store modules is not worth the effort
It is acceptable to have a different ref style for modules and for CLI arguments, especially to handle https://github.com/dagger/dagger/issues/6957#issuecomment-2183575359. Also, it is ok for CLI arguments to expect a future support to other VCS, so for the CLI input ref-style to anticipate a vision for multiple VCS support
The scope of the issue is the module user-input ref, the one being referenced upon dagger install / dagger -m ... by the user, which shall optimize for ease-of-use / familiarity / and clarity ; however, it is ok for its canonical reference or internal reference inside the dagger.json to be more explicit
It is sort of a separate issue and could be scoped as a follow-up, but it is important (or not?) for the same ref with different protos to be resolved internally as the same module
git rewrite rules are not ideal, as they bring the resolving logic client-side, which impacts the ci / local unification

Given that postulate, these 3 ref styles are all pretty solid schemes to support:
github.com/aluzzardi/daggerverse
https://github.com/dagger/dagger.git
git@github.com:dagger/dagger.git

HTTPs
[proto]host/path[.git][subpath][@version]
with proto:

empty (current go-like ref)
https:// or http://, which are the proto proposed by default on the copy button of all Git providers

This introduces a retro-compatible ref-format with an easy mono-repo handling: copy-paste the button from GitHub, add the path and the version, you're good to go. Easy-to-do, easy to remember.
The risk of a ref for http that supports Go-like style and Git-HTTP style is that we could end up with a lot of variations of those refs as valid:
E.g
github.com/aluzzardi/daggerverse
https://github.com/dagger/dagger
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
cc @aluzzardi, I do not remember, when we discussed, did you intend for us to be more strict on the ref format ?

What I mean is that: when we have the https / http protos specified, we expect a .git as present on the ref style of the Git-HTTP style ? Such as https://github.com/dagger/dagger would be invalid. Or do you mean all variations of above are correct ?

On the contrary, when thinking about it, I have the feeling that not including the proto and continuing full-on as a go-style ref for HTTP is also acceptable. People can copy the ref and just remove the http / https proto themselves. They're doing it right now, and it's not that painful. At least, it is for sure not as painful to delete than to write git+ssh://.
WDYT @skycaptain ? @aluzzardi ?
No strong opinion, I just worry about the amount of variations we would see popping up with a more loose scheme.
Remaining on go-like format would look like: host/path[.git][subpath][@version]
SSH refs
Here, we do full SCP-like format. This is the alternative format proposed as the default SSH ref in the copy buttons of those git providers:
[user@]host:path[.git][subpath][@version]

The distinction is indeed the :, which enforces the SSH protocol
When not set, user could be inferred as git (or not?). We could enforce its presence. Same question as above, do we also expect the .git ? (to be wary of all potential variations this implies)
E.g
github.com:dagger/dagger
<EMAIL_ADDRESS><EMAIL_ADDRESS>user<EMAIL_ADDRESS>
In both those examples, users are encouraged to just copy-paste from the provider.
You're on a monorepo ? Just append the subpath ; Need a version ? Just add @ and a version after.
Easy to remember, easy to do
Daggerverse impact
Also, both formats are pretty similar and their ref formats can totally be copy-pasted and tweaked to a Daggerverse URL
Let's take for example: https://daggerverse.dev/mod/github.com/levlaz/daggerverse/docusaurus@6c7c28cd95a9636a04768c8de8b658d724cdecb3.
The current ref is<EMAIL_ADDRESS>to which, the version is resolved to the actual commit in the URL.
Let's try to see a few of those variations for all the supported protocols with the new ref scheme:

<EMAIL_ADDRESS><EMAIL_ADDRESS>git<EMAIL_ADDRESS>
And that all these examples would continue to lead to the same Daggerverse URL: https://daggerverse.dev/mod/github.com/levlaz/daggerverse/docusaurus
If i were to see such ref in any dagger.json or any repo, finding the equivalent valid daggerverse representation is quite easy:

remove protos
transform : into /
strip versions

to be mindful -> remove the .git too ?

There is also a path for the daggerverse to redirect to the proper modules, even with the SSH ref format?
cc WDYT @jedevc ?

Ahh I see the logic for wanting to support scp-style git URLs - I guess I'm happy with it, since users can just do the copy and paste. That's the most important feature (my bad). Also happy to kill the git+ssh idea.
There's one case missing in the above I think - ssh://git<EMAIL_ADDRESS>or similar. Whole not copy-pasteable in the UI, users might attempt to use it and there's really no added cost to us to support it.
One note from a parsing perspective - having two @s in a ref url is tricky, parsing off the optional version at the end needs to be done carefully.

Closed by #8805


 It feels more correct to simply pretend the options endpoint doesn't exist 🤔

I think it can be useful if a specific list of origins is allowed. Also I keep the documentation because of backwards compatibility.
I don't care in the end whether it is documented or not. @tipsy @TobiasWalle what do you think about?

Remove documentation and ignore
Keep it as it is
Add boolean switch to show/ignore it

I think it can be useful if a specific list of origins is allowed

Realistically this should be all origins for a public API, or irrelevant for a on-the-internet-but-not-really-meant-for-non-internal-use API.
I would simply remove it, but I'm not to be trusted when it comes to this. Let's see what @TobiasWalle thinks.

I also think that it is best to ignore the documentation of the CORS Plugin. If I think about a public API, I wouldn't expect this information in the swagger file.
Probably the best solution is to add the @OpenApi(ignore = true) annotation to both CORS Handler, as it doesn't require any modifications of the Plugin code.

I added the OpenApi ignore annotation the the options handler. The before handler is ignored in future in Api Documentation (see , so the handler must not be annotated (see #733 and diff). Because "BEFORE" is not a valid http method

Perfect, looks good to me!

Great, thank you @maxemann96 !


Refactor StorageInstance trait to be usable more easily

StorageInstance is introduced to be used alongside storage types. It was meant to be implemented by macro, thus I tried to make it as straightforward as possible to implement from the macro (just some associated type and constant). But this is a rather ugly trait and it is less usable then.
Thus this PR refactors it to make it more usable and idiomatic.

bot merge

bot cancel


Update README.md with more realistic Transaction example

Add a more detailed slightly more realistic example for a transaction. This example contains error handling and transaction usage that is not reflected in the current README. Hopefully this will help others learn to how use gorm more quickly.

Thank you


Add htmlmin collapseBooleanAttributes

Add htmlmin collapseBooleanAttributes tag, reducing index.html from 3,447 bytes to 3,437 bytes. This will automatically collapse all attributes whose meanings are self evident by their presence (disabled, checked).

Looks perfect for me.
It changed <input type="radio" name="g" id="h" checked="checked"> into <input type="radio" name="g" id="h" checked>.
Will merge now.


Always fetch complete rows in grid view

We should fetch items that are perfectly divisible by the number of columns, so when they load in its always full rows
Example:

Reopening just so we don't forget to do Jellyfin too


Don't fatal out if a peer is not reachable

closing this one. rebased and pushed through https://github.com/packetdrop/quicwire/pull/31


Disk read/write/total rate average values

Brief description of your issue
This will be tough to describe...
Disk tab, Read/Write/Total Rate Average columns: the values displayed appear to be the calculated average values for a (very) long past period.
Steps to reproduce (optional)
An example: even for processes closed tens of second ago, these average values are still displayed. The values are slowly, but constantly decreasing, before finally disappearing from the list.
Expected behavior (optional)
Instead of the behaviour described above, I believe they should be the average calculated since the last refresh.
Actual behavior (optional)
No response
Environment (optional)
System Informer 3.0.6384 x64 nightly
Windows 10 x64 ver 21H2 build 19044.2728

the values displayed appear to be the calculated average values for a (very) long past period.

This is how Microsoft designed the API and show values in their software. If you launch Resource Monitor from the Tools menu and select the Disk tab you'll see the exact same values:

they should be the average calculated since the last refresh.

They should but this is a limitation of the API from how Microsoft implemented the feature. We could remove items more quickly but then you won't be able to see any activity so we're just using the same values/timeouts as Resource Monitor?
The disks shown on the system information window are realtime and more reliable for statistics while the disk tab is better suited for viewing recent file activity instead of statistics.


Create sp-weights crate to store weight primitives

Part of #12176.
In this PR, we create a new primitives crate called sp-weights to store the Weight struct and its associated traits and types. Some existing types related to dispatch have also been relocated to frame_support::dispatch, as I feel like they had never made sense to be put under the weights umbrella.
Aside from that, the main motivation here is to recognize that the notion of weights reaches far beyond FRAME, and so it should be a crate separate from frame_support or sp-runtime.
polkadot companion: paritytech/polkadot#5987
cumulus companion: paritytech/cumulus#1610

bot merge


Add a test asserting the {{view "some-name"}} helper works

Ensure it works without a deprecation be fired.

Re: https://github.com/emberjs/ember.js/pull/11389

closed by 10d361e3e9783675d36aaa8f6be8c179a3513320


Moved Amplify config setup into useEffect in App component

Issue fixed: The 'getAmplifyConfig' function was running before any components were rendered, so during the initial page load, window.location.hostname was not set to either "visit.cumaker.space" or "beta-visit.cumaker.space", causing the default configuration to be used.

Hmmm not sure why this would be the case. I wouldn't think there would be an asynchronous population of that value between script load and react render. You have to visit and resolve that hostname to even retrieve those values and run the script. I may be missing something though.
Benign change either way, merged!


Fixed reading connection response data.

When debugging I noticed the server connect response would come as a Dictionary<string, object> instead of AsObject.
Using IDictionary<string, object> should cover both cases.

hi @jvlppm!
thanks for taking the time to submit this pull request! this is great, and if all tests pass, your change will become part of v0.3 tomorrow. :D
just curiously, which server(s) did you observe transmitting the connect response using an associated dictionary, instead of an AsObject?

I am connecting to avchat ( http://avchat.net/ ).
It requires user information / login token during connect.
Also it requires SharedObjects support, which I am currently trying to implement.
I may submit yet another pull-request with that, when its done.
If you have an idea on how it should be implemented, it would certainly help.

hey there!
it's taken me a little while to find the time for this pull request.
your pull request looks good, but i've updated your proposed api to be consistent with the existing library. i've moved arguments into a property of the connection options, rather than connect() taking an options object plus a second variadic arguments object.
i'd like to mark this pull request as merged, but unfortunately github doesn't give me the option to do that. rest assured that it is: https://github.com/hinaria/rtmp-sharp/compare/b73d08e255bc9432946ec4e4bd5319235abaeac4...fb3144f7a156d89279600ea88f3d31c751158dcc
thanks so much for taking the time!

on shared objects, i'd love to implement add support into rtmp-sharp. i do have a few ideas on how we could go about it, please send me an email (to a@hinaria.com), or give me your email. i'd love to help!


[Fall 2021] Step 3 - Create command in Pyre to initialize a environment for Pysa

Automate the steps in the Quickstart to run when a user executes a Pyre command (e.g. pyre init --pysa), so that after the command is completed, the user has their environment set up to run Pysa (pyre analyze)

Ah I think pyre init has some logic to set up taint_models_path. If the user has a venv activated, I think by default it sets the path to {venv_path}/lib/
Sorry I'm realizing now that this issue might be better as a script instead of a built-in command in Pyre, since the goal of the issue was to automate the setup steps in the Quickstart guide and have some automatic error handling for common issues people run into. I'll update the issue to better describe this


Provide a PPA for ig

From #1444
This issue should also investigate if there is a similar mechanism that we can use for Fedora.

Closing in favor of #3304 as the goal is to package for Ubuntu directly.


Cannot install yarn

I cannot install yarn with the scoop install yarn command:

This is the error:
Installing 'yarn' (1.1.0).
yarn-1.1.0.msi (1,2 MB)
Checking hash of yarn-1.1.0.msi... ok.
Extracting... % : The term 'local:run' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At C:\Users\jelle\scoop\apps\scoop\current\libexec\scoop-install.ps1:107 char:9
+ $apps | % { install_app $_ $architecture $global $suggested $use_cach ...
+         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (local:run:String) [ForEach-Object], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException,Microsoft.PowerShell.Commands.ForEachObjectCommand

I'm running Windows 10 with PowerShell version 5.

Did you set set-executionpolicy remotesigned -s cu?
Does it happen after restarting powershell and trying it again? Maybe related to https://github.com/lukesampson/scoop/issues/1721

Error changed after the set-executionpolicy command:
$ scoop install yarn
Installing 'yarn' (1.1.0).
Loading yarn-1.1.0.msi from cache
Checking hash of yarn-1.1.0.msi... ok.
Extracting... run : The term 'local:run' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At C:\Users\jelle\scoop\apps\scoop\current\lib\install.ps1:567 char:11
+     $ok = run 'msiexec' @('/a', "`"$path`"", '/qn', "TARGETDIR=`"$to` ...
+           ~~~
    + CategoryInfo          : ObjectNotFound: (local:run:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

Failed to extract files from C:\Users\jelle\scoop\apps\yarn\1.1.0\yarn-1.1.0.msi.
Log file:
  ~\scoop\apps\yarn\1.1.0\msi.log

But the ~\scoop\apps\yarn\1.1.0\msi.log file is not there...

Hm, I can't figure out why it doesn't know about the run() function which is also located in the install.ps1 (line 476). Realy strange. Did you run set-executionpolicy from an elevated powershell and then restarted it?

Yes, both. Ran it in a normal PowerShell and also in an elevated PowerShell.

Can you try running . C:\Users\jelle\scoop\apps\scoop\current\libexec\scoop-install.ps1 and then Get-ChildItem function:? The output should look somewhat like this:
...
Function        rm_shim
Function        rm_shims
Function        rm_startmenu_shortcuts
Function        run
Function        run_installer
Function        run_uninstaller
Function        runtime_deps
...

Does it install now?

Thanks for the responses b.t.w. ...

Cool, I would never have guessed it was a problem with a local alias 😁

I could reproduce it. It seems to be a problem with reset_alias().


support u16 and f32 and f64

Great work!
I'm willing to lend a hand to add more swagger support to Rust!
Here is a simple addition of several number types

Thanks and thanks for contribution! Sorry for late review, I was sick.


Boardgeneration

@ZsomborHajzer close "BoardGeneration" as well as that branch is behind this one (mind the capitalization)

lgmt


Email ECST about creating site

We were told that ECST is in charge of the Wordpress pages that Bucknell already have.

After emailing them, they said

You can create a Wordpress site by going to http://blogs.bucknell.edu. There is also another Wordpress network called scholar.bucknell.edu. As far as I know the primary difference is simply the site address, but if you're interested in that and want to know more, I can put you in touch with the Digital Pedagogy & Scholarship group in L&IT.

On Thu, Oct 19, 2017 at 12:37 AM, Benjamin Matase<EMAIL_ADDRESS>wrote:
Hello,
We are a Computer Science Senior Design group trying to create a unified site to host a showcase for the sustainability efforts on campus (specifically Energy Hill). Our senior design project needs a Wordpress site and we think it would be best to have it hosted on Bucknell servers, whether it be a subsite of an existing Wordpress site or a new site.  This site would be for BCSE/RES, specifically Nate Siegel, and we were told that you are the people to contact.  What are your thoughts?
Thanks,
Benjamin Matase

Determined that were going to create the wordpress site on the blogs.bucknell.edu and then see if that is too restricting.  Will reopen if find that we need to look at more options


[ERROR -> libinput] Libinput builds fails on evdev

While running command:
kiss b sway foot && kiss i sway foot
I get an error about make usage and the build fails on evdev.
Complete log file is present here: https://termbin.com/i6ei

Seems like replacing the make in the build with gmake gets it to work. Closing this issue.


rework isolate option to match CNI

The isolate option doe snot work as expected. It currently prevents all
traffic does is not on the same network. Instead it should only block
traffic between two isolated networks, never external connections.
Also it did not work for ipv6 at all.
Fixes #331

@mheon PTAL

LGTM

@Luap99 really  nicely done code, thanks for this contribution!
/lgtm


PLT-1183: fix: Ensure auth options are passed into the Cosign Verifier

This PR fixes signature verification for private registries

Codecov Report
Attention: Patch coverage is 80.00000% with 2 lines in your changes are missing coverage. Please review.
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #166   +/-   ##
=======================================
  Coverage   70.98%   70.99%
=======================================
  Files           3        3
  Lines         355      362    +7
=======================================
+ Hits          252      257    +5
- Misses         77       78    +1
- Partials       26       27    +1

Files
Coverage Δ

internal/validators/oci_validator.go
67.26% <100.00%> (ø)

internal/verifier/verifier.go
71.05% <71.42%> (+0.08%)
:arrow_up:

Continue to review full report in Codecov by Sentry.

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


feat: parallelize feature for tcp

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