ResourceServer.options is unused

From auth0 created by maroux: go-auth0/auth0#80
Should probably remove?

Thanks for submitting @maroux,
For reference, the field in question is this. The docs don't seem to reference the field and its likely removed by Auth0.

The Options param on the ResourceServer is actually still accepted by the API on POST or PATCH requests. It holds external API specific settings.
Closing this down because of this as we won't be removing it for now.


Redirect on login is not bringing users to the get-started process

Fix the routes and add tests to ensure new users are always brought to the get-started pages

Test already existed, issue was with global jquery handler for input changes in surveyAnimation.js.coffee


Rename modules to follow the best practices

It's recommended to use lowercase letters with hyphens instead of camel case
https://devcenter.heroku.com/articles/node-best-practices

I changed my mind.
Shallow googling didn't say that it's the only right way, also the ReactJS applications bootstraper, namely https://github.com/facebook/create-react-app, uses class names as names of files.


Enhance the Styling of the Snapshot #10

Minimalistic Design:
-Updated the snapshot background to have a more minimalistic design with a professional and premium look.
Dynamic Background Sizing:
-The snapshot size adjusts dynamically based on the input text size.
-For shorter text, increases the font size to fill the space proportionately.
-For longer text, reduces the font size so that it remains readable and fits within the snapshot area.
Background Color Options:
-By default, gradient background colors are provided for the user to choose from.
User-Customizable Background:
-Provides a feature for users to upload their own background image for snapshots.

@TheOpenInnovator Kindly look into this and let me know if any changes are required. Thank you!

@TheOpenInnovator Merge conflicts have been resolved. Kindly check

Hey @Divii2205 The functionality is great, but there is some fix required.

What ever text is entered, in the snap shot, it's showing twice. Please check it and if it exists, do fix it.

Input Text :

Snap Shot generated :

@TheOpenInnovator I have fixed it. Kindly check now.Thank you!

Hey @Divii2205 There is still something that you need to fix.
The current live version of the snapshot :

The Snapshot from your PR :

In your PR, the snapshot is showing the  tag whenever there is line break. Please do fix that.

@TheOpenInnovator Kindly check now

@Divii2205 You have made a valuable contribution to the project. Congratulations, Your PR has been merged.


Yet another vertical tab/side panel layout suggestion

I think I finally found the best side panel layout look that can solve all frustration from removing horizontal tab layout.
Pros of this layout:

Keeps everything compact and in one place
All opened tabs can be visible all the time. No need to press dedicated button to reveal them.
Quick access list and tabs list can be switched fast and easy between themselves.

Looks sweet.

@yarikv8601 Thank you for sharing your concept for Files UWP, at the moment, there are no plans to implement the design.


New attribute to set card theme

It would look something like
<dev-widget data-username="saurabhdaware" data-theme="pink"></dev-widget>

This will set appropriate header and content colors. We can have themes like dark, pink, blue

data-theme added in v1.1.0


Support non-async

Do you think it would be reasonable to add support for non-async operations to routemeister? I have a huge code base that has literally hundreds of commands/queries that are all synchronous and do not return Tasks. I am looking into moving some of them to async, but probably not all of them, at least for a while.
I would be willing to submit a pull request if non-async is something you would be interested in routemeister supporting. It looks like these items would probably be affected since they reference a Task return type:

MessageHandlerAction class, Invoke method
MessageHandlerInvoker delegate

I haven't had time to look into what exactly need to change. Is there a change that lower parts might be able to change to return object and then the async path could cast to Task? The sync path can that make use of object for void, otherwise it needs two sub paths there...

That's pretty much exactly what I had in mind. Change Task to Object and cast wherever Async is needed. I guess void's would just return nulls to keep it simple. We'd create a non-async dispatcher also.

PR #7 merged and new release is out on NuGet: https://www.nuget.org/packages/Routemeister/2.1.0

BTW: That IlMessageHandlerInvokerFactory code you wrote is pretty brilliant. I had never played with IlGenerator before and figuring out how to handle void methods was tricky but fun! The runtime threw some pretty gnarly error messages lol 😄


simulation train

When I configure the environment variables and run the training
$ cd ~/DRL-robot-navigation/TD3
$ python3 velodyne_td3.py

I encountered the above error. I use gazebo9, ROS is melodic.
I am new to ROS and I wonder if there is a problem with the  input command.
And What should I type to implement the training example in README.md.
Thank you very much.

Does the program not run after encountering the "QObject" issue?
I don't have the access to the system right now, but if I remember correctly, this issue does not impede the training process and you can ignore it. Let me know if the training is not happening or the robot is not moving after just simply ignoring the issue. Then I will try to set up the system again, but it might take some time.

Yes，The robot is moving normally，but the output of training in following figure does not appear.

Do I need to input any other instructions？

No need to do anything. You just need to wait.
Validation happens only after certain amount of steps. After validation is complete, the "Average reward" will also be output to the terminal.
If you'll go through the velodyne_td3.py file you will notice a variable:
eval_freq = 5e3  # After how many steps to perform the evaluation
This is how many steps it will take to perform the validation and subsequently give similar output to the terminal.
You can reduce it to perform validation more often and have the output.

Thank you very much for your guidance. I have similar output.

That's great to hear. I'll close the issue then.


Make Sure we Persist url params

[Title: describe the change in one sentence]
When we change views and there is a namespace filter applied we should persist it in the URL
[ describe the change in 1 - 3 paragraphs ]
The SectionFilterHeader takes care of if there should be a namespace filter to be applied on its initial render
How to use
GO to a namespace filter, select a few namespaces and now switch views and we have the namespace filter in the URL now for all the views that have the namespace filter, which was only for some certain views before

The namespace filter was already being persisted in some views, and not in others. Your patch seems to make it persistent on all, but didn't touch how it was previously being set up in the views that did have it. Can you make sure we only have/need one way of adding these params?

@joaquimrocha fixed this, so we were actually not passing the search prop to the children render of the SidebarItem, that's why it wasn't working for the child sidebar items

fixes #748


Excess spread arguments are not errored

TypeScript Version:  2.6.1
Code
It appears that extra arguments that are spread arguments are always accepted, which can lead to unintentional errors in the code.  For example the following:
declare const foo: (value: string) => string;

foo('bar', 'qat'); // Expected 1 arguments, but got 2.

foo('bar', ...['qat']); // No error

This is related to #4130 but @sandersn suggested a separate issue, as this subset of the larger issue is likely addressable, where as determining if a spread argument might result in longer arguments is difficult, versus cases where it is easily statically identifiable (this case).
Expected behavior:
That an extra spread argument errors.
Actual behavior:
An excess spread argument does not error.

When I tried to fix this, I found the test that explains why it works this way. It's for functions that use arguments:
function mixed(fixed: number) {
    Debug.assert(fixed > 0);
    for (var i = fixed; i < arguments.length; i++) {
        console.log(arguments[i]);
    }
}
mixed(2, 'hello', 'world', 'goodbye', 'goodbye') // ok ... I guess?

I guess this makes sense, but I think the right thing to do is only allow calls like this for functions that use arguments in the body and disallow it for all other calls.

is that in a .js file?

The test is a .ts file; I haven't tracked the comment in the test back to a discussion on github yet. Maybe restricting that usage to javascript would be an acceptable solution too.

The call is an error in TS if you do not have the spread. i.e. mixed(2, 'hello', 'world', 'goodbye', 'goodbye'). the function should have been declred as:
function mixed(fixed: number, ...args: string[]) {
    Debug.assert(fixed > 0);
    for (var i = fixed; i < arguments.length; i++) {
        console.log(arguments[i]);
    }
}

or
function mixed(fixed: number, ...args: string[]);
function mixed(fixed: number) {
 Debug.assert(fixed > 0);
    for (var i = fixed; i < arguments.length; i++) {
        console.log(arguments[i]);
    }
}

Ah, I see. Yes, the argument has to be a spread, which is what @kitsonk actually has in his code base. I mistakenly converted it to individual arguments.
Here's the actual test case from cases/conformance/expressions/functionCalls/callWithSpread2.ts:
declare function normal(s: string): void;
declare numbers: number[];
normal("i", ...numbers);

I think this should be disallowed. The question is whether it should be allowed if this is the definition of normal:
function normal(s: string) {
  console.log(s);
  console.log(arguments[1]);
}

function normal(s: string) {
  console.log(s);
  console.log(arguments[1]);
}

That is exactly the sort of JS bs TypeScript should help us fix as well...  I suspect it will break some user code because if you are porting some code over, and TypeScript didn't force you to change it, you certainly wouldn't fix it...  I guess it is arguable if it should be strict or not, since it would be a breaking change, but it seems like forcing someone to add an argument (or a spread argument) to strongly type their arguments is worth it for the sanity of code.

@kitsonk that’s a good argument. Unfortunately I didn’t record my previous reasoning in the PR #15849. I think it should be fine to make this an error, although I doubt our test suites will catch anything since this has only been legal since May.

Nope, no failures from RWC or user code.

Here's a counter-example that I thought about and then decided should still be illegal:
function f() { return arguments[0] }
declare var ns: number[];
f(...ns)

By analogy with what we allow in Javascript:
function j() { return arguments[0] }
j(1,2,3)

However, if you're using Typescript, or a version of Javascript that supports ... spread arguments, you also have ... rest parameters, and should always write f as function f(...args) { return args[0] }.

Fix is up at #20071


Add -b flag to purge-service-offering command

Correctly removes the experimental flag for this command, which was causing CI failures in #1567.
cc @nmaslarski @williammartin

Waiting for CLI CI to go green before merging.


Vitis_Accel_Examples 2020.2 error

my infomation as follows,
os                  : ubuntu 18.04

platform             : xilinx_u200_xdma_201830_2

xrt                  : xrt_202<IP_ADDRESS>3

vitis/vivado           : 2020.2

Vitis_Accel_Examples  : 2020.2

i make hello_word accl example,
1、 when make all sw_emu/hw_emu, the following warnings are reported:
   WARNING: /opt/Xilinx/Vitis/2020.2/tps/lnx64/jre9.0.4 does not exist.

i see path : /opt/Xilinx/Vitis/2020.2/tps/lnx64/ which has jre11.0.2,no jre9.04，how is this related jre9.04

2、when make test sw_emu/hw_emu, the following warnings are reported:
  CRITICAL WARNING: [HW-EMU 08-0] Unable to find emconfig.json. Using default device "xilinx:pcie-hw-em:7v3:1.0"

  Trying to program device[0]: xilinx:pcie-hw-em:7v3:1.0

this is not program xilinx_u200_xdma_201830_2, and the emconfig.json is under path _x.hw_emu.xilinx_u200_xdma_201830_2,
why not  find emconfig.json

Hi @crizy ,
Can you try to run the design using "run" target.
make run target=sw_emu/hw_emu
Thanks,
Vishnu

Hi @vishnuchebrolu
  make run target=sw_emu/hw_emu  is ok , I'm sorry that I didn't look at the makefile file carefully. I thought it was the same as the previous version， but how to solve the first problem? Although at present, it does not affect the implementation of accelerated design examples


Latest Alpha 32 Update does not build.

Getting error in the build of the latest Alpha 32.
In the Inspector packaging:
｢atl｣: Using<EMAIL_ADDRESS>from typescript
ℹ ｢atl｣: Using tsconfig.json from /Users/Mackey/Desktop/BabylonJS/inspector/tsconfig.json
ℹ ｢atl｣: Checking started in a separate process...
ℹ ｢atl｣: Time: 782ms
[21:53:02] Version: webpack 4.29.6
Built at: 2019-03-05 21:53:02
                              Asset      Size                    Chunks                    Chunk Names
    babylon.inspector.bundle.max.js  2.66 MiB  babylon.inspector.bundle  [emitted]  [big]  babylon.inspector.bundle
babylon.inspector.bundle.max.js.map  2.79 MiB  babylon.inspector.bundle  [emitted]         babylon.inspector.bundle
Entrypoint babylon.inspector.bundle [big] = babylon.inspector.bundle.max.js babylon.inspector.bundle.max.js.map
[21:53:02] Finished 'buildMax' after 14 s
[21:53:02] Starting 'buildAMDDTS'...
[21:53:13] Finished 'buildAMDDTS' after 10 s
[21:53:13] Starting 'appendLoseDTS'...
[21:53:13] Finished 'appendLoseDTS' after 236 μs
[21:53:13] Starting 'processDTS'...
[21:53:13] Finished 'processDTS' after 110 ms
[21:53:13] Finished 'inspector' after 52 s
[21:53:13] Starting 'viewer'...
[21:53:13] Starting 'build'...
[21:53:33] 'build' errored after 20 s
[21:53:33] Error in plugin "webpack-stream"
Message:
    ./src/assets/img.ts
Module not found: Error: Can't resolve 'base64-image-loader' in '/Users/Mackey/Desktop/BabylonJS/Viewer'
resolve 'base64-image-loader' in '/Users/Mackey/Desktop/BabylonJS/Viewer'
  Parsed request is a module
  using description file: /Users/Mackey/Desktop/BabylonJS/Viewer/package.json (relative path: .)
    resolve as module
      /Users/Mackey/Desktop/BabylonJS/Viewer/node_modules doesn't exist or is not a directory
      /Users/Mackey/Desktop/node_modules doesn't exist or is not a directory
      /Users/Mackey/node_modules doesn't exist or is not a directory
      /Users/node_modules doesn't exist or is not a directory
      /node_modules doesn't exist or is not a directory
      looking for modules in /Users/Mackey/Desktop/BabylonJS/node_modules
        using description file: /Users/Mackey/Desktop/BabylonJS/package.json (relative path: ./node_modules)
          using description file: /Users/Mackey/Desktop/BabylonJS/package.json (relative path: ./node_modules/base64-image-loader)
            no extension
              /Users/Mackey/Desktop/BabylonJS/node_modules/base64-image-loader doesn't exist
            .js
              /Users/Mackey/Desktop/BabylonJS/node_modules/base64-image-loader.js doesn't exist
            .json
              /Users/Mackey/Desktop/BabylonJS/node_modules/base64-image-loader.json doesn't exist
            as directory
              /Users/Mackey/Desktop/BabylonJS/node_modules/base64-image-loader doesn't exist

Can you try running npm install in the tools/gulp folder ?
It fails on the viewer step not the inspector as it does not find some of the components in the node_modules folder of the viewer.

I am closing the issue as It does not repro anywhere so it is probably a config issue on your side. I ll carry on answering on the thread but do not want to let others think it is broken :-)


backport: bump boost min

Issue being fixed or feature implemented
See commit
What was done?
How Has This Been Tested?
Breaking Changes
Checklist:
Go over all the following points, and put an x in all the boxes that apply.

[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have added or updated relevant unit/integration/functional/e2e tests
[ ] I have made corresponding changes to the documentation
[x] I have assigned this pull request to a milestone (for repository code-owners and collaborators only)

Hmm... lots of failures in CI.. there must be smth else then. Also, it looks like 24395 caused high CPU usage https://github.com/bitcoin/bitcoin/issues/27586 and was reverted in 27724... so we need that too (or drop 24395 for now) 🙈

let's try 27783 (887241a07d)?


Functional

Hi! I'm just amazed by your work and examples and I'm trying to figure it out how to make your lib work with a functional approach. Is it possible?
I'm also using typescript so if there's a way to add some types. I could help if you need a contributor to do that.

Please be more specific.
Look to parent project if you need TypeScript
https://github.com/surikov/webaudiofont


Disable AppHost Creation

In general this can be considered an optimization, but it also fixes an error that I'm running into where msbuild tries to copy the apphost.exe, but it doesn't exist.

Yeah, there's absolutely no reason we need to be creating a native executable for anything. 👍


remove noise

Dear author, when using the same namespace for jenkins and other deployments, jenkins-sc-config logs get polluted by stuff like:
INFO:sidecar:Working on configmap default/cert-manager-controller
2019-05-09 10:46:10 INFO     Working on configmap default/cert-manager-controller
INFO:sidecar:Working on configmap default/cert-manager-controller
INFO:sidecar:Working on configmap default/cert-manager-controller
2019-05-09 10:46:12 INFO     Working on configmap default/cert-manager-controller
INFO:sidecar:Working on configmap default/ingress-controller-leader-gitlab-nginx
2019-05-09 10:46:13 INFO     Working on configmap default/ingress-controller-leader-gitlab-nginx
INFO:sidecar:Working on configmap default/cert-manager-controller
2019-05-09 10:46:14 INFO     Working on configmap default/cert-manager-controller
INFO:sidecar:Working on configmap default/cert-manager-controller
2019-05-09 10:46:16 INFO     Working on configmap default/cert-manager-controller
INFO:sidecar:Working on configmap default/cert-manager-controller
2019-05-09 10:46:18 INFO     Working on configmap default/cert-manager-controller
INFO:sidecar:Working on configmap default/ingress-controller-leader-gitlab-nginx
2019-05-09 10:46:20 INFO     Working on configmap default/ingress-controller-leader-gitlab-nginx
INFO:sidecar:Working on configmap default/cert-manager-controller

This PR completely remove this (debug?) messages. We could also consider using an env var and setting logging verbosity, if those messages are really needed.
what do you think? TIA, regards

Yes good idea to reduce noise by not info-logging configmaps we won't process.  Perhaps change these lines to .debug, and instead create a .info line within the "if label found = true" conditional.  Ie:
  logger.debug(f'Working on configmap {metadata.namespace}/{metadata.name}')
  if metadata.labels is None:
    continue
  logger.debug(f'Working on configmap {metadata.namespace}/{metadata.name}')
  if label in event['object'].metadata.labels.keys():
    logger.info("Configmap with label found")
    logger.info(f'Working on configmap {metadata.namespace}/{metadata.name}')

This way, can still discover which configmaps are being ignored when troubleshooting, by enabling debug logging.  Make sense?

seems good to me, I've implemented it this way, thanks!

are you in charge of https://hub.docker.com/r/shadwell/k8s-sidecar ? If yes, could you please consider pushing a 0.0.3 so we can update jenkins' helm chart ? thx

Yes.  Docker was playing up on my workstation.  Pls try 0.0.3 that I've just pushed.


cast_dtype_for_dot=False doesn't work on T4 but works fine on CPU & A100

also, realised that cast_dtype_for_dot=True makes things 2-3x slow - need to understand the reason.
Since T4 is stale GPU, I have decided to remove cast_dtype_for_dot argument.

also, realised that cast_dtype_for_dot=True makes things 2-3x slow - need to understand the reason.

this is wrong statement; earlier, slowdown happened because of less num_stages in ffn kernel; it actually helps little to do matmul in fp16


[DDW-197] create grid layout component

This PR adds layout components Grid and GridItem. This abstracts layout into composable, compound components that facilitate a more uniform and reusable layout solution. Enables third party developers using react-polymorph to craft applications with uniformity of layout specs and style more easily with most of the CSS Grid API.

@DominikGuzei
Regarding Grid.Item not being a recognizable property by flow, I was also trying to figure out a solution for this, but obviously didn't. I should have left you a note. I really like the compound component syntax because it saves the trouble of importing two components to get the full flexbox API or full CSS Grid API. It looks nice as well, but that is subjective 😸
If a user is going to bother using these layout components to implement a grid or flexbox, they're probably going to use the FlexItem and GridItem as well. If these two sub components weren't nearly essential for getting the most out of the functionality, I'd say the compound syntax isn't important. That being said, I'd rather just see the code merged now without errors and then I come up with a better solution for keeping them attached as compound components (without flow errors) later. Blocking everything over some syntactic sprinkles isn't smart (compound components are more than that, but we aren't using any of the prop related benefits from them yet).
I think the withTheme helper saves a lot of noise from entering the component files. It's not only wrapping the components in a context consumer and the forwardRef HOC, but also looking to see if the components are being exported in test mode so as not to wrap them in forwardRef for testing purposes. Enzyme does not play well with forwardRef, so this was the best I could come up with after wasting hours trying appease Enzyme's mount method. Were you thinking of pulling the context consumer and forwardRef HOC into each component file, or something else?

@MarcusHurney great work! Looks much better now - let's move the discussion about withTheme helper and flow types to another work stream!


Performance issue for some data handling in MultipartDecoder

When using werkzeug handling file upload, werkzeug use FormDataParser and MultipartDecoder, in here: https://github.com/pallets/werkzeug/blob/edef71c243e1e1396092f7b5f82ddad6c6f766cf/src/werkzeug/sansio/multipart.py#L187 , if for some part of data, the var data_length is always 0, that will always generate a 'werkzeug.sansio.multipart.NeedData', so the source code will run  self.buffer.find(b"--",...) ( https://github.com/pallets/werkzeug/blob/edef71c243e1e1396092f7b5f82ddad6c6f766cf/src/werkzeug/sansio/multipart.py#L182 ) again and again, which will take longer and longer time(I think it is O(n²)), in the end the upload of file will take much longer time than other most of the files.

Generate a file, which will having a b'\r' in a bound of MultipartDecoder.buffer, and all the data after there is no "\r".
Example of this kind of file:
def test52():
    with open("uploadfile.dat","wb") as f:
        def _gen():
            yield b"\r"
            for i in range(30000000):
                yield b"1234567890"
        for i in _gen():
            f.write(i)

if __name__ == '__main__':
    test52()

Then upload this file with werkzeug: werkzeug.formparser.parse_form_data() , it will reproduce the issue

Need to handle file quickly, but actually very slow
Environment:

Python version:3.6.5
Werkzeug version: latest: edef71c243e1e1396092f7b5f82ddad6c6f766cf

There is a workaround, here( https://github.com/pallets/werkzeug/blob/edef71c243e1e1396092f7b5f82ddad6c6f766cf/src/werkzeug/formparser.py#L348 ) ,  buffer_size: int = 64 * 1024, that's too small, to handle several hundrers of MBytes of data, that will run too many times, if this buffer_size can be given by user, for example user give: 16 * 1024 * 1024, that will reduce the time a lot.

@pgjones could you take a look at this?

I think I'll need some more information here. The parser will still consume the buffer whilst looking for the next boundary, so I don't think there is any n^2 growth. I'm also unsure if this applies as the example given is invalid multipart data and hence should result in a failed parse.

Because every time parser search for the next boundary, it need to traverse all the data, the traverse time is decided by the data length, suppose buffer size is n, the traverse time is about to connec with: n+2n+3n+4n+5n... mn = (1+2+3...+m)n = (m * (m + 1) / 2)*n, so it is m^2 growth.

I think #2441 fixes this.


can not dail with multiple directory via multiple gulp instance?

There are some directories in same level.Each of them is a sub-project.I want do that: the developer can choose which sub-projects they want to packaging by them self,and the packaging logic are same in each of them. The command is like:gulp --gulpfile ./package/gulpfile.js --root home+common. The home and common is sub-project's name.The script code at below. But that's not work,what should I do?
/*roots is home+common*/
roots = arr[1].split("+");
const gulpClone = function () {
};
gulpClone.prototype = gulp;
gulpClone.prototype.constructor = gulpClone;
roots.forEach((root)=>{
    let temp = root.trim();
    temp&&doTask(temp,new gulpClone());
})

function doTask(root,gulp) {
let resourceUrl = path.join(appRootDir,"/resource/",root);

gulp.task('default',["clean","head","other","resource"],function () {});
gulp.task("resource",["compressCss","compressJs"],function () {});
gulp.task('compressCss',["cleanResource"],() => {
...
}

Support questions should be directed to StackOverflow.


Updated README.md

Included information and example on communicating data between thread local and callback scopes. This shows how http-parser can be used in a multi-threaded context.

LGTM, except one nit. cc @bnoordhuis because I'm pretty bad at english :(

LGTM

Landed in 483eca7


fix: update settings grammar

What my changes do:

add formatMinutes function

use "minute" when autoSaveInterval is 1
else use "minutes"
Prevents the scenario phrase "1 minutes."

Improve grammar for autoBackupAfterFileChange plugin

turn message into multiline string for easier readability in code

I did think about omitting the interval value if it's set to 1 i.e.:

"Every minute."
"Every x minutes."

But I believe being more explicit with whatever interval value the user has set reinforces the idea that the application has registered their input.

Thanks for your contribution!


Question: How to use conditional requests with httpcache?

I understand that conditional requests / etags are not supported directly, but instead we should use https://github.com/gregjones/httpcache (https://github.com/google/go-github/issues/2625).
Would someone have an example on how to use it? Especially in combination with static token source as shown in the readme. I fail to understand on how I would create a new client with both token support and conditional request support.

The following repo shows an example of using an external transport with this client library: https://github.com/gmlewis/go-httpdebug
Here is the example I'm referring to:
import (
  dbg "github.com/gmlewis/go-httpdebug/httpdebug"
  "github.com/google/go-github/v49/github"
  "golang.org/x/oauth2"
)
...
ctx := context.Background()
ts := oauth2.StaticTokenSource(
	&oauth2.Token{AccessToken: token},
)
tc := &oauth2.Transport{Source: ts, Base: dbg.New()}

client := github.NewClient(&http.Client{Transport: tc})

Now in theory, you could replace the dbg.New() with the transport provided by https://github.com/gregjones/httpcache
Hopefully this is enough to get you up and running.
Either way, please comment back with your success.
Also, feel free to add more information to our README.md and github/doc.go (in a PR) giving a more detailed example for how to do this if you think it will help others in the future.

Never mind. I've used in memory cache. Testing with diskcache right now.

Closing as resolved.

@luebken Did you have success running httpcache to use conditions requests now?

It seems to be caching certain resources and not others.
It's not caching for SCIM API routes here.


Restrict access to staging hubs and imagebuilding-demo hub

Closes https://github.com/2i2c-org/meta/issues/682

Thank you @yuvipanda!!!


[BUG] databricks init script error

Describe the bug
cannot download package in init script
sudo wget -O /databricks/jars/rapids-4-spark_2.12-21.06.0.jar https://repo1.maven.org/maven2/com/nvidia/rapids-4-spark_2.12/21.06.0/rapids-4-spark_2.12-21.06.0.jar
Steps/Code to reproduce bug
try to run
sudo wget -O /databricks/jars/rapids-4-spark_2.12-21.06.0.jar https://repo1.maven.org/maven2/com/nvidia/rapids-4-spark_2.12/21.06.0/rapids-4-spark_2.12-21.06.0.jar
Expected behavior
0.5.0 working fine
https://repo1.maven.org/maven2/com/nvidia/rapids-4-spark_2.12/0.5.0/rapids-4-spark_2.12-0.5.0.jar

We have no yet release 21.06 so its not available in maven yet.  It will be released once we are finished doing testing on it
You can check the download section of our docs for latest released version: https://nvidia.github.io/spark-rapids/docs/download.html

thanks, @tgravescs . I promoted this question since I met problem when reading from delta table, the error message like ' covert struct type to GPU is not supported' under databricks 7.3ML LST
sudo wget -O /databricks/jars/rapids-4-spark_2.12-0.5.0.jar https://repo1.maven.org/maven2/com/nvidia/rapids-4-spark_2.12/0.5.0/rapids-4-spark_2.12-0.5.0.jar
sudo wget -O /databricks/jars/cudf-0.19.2-cuda10-1.jar https://repo1.maven.org/maven2/ai/rapids/cudf/0.19.2/cudf-0.19.2-cuda10-1.jar""", True)
but the parquet file is working fine. May I ask if the delta table would be supported in next release?

You can look at the docs for 21.06 here: https://github.com/NVIDIA/spark-rapids/blob/branch-21.06/docs/supported_ops.md there is a table there that indicates which operations support structs for that release.  So it depends on what operator you were trying to use that it was complaining about.  We should support most structs when reading from parquet (which is what delta table was using underneath), but 0.5 should have supported it as well.   Delta table does other things though as well so perhaps something is going on there.
if you can share the actual output of the explain (--conf spark.rapids.sql.explain=NOT_ON_GPU  or ALL -> see https://nvidia.github.io/spark-rapids/docs/configs.html for more information on that) it may give me more context. I know we have read from delta tables in the past but don't know if we tried structs and perhaps we didn't hit your case.

@tgravescs ,  Thanks for your explain of details. I found the reason. It is caused by reading from a view which is combination of several delta tables. I persisted this view into a parquet file, then everything working fine including reading from delta table.
create view data_pipeline_v as
select js.id as pipeline_id,
      job.id as job_id,
      job.job_name as job_name,
      job.job_type as job_type,
      job.order as job_order,
      job.notebook_path as notebook_path,
      cust.cust_id as cust_id,
      cust.cust_name as cust_name,
      geo.country_time_zone as country_time_zone,
      geo.state_time_zone as state_time_zone,
      param.input_path as input_path,
      param.output_path as output_path,
      param.input_schema as input_schema,
      param.output_schema as output_schema,
      param.variables as variables
      from delta.`/mnt/eus-metadata/job_subscription` js
inner join delta.`/mnt/eus-metadata/job` job on js.job_fk=job.id
inner join delta.`/mnt/eus-metadata/customer` cust on cust.cust_id=js.customer_fk
inner join delta.`/mnt/eus-metadata/geography` geo on geo.id=cust.geography_fk
left join delta.`/mnt/eus-metadata/parameter` param on param.id=job.parameter_fk
where js.active =1

ok, thanks for the update.  If that unblocks you, I'm going to convert this into a task for us to test with a view to see what we don't support.  Please update if further questions.


Fair enough 👍


chore: add instrumentation on all async calls

Mentioned in the Protocol Weekly on 7/25, instrumentation should be added on all async calls.
Things to keep in mind (via Janis):

we need to remove instrumentation from all long-running tasks (in our case, essentially everything that is called T::run or T::run_until_stopped
we also need to remove all events that run under these (so if you have a loop { select!((....)} construct, then there cannot be events in these
a. The reason is that forever spans are completely useless on an observability platforms; in the best case we will see them at the end of a run, in the worst case we will lose them completely because the gRPC payload is too big (because the span contains too many events).
while we want to have #[instrument(skip_all, err)], we don't necessarily want the errors to be emitted under an ERROR target. ERROR is for service-stopping issues, while WARN is for issues that can be handled (for example, through a retry).
a. using this example, this would be #[instrument(err(level = Level::WARN)]

### Tasks
- [x] bridge-withdrawer
- [x] composer
- [x] conductor
- [ ] sequencer
- [x] sequencer-relayer

┆Issue Number: ENG-670

This issue is stale because it has been open 45 days with no activity. Remove stale label or this issue
be closed in 7 days.


shapes: v2: add SHACL shapes for new RML ontology

These shapes covers the RML-Star specification:

rmls:NonAssertedTriplesMap
rmls:StarMap

The generate_shapes.py script combines these shapes into a single shape for SHACL validators 'star.ttl'

@anaigmo We reworked the shapes in Core to have inheritance for things like joinCondition, etc. which are shared among multiple resources. Once merged in Core, I can update them here to match.


Synthesis microarchitecture automatically

After: #154 #155 #156
We need:

[ ] design metrics to make a decision about the microarchitecture and write a meaningful estimate function
[ ] add CLI  argument: --auto-microarchitecture

if --microarchitecture is not presented, start with empty BusNetwork
if --microarchitecture is presented, start with the specified microarchitecture and auto-modify it
if --auto-microarchitecture is not presented - avoid microarchitecture synthesis.

[ ] debug it on example algorithms and add tests.

@ryukzak
I propose to rename --auto-microarchitecture to --auto-uarch.
Also, based on the implementation that was made in #195 , I propose the following behavior:

--auto-uarch is presented with --uarch - then --auto-uarch is ignored (because there should be prototypes specified in config file)
--auto-uarch is presented and --uarch is not - then we start with BusNetwork without PUs and all default prototypes.
(I guess SPI also should be presented in BusNetwork because SPI prototypes disabled because of #194
4.--auto-uarch is not presented - avoid microarchitecture synthesis, start with default BusNetwork.

Therefore, we need to additionally add the loading of the list of prototypes from the configuration file.


feat: add network sampele for clusterSize more than one

Fix #52
Signed-off-by: Abirdcfly<EMAIL_ADDRESS>

Todo：local test and update sample readme


Forward Euler and Cranck Nicolson solvers

This PR fixes forward Euler solvers and also implements a Cranck Nicolson solver.
Forward Euler raises for branched cells (or networks thereof).

Cool! Will have a look on Monday!

Great, thanks!


chore: fetch main branch when running prerelease action

the main branch wasn't present in the action and was failing when attempting to checkout the changelog file

I think this PR came out of running the wrong action (prerelease instead of snapshot)
If we need this, I wonder if it would be better to use the if option to check that its only run for main branch?
Alternatively, we could disable this action for now to prevent misuse until we actually need it.


[Bug]: "@uploadthing/react" has no exported member 'generateComponents' .

What happened?
This
import { generateComponents } from "@uploadthing/react";
fails with

Module '"@uploadthing/react"' has no exported member 'generateComponents'.

i restarted the IED and reinstalled uploadnothing but still get this error
What did you expect to happen?
import success
Version
4.1.3
Reproduction Steps
import { generateReactHelpers } from "@uploadthing/react";
Reproduction Repository
No response
Relevant log output
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Getting this as well. Pretty major issue.

Import path in the docs is incorrect. Import from @uploadthing/react/hooks. I'll update the docs now.

We forgot to cut a release 🤦 v5.0.0 should have the correct export. Sorry for the confusion.


Default amalgamation build should really include HAVE_USLEEP=1

Hey! I've been using the better-sqlite3 module in Mailspring (a cross platform Electron app) for about 6 years and this is the best sqlite adapter out there.
There's just one problem I have been patching with my own fork (and now via a custom amalgamation). Without HAVE_USLEEP=1 at compile time, if sqlite encounters lock contention it tries to aquire the lock every second instead of every 10 milliseconds, assuming that the system clock does not support usleep(usec) and only sleep(seconds). Letting this loose in your application can be super mysterious - it leads to transactions taking a weirdly long time to aquire, random "database is locked" timeouts, etc. In Electron apps it's particularly likely to happen, because each window of the Electron app is it's own NodeJS process. If two application windows try to write to the database at the same time, the second window won't retry for a full second and the query will take 1s+.
I /think/ that every platform that supports NodeJS also supports usleep (I've been safely setting it and shipping Mailspring for Ubuntu 14+ / linux distros, macOS and Windows 10!)
I would absolutely love if it could be part of the blessed library and I think it would likely make other people's apps faster if they haven't realized it needs to be turned on. Thanks for making (and maintaining) a great library!

I tried adding this, but it caused the CI tests to fail due to sleeping for longer than expected. It worked fine on my local machine. I'm not sure why it was so slow in the CI workflow.

Added in https://github.com/WiseLibs/better-sqlite3/commit/6ee3399932c73c0f34d1b2e604d50b44a4e94f6f


Globally install help on Linux

I would like to install help documents on my Linux system globally, rather than per-user. The documentation for Update-Help states that in order to install help to $PSHome, I should use the command Start-Process PowerShell -Verb RunAs in order to run Get-Help as admin. Without elevated privelages, the help documents are installed in the user's ~/.local/share/powershell directory.
This does not work on Linux (and I assume Mac): Start-Process : The parameter '-Verb' is not supported for the cmdlet 'Start-Process' on this edition of PowerShell. Starting powershell with sudo to run as root does not work either--it instead installs help into /root, the root users home directory.
Is there a way to globally install help on Linux? If not, there should be, if so, it should be better documented.
Of course, it's possible I just missed something, but I have checked the help document for Update-Help several times.

I have a similar problem on Mac. At first:

PS /Users/hudgeo> update-help
update-help : Failed to update Help for the module(s) 'Microsoft.PowerShell.Archive, Microsoft.PowerShell.Core, Microsoft.PowerShell.Host, Microsoft.PowerShell.Management, Microsoft.PowerShell.Security, Microsoft.PowerShell.Utility, PackageManagement, PowerShellGet, PSReadLine' with UI culture(s) {en-US} : Access to the path '/usr/local/microsoft/powershell/6.0.2/en-US/Microsoft.PowerShell.Commands.Management.dll-Help.xml' is denied.                                                                   At line:1 char:1
+ update-help
+ ~~~~~~~~~~~
+ CategoryInfo          : InvalidOperation: (:) [Update-Help], Exception
+ FullyQualifiedErrorId : UnknownErrorId,Microsoft.PowerShell.Commands.UpdateHelpCommand

Also tried Start-Process and sudo ("command not found")

@thnk2wn Here's a function you can put in your profile to make Sudo work with Powershell cmdlets and aliases, with sudo !! functioning like in Bash thrown in:
function sudo
{
	if($args[0] -eq '!!')
	{
		sudo $((Get-History ((Get-History).Count))[0].CommandLine)
		return
	}
	. $(which sudo) pwsh -NoProfile -Command ". $PROFILE *> /dev/null; $args"
}

Probably won't help you with Update-Help though.


Compiler highlights plug-in, do note to synchronize the question to ask? More anxious, please help, thank you

I would like to give up the hypothesis in the android program, I would like to highlight the effective entry, to take notes and try and web-side synchronization test, may I ask someone can help me? Tell me how to do it? Thank you very much!

The default build of readium-shared-js includes the Hypothesis plugin, but you can easily deactivate it by commenting this line:
https://github.com/readium/readium-shared-js/blob/62490d18031c6dd675639b442a7b791274bfe7b1/plugins/plugins.cson#L6
...then simply build your own version of readium-shared-js, by following the instructions:
https://github.com/readium/readium-shared-js/blob/develop/README.md#prerequisites
You can of course re-activate the old "highlight" plugin:
https://github.com/readium/readium-shared-js/blob/62490d18031c6dd675639b442a7b791274bfe7b1/plugins/plugins.cson#L3
...but this will only help you create document highlights, you will have to write your own logic for managing annotations, etc.


Mac M1 stopped working

I recently got an M1 Mac, it stopped recognising the chromium even tho i have chronium installed.
the error:
Launching headless Chrome to perform the OpenID Connect dance...
[ERROR] Error: Failed to launch the browser process! spawn /usr/bin/chromium-browser ENOENT
TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md
at onClose (/Users/Steve/destreamer/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:193:20)
at ChildProcess.<anonymous> (/Users/Steve/destreamer/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:185:85)
at ChildProcess.emit (node:events:394:28)
at Process.ChildProcess._handle.onexit (node:internal/child_process:288:12)
at onErrorNT (node:internal/child_process:480:16)
at processTicksAndRejections (node:internal/process/task_queues:83:21)

i have tried changing the path into chrome with following code and rebuild but still no luck
executablePath: '/Applications/Brave Browser.app/Contents/MacOS/Brave Browser',

Plugging in Brave should work, make sure executablePath is exactly what navigating to ()[chrome://version] shows.

My bad, i think you also need to replace puppeteer with puppeteer for M1 Macs. See this other issue which has the solution -
https://github.com/snobu/destreamer/issues/355

Ok so I followed the post solution...
npm uninstall puppeteer; npm i puppeteer-core
npm i; npm run build
Then on these files src/destreamer.ts, src/PuppeteerHelper.ts, and src/TokenCache.ts,  I changed
import puppeteer from 'puppeteer-core'
Then I build again using
npm i; npm run build
But now I have these errors:
up to date, audited 435 packages in 513ms
46 packages are looking for funding
  run npm fund for details
found 0 vulnerabilities

@.*** build
echo Transpiling TypeScript to JavaScript... && node node_modules/typescript/bin/tsc && echo Destreamer was built successfully.

Transpiling TypeScript to JavaScript...
src/PuppeteerHelper.ts:14:26 - error TS2339: Property 'executablePath' does not exist on type 'typeof import("/Users/Steve/destreamer/node_modules/puppeteer-core/lib/types")'.
14         return puppeteer.executablePath();
                            ~~~~~~~~~~~~~~
src/PuppeteerHelper.ts:17:43 - error TS2339: Property 'executablePath' does not exist on type 'typeof import("/Users/Steve/destreamer/node_modules/puppeteer-core/lib/types")'.
17     const browserPath: string = puppeteer.executablePath()
                                             ~~~~~~~~~~~~~~
Found 2 errors.
Any clue how to fix this?
On 28 Jun 2021, 4:20 AM -0700, Adrian Calinescu @.***>, wrote:

My bad, i think you also need to replace puppeteer with puppeteer for M1 Macs. See this other issue which has the solution -
#355
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

It works perfectly on Mac M1.
My steps are below.

Changed puppeteer to puppeteer-core  (https://github.com/snobu/destreamer/issues/355#issuecomment-811245127)
Update codes (https://github.com/snobu/destreamer/issues/355#issuecomment-813587363)
Commented out codes L. 13 to L. 18 in src/PuppeteerHelper.ts and added const browserPath = ''; on L. 19
npm run build
Yay!

I'm sorry for the late reply but life got in the way. Do you still need help?

It would be nice with a pre fixed M1 version 🤷🏼♂

Happy to be gifted an M1 to build and test on. Let it be an Ultra just to make sure we cover that as well :)
But seriously though, if someone with an M1 sends a pull request with a fix, I'll merge it in.

Happy to be gifted an M1 to build and test on. Let it be an Ultra just to make sure we cover that as well :)
But seriously though, if someone with an M1 sends a pull request with a fix, I'll merge it in.

I’m just gonna win the lottery and it will be on it’s way 😉
Would it need to be in the old script or modified to a new separate m1 script?
@hidehiro98 seems to know what he’s doing. Any chances for a pull request?

if ppl come looking for a fix on M1 macs and/or latest macOS see this https://github.com/snobu/destreamer/issues/487#issuecomment-1605586156


mutableUsers is named confusingly

You can't know if "true" means NixOS can mutate users, or if you can do it yourself.
Something like users.declarative would be more clear I think.
@cillianderoiste also said he found the name confusing.

I must admit I find this confusing too.

I was never confused about this, but I see how this can be confusing. :+1: for something like users.declarative.

Note that in either mode NixOS supports declarative user accounts. It's just that in mutableUsers = false, it only has declarative users.

Suggestion: users.onlyDeclarative

I like @bjornfor his suggestion. Totally self-explanatory.

I kind of like @bjornfor name too, too simple english but also needed for clarity.

(triage) I don’t see what is confusing about the term, but if nobody goes forth and submits a PR I’m gonna close.

I like onlyDeclarative too, anybody up for making that the documented default and making mutableUsers an alias?

making mutableUsers an alias?

reminds me, we don’t have a good deprecation scheme yet. I’d be in favor of actually deleting deprecated stuff after a while (that is with the next official release) and keeping aliases to an absolute minimum.


fix(customization): alias cannot access api

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


modals: Remove in class once modal is hidden.

Rapdly clicking a button that shows a modal cause a race condition
in Bootstrap. Specifically, Bootstrap adds an "in" class to a modal
on the "shown" event and removes it on the "hide" event. Frequent clicks
cause the "hide" event to trigger before the "shown" event. Therefore, the
"in" class isn't removed. We use the "in" class to check if a modal is
active in overlays.js
For now, we manually remove it once the modal is hidden.
So, I just noticed that we use Bootstrap 2 which is like super old.
Newer versions of Bootstrap probably handle this better internally.
Look into removing this once it's upgraded.
For instance, Bootstrap 4 handles rapid clicks better (Demo: https://jsfiddle.net/q256fysj/1/) while Bootstrap 2 doesn't do it so well (Demo: https://jsfiddle.net/3et8ab0x/1/).
So, I think upgrading Bootstrap will fix this naturally.
Before
https://user-images.githubusercontent.com/58626718/120934948-2a721d00-c71e-11eb-88c9-f6b488ce8ae1.mp4
After (I am clicking rapidly here)
https://user-images.githubusercontent.com/58626718/120934970-41b10a80-c71e-11eb-9ab8-dbbde6c77fc5.mp4
Similarly
https://user-images.githubusercontent.com/58626718/120935010-6c02c800-c71e-11eb-95a6-a8a80bba0c96.mp4

This looks great, merged, thanks @ganpa3!
I think our medium-term plan is to replace the bootstrap modals with a more modern library built for that goal; I'll be opening issues and posting to #frontend about them over the next couple days.
@aryanshridhar @sahil839 FYI.


Add night sky brightness calculator

This is similar to #27 by @ejeschke, but I'm making a new issue because what I propose here is a larger and probably post-GSoC project.
What really matters for observing is the night-sky brightness in the target direction, not just the moon phase or separation to the moon.
There's models for the contribution from scattered moonlight:

http://labs.adsabs.harvard.edu/adsabsadsabs/abs/1991PASP..103.1033K/
http://labs.adsabs.harvard.edu/adsabsadsabs/abs/2001MNRAS.322..201B/
http://www.eso.org/sci/facilities/eelt/science/drm/tech_data/background/

It would be great to have some night sky brightness calculator implemented in astroplan.
I don't know if there's a really simple model that can be implemented in a day, or if they are all complex.

:+1: to this in principal.
This is a pretty big job to do right, though, because it's highly wavelength-dependent.  For example at CTIO, the sky varies by ~2 mag from the blue to red sides of just the optical, but on the blue end it can easily be 5 mags from new to full moon.
More broadly, it might be useful to make this a part of a full sky brightness calculator that includes both moon and site-specific sky brightness (which would need to be provided/customizable by the user).

I hear that @yoachim has suggestions for how to do this, since he has implemented similar functionality for LSST. Any comments @yoachim?

Did someone say sky brightness model?
Here's the model for LSST: https://github.com/lsst/sims_skybrightness
hHere's a notebook showing it in action:  https://github.com/lsst/sims_skybrightness/blob/master/doc/Sky_Model_demo.ipynb
It's mostly interpolating a set of spectra from the ESO calculator, plus an analytic model I made for twilight.

I guess no-one wants to duplicate this in astroplan, right?
In that case, how about adding a section "related packages" to the astroplan docs and pointing people to the LSST code?

What we really need is for ESO to open source the code behind this web page:
http://www.eso.org/observing/etc/bin/gen/form?INS.MODE=swspectr+INS.NAME=SKYCALC
I'm pretty sure the code was written in a way that it could be modified to other locations (and elevations), but they haven't exposed that on the web API.
It wouldn't be too painful to just use the ESO calculator for a few select pointings and fit some simple functions to the sky brightness for a set of filters.


I need oracle database to connect with CodeIgniter 4

Sir, In Codeigniter 3 there is feature available for connect with oracle database.
Sir, But Codeigniter 4 there is no feature I found to connect with oracle database.
Sir, is there any way to connect with oracle database in Codeigniter 4? or there is no feature to connect?

See #2487

The open PR is enough to track the Oracle requirement. No need to keep this open.


Screen/Monitor names not being shown in the screen: dropdown menu

Plugin Name: Windows-Action: Move Window To New Monitor/Screen
Stream Deck Model: Stream Deck XL
Description of Problem:  I was using Windows Mover for a while, but last week, when trying to use the keys (Which I used to move windows to different screens or sections of the screens) I started getting a ⚠
After reading the trouble shooting site, I noticed that the screens are not being displayed in the drop down menu of the plugin, while troubleshooting I tried other alternatives
WIndows-Action being one of them, but the same problem persisted, I noticed that in both plugins the drop down menu for selecting the main screen wouldn't show my screen names,

(the dropdown arrow has been pressed in that screencap)
Troubleshooting Done:
-Installing and re-installing plugins (both of them)
-Installing and re-installing stream deck
-Installing and re-installing/updating Nvidia Drivers
-I read on the bar raider troubleshooting that a software called "team Viewer" could cause that, I make sure I don't have that installed
Other than that I found two reddit posts with that issue
https://www.reddit.com/r/elgato/comments/1euaaeu/streamdeck_barraider_windows_mover/
and I made a different one
https://www.reddit.com/r/elgato/comments/1g3tk9i/stream_deck_plugins_not_detecting_screen_names/
(Thanks again for answering there)
I know there was a windows updated after I came back that week, alongside some things I installed,
Windows 10 Home, version:22H2  Build: 19045.5011
Other than that, I ran youtube music
and I think that update and trying that software are the only things that changed from when it worked and when I noticed it stopped working

Cool! I'll take a this weekend and see what I can find.
Can I also get the monitors you are using? The product name with they year, should be enough. Usually this can be found on the back of the monitors :) !

Absolutely:
•Monitors:
VG248QG Version VG248QG August 2020 (Main display)
VG245       Version VG245HE December 2018
VG245       Version VG245H   January 2019
I have a TV connected as well
Sony XBR-55X81CH  September 2021
and a drawing tablet
XP-PEN  22 plus (MD-220FH)
which I usually only have either the TV or the drawing tablet active, never both since my GPU only allows for 4 simultaneous displays
(When I have the drawing tablet I have it in Duplicate mode, while the TV is in the Extend mode when pressing Windows+P)
•Stream Deck:  6.7.3 (21005)

@Reberebe Hey! Sorry about the long wait, but I found some time to try to debug your issue today.
So after running this on a Windows 10 Machine with the same verison, I did see that an update some Window's DLL logic might have been causing the plugin to silently crash. I updated this, and everyone was working fine. Before I push this to production, I want to ensure this will fix your issue.
Please follow the following steps:

Complete clear you computer of your current Window Actions plugin:

[ ] Close and exit out the StreamDeck app completely (Force quit in the bottom mini toolbar as well)
[ ] Open up Task Manager.
[ ] In Task Manager please FORCE QUIT a program called run.exe. It should have floppy disk icon next to it
[ ] Open up File Explorer, and in the search bar, write the following command
%APPDATA%/Elgato/StreamDeck/Plugins. Find 'com.arkyasmal.windowactions.sdPlugin' and completely delete the directory
This is a video of me going through this process:

Install the new release file

[ ] Download the following new testing release file. Don't worry, downloading this release from here will not stop the auto-updates from Elgato. You can download it by clicking the link above, and clicking on the three dots on the top right.

Try to find your windows through the dropdown again.

@Reberebe I'll be closing the issue because 4.2.1 is now on the Marketplace, and includes the fix :) ! If you encounter the same bug, feel free to re-open the issue


Lost Head Tracking after setting OSVR in Direct Mode (with steamVR)

Hello,
I've been looking to setup OSVR HDK 1.4 for Elite Dangerous. It was impossible to make it work using a combination of driver versions for the different components (including the last up to date) in extended mode. So I switched to Direct mode and... Tadaaaaaaa! Could have a clean screen on my device after launching E:D... But I realized that I have lost the head tracking when i wanted to enjoy it.
I tried to troubleshoot using the tracking tool provided with OSVR SDK but still didn't figure it out (restarted several times both HDK and computer).
Must also notice than Steam compositor is still displaying a red screen of death and steamVR is set to status "Not Ready"...

Same issue in Direct Mode, I loose the head tracking, then the USB connection.

I have issues with this as well, but I noticed mine were intermittent.  I think it's not specifically head tracking that's dying, but the USB connection as @demonixis pointed out. I have other USB devices connected that die as well (in particular my mouse just stops working and I have to re-plug it), so maybe it's something to do with USB bandwidth or some other conflict.

@djdevin which firmware version are you using for the OSVR headset? Some of the newer versions have partially or completely solved this issue

@Ay0w if you're getting a red screen of death, try adjusting the resolution in Display properties — switch from 1920x1080 to 1080x1920 or vice-versa, and see what happens. The autodetection code for resolution and specifically rotation is not quite perfect yet.

@VRguy I use the latest version 1.92

@d235j Ok i will try swapping between resolutions and give a feedback.
@djdevin I will double check that. But if i remember correctly it seems to me that the green led on the camera was green :) which normally is not the case if the USB connection is dead, and on OSVR server logs i couldn't see anything particular mentioning a "not found" camera. But thank you for your input. I'm gonna use the weekend to perform a clean re-installing of the latest drivers/runtime and test all that...


Flickering/App stays black with compose >0.3.1

Hi,
I am  experiencing a weird issue with compose 0.3.1 on Windows 10.
When I build any app, the app is either flickering or completely black. The same behavior could be observed with compose 0.4.0-build168.

This is also true for the widgetsgallery and imageviewer examples, as well as for my own app.
As soon as reverting back to 0.3.0 and doing a clean rebuild, everything works again.
Unfortunately I cannot provide more information at the moment, because there really is no difference other than the version, but I can provide more infos upon request.
Best
Tobi

Very hard to say anything without reproducer.

I think this is the same problem like #413. I have the same problem with Windows 10.
When I do the following there is no flickering or black screen:
gradlew -stop
set SKIKO_RENDER_API=SOFTWARE
gradlew run

Will set SKIKO_RENDER_API=OPENGL work for you?

OPENGL is also working.

Very hard to say anything without reproducer.

Yeah unfortunately I have no idea what causes the issue other than the version.

I think this is the same problem like #413. I have the same problem with Windows 10.
When I do the following there is no flickering or black screen:
gradlew -stop
set SKIKO_RENDER_API=SOFTWARE
gradlew run

I can try this once I have time. Will take a couple of days though.

Will set SKIKO_RENDER_API=OPENGL work for you?

Will try this as well.

Could you please give your PC specification?
OS version: ?
Graphics card: ?
Graphics card driver version: ?

Notebook Asus ROG
Windows 10 Version 2004
Graphic Cards:

Intel HD Graphics 530 - driver version <IP_ADDRESS>50
Nvidia GeForce GTX 960M - driver version <IP_ADDRESS>40

Could you please check if the example from skiko works?
To build skiko you need to run in terminal ./gradlew publishToMavenLocal from skiko/skiko directory.
To run the example (rendering clocks) you need to run in terminal ./gradlew run from skiko/samples/SkijaInjectSample directory.
For more info on how to build skiko, please read the manual on the skiko github repository.

I guess I have the same problem. The project is almost blank. Approximately, a black screen appears in every 4 to 9 executions of the project; it doesn't have a flickering problem though.

Kotlin 1.4.31
Compose 0.4.0-build173
Windows 10
Asus ROG Laptop
Nvidia GeForce GTX 960M

Sorry for the late response, my graphics adapters are

Intel HD Graphics 4600 - driver version <IP_ADDRESS>58
NVIDIA Quadro K2100M - driver version <IP_ADDRESS>91

set SKIKO_RENDER_API=SOFTWARE works
set SKIKO_RENDER_API=opengl does not work
As far as I have read you already have enough information to work on this? If not let me know and I can also try the stuff with the skiko examples.

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


pypy support

there's a few test failures with pypy, need to dig and resolve and add to .travis builds

so the pypy test failures all appear to be wrt mocking datetime for the offhours tests, and one schema error check failure (total 9)


Shadow endpoints navigation within same route

Describe the bug
How can we navigate if route component and endpoint won't change?
Currently its not work as expected.
If we have say:
/example/[...rest].js
/example/[...rest].svelte
And try to use links on page like:
href="/example", href="/example/1", href="example/2" — navigation between them won't work (page not updates, only address bar changes)
Reproduction
https://stackblitz.com/edit/sveltejs-kit-template-default-x92deg?devtoolsheight=33&file=src/routes/example/[...rest].js
Logs
No response
System Info
kit next 260

Severity
serious, but I can work around it
Additional Information
No response

but I can work around it

@livehtml I've run into the same issue. Would you mind sharing your workaround?

@ambiguous48 sure:
export const load = async ({ params, props }) => {
    if (params.rest) '';
    return { props }
};

Just highlight needed params to watch it in the load function and it works as expected.
But I think it's more like a 'hack' other than right way.

I've tried your workaround and it doesn't work for searchParams as far as I can tell.
In my case I'm using url.searchParams (not params) and I can't seem to get the endpoint to pick up changes in the url.searchParams after navigating with goto.
After a manual refresh, the first time calling goto works as expected. Then, the url continues to change as expected, the load function is able to pick up the changes, but not the endpoint.

Noticed the same issue with both:

search params, e.g. navigating from /movies to /movies?q=foo using goto()
dynamic params, e.g. navigating from /movies/1 to /movies/2 using a regular link

I was testing this and as it turns out prefetching works for those routes without any issue, but the actual navigation doesn't, @benmccann @bluwy  as far as I can see, it looks like the code that checks is the route the same as previous is causing this, I'm trying to fix it, but I didn't succeeded yet. if I do, I'll push PR


Error check for invalid TDS login request

Issues Resolved
BABEL-5214
Authored-by: Kuntal Ghosh<EMAIL_ADDRESS>Signed-off-by: Kuntal Ghosh<EMAIL_ADDRESS>Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is under the terms of the Apache 2.0 and PostgreSQL licenses, and grant any person obtaining a copy of the contribution permission to relicense all or a portion of my contribution to the PostgreSQL License solely to contribute all or a portion of my contribution to the PostgreSQL open source project.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>4
Details

1 of 2 (50.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 73.493%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

contrib/babelfishpg_tds/src/backend/tds/tdslogin.c
1
2
50.0%

Totals

Change from base Build<PHONE_NUMBER>7:
0.0%

Covered Lines:
42557

Relevant Lines:
57906

💛  - Coveralls


Setting up basic linting

This sets up basic, repo-wide linting for Scss, JS, Twig, and Shell Scripts. You can run them all with npm run lint. There's more to talk about and do, like:

How do we go about resolving the mountain of warnings?
How do we feel about running these with --fix?
Setting up linting that happens while build tools are running.

Drupal devs use linting as well, they could use this.
Let's make sure that they only get lint warnings for there code, not the bolt deps.

How to handle linting only recently changed files
Do we want Drupal devs to be able to override, extend, or disable those rules?
Adding this to Travis checks (which I have not done yet)

Can we kill off the .Xeslintignore and .Xeslintrc.json files instead of just renaming?

@EvanLovely this'll be good to go from me once ^ is done


subprocess.call and mlflow.log_artifact checks inconsistent in linter

Describe the bug

 f'subprocess.call([\'conda\', \'env\', \'export\', \'--name\', \'{self.project_slug_no_hyphen}\'], stdout=conda_env_filehandler)',
 f'mlflow.log_artifact(f\'{{reports_output_dir}}/{self.project_slug_no_hyphen}_conda_environment.yml\', artifact_path=\'reports\')'

Those two linting functions caused the template create WFs (and sometimes even local) to fail
Expected behavior

They should pass. We should discuss why they fail and how to fix!
So currently they are outcommented!

@Emiller88 the linter should for all templates just check that these methods are called in the templates. Ideally you just need to add those two lines to the linter checks.
I won't explain the original issue here since I just expect it to work :) If it still doesn't I will reassign @Imipenem and me.


Move embedded files outside the cloud init yaml

Enables us to pass in the gzip/base64 encoded version of the files into cloud init yaml

/retest

/lgtm


style: add the basic style structure

Description

Type of change

[x] New feature (non-breaking change which adds functionality)
[x] Refactor ( rewrite or restructure code)
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas

Data Results

none

Additional Info

none

this pr is merged to the https://github.com/rayanfer32/nexus-market-cap/pull/12. Hence closing this


Layout defaults to 100% regardless of previous size

The last couple of weeks the layout has defaulted to 100% size when loading the game for the first time each day.
Unsure if this is a bug or a cache issue on my individual setup.

Is this only affecting your zoom though - and not any other settings? This is the only report I've had of this and if it was an issue with your Chromium LocalStorage then it should affect all settings and not just scale.

Only affects the zoom from what I have seen, but I only use it for the visual indicator for necromancy so no audio or other styles. I can give it an uninstall and reinstall later today to see if that makes a difference and report back.
I have also tried both exiting Alt1 when closing RS, and leaving it open. Usually use at 160% zoom, but have to do a + and - to make it adjust to the correct size again.


Check Beta Database to Confirm that the Client Id used by ecmps-ui to call camd-services is present

(identified as part of issue in #6439 )

missing ecmps-ui client_config record has been added on beta database.


CS:GO IP ERROR

Hi,
The server has 2 ip.
1 : <IP_ADDRESS>
2 : <IP_ADDRESS>
http://i.epvpimg.com/xVh7eab.png
cs works at first ip address. But the second ip address does not enter the game
http://i.epvpimg.com/D83caab.png
http://i.epvpimg.com/5WVGdab.png
start command : ./srcds_run -game {{SRCDS_GAME}} -usercon +ip <IP_ADDRESS> -port  ......    causing the fault
start command : ./srcds_run -game {{SRCDS_GAME}} -usercon -port  ...... no ip command. The server does not receive the address <IP_ADDRESS>. The server receives the address <IP_ADDRESS>.
This error is only in cs game.How can I solve it.

User is being helped at https://forums.pterodactyl.io/topic/109-csgo-server-error/#comment-288


Error reading file from S3 bucket with "Transport endpoint is not connected"

Mountpoint for Amazon S3 version
1.10.0
AWS Region
us-east-1
Describe the running environment
Running Debian bookworm on a t2.nano ec2 instance in us-east-1.
Mountpoint options
mount-s3 --debug --log-directory <directory> --read-only <bucket> <directory>

(Normally it runs without the '--debug' and '--log-directory' but in #630 I was asked to run with these options. The error happens in either case.)

What happened?
$ cp
cp: error reading '': Transport endpoint is not connected
cp: failed to close '': Transport endpoint is not connected
$ sudo dmesg -T | egrep -i 'Out of memory'
[Mon Oct 28 20:46:38 2024] Out of memory: Killed process 3470 (mount-s3) total-vm:925588kB, anon-rss:282932kB, file-rss:0kB, shmem-rss:0kB, UID:33 pgtables:752kB oom_score_adj:0
Relevant log output
I'll attach a file because it's large.

Log output attached.
mountpoint-s3-2024-10-28T20-44-13Z.aQxxIO.log

Hey! Thanks for opening this issue. I can see that you're using t2.nano instance, which has 512MiB of RAM. This explains the OOM as currently Mountpoint enforces the minimum memory target of 512MiB which allows MP to consume the entire RAM.
We'll continue looking into it and will provide updates here when we'll have them.


HTTPS problems

I just want to note for anyone who can stuck on problem with SNIMissingWarning messages like this:
/usr/local/lib/python2.7/dist-packages/requests/packages/urllib3/util/ssl_.py:315: SNIMissingWarning: An HTTPS request has been made, but the SNI (Subject Name Indication) extension to TLS is not available on this platform. ... etc.
I've solved this with:
pip install ndg-httpsclient
pip install pyasn1
additionally you can try also (but not needed in my case):
pip install urllib3
pip install pyopenssl
Cheers

Thanks for the note. Your system must have a strange SSL library, if it can't support SNI, but it's not unheard of. Glad you found a workaround.


RFC: Move mcugmr functionality as internal Zephyr service

Origin
Zephyr port of mcumgr: https://github.com/zephyrproject-rtos/mcumgr
Purpose
Currently used fork is, snapshot updated, copy of https://github.com/apache/mynewt-mcumgr that relies on modified fork of TinyCBOR (https://github.com/zephyrproject-rtos/tinycbor) , taken from https://github.com/apache/mynewt-core/tree/master/encoding/tinycbor.
Mcumgr is missing some features, for example "image" number parsing that allows to select image which will be uploaded, has some logic that does not suit Zephyr hardcoded in common code, or written in a way that does not allow Zephyr to easily extend it's functionalities.
Ownership of mcumgr will allow Zephyr to provide required, or Zephyr specific, features in more system optimized and development process efficient way; additionally an implementation of client-side library may be considered that may benefit many projects, by making it easier to update one device from another.
Additionally to above the mcumgr uses "non-standard" (https://github.com/intel/tinycbor) version of TinyCBOR, which means that there are possible two, incompatible, sources of changes to TinyCBOR that may collide, and may force us to basically implement any changes by hand, making the Zephyr the third possible source of changes; although there have not been may updates lately to both forks, the risk is there.
Moving the mcumgr into the Zephyr code base could enable switch to the CDDL-gen (https://github.com/NordicSemiconductor/cddl-gen)  CBOR API and codec generator, a move similar to done by the mcuboot (https://github.com/mcu-tools/mcuboot/pull/997); the API of the project is quite similar to TinyCBOR, but it also allows to auto-generate coding-decoding functions for structures; the project is actively maintained.
Mode of integration
The mcumgr is currently a module of zephyr (modules/lib/mcumgr) and its integration would require moving it to zephyr/subsys/mgmt/mcumgr/.
Then the work on optimizing the code for Zephyr may start.
Afterwards a switch to CDDL and implementation of client side library may be performed.
Dependencies
Currently the mcumgr depends on TinyCBOR fork within Zephyr modules (https://github.com/zephyrproject-rtos/tinycbor),
but it is already there anyway.
License
Current license of mcumgr source code in modules/lib/mcumgr/, and in https://github.com/apache/mynewt-mcumgr, is http://www.apache.org/licenses/LICENSE-2.0

FYI @carlescufi @nvlsianpu @oyvindronningstad @nandojve @mniestroj

+1 for this change.

+1.

+1

Has there been any thought of just forking mcumgr completely and maintaining it under zephyr? Such that it can still potentially be used by other projects outside of Zephyr and imported into Zephyr by west?

Is there any chances the changes you want to make (remove some hard-coded logic from common code, change to CDDL-gen, etc ) would be accepted upstream ?
I do see the advantage to move mcumgr to an internal Zephyr service but that also means than any features added to upstream mcumgr would be quite hard to merge back.
I'm also wondering about the compatibility with mcumgr-cli do you plan to have an internal fork of it as well ?

Is there any chances the changes you want to make (remove some hard-coded logic from common code, change to CDDL-gen, etc ) would be accepted upstream ?

I don't know. We may try to push them there, but lack of acceptance upstream will not block us here.

I do see the advantage to move mcumgr to an internal Zephyr service but that also means than any features added to upstream mcumgr would be quite hard to merge back.

Yes, they will have to be ported. Note that it may be easier for us to bring things here or reimplement as we will have full control.

I'm also wondering about the compatibility with mcumgr-cli do you plan to have an internal fork of it as well ?

No, rather not. The current feature set of mcumgr-cli will keep working; bringing new features, added to Zephyr, to the mcumgr-cli will depend on the person that implements them.
We will probably rewrite the mcumgr to Python, as it is more known and easier to maintain than go; it should also allow us higher level of protocol instrumentation and black-box testing of specific features. But the work has not yet been started, so for now we rely on mcumgr-cli.


refactor(biblio): update citar config

Remove outdated config for org-roam.
Set org-cite-bibliography to citar-bibliography

Sigh ... need to fix the git.

you don't have to close pull requests to fix the git, you can just force push the branch once you've got it working.

I know; but I screwed it up more than I knew how to fix.


Note to Taras:

GitHub

This is the job platform. Our root URL is here: https://github.com/chassis-app
Repositories
All projects are in a single / multiple repositories. The readme.md should highlight the important facts and gives intro to each repo, if not perhaps the repo is just started and pending to update
Issues
Issues in our team has 2 uses. Tasks will be spec out as issues. If there's any bug/issues that other teammates found, they can also file them as issues.
Pay attention to issue labels, the lifecycle of a task is all controlled by labels

label
meaning

drafting spec
Project Lead is still working on the spec. But please feel free to discuss if you have an idea! This is a task that you can soon work on.

ready to be worked on
This is a task with complete spec and scope, that is suitable for any teammate to pick up.

work in progress
After you picked up a task from the list, please 1. Assign task to yourself; 2. change to this label

review required
When you finished your work, please change to this label + create a PR

help wanted
If you work on a task and face some issues, want someone's attention, please add this label

high priority
This is an urgent task / issue, please pay attention to this first

question
This is a discussion and not yet turned into a task

required changes
Some work maybe going in wrong direction, need the assigned dev to check and review

Branch
When you start a new task, it should be in a Github issue.  If not you should create a new task.
The new branch should be named {taskid}_{task name}
E.g. A task #123 [Component] Create a new input box, you can name the branch 123_new_input_box
Pull Request
Once you completed the task, you can create a Pull Request.  It:

Announce that you think your work is done
Ask for project manager to review
Run test on your new codes and make sure they are all ok

To create a PR, please note:

You should link the PR with the tasks you worked on, so task status will auto upate when PR status change.
Asking for a reviewer is optional, project manager / team leads should be responsible to check PRs regularly
WHen creating a PR, you should already tested locally and make sure all tests passed.

@Risk-taker0501 above is for your information as it's your first time picking up tasks.  This applies to all current and future projects.


Added Bmp, Farbfeld and Ico formats

Extend Support for More Image Types #14

Awesome! Thank you for the contribution :) Merging it 🚀


add ABTR SAM model

This is a demonstration SAM model for the Advanced Burner Test Reactor (ABTR) conceptual design. It includes the recent SAM capability enhancements of structure thermal expansion and reactivity feedback modeling. Both the steady state and an unprotected loss-of-flow (ULOF) accident are simulated within the system models. Case setups and SAM results are discussed in the documentation.

The tabs are removed in the input files
There should be one commit now based on the latest devel branch

Still failing because of tabs
Btw do you have a paper we can cite for this?

Thanks for the heads-up, @GiudGiud. It turns out there are still some tabs in the bib file when I inserted the BitTex entry from Mendeley to the bib file. I have removed the tabs. Regarding the publications about this specific SAM model, there is only one Argonne report:
Hu, G., Zhang, G., & Hu, R. (2019). Reactivity Feedback Modeling in SAM. https://doi.org/10.2172/1499041

Somehow it still fails. I have no clue here. Please help if you could have more information. Thanks.

Job VTB Documentation on 876982c wanted to post the following:
View the site here
This comment will be updated on new commits.

looks like the results generated on my machine with latest SAM from INL repo dont match the ones generated by civet

Hi Guillaume, what is the SAM version on civet? Could you please more information on the results inconsistency so I can work with the SAM team to get it resolved? Thanks a lot.

last time it tested it was
data/civet0/virtual_test_bed/sfr/abtr.steady: SAM Version: derived from v<IP_ADDRESS>, git commit 2f547f17 on 2022-06-09

Sorry about not mentioning it the first time, but what is the latest version of SAM from the INL repo? I only ran the model with the SAM version (v<IP_ADDRESS>-843-g5383714) on ANL cluster.


examples/qm9/test_qm9.sh: swap parameter position to correctly recognize GPU#0

This PR will fix #272

Codecov Report

Merging #273 into master will decrease coverage by 6.89%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master     #273     +/-   ##
=========================================
- Coverage   89.13%   82.24%   -6.9%
=========================================
  Files         116      116
  Lines        5834     5834
=========================================
- Hits         5200     4798    -402
- Misses        634     1036    +402

@mihaimorariu Could you review and let me know your opinion?
This is a matter of where to fix.
test_qm9.sh and evaluate_own_dataset.sh receives argument in order epoch gpu but other shell script receives gpu at first.
This makes the below test_example.sh wrong.
https://github.com/pfnet-research/chainer-chemistry/blob/master/examples/test_examples.sh
So

Option 1: fix test_qm9.sh and evaluate_own_dataset.sh to receive argument in order gpu, epoch
Option 2: fix test_examples.sh to pass argument in correct order epoch gpu for test_qm9.sh execution.

I think Option 1 may be easier to understand for users. What do you think?


About naming convention, what's the meaning of those alphanum? a0, a1, p5, p6, p8....

I try to read your code, those names seems strange to me, a0_xxx, a1_xxx, p5_xxx, p6_xxx, p8_xxx....

it is not for people to read, but for machine to read.


Add a few more clarifications to .mailmap

This removes a few more duplicates when generating a list of contributors.

@swift-ci Please smoke test

@jrose-apple Thanks!  I picked up a few more of those in this round…

@swift-ci Please smoke test


Checkbox Render Logic Fix

Description
Modified the checkbox logic to check for a boolean, if true will add checked=checked to the checkbox.
Additionally this sets the value of the checkbox to true, to be read in during parsing.
Correct setup still includes setting any boolean values in .orig.tfvars.json files to false.   Current parser logic would not be able to see a missing value (checkbox values are simply not included in the post/get request.
Issue reference
The issue this PR will close: #213
Checklist
Please make sure you've  completed the relevant tasks for this PR, out of the following list:

[X] Code compiles or validates correctly
[X] BASH scripts have been validated using shellcheck
[X] All tests pass (manual and automated)
[X] The documentation is updated to cover any new or changed features
[X] Markdown files have been linted using the recommended linter. (See .vscode/extensions.json.)
[X] Relevant issues are linked to this PR

Does the trick 👍

Just confirming: there are currently no checkboxes in the UI that default to checked, correct?
The code deploys the UI and checkboxes appear to function normally.

Yes that's correct.  For testing I flipped them to ensure it worked, and then flipped them back.

Just confirming: there are currently no checkboxes in the UI that default to checked, correct?
The code deploys the UI and checkboxes appear to function normally.

The create_bastion_jumpbox value defaults to true: https://github.com/Azure/missionlz/blob/main/src/core/saca-hub/saca-hub.front.json#L153-L159

Just confirming: there are currently no checkboxes in the UI that default to checked, correct?
The code deploys the UI and checkboxes appear to function normally.

The create_bastion_jumpbox value defaults to true: https://github.com/Azure/missionlz/blob/main/src/core/saca-hub/saca-hub.front.json#L153-L159 -- but, you'd have had to merged latest into this branch to see that value

Confirmed, I do see it now that it's merged to main. Thank you!


Add option to limit amount of enemy health

It'd be nice if you could add a slider from 1-20, for example, of shown hp bars

I'll move it to suggestions


docs: update keycloak server url in operator docs and examples

Default Keycloak server URL is no longer /auth (see https://github.com/Apicurio/apicurio-registry/issues/3315)
Clean up branding

@jsenko Can you review/merge this one when you get a chance, thanks!
Keycloak v17 removed /auth from default context path, so this is no longer required.


Add Snapchat Clone

Project title
Snapchat clone
Project Description
It's just a UI of Snapchat
Stack:
And in order to tick the check box just put x inside them for example - [x] like this. Please delete options that are not relevant.

[x] Html
[x] CSS

/assign


Add Attributes#{removed,removedAll,-,--}

@NthPortal should we merge this one?

@iRevive sorry, been sick recently. I'll squash and merge.
... also sorry for not reviewing any of your PRs recently

@iRevive sorry, been sick recently. I'll squash and merge.
... also sorry for not reviewing any of your PRs recently

no worries, get well!


Remove ubuntu1604 from presubmit.yml

Ubuntu 16.04 is end-of-life, we're going to remove it from Bazel CI.
If you like you can add testing on ubuntu2004 platform which we also support.

Friendly ping. This config file is used to test your project on Bazel's CI: https://buildkite.com/bazel/cartographer and without the changes it will soon break.
If you are no longer interested in having your project tested on our CI, that's also fine, please just let me know.

@philwo I'd be happy to merge, but would need you to please sign off the commit. The easiest way is to use git commit --amend --no-edit --signoff. See https://github.com/cartographer-project/cartographer/blob/master/CONTRIBUTING.md for details. Thanks!


[WIP] Webpack and TypeScript refactoring

Work in progress for #732

[x] Add Webpack && Typescript configuration
[x] Refactor JS files to TS files
[ ] Add types on every variable
[ ] Fix movable plugin
[ ] Demo app should be available through rawgit
[ ] Bring back bower.json
[ ] Update contributing docs with new workflow
[ ] Add hot module reload
[ ] Make scripts build both minified and non-minified assets

To test this branch, run yarn dev (or npm run dev).

Hey @Schweigi ! Could you give this branch a test on the demo app ?

Demo app available at http://rawgit.com/angular-gantt/angular-gantt/2.0.x/demo/dist/index.html

@Toilal will test the demo app. nice work!

@Toilal Tested each feature of the Demo app. It works great. There are two small issues regarding custom sorting of sub-rows in the tree view and "disabling dependencies" still shows the dependency endpoints when hovering with the mouse over a task - but I think both issues are unrelated to your Demo changes.

Btw. used Safari (10.1)

Thanks for running some tests @Schweigi. It seems both issue you've noticed are also here on master branch.

Hi, can you release the version for Angular 2?
thank you very much

It's not planned, unless you want to pay for this.

@Toilal what do you mean by 'it is not planned'? Is the the whole point of this WIP is to transfer codebase from AngularJs to Angular?

This pull request is written to provide a TypeScript/Webpack based version of angular-gantt, but it's still written for AngularJS and heavily relies on AngularJS API (directives, $templatecache, $scope ...)
Of course, it's a good step to go for Angular, but there's still much work to really perform the migration.
I'm currently working with VueJS on some projects, and don't use Angular at all, so there's more chance to see a port of this component to VueJS than to Angular.
There's so much things that are written the AngularJS way in this project and that may cause issues in younger frameworks (Vue, React, Angular ...), that I think I need to rewrite many parts from scratch to handle them.
It would be great to implement this module for multiple frameworks, including Angular, but i'm not sure i'll be able to share much code between frameworks implementations. And I don't have much spare time to support everything, so I think i'll focus on VueJS
But I'm still opened for contribution to migrate in the other frameworks.

@Toilal Thanks, now I understand.
I was really confused by webpack and typescript in the name to such a point that I was thinking that this PR is about upgrading to angular 2/4. Judging from the code there are 5k lines of src/core and 10k lines of 'src'... quite large to migrate.

It's now the default develop branch.


monitor -- Traffic Overview

What is the purpose of the change
XXXXX
Brief changelog
XX
Verifying this change
XXXX
Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[ ] Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist.
[ ] Run `mvn clean compile --batch-mode -DskipTests=false -Dcheckstyle.skip=false -Drat.skip=false -Dmaven.javadoc.skip=true to make sure basic checks pass.

Codecov Report

Merging #1047 (09ed4cd) into refactor-with-go (8d4b93e) will decrease coverage by 2.46%.
The diff coverage is 0.00%.

@@                 Coverage Diff                  @@
##           refactor-with-go    #1047      +/-   ##
====================================================
- Coverage             64.29%   61.83%   -2.46%
====================================================
  Files                    24       25       +1
  Lines                  1840     1905      +65
====================================================
- Hits                   1183     1178       -5
- Misses                  578      647      +69
- Partials                 79       80       +1

Impacted Files
Coverage Δ

pkg/admin/services/prometheus_service_impl.go
0.00% <0.00%> (ø)

... and 2 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Update toleration for k8s control-plane nodes

This MR updates the taints tolerated by the agent's pods to enable scheduling on control plane nodes in Kubernetes v1.24+

Mind adding a changelog?


Fix documentation for UUID_FORMAT setting

Looks like a simple copy-n-paste error ;)
Keeping it consistent with code and tests in:

https://github.com/snok/django-guid/blob/main/django_guid/config.py#L67
https://github.com/snok/django-guid/blob/main/django_guid/config.py#L86-L91
https://github.com/snok/django-guid/blob/main/tests/functional/test_sync_middleware.py#L11-L24
https://github.com/snok/django-guid/blob/main/tests/functional/test_sync_middleware.py#L45-L55
https://github.com/snok/django-guid/blob/main/tests/functional/test_sync_middleware.py#L73-L83
https://github.com/snok/django-guid/blob/main/tests/unit/test_config.py#L12-L13
https://github.com/snok/django-guid/blob/main/tests/unit/test_config.py#L93-L120
https://github.com/snok/django-guid/blob/main/tests/unit/test_uuid_length.py#L18-L24

Thanks 😊 I also remember your name, you helped me out a lot when I started programming with Django on the Django Discord ~5 years ago. I appreciate you 😊


Fix graph showing alternate 1 month selections properly

When consecutive 1 month increments are selected, e.g. Feb, (no Mar), Apr (no May), Jun, it appears as a single line across all months (because all of the months are selected for points given that the selection is rendered as a 1 month duration. These should appear as different, 1-month intervals with a line. This also is the cause of repetitive wildlife type labels appears at multiple points across the single line

PlantPlot lines ~#190-200

^ like for the 'bees' labels above


Hit Highlighting Thoughts

http://bcbjournal.org/articles/vol3/9910/Faster_rich_edit_syntax_highlighting.htm

https://stackoverflow.com/questions/24599547/syntax-highlight-richedit-control-not-working-poperly

Addressed in #238


husky lens

Before issuing a pull request, please see the contributing page.

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#5  👈
#3
master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @minerkid08 and the rest of your teammates on  Graphite


Add deauth tile

Added the Deauth tile following the issue #41
I put a video on the Discord where you can see how this new tile works on my T-Watch v2.

Hi, I just compiled with 4.4.2 and tested on v3 Watch.

Graphically it is great and like the "Rogue AP" with the graphical glitch #39 so when that one is fixed, the fix need to be shared.
Practially, I tested Deauth and it works super great (maybe there should be an enhanced version where you can deauth a specific host on a Wifi and not the whole wifi... well I assume it is possible, would require a scan of the active host on a specific SSID.
Functionnaly, I had a Freeze in the new Deauth menu, and I think there was no Deauth active. I was on that page, I tested multiple time Start and Stop. Then I left it a little bit doing nothing on that page... but then nothing was responding and I could not start it or escape from it.
Codewise... I did not look at the code, I just hope there is some re-use for the AP selection part, but maybe that would make the compilation more complex, you would need that piece of code if one of the two Tile that use it is activated... maybe duplication of the code is easier in the current use case ???

Maybe the main scan need to be modified to make it "read-only" because now there are two locations to do Deauth (but that is another change to another Tile.
It's really great somebody took the idea and implemented it!
So fast!!!

For the moment, I only ported the code of the RogueAP tile and I modified it to integrate the Deauth to avoid too big a modification of the code and the risk of adding new bugs.
I didn't make any correction about the graphical glitch, but if it is fixed, it will also be applied on the new tile.
The select AP part is not reused, it is initialized in each of the tiles.
There are many improvements to review but this requires major code changes that cannot be applied for version 2.0 which should be available Tuesday evening:

The scanner is permanently active on the Deauth and RogueAP tiles, I think it would be better to integrate the scanner in the Select AP modal but that requires revising the design of the modals or creating a specific modal.
Added the ability to select a specific client, this part does not exist at the moment.
Remove the select AP part of the tiles to move it into the wifi module.

Graphical issues will be fixed next Tuesday as the bugs lie in my twatch-lib library and not in this repository. These issues should be quite simple to fix and I hope it won't take too much time. As @Nels885 wrote, the main goal for now is to reach a working version of HackWatch version 2 including WiFi and BLE features, we will take care of the proposed enhancements in version 2.1 I think.
However, this freeze you experienced while trying the deauth feature is still concerning. I'll try to reproduce and fix this before releasing v2.


[JBPM-5366] replace kie-remote-common with kie-server-common

@mswiderski we need this one as well :)
I am wondering though if console-ng should depend on this artifact? I know its used to catch the particular exception, but I am wondering if it we should be it using here, since the exception seems low level?

+1 to merge
looking at how it's actually used I think you're right, it could then be wrapped with KieServicesException


fix: bug 1645 display error fix

:tada: This PR is included in version 0.324.15 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Seamless az cli login within local docker container using MSAL

Related command

Is your feature request related to a problem? Please describe.

Describe the solution you'd like

Describe alternatives you've considered

Additional context

Thank you for opening this issue, we will look into it.


Sorted collections

For some collections (ARGS, REQUEST_COOKIES), it may be necessary to have them sorted in order to concatenate them in an intelligent way (i.e. concatenated all ARGS named "a" without others in the middle). Think about HTTP parameter pollution...
SORTED_MATCHED_VARS should be sufficient to handle sorting of any collection with an intermediate rule.
The sorting should be alphabetically (case-insensitive for the name) but keep the entries with the same name in the original order.

@marcstern can you give a concrete example where such sort will be needed?

Based on the example, it doesn't seem like this proposal actually has anything to do with sorting per se.  I.e. there is no processing difference between varying orders of unlike-named arguments.
Your example seems to only be about aggregating like-named arguments.
(For anyone following this who is unfamiliar with the concatentation being referred to, some backends (chiefly IIS) will concatenate like-named parameters.  See for more detail (particularly the chart): https://www.acunetix.com/blog/whitepaper-http-parameter-pollution/ )
Or am I missing something?

As I explained, if you try (like in the CRS rules) to do it on unsorted ARGS, you can evade it. This is why we need (also) a sorted collection.
But, as I said, being able to create our own collection would be much better (and allows a lot of other use cases).


Build Improvements

Remove PMD
Address build file technical debt

Coverage increased (+0.05%) to 92.739% when pulling 14179b2962bef3363ee74a446bf2f013c3df8359 on tgianos:removePMD into d982a364cd1a509e8e1cd7aa365635c1a932312b on Netflix:master.