Springfox swagger ui won't render 1.2 spec

I was asked to include both 1.2 spec and the 2.0 spec in a project that I'm involved in and I'm using Springfox 2.2.2 and Springfox-swagger-ui 2.2.2.
I have an issue where the 1.2 spec will not render in the swagger ui. The 2.0 spec will render fine and I can view the 1.2 JSON objects when hitting their respective default endpoints (/api-docs/default/**).
When viewing the 1.2 spec from swagger-ui.html the page says "Finished loading resource information. Rendering Swagger UI..." and just sits there.
Here's what I have for the swagger config:
@Configuration
@EnableSwagger
@EnableSwagger2
@ComponentScan(basePackages="org.business")
public class SwaggerConfig {

	   @Bean
	   public Docket api(){
	        return new Docket(DocumentationType.SWAGGER_2)
	            .select()
	            .apis(RequestHandlerSelectors.any())
	            .paths(PathSelectors.any())
	            .build()
	            .apiInfo(apiInfo());

	    }

Is there something else I'm missing or am I doing something wrong?

You need to add another docket unfortunately
@Bean
       public Docket api(){
            return new Docket(DocumentationType.SWAGGER_12) //<---- this!
                .select()
                .apis(RequestHandlerSelectors.any())
                .paths(PathSelectors.any())
                .build()
                .apiInfo(apiInfo());

        }

Here is what I have now:
@Configuration
@EnableSwagger
@EnableSwagger2
@ComponentScan(basePackages="org.business")
public class SwaggerConfig {

	   @Bean
	   public Docket api2(){
	        return new Docket(DocumentationType.SWAGGER_2)
	       	    .groupName("swagger2")
	            .select()
	            .apis(RequestHandlerSelectors.any())
	            .paths(PathSelectors.any())
	            .build()
	            .apiInfo(apiInfo());

	    }

	   @Bean
	   public Docket api(){
	        return new Docket(DocumentationType.SWAGGER_12)
	            .select()
	            .apis(RequestHandlerSelectors.any())
	            .paths(PathSelectors.any())
	            .build()
	            .apiInfo(apiInfo());

	    }

After adding this in I get this in swagger-ui.html:

It seems that two dockets were made for each swagger spec and group when checking the dropdown:

The 2.0 spec can be viewed fine but for the 1.2 spec it hangs on that rendering.
This is after adding the servlet mapping for "/*" since the swagger ui seems to look for the resources on the root context, although the api-docs are served under /rootContext/rest/. Without the mapping the resources for the 1.2 spec will not be found.

You can add a custom path mapping per docket using the pathMapping method on the docket

I've tried doing that and it works fine for the 2.0 spec. However the 1.2 spec generates incorrectly.
When adding the path mapping to the 1.2 spec the paths for the individual resource listings are wrongly created. The paths get prefixed with "rest" like so:
/rest/default/service-controller

Swagger UI then looks for the individual resource listings at
/api-docs/rest/default/service-controller

when "rest" needs to be at the beginning.
Another thing is that one of the api's resource path is generated incorrectly.
The resourcePath seems to follow the base path and it is also empty, unless you have the path mapping which it then just shows that.
"resourcePath":"/"
"resourcePath":"/rest"    <-- with rest path mapping
"resourcePath":"/Service"   <-- it should be this

Is there a way to specify the resourcePath in the 1.2 spec? How is the resourcePath generated?
Is it possible to generate both versions for the same api?

Hmmm it might be a bug.. any particular reason you don't want to move to 2.0? feel free to re-open. However I really don't have the bandwidth to track this down


[$1000] Task title briefly changes to "Chat Report" for User B after User A sends the first message in the newly-created task chat

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Log into two accounts on Chrome (one may have to be in an incognito browser).
Open a chat with "User B" and click on the "+" in the composer.
Choose "Assign task", add a title, set "User B" as the assignee, and then click on the big green button that says "Confirm task".
Send a message in the newly-created task chat while observing "User B's" main chat with you.

Expected Result:
The task title remains the same in "User B's" main chat with you.
Actual Result:
The task title briefly changes to "Chat Report" in "User B's" main chat with you.
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[x] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number:
Reproducible in staging?: needs reproduction
Reproducible in production?: needs reproduction
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/43996225/d5d0f7bc-2dd9-44b4-a29e-17f0f6a9da6c
Expensify/Expensify Issue URL:
Issue reported by: @Victor-Nyagudi
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1691071965161749
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01e2799b14e4189cb2
Upwork Job ID:<PHONE_NUMBER>970010624
Last Price Increase: 2023-08-16

Cannot reproduce on staging and on dev 7f13cdd9f5 (Mac OS Chrome/Safari)

Hmm. Perhaps it was fixed by something else?

I think this is fixed and was likely a duplicate report accordingly.


dm: fix validator deadlock and enhance retry

What problem does this PR solve?

Issue Number: close #9257
What is changed and how it works?

fix deadlock between error-process-routine and worker routine when err channel is full
remove object lock when fillResult
enhance retry by reusing the resumable errors in syncer

Check List
Tests

[x] Unit test
Integration test
Manual test (add detailed scripts or steps below)
No code

Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note
dm: fix validator deadlock and enhance retry

@lance6716 @GMHDBJD

/retest


RabbitMq management Rest Api connection issue with client using non public certificates

Creating a RabbitManagementTemplate instance there is no way to add trusted certificates or to change the http client. The underlying class Client creates a rest template instance without any option to configure trusted certificates. The HttpClientBuilder used to create the HttpComponentsClientHttpRequestFactory used by the RestTemplate doesn't call useSystemProperties() method so default properties like javax.net.ssl.trustStore doesn't work too.
Is there a way I messed by now I couldn't see a way to trust the server certificate with the RabbitManagementTemplate.

Since the RabbitManagementTemplate is a lightweight wrapper around the Client, I suggest you raise this issue against hop.

M-m-m. I wonder why ctor like below isn't appropriate for you?
/**
   * Construct an instance with the provided url and credentials.
   * @param url the url e.g. "http://localhost:15672/api/".
   * @param username the user name.
   * @param password the password
   * @param sslContext ssl context for http client
   * @throws MalformedURLException for a badly formed URL.
   * @throws URISyntaxException for a badly formed URL.
   */
  public Client(URL url, String username, String password, SSLContext sslContext) throws MalformedURLException, URISyntaxException {

Thanks for your quick response, I used the latest version (1.4.3.RELEASE) of spring-boot-starter-amqp which includes spring-rabbit in version 1.6.6.RELEASE and this includes the http-client in version 1.0.0.RELEASE. This version of http-client doesn't has no constructor like mentioned by @artembilan.
Excluding http-client from spring-boot-start-amqp and add latest version manually solved the issue for me.


[IQE] : [Ctrl+PageUp/PageDown] shortcuts on Navigate menu are not localized

Steps To Reproduce:

Launch Brackets
Open and edit some files in the Working set
Go to Navigate menu

Result:  Next Document (List Order) and Previous Document (List Order) are not localized
ENV : Release 1.4 build 1.4.0-16190 (master e35f2a4) (MAC and WIN)

@rawat11 Hey.. We are not getting ALF automation update for string changes. Last update we got was on 22 April. Can you please look into it.

@prafulVaishnav Yes I have  recieved the strings for it, we will send it for translation


Bump 0.49 to React 16 [fix]

Corrects the missing cherrypicks from #19274 that were required to fully sync React 16. Sorry about the mixup! Also cherrypicks https://github.com/facebook/react-native/commit/ca834f96afcb99a7f1f4eec0a864f4f5b33a632b so that this issue isn't introduced to 0.49. Relates to https://github.com/react-native-community/react-native-releases/issues/18.
Test Plan

Local run of tests, lint, and flow were successful. Verified against 'react-native init' and RNTester on iOS and Android.
Related PRs

Corrects https://github.com/facebook/react-native/pull/19274
Release Notes

[GENERAL] [MINOR] [-------------] - Updated React to v16.0.0

Closing, as we've decided to revert our changes for 0.49-stable with #19399.


Some changes to get ncollide working with Rust 1.0.0.beta4

This is not the full set yet, I'm currently stuck on:
ncollide_utils/optimization.rs:174:39: 174:46 error: cannot apply unary operator `-` to type `V`
ncollide_utils/optimization.rs:174         let mut search_dir = hx.rmul(&-new_dx);
                                                                         ^~~~~~~
ncollide_utils/optimization.rs:179:26: 179:33 error: cannot apply unary operator `-` to type `V`
ncollide_utils/optimization.rs:179             search_dir = -new_dx;
                                                            ^~~~~~~
ncollide_utils/any_private.rs:13:9: 13:24 error: the trait `core::marker::Reflect` is not implemented for the type `T` [E0277]
ncollide_utils/any_private.rs:13         TypeId::of::<T>()
                                         ^~~~~~~~~~~~~~~
ncollide_utils/cov.rs:55:38: 55:55 error: cannot apply unary operator `-` to type `V`
ncollide_utils/cov.rs:55                 *pt = icov * (*pt + (-*center.as_vec()));

Thanks for your work so far. I believe you figured out why the - operator was not found (cf. nalgebra#125). For the error related to TypeId, you might just have to add the core::maker::Reflect trait bound to T.
Though, I think that you probably should not pursue your work before the 1.0 rust compiler is released (next week IIRC). Currently, a clean fix of ncollide compilation problems require associated types, which still ICE when I try to use them (see #72). If the 1.0 version still ICEs, then we will have to find an alternative to associated types (which migh tbe the PhantomData) in order to remove #[old_impl_check].

Hi, my e-mail notifications broke so I didn't see you had already responded. I'm just messing about learning Rust so it's no big deal if it's not good to pull :) I'm knee deep in the associated types stuff now, so I'll find out about the ICE soon enough probably :P

I am currently working on a proper fix for ncollide. Since the ICE is not gone, I believe it might take a few days until I figure out how much associated types I can use without killing rustc.

Alright, it's weekend again and I have some time. If there's anything I can do to help you let me know :)

By the way did you see I put a vecmap implementation in this pull request? Not sure if that's a good idea, but they removed the old one and I couldn't figure out how to get it in so I just copied it and made it work.

Yes, I've seen this. I don't know if we have any alternative. Could this copy/paste cause licensing issue ?

Well it's MIT licensed, I included the copyright notice in the file to make it clear that it's originally by the Rust team. MIT licenses are basically compatible with any other license. As long as you keep the copyright license in there it should be fine.


rails db:migrate running into issues with errors table

after upgrading to <IP_ADDRESS> running into this issue. Please help
rails db:migrate
/home/jdeinteg/.rvm/gems/ruby-3.0.0/gems/exception_handler-<IP_ADDRESS>/lib/exception_handler/config.rb:143:in `initialize': Migration Required → "errors" doesn't exist (ExceptionHandler::Error)
        from /home/jdeinteg/.rvm/gems/ruby-3.0.0/gems/exception_handler-<IP_ADDRESS>/lib/exception_handler/engine.rb:45:in `new'
jdeinteg@JDEDMZBETA:~/sites/hitt_jdedmz$        from /home/jdeinteg/.rvm/gems/ruby-3.0.0/gems/exception_handler-<IP_ADDRESS>/lib/exception_handler/engine.rb:45:in `block in <class:Engine>'
        from /home/jdeinteg/.rvm/gems/ruby-3.0.0/gems/railties-<IP_ADDRESS>/lib/rails/initializable.rb:32:in `instance_exec'
        from /home/jdeinteg/.rvm/gems/ruby-3.0.0/gems/railties-<IP_ADDRESS>/lib/rails/initializable.rb:32:in `run'
        from /home/jdeinteg/.rvm/gems/ruby-3.0.0/gems/railties-<IP_ADDRESS>/lib/rails/initializable.rb:61:in `block in run_initializers'

To anyone with this problem use rake db:migrate.
In the file exception_handler-<IP_ADDRESS>/lib/exception_handler/config.rb:143 there is a validation for the passeds ARGV and validates the use of rake, instead of rails.


#34: Implemented ToolCommandlet for SonarQube

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


Repeated crashing of VSCode's chrome_crashpad_handler

Does this issue occur when all extensions are disabled? Yes

VS Code Version: 1.88.1
OS Version: MacOS 14.4.1

Steps to Reproduce:

Open visual studio code
Begin editing any file
Many many crash dialogs will appear like below:

I was able to fix this problem temporarily by downgrading to vscode 1.87, seems to be something breaking with the update?

Also seeing this on 1.88.1, with crashreport also taking a significant amount of CPU. Downgrade to last version resolves for me.

Seeing the same issue on 1.88.1, MacOS Ventura 13.5.2

Noticed some interesting behavior, I was able to reinstall the latest version of vscode without the issue returning, but the instant I made use of the code terminal command to open a file, the crashing behavior returned, with or without launching vscode through terminal. Not sure if this is related or not.

My info:
Version: 1.91.1 (Universal)
Commit: f1e16e1e6214d7c44d078b1f0607b2388f29d729
Date: 2024-07-09T22:07:54.982Z
Electron: 29.4.0
ElectronBuildId: 9728852
Chromium: 122.0.6261.156
Node.js: 20.9.0
V8: 12.2.281.27-electron.0
OS: Darwin arm64 23.5.0

I had no problems last week. Problem started when upgrading to this version.
I can confirm that this version also produces this error.
Reinstallation of VSCode did not solve the problem.
Rebooting laptop also didn't solve the problem.
I had several windows with projects open and one of them had the Terminal window open.
Per @YonatanAhituv 's suggestion I closed the Terminal window and it seemed the errors became less frequent.
Finally I closed all windows and restarted VSCode.
For now I have one window open but the Terminal window closed and there is no error anymore.

I just started seeing this today on macOS 14.6.1, VSCode 1.93.1
Version: 1.93.1
Commit: 38c31bc77e0dd6ae88a4e9cc93428cc27a56ba40
Date: 2024-09-11T17:20:05.685Z
Electron: 30.4.0
ElectronBuildId: 10073054
Chromium: 124.0.6367.243
Node.js: 20.15.1
V8: <IP_ADDRESS>-electron.0
OS: Darwin arm64 23.6.0

I noticed, for me at least, it has something to do with the ability to locate a Python interpreter.
I didn't set a path to the Python interpreter in my user settings nor the default profile (never needed to) and I noticed that VSCode works fine in profiles where Python extensions are disabled, but crashes  otherwise. Just to be clear: in that case it throws 2 error boxes every few seconds, one with the chrome crashpad handler and one with an 'unable to locate Python....'.
I have been able to set the path in the user settings and in all profiles and now the frequency is down to a level that makes VSCode usable.

If the issue is present with latest stable, please share the crash logs following the steps at https://github.com/microsoft/vscode/wiki/Native-Crash-Issues#creating-a-crash-report

The issue persists. Still crashing.


Anyway to access to the public leaderboard?

I cannot find any public data on the leaderboard.

What kind of data? here's the leaderboard https://huggingface.co/spaces/bigcode/bigcode-models-leaderboard


feat: tfsec task should report its version and show the latest

tfsec task should report its version and show the latest one.

The latest version will be used with version input ommited.
- task: tfsec@1
   inputs:
     dir: 'terraform'


Global emit

Its possible to emit to all connected clients across workers?

@trzyrazyzero Yes, you can setup a global channel like 'some-global-channel' and make all your client sockets subscribe to it. Then, whenever you want to broadcast a message to EVERY client, you just do socket.publish('some-global-channel', {foo: 'bar'});

Its only way?

No but it's the most scalable way. With this approach, your system can scale infinitely to any number of users. Another approach is to iterate over all scServer.clients and call emit(...) on each socket individually but this doesn't always scale as easily.

Okey, thanks for response


mvn clean in build.sh.

Sad but true, need to clean to avoid keeping around removed stuff.

Hmm, not sure i wanted this. You could have just done a mvn clean, then ran the ./build.sh. because majority of the time you don't need to rebuild the less.


[downloader/external] Respect --no-check-certificate for curl and aria2c and --proxy for curl

if i didn't set --no-check-certificate the value of param is False then it pass this condition:
if isinstance(param, bool):

that makes it apply regardless of setting it or not.
so i added this condition to fix it:
or param is False

This breaks the original semantics for bool options without value. These have to be always passed as bare option switch without value whether they true or not. If you really need to pass value to bool option then it's probably better to add a new method something similar to this:
def _bool_option(self, command_option, param, true_value='true', false_value='false'):
    if not isinstance(param, bool):
        return []
    return [command_option, true_value if param else false_value]

but it won't work with aria2c because this command is working:
aria2c --check-certificate=false url

and this don't work:
aria2c --check-certificate false url
Exception caught
Exception: [download_helper.cc:417] errorCode=1 Unrecognized URI or unsupported protocol: false

because aria2c will execute the command like it was
aria2c --check-certificate=true false url

Add a separator=None parameter.

i added the function and used it.

i added the _argless_option function and used it for nocheckcertificate

i changed the function name to _valueless_option.

Thanks.


add github secrets token

https://www.theserverside.com/blog/Coffee-Talk-Java-News-Stories-and-Opinions/GitHub-Actions-Secrets-Example-Token-Tutorial
build-docs-ghpages.yaml
# - name: Push changes to github repo/gh-pages
#   uses: ad-m/github-push-action@master
#   with:
#     branch: gh-pages
#     directory: gh-pages
#     github_token: ${{ secrets.GITHUB_TOKEN }}

Maybe need this setup for gcp too.

Lines uncommented, token inserted SECRET_TOKEN


Unable to open the page..........!

Hi,
Someone help me, I'm getting the following error.

ERROR: Service 'consoleme' depends on service 'consoleme-redis' which is undefined.

Hi, it sounds like you've followed the docker deployment instructions here. Is that correct, or are you running any part of ConsoleMe locally?
If it is correct, what do you see when you run docker ps after running docker-compose -f docker-compose-dockerhub.yaml -f docker-compose-dependencies.yaml up -d ?
You can also try docker logs and determine if a container failed to start for some reason.

Hi,
I'm getting the same output that you mentioned above currently My console me application running in Docker, But when I try to open the application I'm getting "session expire", So kindly help me on this issue.

Hi @Harsha-kumar-654 , can you run the below commands to stop your containers, start them up again, and follow the logs of the consoleme container as it starts? Please observe this for any errors, and share those logs here if appropriate.
docker-compose -f docker-compose-dockerhub.yaml -f docker-compose-dependencies.yaml down
docker-compose -f docker-compose-dockerhub.yaml -f docker-compose-dependencies.yaml up -d
docker container logs consoleme_consoleme_1 -f

When I've seen this problem before, it was due to the host having a low inotify limit. There's a section in the docs about increasing your inotify limits that you can also try.

@castrapel Now I'm able to open the application console. I've followed the above steps it's working thanks for the help, But I'm facing another issue following a screenshot for your reference, Kindly check and share your ideas on this concern.

I suspect either:

Your ConsoleMe configuration is not correct
Your ConsoleMe permissions don't allow you to create an IAM role on the target account

To dig in deeper, try using the Chrome Inspector Network tab (Instructions). Once you have the network tab open, repeat your request to create a role. You should see a response from the ConsoleMe backend that might give you a specific error. I should fix this to properly show the error to the user.
The second thing you can try (This is always a good practice), is check the logs for your consoleme web container. IE: 1) Run docker container logs consoleme_consoleme_1 -f , 2) Make your web request again, 3) Observe those container logs for errors.

Hi, any luck @Harsha-kumar-654  ?

Still, I'm facing the same issue.

Per my previous message, I'll need  more context about your configuration and container logs to replicate/assist.

I am seeing the same problem.  The application on port 8081 doesnt seem to come up in the docker container.  I execed into the container and curled the url and got a could not connect.  when I try to reauth via the web app I see this in the logs:
Proxy error: Could not proxy request /auth?redirect_url=http://localhost:3000/ from localhost:3000 to http://localhost:8081.
See https://nodejs.org/api/errors.html#errors_common_system_errors for more information (ECONNREFUSED).
when I run ps aux in the container I see a python process running:
ps aux
USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root         1  0.0  0.0   5492  3268 pts/0    Ss+  16:48   0:00 bash -c  python scripts/retrieve_or_decode_configuration.py; pip install argh watchdog; pip install -e /apps/consoleme/default_plugins; watchmedo auto-restart --recursive --pattern=".py" --directory="." python consoleme/main.py & FORCE_COLOR=true yarn --cwd /apps/consoleme/ui/ start | cat
root        23  0.1  0.2<PHONE_NUMBER>2 pts/0    Sl+  16:48   0:00 /usr/local/bin/python /usr/local/bin/watchmedo auto-restart --recursive --pattern=.py --directory=. python consoleme/main.py
root        24  0.1  0.6<PHONE_NUMBER>0 pts/0    Sl+  16:48   0:00 node /usr/bin/yarn --cwd /apps/consoleme/ui/ start
root        25  0.0  0.0   4192   688 pts/0    S+   16:48   0:00 cat
root        32  1.7  5.3 1168288 490852 ?      Ssl  16:48   0:08 python consoleme/main.py
root        37  0.0  0.0   2396   768 pts/0    S+   16:48   0:00 /bin/sh -c cp -a public/ ../consoleme/templates; react-app-rewired start
root        39  0.0  0.3<PHONE_NUMBER>6 pts/0    Sl+  16:48   0:00 /usr/bin/node /apps/consoleme/ui/node_modules/.bin/react-app-rewired start
root        47  6.4  5.5 11827036 509376 pts/0 Sl+  16:48   0:31 /usr/bin/node /apps/consoleme/ui/node_modules/react-app-rewired/scripts/start.js
root       117  0.4  0.0   5492  3136 ?        Ss   16:56   0:00 /bin/bash
root       123  0.0  0.0   9396  3104 ?        R    16:56   0:00 ps aux
Any idea how I can debug this further?

I followed this guide: https://hawkins.gitbook.io/consoleme/quick-start/docker
when the python app runs in the container config.get("tornado.port") is returning None which is stopping the app from running.  I have modified the python code to config.get("tornado.port", 8081) just to get it working and now when I hit re-authenticate I get the following error:
HTTPServerRequest(protocol='http', host='localhost:8081', method='GET', uri='/auth?redirect_url=http://localhost:3000/', version='HTTP/1.1', remote_ip='<IP_ADDRESS>')
Traceback (most recent call last):
File "/usr/local/lib/python3.8/site-packages/tornado/web.py", line 1683, in _execute
result = await result
File "/apps/consoleme/consoleme/handlers/auth.py", line 11, in prepare
await super(AuthHandler, self).prepare()
File "/apps/consoleme/consoleme/handlers/base.py", line 170, in prepare
return await self.authorization_flow()
File "/apps/consoleme/consoleme/handlers/base.py", line 376, in authorization_flow
self.user = await auth.get_user(headers=self.request.headers)
File "/apps/consoleme/default_plugins/consoleme_default_plugins/plugins/auth/auth.py", line 130, in get_user
raise Exception("auth.get_user not configured")
Exception: auth.get_user not configured
I did not expect this as I thought I had disabled auth by adding this to my config:
_development_user_override<EMAIL_ADDRESS>A development configuration can override your groups locally
_development_groups_override:

<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
I will raise this as another issue but I think this one can be resolved by adding instructions on how to set the config option of tornado.port or adding a default to the code.

@eamonnfaherty Thank you for your comments. Can you pull the latest docker container from dockerhub again? A new version was created, and the backend should start up properly now.


adding missing cities to addresses data

adding missing cities to 5 addresses in the data

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 89.00%. Comparing base (181bd1b) to head (fd87534).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main      #51   +/-   ##
=======================================
  Coverage   89.00%   89.00%
=======================================
  Files          13       13
  Lines        1828     1828
=======================================
  Hits         1627     1627
  Misses        143      143
  Partials       58       58

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

LGTM, i will merge this.


Consolidate SOAP flags

One flag for using SOAP that always includes the hiding of envelope
Combine flag with version specification?
Keep the two action options (namespace and full action)?

We have kept all the flags, but made the hiding of envelope default when a soap version is specified.


migration from Express 3.2.6 to 4.8.0

Hi Abdelkrim,
I have migrated your project from express 3.2.6 (deprecated) to 4.8.0.
Hope you are happy to merge it!
Regards,
Agnieszka

Dear Agnieszka, I'll check it in the following days and merge your code.
THANK YOU!

Hi Abdelkrim,
Great. Thanks.
Kind Regards,
Agnieszka
On Mon, Mar 14, 2016 at 11:02 AM, Abdelkrim from Brussels <
<EMAIL_ADDRESS>wrote:

Dear Agnieszka, I'll check it in the following days and merge your code.
THANK YOU!
—
Reply to this email directly or view it on GitHub
https://github.com/ALT-F1/bootstrap3-jade-node-express-grunt/pull/8#issuecomment-196260198
.

--
Kind Regards,
Agnieszka


A working prototype

Planned to create a working prototype for W-Learn. For prototype, no language restriction has been introduced. Thus, the prototype will be built with PHP-Laravel framework, with MySQL database.

The initial prototype has been created. The updates will be followed on this issue.


Fix for concat_vcf for miniwdl.  Link all inputs into a single directory so that vcfs and indices are together.

concat_vcf receives an array of vcf.gz and an array of vcf.gz.tbi. Cromwell groups each pair together in a separate inputs folder (because they were generated by the same upstream task), but miniwdl provides each input independently in its own directory, so the index isn't grouped with the VCF.  This PR links all inputs together into a single directory so bcftools can find the indices.

Looks good to me, hopefully this takes care of the index grouping issue


Supporting code push

These Additional checks will help in pushing code accessing RNIap plugin to SDK that does not have the plugin in it.
I am sure this will help other developers also to push code remotely without any breakage

@Rinkuk1993 Thank you for the contribution. This feature is definitely needed to supports phones that doesn't support IAP.

Sure. Thanks for the feedback. I will correct the code and push again

@Rinkuk1993 Could you do me one last favor? Since there is some conflict with master branch, I would like you to rebase your code to our master branch and push once more.

You can check now. Rebase is done and pushed


POST request with Content-Type: application/json

Can you show me example how to fake POST request with Content-Type: application/json?
For this curl?:
curl --header "Content-Type: application/json" \
  --request POST \
  --data '{"username":"xyz","password":"xyz"}' \
  http://localhost:3000/api/login

response can be also Content-Type: application/json
for example:
{
"name": "Martin",
"surname: "Jablecnik",
"logged_in: true
}
In your examples I see only GET for Content-Type: application/json and POST for Content-Type: application/x-www-form-urlencoded
Thank you very much.

POST /aaa HTTP/1.1
Content-Type: application/json
HTTP/1.1 200 OK
Content-Type: application/json
{"username":"xyz","password":"xyz"}

Works for me.
If you have trouble with it, please send me as an attachment your example.

Yes.

POST /aaa HTTP/1.1
Content-Type: application/json

{"username":"xyz","password":"xyz"}

HTTP/1.1 200 OK
Content-Type: application/json

{
    "name":"Martin",
    "surname":"Jablecnik"
}

Works for me also right now.
My previous experiment was similar to:
POST /aaa HTTP/1.1
Content-Type: application/json

{
    "username":"xyz",
    "password":"xyz"
}

HTTP/1.1 200 OK
Content-Type: application/json

{
    "name":"Martin",
    "surname":"Jablecnik"
}

Where request body have a little different format of body so it didn't work because the json --data wasn't exactly same. Isn't true?

You're absolutely right. If there is a difference in the first line of the query, headers, or body, the status will be given: 400 Bad Request.
To get the query to pass, you need to remove from the dump what does not match the real query.
Wildcards (*, ?) are allowed in query path and headers. This gives some flexibility.

Sorry! Wildcards are allowed in query parameters values.
In path you can use OpenAPI styled parameters: GET /customers/{country}/{id}/info HTTP/1.1

Yes ok. Now my question is: Can the request body of Content-Type: application/json be parsed and compared by keys and values instead of all body?
Because json:
{
    "username":"xyz",
    "password":"xyz"
}

and json:
{"username":"xyz", "password":"xyz"}

are same. Different is only format and indentation.
This should be useful because when I have:
{"username":"xyz", "password":"xyz"}

and
{"username":"xyz","password":"xyz"}

So finding difference and why it doesn't work can be very hard because diff is in only one small space..

I understand where this concept comes from. In terms of JSON semantics, the samples given are identical. But the purposes of comparing dumps may be different. Perhaps someone just wants to know that the server response has not changed. Or someone can just snatch JSON data with substring(). I don't think this is good practice, but in the interest of increasing performance, why not?


Adding updated Kusto extension

This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your PR is merged into master branch, a new PR will be created to update src/index.json automatically.
The precondition is to put your code inside this repo and upgrade the version in the PR but do not modify src/index.json.

add to S169

@AssafTaubenfeldMSFT  please address comments raised by @MyronFanQiu

@AssafTaubenfeldMSFT please address comments raised by @MyronFanQiu

In progress.

@MyronFanQiu @yonzhan
The requested changes are completed

@AssafTaubenfeldMSFT Based on my knowledge, the auto-generated cmdlet has many differences and user experience compared to manual cmdlet. Since auto generation tool is still under development and you have a tight schedule for JEDI requirement. My suggestion is to fix major issues and add experimental label(already did) first. We can release 0.1.0 version first and refine the extension later. @qiaozha It's should be a good chance for us to improve the auto generation tool and continue finding the best cooperation model.


Migrating from 0.19 to 0.22.9

I migrated from 0.19 to 0.22, the main difference I pick up is the use of the entryPointStrategy option. Since I wanted the behavior to be the same one, i used the expand option.
I removed some of the option that was removed in some release :
{
 "stripInternal": "true",
 "mode": "modules",
 "ignoreCompilerErrors": false,
 "preserveConstEnums": true,
}

Also, i changed my typescript version from 3.9 to 4.3, since 0.22 use typescript 4.0 and up.
Now, with all those change, when i run typedoc I get this error :
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
It look like running typedoc take now a lot more memory and time. If I enter only half the entrypoint, it work. It still take more time than the older version, and for half of the entry point.
I am wondering what im doing wrong in my migration of version. Did one of the option removed was important? Im trying to find what exactly they were doing, and I can find it anywhere.
If you have any lead for me, I will gladly take them!
Also, I upgraded NODE_OPTIONS=--max_old_space_size=16384 and it just took longer to crash.
Thank you in advance

stripInternal might be important. That's a TypeScript option, the equivalent one for TypeDoc is excludeInternal
This could definitely be a bug, but it's hard to say without a reproduction to look at.


audible-cli: 0.3.1 -> 0.3.2b3

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for audible-cli is: A command line interface for audible package. With the cli you can download your Audible books, cover, chapter files
meta.homepage for audible-cli is: https://github.com/mkb79/audible-cli
meta.changelog for audible-cli is: https://github.com/mkb79/audible-cli/blob/refs/tags/v0.3.2b3/CHANGELOG.md
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.3.2b3 with grep in /nix/store/33mq6jyc5k7q58gn0xw6f0pq600zpdj4-audible-cli-0.3.2b3
found 0.3.2b3 in filename of file in /nix/store/33mq6jyc5k7q58gn0xw6f0pq600zpdj4-audible-cli-0.3.2b3

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
audible-cli

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/33mq6jyc5k7q58gn0xw6f0pq600zpdj4-audible-cli-0.3.2b3 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A audible-cli https://github.com/r-ryantm/nixpkgs/archive/ab1f3a56afefe1d20fad5a157213c18bd15c83ca.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/ab1f3a56afefe1d20fad5a157213c18bd15c83ca#audible-cli

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/33mq6jyc5k7q58gn0xw6f0pq600zpdj4-audible-cli-0.3.2b3
ls -la /nix/store/33mq6jyc5k7q58gn0xw6f0pq600zpdj4-audible-cli-0.3.2b3/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

2 packages built:

audible-cli
audible-cli.dist

Maintainer pings
cc @jvanbruegge for testing.

For some reason the bot tries to update to a pre-release, I've opened an issue.


Using own camera to capture the frames

It would be possible to use our own camera source from which we get the frames instead of using the camera source provided by Twilio.
The use case I am asking about would be to be able to use our own camera with which to capture the frames in order to process them with a better quality than the one we get now. As we are doing now, we get the frames provided by Twilio through the camera capture of the SDK.
To create the video track we have created a camera (CamaraPropia) that extends CameraCapturer and overrides the methods provided by that class.
cameraCapturer = new CamaraPropia(context, CameraCapturer.CameraSource.BACK_CAMERA, videoFrameListener);
VideoConstraints videoConstraints = new VideoConstraints.Builder()
.aspectRatio(AspectRatio.ASPECT_RATIO_16_9)
.build();
localVideoTrack = LocalVideoTrack.create(context, true, cameraCapturer, videoConstraints);
localVideoTrack.addRenderer(videoView);
All the posts I've seen refer to Twilio 6.x version, in my case we are using a 5.1.0 version.

Hello, we have the same problem here.
Right now, we're using Twilio's camera but we need to use the frames captured by Android native camera or even our own custom camera. Does any Twilio method accept the frames captured from Android native camera?
Can we do this with version 5.x or is it mandatory to update to 6.x? Also, if we update to 6.x, could be receive the frames with a higher quality?
Thank you

@AliciaCamCas & @Laritaa Sorry about the late response. Yes, we do support creating a custom capturer. In our quickstart we have an example which you can use to help get started.


Ran out of memory on examples

Hi!
I tried to run examples using PCSX-Redux emulator.
But when I try to run "Monkey" and "Donut" examples, they are immediately falls into panic. Even in the case when I maximize system RAM to 8MB  in emulator settings.
Monkey error:
Panicked at /home/hlupa/Sources/psx-sdk-rs/psx/src/lib.rs:128:5
Ran out of memory Layout { size: 7000, align: 2 (1 << 1) }

Donut error:
Panicked at /home/hlupa/Sources/psx-sdk-rs/psx/src/lib.rs:128:5
Ran out of memory Layout { size: 4608, align: 2 (1 << 1) }

Am I doing something wrong? I don't think examples should fall into error like that.

Hello! The examples define a small fixed-size heap like this. Have you tried increasing it as explained in the docs?


Get article by slug

Resolves #161

Thanks for your review @nomisRev, and for the project, it's a really good place for learners !
Hope you feel better now :)


Paper structure

Re: https://github.com/openjournals/joss-reviews/issues/3617
Once or twice I had the feeling that the paper switches between topics or mixes things. As example, under 'statement of need' it switches from explaining the need directly to explaining how eyecite itself works.
Maybe this could be its own section?

@step21, I just merged #99, which attempts to address this. Are you a good person to decide if this issue is thus resolved?

Seems great. Thanks! I'd say as I raised the issue, I am also a good person to decide it is solved.

Thank you!


Angular 17 ready or not ?. (fails install)

I see some recent  git updates your working on angular 17.x.x compatibility ?.,
I'm asking since the project does not seam to run though when i install
npm i @runopencode/ngx-http-client
I get a conflict
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@angular/common
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@runopencode/ngx-http-client
npm ERR!   @runopencode/ngx-http-client@"*" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

Will it soonish be released ?, will it get to npm or should i install from Git ?.

There is an issue with versioning
"@angular/common": "^17",
NPM does not resolves this correctly, I will fix it and send new version, will let you know.

Oh thats great i'm in he middle of an upgrading my project

Ok, I have published v 17.0.6, it is available on NPM. Image below is package.json, there is no reason for you to have any conflicts, required angular versions are >=17.0.0 and <18.0.0 so you should be good.
Notify me if this fixes your issue.


Cleanup: Move Swift to ObjC name translation APIs to libAST to allow larger audience body. NFC

@swift-ci please smoke test


[CONCEPT] Handling transient status transitions in Trace-X

As ...
I want ...
so that ...
Hints / Details

Acceptance Criteria

[ ] Concept how to handle status transitions in the Trace-X Notification model in a sufficient way

Out of Scope

...

label concept is missing

Might be duplicate to https://github.com/eclipse-tractusx/traceability-foss/issues/423
Discussion in PL


Mixed Content results are not styled properly

When the extension detects mixed content within a page, the results are not styled properly.

Fixed


Fix Dtmf for IOS

Path to source was wrongly defined

@MateWW thanks for the PR, and sorry for the feedback delay! I haven't had time to test this, do you or @thymikee know what the effects of this change are on RN < 0.60? Obviously, we don't have any CI around this, so we'll have to experiment or decide "that's fine" if it breaks older versions.

Actually, I think this still doesn't work. My Podfile has:
pod 'RNDtmf', :path => '../node_modules/react-native-dtmf/ios'
With either the existing value of s.source_files  = "RNDtmf/**/*.{h,m}" or the proposed new value of s.source_files  = "ios/**/*.{h,m}", I don't get the actual Objective-C files included in the Pod at the iOS workspace level. I think this actually should be s.source_files  = "**/*.{h,m}", as the structure is based of the current directory of the Podspec file, which is RNDtmf/ios. What are your thoughts?

With autolinking you can remove this entry entirely from the Podfile.
This is breaking for anybody that imported the library directly in Podfile. I recommend releasing this in a major update :)

I believe this is actually fixed upstream in this commit: https://github.com/lucbelliveau/react-native-dtmf/pull/9/files
I'm going to merge upstream in, please take a look after that happens to see if this is still necessary.

@thymikee can you target the upstream then? I'd rather push these things into the root repository instead of further diverging here.

@MateWW would you be so kind and send another PR? 😅 Or @kkurz-sangoma feel free to move the file yourself 👍🏼

I'm not actively maintaining this fork at this point, so I'm going to let you guys push the upstream.


nuclei: 3.2.7 -> 3.2.8

Diff: https://github.com/projectdiscovery/nuclei/compare/v3.2.7...v3.2.8
Changelog: https://github.com/projectdiscovery/nuclei/releases/tag/v3.2.8
Description of changes

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

Result of nixpkgs-review pr 314448 run on x86_64-linux 1

1 package built:

nuclei


Support request mirroring

Mirroring is an optional feature that we do not support. This issue tracks the associated conformance test.
https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.HTTPRequestMirrorFilter
https://github.com/kubernetes-sigs/gateway-api/blob/v0.7.1/conformance/tests/httproute-request-mirror.go

Request mirroring is also required for HTTPRouteRequestMultipleMirrors test https://github.com/kubernetes-sigs/gateway-api/blob/v0.8.1/conformance/tests/httproute-request-multiple-mirrors.go


Fixed #445: Incompatibility with TensorFlow 2

Unfortunately, PR #453 didn't actually solve the issue #445.

The comment of @elbaro in #445 wasn't addressed.
Tests were not updated.

Additionally, two new test environments for TensorFlow 1 and 2 were declared.

Coverage increased (+0.07%) to 83.939% when pulling 2be875ffbfc51abd9f6a0bd26c94576fdb0bcc67 on tarik:tensorflow-2-support into<PHONE_NUMBER>139f4bcb75616e6674bda89f3ac26d on IDSIA:master.

Really nice work! Do you have any idea when compat.v1 was introduced in tensorflow. I wonder if we would break compatibility with older tf versions, if we solely rely on it.

A good point... This was introduced with the latest version 1.13.0.

Then maybe it would be a good idea to do an explicit version check for tf versions below 1.13 and in this case simply import tf as it is. We could then also print a deprecation warning, telling that tf versions below 1.13 will not be supported in the future.

Codacy complains about an assert statement in a test. And Coveralls' stated coverage decrease is actually covered through the new test environments.

Great work! It feels like codacy is complaining on every PR :D I will merge once the new checks passed.


"astimezone() cannot be applied to a naive datetime" when adding periodictask

Hi,
I recently updated my whole stack to the latest versions of django, celery and django-celery.
To update my database I just deleted all djcelery related tables before installing packages.
When I add a new periodictask with a "crontab" entry in the django admin (admin/djcelery/periodictask), I have this issue :
Exception Type: ValueError at /admin/djcelery/periodictask/add/
Exception Value: astimezone() cannot be applied to a naive datetime
here is my stack :
Django==1.5
celery==3.0.17
django-celery==3.0.11
django-celery-with-redis==3.0
redis==2.7.2
I tryed to set USE_TZ to False in the django settings with no success.
Here is the end of the error trace :
File "/home/dotcloud/env/lib/python2.6/site-packages/django/dispatch/dispatcher.py" in send
  170.             response = receiver(signal=self, sender=sender, **named)
File "/home/dotcloud/env/lib/python2.6/site-packages/djcelery/models.py" in changed
  179.                                          defaults={"last_update": now()})
File "/home/dotcloud/env/lib/python2.6/site-packages/djcelery/utils.py" in now
  65.         return timezone.localtime(timezone.now())
File "/home/dotcloud/env/lib/python2.6/site-packages/django/utils/timezone.py" in localtime
  237.     value = value.astimezone(timezone)

Exception Type: ValueError at /admin/djcelery/periodictask/add/
Exception Value: astimezone() cannot be applied to a naive datetime

I'm also running PostgresSQL as my main database (9.0.4).
I know Postgres has a special DB type for TZ datetimes, I just checked and it seems to be alright ("timestamp with time zone" everywhere).
any clue?

I'm seeing this in 3.1.16


Java is missing

I'm getting bunch of  missing errors when running setup.buildAPKs.bash
First time
Followed this
https://sdrausty.github.io/docsBuildAPKs/easilyBuildAndroidAPKsOnDevice

Using Android Pie Oneplus 6

This is due to https://github.com/termux/termux-packages/issues?q=is%3Aissue+is%3Aopen+ecj ecj error.  Repost at https://github.com/termux/termux-packages/issues.

In the meantime try fixing the error by running fix.ecj.error.bash and fix.ecj4.6.error.bash located in ~/buildAPKs/debs.

@hjyoung1 please confirm this resolution: https://github.com/sdrausty/buildAPKs/commit/fa0cfdae35fc3d363407a25a1d9ef1073597ff83

Use git pull to update.

Works fine now. Thanks.

Thank you for confirming.  You still might want to repost at https://github.com/termux/termux-packages/issues?q=is%3Aissue+is%3Aopen+ecj to help other users, and this project, too.  Eclipse Java Compiler should be working from the main repository, and it has been broken for quite a while.

You're welcome and thank you for confirming.  You still might want to repost at https://github.com/termux/termux-packages/issues?q=is%3Aissue+is%3Aopen+ecj to help other users, and this project, too.  Eclipse Java Compiler should be working from the main repository, and it has been broken for quite a while.

You are welcome, and thanks for confirming;  This issue may want reposting at https://github.com/termux/termux-packages/issues?q=is%3Aissue+is%3Aopen+ecj to help other users, and this project, too. Eclipse Java Compiler should be working from the main repository, and it is broken for quite some time now.

You are welcome, and thanks for confirming;  This issue may want reposting at https://github.com/termux/termux-packages/issues?q=is%3Aissue+is%3Aopen+ecj to help other users, and this project too. Eclipse Java Compiler should be working correctly from the main repository, and it is broken for quite some time now.


proposal: os: add Touch to set access/mod times to current time

What version of Go are you using (go version)?

$ go version
go version go1.12.5 linux/amd64

Does this issue reproduce with the latest release?
Yes.
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/flamencoadmin/.cache/go-build"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/flamencoadmin/go"
GOPROXY=""
GORACE=""
GOROOT="/opt/go"
GOTMPDIR=""
GOTOOLDIR="/opt/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/home/flamencoadmin/gotouch/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build400479428=/tmp/go-build -gno-record-gcc-switches"

What did you do?
Call os.Chtimes(filepath, now, now) where filepath is poining to a regular file on an SMB share and now := time.Now().
What did you expect to see?
No error, and the mtime of the file changed to 'now'.
What did you see instead?
An os.PathError is returned as follows:
Error type: *os.PathError
Error msg: chtimes /mnt/flamenco-input/file-store/stored/d6/2d13ed80d57784d9c5113a4bb32541c2b23a1e7ef02117f49084985bee144d/8271557.blob: operation not permitted
    op  : chtimes
    path: /mnt/flamenco-input/file-store/stored/d6/2d13ed80d57784d9c5113a4bb32541c2b23a1e7ef02117f49084985bee144d/8271557.blob
    err : operation not permitted

The SMB share is served from a Microsoft SMB server (an Azure Files share), which apparently doesn't support setting the modification/access time to a specific timestamp. However, what it does support is setting the mtime to "now" using the Linux touch CLI application. By using strace touch thefile I found that it actually calls utimensat() with NULL as timestamp, rather than passing an explicit timestamp.
To test whether passing NULL would work, I added the following function to src/syscall/syscall_linux.go:
func UtimesNanoNow(path string) (err error) {
	err = utimensat(_AT_FDCWD, path, nil, 0)
	if err != ENOSYS {
		return err
	}
	return utimes(path, nil)
}

The following now works fine on the SMB share:
func ChtimesNow(name string) error {
	if e := syscall.UtimesNanoNow(name); e != nil {
		return &os.PathError{"chtimes", name, e}
	}
	return nil
}

I tested this on Linux (4.18.0-1014-azure) on Ubuntu (18.04.2). The SMB share was mounted with the following options, as per the Microsoft documentation:
//${ACCOUNT_NAME}.file.core.windows.net/flamenco-resources on /mnt/flamenco-resources type cifs (rw,relatime,vers=3.0,sec=ntlmssp,cache=strict,username=${ACCOUNT_NAME},password=${ACCOUNT_PASSWORD},dir_mode=0770,file_mode=0775,gid=flamenco,forcegid,sec=ntlmssp,mfsymlinks)

I guess the question is whether we should add os.ChtimesNow to support this edge case, or whether we should expect programs to call unix.UtimesNanoAt, from the golang.org/x/sys/unix package, instead.

Touching a file is a common operation. I suspect it is even more common than setting the timestamps to a different time, although that's just my gut feeling.
I vote for os.ChtimesNow (or simply call it os.Touch), as the operation is at the same level of abstraction as os.Chtimes. Just setting a file's mtime to "now" should IMHO not require any platform-specific branches in your code.
unix.UtimesNanoAt doesn't accept nil, so I doubt that it'll fix this issue. Or did you mean my UtimesNanoNow function @ianlancetaylor ?

When I look at the implementation of unix.UtimesNanoAt I see that it does accept nil as the []Timespec argument, and that it does the right thing.  This dates back to https://golang.org/cl/12690.

I turned this issue into a proposal for os.Touch.

If this is named Touch(), then will it also create the file if it does not exist, as per the touch unix command?

@beoran for me personally that wouldn't be necessary, but I wouldn't object (unless it delays the availability of the function. All I need is a Chtimes(now) call that works for my use case.

It seems that there are two special cases for os.Chtimes: leave the time unchanged, and set the time to "now".  Adding os.Touch will help with the latter but not the former.

Other gross/weird idea: add sentinel time.Time values for UTIME_NOW and UTIME_OMIT, perhaps within a sentinel *time.Location.

I kind of like that, actually.  We could add os.ChtimesUnchanged and os.ChtimesNow of type time.Time.

It seems that there are two special cases for os.Chtimes: leave the time unchanged, and set the time to "now".

According to whom?

We could add os.ChtimesUnchanged

What would the normal English interpretation be of a name like ChtimesUnchanged? To me, "Change time unchanged" sounds cryptic at best.
What is the use of calling a "change times" function with argument "do not change"?

The source for the observation that there are two special cases is 1) examination of actual calls to os.Chtimes in Google's code, and 2) the observation that the Linux kernel supports two special cases UTIME_NOW and UTIME_OMIT (see http://man7.org/linux/man-pages/man2/utimensat.2.html).
I agree that os.ChtimesUnchanged is not the best name, happy to hear alternatives.  Note that it is not a function, but a value of type time.Time.
The use of the argument is that os.Chtimes takes two arguments for two different times, and some code wants to only change one of them.  Currently that code must first call Stat to get the time to pass to os.Chtimes; an os.ChtimesUnchanged, whatever we call it, would simplify that code.

We don't need Chtimes in the name. It'd look pretty stuttery with them:
os.Chtimes(path, os.ChtimesUnchanged, os.ChtimesNow)

How about:
package os

// Special time.Time values for os.Chtimes:
var (
    // KeepTime is recognized by Chtimes to mean that the access or modification
    // time should not be changed. It is not a valid Time value otherwise.
    KeepTime  = time.Unix(0, 1).In(utimeLocation)
    // TouchTime is recognized by Chtimes to mean that the access or modification
    // time should be set to the current time. It is not a valid Time value otherwise.
    TouchTime = time.Unix(0, 2).In(utimeLocation)
)

@bradfitz that looks good to me!

The special time location bothers me but a sentinel time seems OK.
We already have the zero time for 'don't update this', so really we just need a sentinel for "now".
Maybe time.Date(10000, 1, 1, 0, 0, 0, 0, time.UTC)?

I already use such a value as a sentinel for "forever" in a large
professional application. I don't see how it could mean "now". We already
have time.Now() for this use case.
Op di 28 mei 2019 22:51 schreef Russ Cox<EMAIL_ADDRESS>
The special time location bothers me but a sentinel time seems OK.
We already have the zero time for 'don't update this', so really we just
need a sentinel for "now".
Maybe time.Date(10000, 1, 1, 0, 0, 0, 0, time.UTC)?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/golang/go/issues/31880?email_source=notifications&email_token=AAARM6IC32AEO5VQZ4BHPFDPXWLNHA5CNFSM4HLHNDM2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWNMWSY#issuecomment-496683851,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAARM6O5UNTEZGU7HLAKOGLPXWLNHANCNFSM4HLHNDMQ
.

time.Now isn't a sentinel value. It's a function that returns a time value.

Also kind of the point of this issue is that there is at least one case where using time.Now() doesn't work.

Last week we talked about a sentinel for meaning "tell the FS 'now'". One problem with this approach is that it only works when people think to use it, and more importantly not doing it only breaks on Azure Files or other SMB servers. So most code will work everywhere except Azure and it will be hard to get everyone to fix their code for a use case they may not directly need.
One possible alternative, following a bit @beoran's suggestion, is to say that if the time passed to Chtimes is "within epsilon" of the current time, then Chtimes just automatically tells the file system to use the special "now" form instead of an explicit time. For example you could define "within epsilon" to mean "has monotonic time at most 100ms earlier than now". That would have an unfortunate effect if you did os.Chtimes(time.Now()) and the code was interrupted between those calls. But it would work most of the time without requiring everyone to learn a new way to spell that call.
On balance it is probably still better to have the sentinel instead?

Does anyone know more about the underlying issue with Azure Files / SMB? Is this a fundamental limitation of the SMB protocol that there is no "set mtime" RPC, or is it a problem specific to Azure Files not implementing that call?
/cc @ashleymcnamara

Last week we talked about a sentinel for meaning "tell the FS 'now'". One problem with this approach is that it only works when people think to use it, and more importantly not doing it only breaks on Azure Files or other SMB servers. So most code will work everywhere except Azure and it will be hard to get everyone to fix their code for a use case they may not directly need.

This is a good point. I think it can be partially solved by good documentation, making the correct choice (using the sentinel value) more obvious than using the probably-works choice. This is also partially why my initial suggestion had a different, parameterless function; when ChTimes() and ChTimesNow() appear next to each other in a module function list, it's easier to just pick the ChTimesNow() and harder to think "I can use time.Now() and pass its return value to ChTimes()".
I would certainly add a warning to ChTimes() that states that setting an arbitrary mtime/atime isn't supported on all filesystems.

One possible alternative, following a bit @beoran's suggestion, is to say that if the time passed to Chtimes is "within epsilon" of the current time, then Chtimes just automatically tells the file system to use the special "now" form instead of an explicit time. For example you could define "within epsilon" to mean "has monotonic time at most 100ms earlier than now". That would have an unfortunate effect if you did os.Chtimes(time.Now()) and the code was interrupted between those calls. But it would work most of the time without requiring everyone to learn a new way to spell that call.

I wouldn't like this approach; I don't like code that should work most of the time. Sure, in the point you make above we also have code that works most of the time. The distribution of failure is different though: it reliably never works on those Microsoft SMB servers, and it reliably always works on other filesystems. The "epsilon approach" would unreliably work most of the time, which I think is much worse.

Right now we have:

os.Chtimes(a, m) - sets a, m

We might want:

os.Chtimes(_, m) - set only m
os.Chtimes(a, _) - set only a
os.Chtimes(_, NOW) - set only m to NOW
os.Chtimes(NOW, _) - set only a to NOW
os.Chtimes(NOW, NOW) - set both to NOW

We can handle the "don't set this" case with time.Time{}. That seems unobjectionable. What's left is the NOW cases.
We could add os.ChtimesNow but with no arguments it would only cover one of those three. To cover all three we'd need arguments, like os.Chtimes(false, true), which is mysterious. We could add os.ChtimesModNow and os.ChtimesAccessNow but that would leave no way to do the "NOW, NOW" and guarantee they got the same time. None of these sound good. We need a better idea.
I am still confused about why it is not possible to set the times to anything at all. I looked briefly at the latest CIFS spec and can't see where it says "you can't set atime/mtime to anything but right now" nor do I even see "here is how to set them to an abstract right now". Or is Azure imposing the constraint? If so, where is that documented? I'd really like to hear something authoritative from Microsoft before we start adding workarounds that show up in package os's exported, long-term API.
It seems like maybe Go is not using the right Windows call inside Chtimes. If that's the case, let's fix that.
/cc @spf13

Started #32558 for the _ (don't set me) case. This issue will be about time.Now() vs NOW vs Azure.

I was working on a program recently that encountered a similar issue. Specifically that from Go, SMB operations don't respect calls to change the mtime of files.

I think os.Chtimes is doing too much at once. I would split it into
os.Chatime and os.Chmtime, and give it a (time.Time, is.Chtimeflags)
signature, where the flags are used to indicate special features such as
time.Now.
Op di 11 jun. 2019 22:42 schreef Russ Cox<EMAIL_ADDRESS>
Right now we have:

os.Chtimes(a, m) - sets a, m

We might want:

os.Chtimes(_, m) - set only m
os.Chtimes(a, _) - set only a
os.Chtimes(_, NOW) - set only m to NOW
os.Chtimes(NOW, _) - set only a to NOW
os.Chtimes(NOW, NOW) - set both to NOW

We can handle the "don't set this" case with time.Time{}. That seems
unobjectionable. What's left is the NOW cases.
We could add os.ChtimesNow but with no arguments it would only cover one
of those three. To cover all three we'd need arguments, like
os.Chtimes(false, true), which is mysterious. We could add os.ChtimesModNow
and os.ChtimesAccessNow but that would leave no way to do the "NOW, NOW"
and guarantee they got the same time. None of these sound good. We need a
better idea.
I am still confused about why it is not possible to set the times to
anything at all. I looked briefly at the latest CIFS spec
https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-cifs/d416ff7c-c536-406e-a951-4f04b2fd1d2b
and can't see where it says "you can't set atime/mtime to anything but
right now" nor do I even see "here is how to set them to an abstract right
now". Or is Azure imposing the constraint? If so, where is that documented?
I'd really like to hear something authoritative from Microsoft before we
start adding workarounds that show up in package os's exported, long-term
API.
It seems like maybe Go is not using the right Windows call inside Chtimes.
If that's the case, let's fix that.
/cc @spf13 https://github.com/spf13
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/golang/go/issues/31880?email_source=notifications&email_token=AAARM6LU7LNJEHZXOXEU5CTP2AE4ZA5CNFSM4HLHNDM2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXON4RA#issuecomment-501014084,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAARM6I44PBJ24XFFOQUJTLP2AE4ZANCNFSM4HLHNDMQ
.

@beoran That doesn't provide a clear way to set both times to "now" and to the same "now".  Also it's worth noting that on Unix and Windows the underlying system call takes both times.  And also there is really only one flag--set the time to "now"--and it's hard to see why there would ever be another one.

Yes, you are right. I checked the system calls SetFileTime() and utimens(), and I realized that now. It makes sense because if two system calls were needed, it would be impossible to synchronize both times. But I do notice that on both OS, the system calls do no take a wall clock time like LPSYSTEMTIME  or struct time, but a specific file-related time, FILETIME or struct timespec, which allows more easily to specify special values than time.Time does.
So, I would say that this is then the problem with os.Chtimes, it takes plain time.Time, but it should probably take a file system specific time, e.g, os.FileTime. For backwards compatibility, os.Chtimes can be left as it it, and the new function that takes the os.FileTime could be named something like os.Chfiletimes. The os.FileTime could be something like type FileTime struct { time.Time ; Now bool ; Ignore bool }.

os.FileTime could be something like type FileTime struct { time.Time ; Now bool ; Ignore bool }

To me this looks like a hassle, compared to just passing a time.Time instance. Furthermore, it allows for the invalid combination Now=true; Ignore=true; those two are mutually exclusive.

I don't think we should make any decisions here without some kind of definitive clarification about what the Azure- or SMB-imposed limitations are. We are designing around something and we don't even know what shape it is. Let's not kick around any new APIs until we understand that better.
See https://github.com/golang/go/issues/31880#issuecomment-498838303 and https://github.com/golang/go/issues/31880#issuecomment-501014084.
/cc @ashleymcnamara @erikstmartin

Marked this last week as likely decline w/ call for last comments (https://github.com/golang/go/issues/31880#issuecomment-525469841).
Declining now.

I couldn't answer earlier as I was on holiday.

We asked for details about what the specific CIFS/SMB/WinAPI/Azure restrictions might be, in #31880 (comment) and #31880 (comment) and #31880 (comment). No answers here.

I'm far from a CIFS/SMB expert, I just know that one thing worked and another thing didn't. I was hoping someone else from the Golang community could chip in.


E8S Mirror Mirror 3 sometimes does wrong directions

Description
Description of the issue you're seeing.
Additional information
If available, please include any logs or screenshots depicting the issue you're experiencing.

Could you file this on https://github.com/OverlayPlugin/cactbot/issues/new instead?

Could you file this on https://github.com/OverlayPlugin/cactbot/issues/new instead?

Ok I submitted there instead.


Grand Theft Auto: San Andreas has graphics and gameplay issues

Please describe your issue as accurately as possible. If you run into a problem with a binary release, make sure to test with latest master as well.
Important: When reporting an issue with a specific game or application, such as crashes or rendering issues, please include log files and a D3D11 Apitrace (see https://github.com/apitrace/apitrace) so that the issue can be reproduced. In order to create a trace, run wine apitrace.exe trace -a dxgi YOURGAME.exe. DO NOT use DXVK together with apitrace!
Software information
Grand Theft Auto San Andreas (Steam 12120)
System information

GPU: Nvidia GTX 960
Driver: 430.34.0
Wine version:  4.12.1 TKG
DXVK version: https://github.com/Joshua-Ashton/d9vk/commit/bc64e8e0263004908090da60b4c478a6573fe7d0

Apitrace file(s)
https://drive.google.com/file/d/1PmN6V0aXpUYCKG14GS2BCpL5_4ZrwcYi/view?usp=sharing
Motion blur and first mission lockup trace:
https://drive.google.com/file/d/1ADG7IdhmrCxUgb3KRIMg9icgnZkkmgwt/view?usp=sharing
Log files

d3d9.log:
gta-sa_d3d9.log

Hello! I've noticed a weird bug where most vehicles are colored beige up close, but regain their color when viewed at a distance. Some environmental elements are also affected (walls, lights, etc.) It doesn't seem to affect people or motorcycles.
Thanks!
EDIT: Replaced the trace with a tar.xz.
EDIT 2:
Here's a summary of what's been seen so far:

[x] Lighting issues

[x] Car texture coloring

[ ] Motion blur

[ ] First mission freeze

I added another trace which includes motion blur and the first mission gameplay. Cheats were used to obtain a fast car with nitrous, but shouldn't affect anything else.

The game has also a lighting issue.
with d9vk

without d9vk

^ That's because D9VK is lacking fixed function lightning implementation.

To avoid spam I'm just going to report here that the "motion blur" when traveling fast on vehicles is broken on d9vk

Master has ff lightning now so please retest.

Lighting looks like it's fixed.

texture problems still present.
would be nice to get some screenshots of that mb?

Alright, I'll get a screenshot of that soon.

Cars when they are close:

When they are far:

Ha, beat me to it.
Also, there's this weird case in the intro where the car texture is blue instead:

Also, I haven't been able to get through the first mission; The game seems to lock up when starting it and my computer slows to a crawl, requiring me to kill the process.

@Guy1524 , this is the closest I could get to showing motion blur. I can't really tell the difference between native and d9vk here. Could you post a screenshot or something else that shows the motion blur issue? It'd be really appreciated. Thanks!
D9VK:

Native:

All right, I added a second trace which hopefully highlights these issues.

Starting from 3831767, CJ and all the NPCs look like this:

gta_sa_d3d9.log
I tried making an apitrace, but it doesn't show the issue.

I can confirm.
With #716 the game was perfect.

I've got the same thing here. Also, the fullscreen game window is only using the top-left corner for me instead of the whole screen, but I don't know if that's D9VK's issue (it didn't happen with previous commits).

Can't replicate the fog issue on any of my GTA SA traces

Can you make a trace with d9vk?

d9vk trace that showed the issue for me on replay:
https://drive.google.com/open?id=1Zg2BgHB8yeh9dFggJXFa7qvqqKOAJTmT

@CartoonFan The issue actually only happened on my first session playing, the motion blur was offset by about 50% of the screen.  However now I can no longer reproduce it, so it's probably best to just ignore it unless somebody re-encounters it.

@Guy1524 Sounds good to me. I'll update the main post accordingly. Thanks for replying!

The fog issue looks like it's fixed for me as of https://github.com/Joshua-Ashton/d9vk/commit/625bf3032a0e1e1b22de739e7651f23fc8da6ae9 . Great job! I also noticed that with the first mission issue, the audio continues to play while the video stays at the mission title, and the audio is fairly quiet compared to what I remember.
With my resolution issue, this is supposedly 1024x768 fullscreen, according to the game:

The game renders it as seen, black borders and all.

So, a small update:

The resolutions are still weird for me. I might try a widescreen patch in the future to make my native resolution available, if nothing else (It's not available at all, probably a fault of the game).

The video freezing on the first mission (and consequently the audio issues) seem to be related to anti-aliasing. Turning it off allows me to progress further.

On my side, with #778, everything is good. But yes, the game freezes when there is a transition to a cutscene when the antialiasing is on (could it be related to https://github.com/Joshua-Ashton/d9vk/issues/264#issuecomment-515771619 ?)

Awesome! I managed to get my resolution fixed for now by disabling the proton fullscreen patch on Wine-TKG 4.13+. I'm pretty sure it worked before, but maybe something happened. Who knows? I'm just happy to find a workaround.

I don't have any issue with the resolution with Proton, it's weird, but I don't think it's related to d9vk.

I agree, at least for now. With wined3d, it's like a borderless window, and with d9vk, those black borders are there. That's pretty much the only difference I can see. Virtually every time I changed resolution, I got an effect similar to https://github.com/Joshua-Ashton/d9vk/issues/270#issuecomment-524122513, even with a clean prefix (+d9vk/dxvk), changing settings, etc. Right now, disabling the fullscreen patch is the only thing so far that has worked almost every time. But I'm definitely glad to hear that it works well for you.

I have a fix hopefully in the works for this.

Can you try with https://github.com/Joshua-Ashton/d9vk/commit/8490b27bf20b3ee20d0aa5d850e430841415e7e0?

All right, I'll give it a try.

Great work! The fullscreen issue seems to be fixed for me with both games I had problems with (this one and Forgotten Realms: Demon Stone). On another note, it's still amazing that I can make a game like this hang indefinitely simply by changing resolutions too often, but as usual, I'm not sure if that's a D9VK bug yet or not. More testing, right? Again, though, stellar job!

Forgotten Realms: Demon Stone

Btw, if you have the time, can you upload an apitrace for this game? (issue with the logo and the white textures)

Forgotten Realms: Demon Stone

Btw, if you have time, can you upload an apitrace for this game? (issue with the logo and the white textures)

Yeah, I noticed that too. I have a Windows trace already, but the issues don't show up there, so I just want to make one with D9VK and then I'll be ready. Thanks!

Can this be closed?

What should I about the antialiasing-related hang? Should I make a separate bug, or close this and wait for #264, or something else? I'm OK with closing it if the remaining stuff is handled in another bug.

@CartoonFan could you try #328 and see if it fixes the hang?

All right, I'll try it.

OK, It seems that the game no longer hangs during cutscenes. There are a few stutters for me near the beginning of the game, but those seem to go away eventually. However, the game seems to be ignoring Wine-TKG's Proton fullscreen patch and changing my desktop resolution when I change it in-game. Do you happen to know anything about this? I can open a separate bug if you think it's not related.
In any case, I guess it's time to close this bug, as the original issues are fixed and my problems here are smaller and more specific.
Closing #270.


Random crash when deleting multiple addresses

Not sure if specifically using the shift key to highlight multiple addresses causes this, but I've only had it happen when doing so. Randomly, highlighting a bunch of addresses with the shift shortcut, right clicking, and hitting delete, then pressing yes on the prompt will cause it to crash.

I don't thinks its related to shift, as it happens randomly to me when I remove a single entry.

It is not related to the shift key, from my tests, it doesn't seem random at all, it seems the order of the selection and the items matters.  I am not sure if I got it to crash with a single deletion, but I suspect it's likely related to this issue tbh.

I can't seem to reproduce this issue reliably which is odd because I used to make files to do it, I really should have documented it how I did it :(
If anyone knows of a way to reproduce it, please say it here because I have no idea.

I also cannot get it to reproduce consistently. I get the crashes occasionally.
One way is when toggling 'is a pointer' on/off. Similarly when changing the address of a pointer or a type (word, byte, string)

I also cannot get it to reproduce consistently. I get the crashes occasionally.
One way is when toggling 'is a pointer' on/off. Similarly when changing the address of a pointer or a type (word, byte, string)

For the pointer, see #26 which I just found the cause and fixed.
For changing types, that one I can't get it and I am pretty sure #26 would have nothing to do with this issue because it only involved the dialog.
To be honest, I do not know if I can get a diagnosis and a fix before the 0.5 release. It turns out I want to start another project after I release 0.5 so I want to get it done asap as this program badly needs an update. I also just pushed the biggest feature I wanted for this release meaning I won't do too much before the release.

I have experienced this crash myself quite a few times.
I believe this issue is caused when you lock a value in the watch list. After a value has been locked, regardless of if it has been unlocked afterwards or not, appears to cause the crash.
The above conditions conditions appear to cause the crash nearly 100% of the time, from what I have observed.

Hi @Reshiram110 , I am unable to reproduce the crash by locking values and deleting them.
Which version was this, and can you provide a .dmw that does it consistently?

To check:
Group selection, invalid nodes

Did a bunch of checks, I think this was resolved 0.5.0
Please re-open if you encounter crashing again while using 0.7.0+ version of DME.


If any host or port is specified use a TCP language client instead of STDIO

Note - Blocked until #238 is completed.
As part of #238 the default transport will be STDIO.  This means we can change the lang. client behaviour to use the TCP transport if either Port or Host are specified.
https://github.com/jpogran/puppet-vscode/blob/8fdfb7894d08de673bac319991a2499050df97f6/client/src/connection.ts#L76-L82

This is implemented slightly differently than originally written in this. This is now decided by the puppet.languageclient.protocol setting. It defaults to STDIO, but if you specify TCP it will inspect the puppet.languageserver.host and puppet.languageserver.port configuration settings for what to use to connect to the languageserver. If they aren't set (the default), it will choose it's own port. If they are set, then it will use those settings. This is implemented in PR #292


liquid-with broken

This commit broke liquid-with for me:
https://github.com/ef4/liquid-fire/commit/628b2148738dc24002c01fdc728191a2931c8bf2
My usage is near verbatim from the docs, and as far as I can tell from the changelog there was no planned breaking change for the liquid-with helper.

Ugh, you're right. You must have a liquid outlet capturing the change.
We will need to revert this until we're ready to switch entirely to
liquid-outlet for model-to-model transitions.
On Apr 5, 2015 5:58 AM, "Dustin Farris"<EMAIL_ADDRESS>wrote:

This commit broke liquid-with for me:
628b214
https://github.com/ef4/liquid-fire/commit/628b2148738dc24002c01fdc728191a2931c8bf2
My usage is near verbatim from the docs, and as far as I can tell from the
changelog there was no planned breaking change for the liquid-with helper.
—
Reply to this email directly or view it on GitHub
https://github.com/ef4/liquid-fire/issues/235.


Make pls builds

Hello. Thanks for u work , can u make builds for Linux and windows ?

@roi35, Thank you for you feedback.
Primary platforms build released.
Include:

Linux x64
MacOS x64
Windows x64

See release: 0.2.0


[#14] UI bugs fix in tableviews for all screen

[#14] UI bugs fix in tableviews for all screen

Looks good to me!


Combine DEVELOPER.md into CONTRIBUTING.md

Addresses https://github.com/OctoLinker/browser-extension/issues/86#issuecomment-222381365:

[ ] Merge CONTRIBUTING.md and DEVELOPER.md

This commit makes a few changes:

Make the "Quick Start" and "Pull Request Guidelines" sections into
subsections of "Developer guide" in CONTRIBUTING.md
Move the "Overview" section of DEVELOPER.md to the "Architecture
Overview" subsection of CONTRIBUTING.md
Remove DEVELOPER.md, and don't reference it from README.md

Thank you @josephfrazier


randomise-source-coords

Additionally to randomising the irf and pointing, the wrapper should include the randomisation of the source coordinates.
It requires to update the xml model each run.

Task completed.


no way to install cargo when built with cargo

If you build cargo with cargo build --release, then there is no mechanism to install it on the system.
Running ./configure && make install is not really an option because that tries to download a snapshot, and there may not be a snapshot and/or downloading it may be undesirable in a package build situation.

There's a ./configure --local-cargo=/path/to/cargo which doesn't download a snapshot, does that suffice?

This would be perfect, but there seems to be a problem, when I do a gmake install I get:
sh: /home/rkitover/src/cargo//src/rust-installer/gen-installer.sh: No such file or directory
Makefile:320: recipe for target 'target/x86_64-unknown-openbsd/release/dist/cargo-0.10.0-x86_64-unknown-openbsd.tar.gz' failed
gmake: *** [target/x86_64-unknown-openbsd/release/dist/cargo-0.10.0-x86_64-unknown-openbsd.tar.gz] Error 1

Oh the src/rust-installer directory is actually a submodule and the configure script doesn't currently check it out just yet, so if you run git submodule update --init head of time, does that fix it?

Yes this works fine, thank you. However, there are no tags for rust-installer and therefore no github tarballs of it, which is also a problem for packaging, because you cannot download things during a build.
Could you please make a tag for rust-installer?

cc @brson

Ok, closing in favor of https://github.com/rust-lang/rust-installer/issues/45


Remove the g_i hidden state

It seems like we can calculate the G_i values from F_i (stored in the upwards variable) and the likelihood for an (non-sample) edge, which is cached anyway. So we probably don't need to save g_i as a separate variable.

As discussed with Gil at genomics, this is still needed, but the calculation is different. Closing as obsolete


chore: replaced use of mod https with got

Also, if you wouldn't mind, could you please amend the commit message to follow the pattern below?
chore/feat/fix: <subject>

<body>

Contributes to/Closes: camelotls/actions-jira-integration#<issue-number>

Signed-off-by: FirstName LastName <email>

Removed/.gitignored .vscode dir. Fixed formatting violations.

@perpk please have a look a the linter once more :)


Update Kopernicus

Update forum page.
Kopernicus only works with MM 2.6.16 or higher.
Use suggest instead of recommends because this is only a modders tool.

:+1:


Addition of new release and tag workflow files

Aim: To separate the release of the SPS Frontend from the SPS Framework by adding the ability to tag and release container images of the frontend and to push the frontend npm package all from the frontend repo sepera.
What was added:

tag-workflow.yaml: the github workflow for building container images upon taging
release-workflow.yaml: the github workflow for building and pushing the frontend to NPM when making a github release.
build-images-core.sh: the script that gets our cloud provider and version and builds and pushes our docker container
http-server.dockerfile: the script that gets executed in build-images-core to build our docker container from our npm taged repo

Purpose: The aim of this merge is to merge in the new tag and release workflow files as well as the new sps-frontend docker file. These files will be responsible for carrying out the new release method for the sps frontend.
How to use Tag-Workflow:

bump the version of the sps library
commit the version bump
tag the version git tag v1.0.1dev
commit and push the tag git push && git push origin v1.0.1dev
head to the Actions tab for the SPS Frontend repo to view the workflow https://github.com/ScalablePixelStreaming/Frontend/actions
The workflow will create an sps-frontend docker image for useage in the tensorworks/sps-frontend repo

How to use the Release-Workflow:

after running the Tag-Workflow successfully head to https://github.com/ScalablePixelStreaming/Frontend/releases/new to create a new release based on the new tag
publish the new release
view the workflow at https://github.com/ScalablePixelStreaming/Frontend/actions
The workflow will create a new npm package for users to consume

Looks good to me


Very SLOW  For BigData Store

I store a video chunks on indexeddb via dexie ,  approx 2GB video chunks (~600 rows).
!!!!! Time of First lookup and fetch row  with primary key  -> 40 Second  (db.chunks.get(1)-> took 40 second)
!!! Second and others fetches took in millisecond.
What happening in this period.
When database size increased , first fetch  take a long time linearly.
Note: Tried Latest version of dexie  and browser of latest  Chrome&Opera&Firefox
DB Schema:
db.version(1).stores({
videos: "++id,url,content,size,httpUrl,hiveCdnUrl,createdDate"
});  //* content propert is ArrayBuffer

What browser type and version are you using? Device type desktop or mobile? Can you try fetching your data directly from native indexedDB just to check what time you would get there?
db.transaction ('r', 'chunks', trans => {
  return new Promise (resolve => {
    var store = trans.idbtrans.objectStore('chunks');
    console.log(Date.now());
    store.get(1).onsuccess = ev => {
      console.log(Date.now());
    };
  });
});

I updated the code snippet in my last comment to measure time taken (milliseconds).
Side note: It is also interesting to know whether you store your gigabyte chunks in Blob or Uint8Array - just for curiousity. I have no experience of storing that large amount of data in indexedDB and chances are that it would not be optimized for it. It may be worth it to try divide your data into smaller chunks than 2 GB - maybe in the MB range.

@mesutyigit Do I understand you correctly: Are you are really storing 2 Gigabyte (!!) into a single indexedddb row (object)? That will not work well as each row needs to be loaded into memory. Should really divide your data into much smaller chunks as suggested in my previous comment. Client devices may have very limited RAM memory to work with.

Not single row. There are thousands rows.  Each row approx. 900Kb size.
Dexie db.open function resolving very long time. Why?

db scheme is here

my metrics is here:
first read time (including db opening time): readtime(378352ms)
and first is completed then second readtime(db has opened): readtime(20639ms)
and second  is completed then third time : readtime(1418ms)
and third is completed then fourth time : readtime(311ms).

You index a property named 'content'. What data is stored into it? I hope no large content. I hope you know that you don't need to index all properties. I've had other issues reported where people indexed properties containing images or videos. That can starve out the db completely. Indexes are only for properties to use when searching whitch is typically numbers or small strings.

schema : "&url:String,content:ArrayBuffer,size:Int,createdDate:Long"   url:Primary Key (index is here )
content is arrayBuffer of this object (a small chunk of video (500Kb- max 1mb)), no index in here.

Aha. You say 'no index here' but in your code you list it among other indexed properties (!) Please add a version 2 with 'content' from videos table to remove that index (!)
db.version (2).stores ({
  videos: "++id,url,size,httpUrl,hiveCdnUrl,createdDate"
}) ;

This seems to have become a common pitfall, that people think they have to list all properties in the schema (as they were SQL columns), not aware that they should only list those properties that they wish to index.

I opened this issue a few months ago so schema changed more times.
you say videos:"++id,url,size,httpUrl,hiveCdnUrl,createdDate"  not usefull for my purpose.
Please tell me best effective indexedDB schema for my purpose.

I want to store chunks of videos.
think that  VideoChunk(url:String , size:Int,createDate:Long, data: ArrayBuffer).

I want to lookup chunk with URL as soon as fast   like this

db.videos.get('www.example.com/1.ts') !== undefined

I want to read  chunk object with URL  as soon as fast

db.videos.get('www.example.com/1.ts')

I want to store thousands of row in this table ( Max limit is client Qouta Exceed)

My current schema is:
db.version (1).stores ({
videos: "&url,data,size,createdDate"
}) ;
I don't use ++id column because  URL column unique for me. All lookup queries using URL.
How I can do it.

http://dexie.org/docs/Version/Version.stores() clearly states schemaDefinition is just for primary and secondary indexes and there are few more warning below.
If one reads the documentation and remember all there are no problems, however I think it is still a pitfall.  schemaDefinition parameter name can be changed to indexDefinition or indexedFields or something similar to reflect that, that parameter is just for indexes ,and dexie is a   schemaless database.


Suggest Way to Unpack .mustache files in README.md

Instead of making a brief example, a new wiki page was set up: https://github.com/Chrimle/openapi-to-java-records-mustache-templates/wiki/Walkthrough-(Step‐by‐Step)
Refer to this in a TIP-quote or something...