Delete file on premise after copy

Please provide an example how to delete a file on premise after it has successfully been uploaded to a blob storage. Your article says: " Move data between data stores in public network and data stores in private network" - but what the article describes is how to COPY data, not MOVE.
Thanks.

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

ID: d1a34b3c-a9b8-29ce-1eca-86f7f42981a1
Version Independent ID: 61d6e6b3-ec54-552d-1bef-86bbcbfea8ff
Content: Integration runtime in Azure Data Factory
Content Source: articles/data-factory/concepts-integration-runtime.md
Service: data-factory
GitHub Login: @linda33wj
Microsoft Alias: jingwang

Thanks for the feedback! We are currently investigating and will update you shortly.

@maecky Hope your query was resolved using the suggestion by Martin on your Stack Overflow post .
I agree that the doc talks about copying and not moving data. We will review it and make changes to the doc as appropriate.
Thanks for bringing this to our notice.


Remove verified/unverified from extensions

We currently have no way to verify extensions. So the badge should be removed. It already upsets people when they feel forced to do it, or when third-party come and file issues about it, so if they can't even address it, it's even worse.

thanks !


Ability to maximize in portrait mode on GNU/Linux

Is your feature request related to a problem? Please describe.
Discord won't maximize on portrait mode on GNU/Linux.
Describe the solution you'd like
Add fonctionnality to maximize window in portrait mode.
Describe alternatives you've considered
No alternatives found, however Discord can maximize in portrait mode on Windows, it should be possible to make it maximize on GNU/Linux as well.
Additional context

Unfortunately, I cannot feasibly implement this feature because Discord on Linux does not (cannot?) use a custom title bar. Furthermore, it appears that Electron (Discord's backend renderer) does not support controlling the maximize event on Linux. Essentially, though I would love to make this work, it is a Discord/Electron issue and is outside the scope of this project.

Sad, thanks for your reply anyway.


Linux / Mono?

I notice that this requires .NET framework - I assume that it is Windows only - or does it work on Linux with Mono?

Thank you.


Adjustments after issue #620 is merged

The following adjustments need to be made once the 620-operations branch is merged into main:

[ ] In cli.ts, adjust the scaffoldProject() function to not checkout a branch after git clone
[ ] In e2e/taqueria-cli-scaffolding-functional.spec.ts, reactivate all other tests

Issue Number 1:
The main branch of the taqueria-scaffold-quickstart repo has a .taq/config.json file which is using an outdated schema, and therefore doesn't work with the 620-operations branch.
To workaround this, I've added a 620-operations branch to the taqueria-scaffold-quickstart repo which contains an updated schema. I then adjusted the scaffoldProject() function to not checkout this branch after cloning.
Issue Number 2
The taqueria-scaffold-quickstart repo has the latest official version of taqueria plugins installed from the NPM registry. These plugin returns a pluginInfo schema which has also been outdated. As such, I disabled some of the tests in e2e/taqueria-cli-scaffolding-functional.spec.ts
Update:

[ ] taqueria-scaffold-quickstart-demo
[ ] taqueria-scaffold-demo
[ ] taqueria-scaffold-hello-tacos-tutorial
[ ] taqueria-scaffold-taco-shop

@alexzbusko adding you here so that you're aware, and so that you can possibly brainstorm how to handle this going forward.

This will need to include the new scaffolds as well (hello-tacos, taco-shop, demo) and I can take on updating all 4
Just to confirm @mweichert , the changes to the scaffold task are just in your branch to get the tests passing right?
If so, then would this ticket would be implemented immediately after merge (timed with updates to the scaffolds)?

@hu3man I'll need to create a branch for those other scaffolds as well.


Testing overridden remote working

#70  👈
main

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

Join @CatChen and the rest of your teammates on  Graphite


[Fixes from China Hack feedback & Updates to Lab 301 re: notes/tips/w…

Hi Matt,
I needed to do some updates for Lab 1, so also attempted to update the note/tips/warnings sections, so to ensure it is correct, before doing it for the other 7 labs.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

mixed-reality-docs/mr-azure-301.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mr-azure-306.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

@elliotmoule the indented note changes look great! thanks!


Feels like values remain unchanged

Where did you find this bug ?
Feels like sunraise and suset values
Explain about the bug.
For every place those values remain same

Can I contribute?


test: add unit test for isCgroupMounted function

this patch adds the unit test for isCgroupMounted function
Fixes #405
Signed-off-by: Julio Montes<EMAIL_ADDRESS>

lgtm

Hi @devimc - TestIsCgroupMounted is failing under Travis. I think this is because the test assumes the usual /sys/fs/cgroup/... mounts will be available. But under Travis they aren't (they are under Semaphore). See for example:

https://travis-ci.org/jamesodhunt/procenv/jobs/233252731#L2978

I don't think the tests should attempt to mount the cgroup fs if not already mounted so maybe you could make it call t.Skip() if that test detects that memoryCgroupPath isn't actually mounted (you could make the test call out to mount(8) rather than re-implementing isCgroupMounted()).

Coverage increased (+0.2%) to 55.872% when pulling a1438312f15161591e88de0c81fe8216e63ffaaa on devimc:test/oci into 80cee62d9b8672884f7e389633c9e8d78e6d1040 on clearcontainers:master.

@jodh-intel  Fixed, thanks


LocalStorage value types

From @hdsnet on July 14, 2016 11:19
Short description of the problem:
LocalStorage lets you set a Boolean value to a given key (even though the only supported type is a string according to the documentation) and when you retrieve such a value it is converted into string. I guess this is intended but if that's the case at least it should be documented because it's very, very confusing. I am ashamed to admit it but it took me an hour to debug this behaviour after quickly prototyping a few hundred lines of code.
let local: Storage = new Storage(LocalStorage);
local.set('someKey', true);
local.get('someKey').then((value) => {
    if (value == "true") {
        // Do something if it's true
    }
})

Copied from original issue: driftyco/ionic#7313

Fixed! 🎉


BigSampler fails to run with fat jar

Exception in thread "main" java.lang.IllegalAccessError: tried to access class org.apache.beam.sdk.io.gcp.bigquery.BigQueryServicesImpl from class com.spotify.ratatool.samplers.BigSamplerBigQuery$
	at com.spotify.ratatool.samplers.BigSamplerBigQuery$.sampleBigQueryTable(BigSampler.scala:427)
	at com.spotify.ratatool.samplers.BigSampler$.singleInput(BigSampler.scala:142)
	at com.spotify.ratatool.samplers.BigSampler$.main(BigSampler.scala:162)
	at com.spotify.ratatool.samplers.BigSampler.main(BigSampler.scala)

#72 fix will likely be moving to sbt pack based solution, which should solve this problem as well.

Moving to sbt pack, currently there is 0.3.2-SNAPSHOT available for this and will be releasing in this manner in the future


Image not shown (missing html tags), (chap 3.2 superdense coding step2.2,2.3)

Describe the Issue
In step 2.2:
Instead of images in the html the following is shown:
"![image2] (images/superdense_table1.png)"
In step 2.3:
The subtitle is in the middle of the text:
"### 2.3 Step 3"
In the html there are no tags.
Expected Solution
Add right tags.
Anything else we should know?

Good spot! I've jiggled it around a bit, rebuilt the site and it seems to have fixed it. Thank you.


CameraSLM simulation

Add ability to implement all CameraSLM functionality (e.g. wavefront correction) on a simulated camera and SLM. Useful for testing and implementing new wavefront correction algorithms.

Dear @cpanuski ：
I want to see the simulation effect, but two files from slmsuite.hardware.slms.simulated import SimulatedSLM and from slmsuite.hardware.cameras.simulated import SimulatedCam do not exist, can you help me solve it.
Appreciate your help.
Thanks and regards.

Hi @LiuTongZan ,
Are you using the sim branch? These changes on this branch have not yet been merged into main. You will need to pull directly from git (git clone) to be able to checkout (git checkout sim) these features. The pip version will use the as-released main branch. Keep in mind that this is a development branch and features might be changed and/or renamed as they are polished.
Let us know if you have any ideas or suggestions regarding the sim branch. Just to list a few things that we've discussed adding:

[ ] Simulation of camera noise (readout, dark current, etc).
[ ] Simulation of SLM pixel crosstalk (due to the fringing field of the liquid crystal).
[ ] Simulation of SLM phase nonlinearity, potentially per-pixel.

Hope this helps!
Best,
Ian

Basic functionality added in #52. Camera/SLM non-idealities discussed above will be added on an "as-needed" basis.


'npm test' command hangs/doesn't exit

Hello, I'm having an issue executing tests in my terminal. When I type in npm test, the test will start to run, and then it never exits -- it just hangs there. I have to keep canceling the test with ^C. After doing some googling this morning I uninstalled and reinstalled npm for node, updated yarn, jest, and homebrew.
However, none of these actions have solved my issue. I just want to be able to run my tests smoothly again and focus on learning instead of troubleshooting. Can anybody help me out?
Here is the full output on my terminal after running a test:
><EMAIL_ADDRESS>test /Users/bobbychicano/Exercism/javascript/resistor-color-duo
> jest ./*

 FAIL  ./resistor-color-duo.spec.js
  Resistor Colors
    ✕ Brown and black (2 ms)
    ○ skipped Blue and grey
    ○ skipped Yellow and violet
    ○ skipped Orange and orange
    ○ skipped Ignore additional colors

  ● Resistor Colors › Brown and black

    Remove this statement and implement this function

      5 |
      6 | export const decodedValue = () => {
    > 7 |   throw new Error("Remove this statement and implement this function");
        |         ^
      8 | };
      9 |

      at decodedValue (resistor-color-duo.js:7:9)
      at Object.<anonymous> (resistor-color-duo.spec.js:5:12)

Test Suites: 1 failed, 1 total
Tests:       1 failed, 4 skipped, 5 total
Snapshots:   0 total
Time:        1.08 s
Ran all test suites matching /.\/README.md|.\/babel.config.js|.\/node_modules|.\/package-lock.json|.\/package.json|.\/resistor-color-duo.js|.\/resistor-color-duo.spec.js|.\/yarn.lock/i.

Thank you.

Hi there!
It's not fun that you're having issues. Sorry for that. I don't know if I'll be able to resolve this for you, but let's try!
Tools

After doing some googling this morning I uninstalled and reinstalled npm for node, updated yarn, jest, and homebrew.

In general, you'll never need to uninstall npm; instead you would install a new node version, and update the npm binary that comes with it. In that sense, can you run node -v and npm -v and give us the output? The current LTS is 14.5.0, so we'd expect:
node -v
v14.15.0

npm -v
6.14.8

System packages
Next, you mention yarn, jest and homebrew.

Updating homebrew is definitely a good idea.
yarn isn't used by the exercism/javascript track (and is a replacement for npm -- we use it in exercism/typescript).
jest is used, but should be installed via package.json, and not globally managed. This means that you'll never need to update your own jest, in order to make exercism work.

Dependencies
That said, the instructions say to go into your exercise directory, and install the dependencies:
cd /Users/bobbychicano/Exercism/javascript/resistor-color-duo
npm install

After its done, the result should be something like (numbers might differ slightly when on different OSes):
added 915 packages from 421 contributors in 18.136s

48 packages are looking for funding
  run `npm fund` for details

Running the tests
Per the track instructions, tests can be ran with npm test. This yields something like:

Note: there are slight differences in my screenshot versus your output. It really should say jest --no-cache ./* (and not jest ./*). The process does cleanly exist. If you must use CTRL+C, it means that there is something interfering (as you correctly says hanging). It is possible that this is us, but it's also possible that it is completely unrelated. For example:

virus scanner is preventing the process to log somewhere
process tries to log somewhere, but doesn't have access (write access)
something on your system has modified node to run some code on exit (which hangs)

If you've taken all the above steps, and still get different values, I'm happy to collect a Mac and try to replicate your exact system. Feel free to ask anything in this issue.

Hi,
Thanks for checking this out for me. I definitely did not know what I was doing and was desperately trying to find a solution.
This is the output when I run the node and npm commands:
node -v
v14.15.0

npm -v
6.14.8

Also, thanks for the brief explanation of yarn, jest, and home-brew. That helps put those tools a bit more in perspective.
I also make sure to run npm install for every exercise. This is the output I received when running that command again for the resistor-color-duo exercise:
removed 2 packages in 2.913s

48 packages are looking for funding
  run `npm fund` for details

Finally, in regard to jest, that was my fault. I had changed the cache setting hoping it did something. I’ve changed it back but it doesn’t solve the issue.
My only other thoughts are that my javascript could have broken the test? I was trying to solve the reverse-string exercise with recursion and I noticed it caused a bunch of test/statements to come on screen and hang.
This last part is embarrassing — I didn’t know how to exit the npm test command when the test was hanging so I pressed every button on the keyboard and kind of got lucky and accidentally hit control+Z and that suspended the command. Is it possible I changed some setting in terminal just by clicking random keys?
Thanks for all the help so far! I appreciate your friendliness and your patience with someone that is not as experienced as you.

Would you be so kind to run npx envinfo --preset jest and give us the results? This will tell us a bit more about your environment. That way it's easier for me to reproduce, hopefully.

Finally, in regard to jest, that was my fault. I had changed the cache setting hoping it did something. I’ve changed it back but it doesn’t solve the issue.

It still hangs? You can try to add --forceExit to the package.json script, or when running in your terminal: npm test -- --forceExit. If that works, let me know. It's not a solution, but may bring us closer to the issue at hand.

My only other thoughts are that my javascript could have broken the test? I was trying to solve the reverse-string exercise with recursion and I noticed it caused a bunch of test/statements to come on screen and hang.

If you have an infinite loop, the tests will definitely hang. CTRL+C might not even close it. Without going in too many details (but feel free to ask more), best is to go into the process manager and kill it manually (or use a new terminal and find the process ps aux, and kill it kill -9). Other option is to restart your computer.
However, it shouldn't affect other directories --

Is it possible I changed some setting in terminal just by clicking random keys?

I suppose so! But I wouldn't know what 😅 . Here I would also start with restarting the machine, just in case.

Hey SleeplessByte, I hadn't thought about restarting my machine.
I was hoping it would be that simple, but I just closed all of my applications and restarted and I still have the same issue.
Here is the result of npx envinfo --preset jest:

Also, I tried npm test -- --forceExit and it was successful in ending the test. Here is the result:

I also tried npm test -- --detectOpenHandles like the terminal suggested but that also just hangs and I never got a result.
Thanks for the quick responses by the way.

Also, I tried npm test -- --forceExit and it was successful in ending the test. Here is the result:

Okay great. Then at least you have a way to do this before we figure out what the heck is going on!
I'm outta ideas at this moment, but will try to reproduce on a Mac here. @NobbZ you have any ideas? Seen this issue on gitter?

@bobbychicano can you create a gist (gist.github.com) and paste in your exercise file, test file (one ending with spec.js), package.json so we can see if there is something with your code?

Hi Neenjaw,
Gist created here:
https://gist.github.com/bobbychicano/704b3ce296205e5bdf3d60becfcd9204
Thank you.

It certainly doesn't seem to be anything in your code. Hopefully we can rustle up someone with a mac to be able to help you trouble shoot this.
Oh, does this always happen with every exercise? or just this one?

So far it happens on the reverse-string exercise and on the resistor-color-duo exercise. It definitely wasn't happening before on any of the other exercises I had worked on.
Thanks for the help so far. I know it can be difficult trying to troubleshoot across the web. Wish there was more I could do to help.

All good. It's interesting.
Van you post a list or screenshot of your Exercism folder do we know which exercises you did (in an attempt to find commonality between those two and not the rest).

@NobbZ you have any ideas? Seen this issue on gitter?

Sorry beeing late, just realised this in my inbox by accident…
No, so far this behaviour has not been mentioned in the gitter, and I even asked an ex coworker (the only one I know im my proximity who has done JS for quite a while now) if he had observed something like this before, though he hasn't as well.

Quick update guys:
I've moved on from the exercises I was having trouble with. I added --forceExit in the package.json file so that I could get through them.
I'm currently on the 'triangle' exercise and running npm test works smoothly and does not hang.
Thanks y'all for having taken the time to look into this.

I'll close it as "non-reproducible", but if you or anyone else has this issue, feel free to post again or open a new issue.


build images on travis

Our custom images used by the charts and docker-compose should be available from dockerhub (i.e. built on . The custom configs should be baked into the images and not mounted.

[x] jupyterhub
[ ] keycloak
[ ] gitlab
[ ] notebook
[x] apispec

Note: the charts use non-custom keycloak and gitlab. Custom images can be avoided there.

right, but I'm advocating for baking the configuration in with the image instead of copying the configuration in via templates.

@jirikuncar this won't necessarily solve the issue for dev environments using docker-compose since the image tags will use commit shas.

@rokroskar we can also tag them with :<branch|"latest"> name.


Bravetools image naming schema

At the moment Bravetools image definitions span several fields, and may possibly expand in future as bravetools moves towards multiple remotes. These fields are generally just concatenated together internally anyway to uniquely identify an image. It would be nice to allow the users to specify the image they want using just one field.
The lxc tool and LXD public image store already has a schema which we may want to emulate to better integrate with the existing ecosystem. It is also much briefer, which is nice. Here's the schema:
[remote:]name[/version][/arch][/type]
The public LXD image store hierarchical directories can be browsed here. These public images are associated with the "images:" remote in the lxc tool.

Addressed in #164


feat: pdf enhancement

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


AN-179: Rename request in config.triggers as rrp

Changes were merged to master https://github.com/api3dao/airnode/pull/561


watchdog

I think a simple watchdog is needed. It can happen that the Modbus client hangs while establishing a connection. Either the modbus client is destroyed or the adapter is restarted.

implemented in version 0.1.0


set comment_date_gmt

This should close #102
I don't have a clever idea for "rescuing" old comments, though.

thanks


add CODEOWNERS file

Just quickly setup a CODEOWNERS file as explained here. It's a pretty new feature I fell over this summer that I found quite neat and thinking about how we would for example want @zanemountcastle to look over @joaquinkunkel's css changes before it merged in etc. just made me think I'd quickly set one up.
@zanemountcastle if you could just take a look, if you see any typos feel free to correct of course, and otherwise if you feel something is off, like if I was too heavyhanded only putting me on lib or something like that just say so. Remember that this doesn't mean that no one else can review the PRs of course, it just means the PRs can't be merged (at least without admin privileges) without the code owner(s) having approved the PR, and it for example I guess would be nice for that to work for having you having to look at the styles folder or the main components folder, and me looking at all changes to db.js, falcorRouter etc.

Hmm, I think I mostly thought of it as lead engineers, or maybe junior engineers if they have proven themselves, but in that case they might be considered lead engineers anyway?
When you say:

If it's only for the lead engineers, is the system we have now not enough where we both need to review PRs that come in?

That's of course true, but my reason is also simply in agreement with what you said above:

It seems like a neat little feature.

And not really anything else, what this does is simply ensure that at least one (or maybe both in the cases where we are both owners, I'm actually not quite sure of the functionality) of us have reviewed the code before it can be merged. Right now I believe that in theory anyone also other than the two of us could approve a PR and then it would be eligible for review, so I just thought we'd add this quickly.
So yeah if you agree with this you can approve and merge it :)


Rendering of markdown in HTML tags

Hi,
I have asked a question at StackOverflow that I suspect may be a bug (or lack of features) in this Markdown parser.
Thanks for your time,
Brenton

Hi @fusion809,
This is actually not possible at the moment (see #13) ; we may support this feature in the future if we follow the CommonMark specs that basically allow you to put Markdown between HTML tags if there is an empty lines between the markup and the tags.
I'm giving it a close but thanks for proposing this feature anyway!


fix Issue 15629 - [REG2.066.0] wrong code with '-O -inline' but correct with '-O'

https://issues.dlang.org/show_bug.cgi?id=15629

Auto-merge toggled on


Add last_exported date column to exportdb export_data table

It would be helpful to know the date/time a file was last exported -- could easily add a column to export_data to track this.

Done! 0.49.4


.NET Core 3.0.100-preview9-014004 gives warning and links to this page

Latest .NET Core 3 preview ( 3.0.100-preview9-014004 ) gives below warning on dotnet pack, links to this page but seems to be no details yet about the new upcoming elements.
- error NU5048: The 'PackageIconUrl'/'iconUrl' element is deprecated. Consider using the 'PackageIcon'/'icon' element instead. Learn more at https://aka.ms/deprecateIconUrl

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

ID: 06a19d7d-253d-f17f-6421-624c9867473d
Version Independent ID: cc37eb17-f715-080c-7bfc-9eae868d50ba
Content: .nuspec File Reference for NuGet
Content Source: docs/reference/nuspec.md
Product: nuget
GitHub Login: @karann-msft
Microsoft Alias: karann

It looks like the documentation is still in progress with pull request https://github.com/NuGet/docs.microsoft.com-nuget/pull/1661. Here is the latest preview: https://github.com/NuGet/docs.microsoft.com-nuget/blob/1d0a27127fb7814c9da9c767e3fcb3bacf397327/docs/reference/errors-and-warnings/NU5048.md
Feel free to leave comments on the pull request if you have any feedback!

Ok, maybe https://aka.ms/deprecateIconUrl should go to that PR or nuget wiki then for now. A bit confusing otherwise.

Ah PR seems merged now,  so guess it'll be out on web soon.

And it's out would probably be good to document minimum required nuget version.


Add loading component

with its beautiful minimal progress loading css animation

+1
I found a beautiful progress bar here.
https://github.com/rstacruz/nprogress/
I am wondering if we can implement a progress bar in this way?
https://github.com/rackt/react-router/blob/master/examples/async-data/app.js
Call "fetchData" and pass a "progress" object in each react component  before the route.path change.
But how do we control percentage of the progress bar, and should "fetchData" in Action.js?

Thank you. I will probably use it but we can control percentage only for data upload or sequenced loading aka many requests or web sockets.

I am successfully using https://github.com/quickleft/react-loader in a parent component to preload all the needed data and works quite well. Any other suggestions how we can improve that?

gsit

@steida so clean, nice! Will give it a go later today as I am figuring out the bast way to handle that particular case.

Then can send pull request with an example to Este ;-)

Already plugged in. All good. Needed to add React.PropTypes.element to anyOf as I am using it like below:
render() {
    let isLoaded = isStoreLoaded();

    return (
      <Loading
        children={<RouteHandler />}
        loaded={isLoaded}
        />
    );
  }

In my case, here's the flow I've decided to go with (the most obvious one, not sure if the best):

The above route acts as a placeholder for common views inside dashboard that use this store data (e.g. GroupsListPage, GroupsAddPage and so on)
When the above route loads, it gets data from the store by calling getGroups elsewhere (in a constructor). Store invokes getGroupsAction lazily if isStoreLoaded is false
Views just listen to props, flux for the win!

I could've passed groups to RouteHandler to make pages state-less, but not every underlaying component is actually using groups cursor, some of them, like EditGroup just want to make sure the data has been loaded.
Any ideas how this can be improved before PR? :)

Try React.PropTypes.node for any children.

? @steida missclick?

Now, I want to add similar component :-)

No time.


Please fix popsplit behavior

hello i am newbie , the popsplit not working totally.

Well this is a duplicate, and quite frankly a useless issue.

ok thx.


Increase Test coverage for CacheHealthCheck

This adds a test to cover the case where the incorrect value is received from Cache and brings coverage of CacheHealthCheck to 100%

Thanks for this PR too @srichter! 👍🏻

Tagged at v1.5.0
https://github.com/ukfast/laravel-health-check/releases/tag/v1.5.0


fix engine mounting

@alexanderadam so that we can mount the engine on a custom path in our apps. Do you like it? :tropical_fish:

Just curious: Do you know what is the constraint for? Why shouldn't it match to sth like blabla-4-columns?

I don’t know, Alex. Do you think we need it? Or can I just delete that constraint?

On 09 Jun 2015, at 14:46, Alexander Adam<EMAIL_ADDRESS>wrote:
Just curious: Do you know what is the constraint for? Why shouldn't it match to sth like blabla-4-columns?
—
Reply to this email directly or view it on GitHub.

I think that Felipe most probably had something in mind and I would keep it for the moment.
IMHO it should be fine if it works on your project locally.


Fix default adapter method entrypoints' default and object method calls

Also moves tests to dedicated quilt package
Note: without this change, the new test will fail on the addition of the first method-based entrypoint, as method-based ones have broken object methods and cannot be added to hash sets.

The developer that submitted this PR has been blocked from interacting with this GitHub organisation. For the sake of transparency, we thought it appropriate to state that this was not due to the content submitted in the PR.
The community team elected to block the submitter due to actions they've taken in other, related communities. Specific concerns include the apparent endorsement of lethal force used by governments to oppress protestors, as well as posting discriminatory material encouraging people to exclude members of the LGBT community and people with disabilities from their spaces.
Actions like this break our Code of Conduct, which also provides a provision for us to take action when people break it outside our community spaces. This provision exists to allow us to protect members of minority groups in our community, by pre-empting issues before they occur.

Some of the development team members pointed out that we should have written this up and posted it at the time of blocking - we'll make sure we do this promptly in future.


Incorrect maximum value specified for "MaximumExecutionTime"

Hi,
On this page one of the code snippet state that the maximum possible value for "MaximumExecutionTime" is 10 seconds but later in the specification table the default stated value is 120 seconds (which doesn't seem to be consistent).
Looking in the source code it seems like the maximum value is 24 days.
Thanks,

Yeah, the comment in the code snippet is ambiguous. We'll update this doc. thanks!


Monster Hunter Stories 2

I tried doing this myself. Got it to work on Windows but not Steam Deck so requesting an update
Config files are located at
Windows: Program Files (x86)\Steam\steamapps\common\Monster Hunter Stories 2\config.ini
Steam Deck:  home/deck/.local/share/Steam/steamapps/common/Monster Hunter Stories 2/Config.ini

I did some testing and it seems that the config.ini does nothing not sure why it exists. The settings seem to be actually stored in a fille called mhr_sys.sav
the paths are inside the userdata folder of steam like so
Program Files (x86)\Steam\userdata\USERID\1277400\remote
I've been messing around trying to figure this out myself but ive never done any kind of batch file/coding so not sure how id direct it properly


unable to build

=== BUILD TARGET fluttertoast OF PROJECT Pods WITH CONFIGURATION Debug ===
<module-includes>:1:9: note: in file included from <module-includes>:1:
#import "Headers/fluttertoast-umbrella.h"
        ^
/Users/huangyicheng1/Downloads/flutter_app/ios/Pods/Target Support Files/fluttertoast/fluttertoast-umbrella.h:13:9: note: in file included from /Users/huangyicheng1/Downloads/flutter_app/ios/Pods/Target Support Files/fluttertoast/fluttertoast-umbrella.h:13:
#import "FluttertoastPlugin.h"
        ^
/Users/huangyicheng1/.pub-cache/hosted/pub.flutter-io.cn/fluttertoast-2.0.1/ios/Classes/FluttertoastPlugin.h:1:9: error: 'Flutter/Flutter.h' file not found
#import <Flutter/Flutter.h>
        ^
<unknown>:0: error: could not build Objective-C module 'fluttertoast'

any update?

@PonnamKarthik  I found delete  SwiftFluttertoastPlugin.swift, ios build will be done.
so please update.
thanks

plugin updated check version 2.0.2


How to specify config in repo so it uses that

Hello I am trying to deploy it but facing server not responding to port. And I can't edit config in that place so is there any way that I can place config in repo and it uses that while deploying like specify port, ip, vmess I'd
And someone specify demo config in reply also.
Thanx

Hello I am trying to deploy it but facing server not responding to port. And I can't edit config in that place so is there any way that I can place config in repo and it uses that while deploying like specify port, ip, vmess I'd
And someone specify demo config in reply also. Thanx

I am new to this project like you, but you should have a look into the Readme as there is a link to the documentation and especially to the guide for novices like you and me.
Please have a look here.

@killerlearner I would suggest, that you should take minute and reflect on your issue.
You are asking for help but you do not provide any form of information on what you did but instead you demand a demo config.
Ask yourself, how could a person help you as your issue lacks all necessary informations on how to reproduce your setup.
Are you running on Windows, macOS, Linux, a server, a desktop, some Raspberry Pi setup.
Self compiled (as the config-in-repository suggest) but then you write, that you cannot change the config on your target system?
Are you running the software in a Docker container? Maybe you are missing the option to mount a local config into the container on startup?

@Comradin yeah I am deploying in docker so can you tell me where should I put this server config file in repo to make it automatically detect and take this config be default.


Entering vi(1) commands in JupyterLab notebooks causes scroll to bottom of cell ...

Hello Friends:
I originally posted the following here, and they suggested posting this issue here.
I'm running the below library versions in a Python virtual environment.
My JupyterLab Notebooks use vim(1) emulation.
I don't know when this problem started, but every time I perform, say, a w! editor operation to save changes, the Notebook scrolls to the bottom of the current input cell, but doesn't go back up to the cursor input location so that I can continue working. I have to scroll back up each time and find where I was.
The behavior use to be a convenient and quick appearance of the ed(1) one-line editor at the bottom of the display as you typed a vi(1) command, then it would disappear and you were taken back to your cursor. It no longer does that.
Can anyone suggest what to check for and/or how to fix this?
Thank you in advance! (See below).
Python 3.12.4
jupyter==1.0.0
jupyter-console==6.6.3
jupyter-events==0.10.0
jupyter-lsp==2.2.5
jupyter_ai==2.18.1
jupyter_ai_magics==2.18.1
jupyter_client==8.6.2
jupyter_core==5.7.2
jupyter_server==2.14.1
jupyter_server_terminals==0.5.3
jupyterlab==4.2.3
jupyterlab-vim==4.1.3
jupyterlab_pygments==0.3.0
jupyterlab_server==2.27.2
jupyterlab_widgets==3.0.11

Hello Friends:
I originally posted the following here, and they suggested posting this issue here.
I'm running the below library versions in a Python virtual environment.
My JupyterLab Notebooks use vim(1) emulation.
I don't know when this problem started, but every time I perform, say, a w! editor operation to save changes, the Notebook scrolls to the bottom of the current input cell, but doesn't go back up to the cursor input location so that I can continue working. I have to scroll back up each time and find where I was.
The behavior use to be a convenient and quick appearance of the ed(1) one-line editor at the bottom of the display as you typed a vi(1) command, then it would disappear and you were taken back to your cursor. It no longer does that.
Can anyone suggest what to check for and/or how to fix this?
Thank you in advance! (See below).
Python 3.12.4
jupyter==1.0.0
jupyter-console==6.6.3
jupyter-events==0.10.0
jupyter-lsp==2.2.5
jupyter_ai==2.18.1
jupyter_ai_magics==2.18.1
jupyter_client==8.6.2
jupyter_core==5.7.2
jupyter_server==2.14.1
jupyter_server_terminals==0.5.3
jupyterlab==4.2.3
jupyterlab-vim==4.1.3
jupyterlab_pygments==0.3.0
jupyterlab_server==2.27.2
jupyterlab_widgets==3.0.11

BUMP. Can anyone take a look at this please?

Thanks for reporting. As suggested in the original issue you filed, have you confirmed whether it's an issue upstream with replit/codemirror-vim, using their sandbox at https://raw.githack.com/replit/codemirror-vim/master/dev/web-demo.html?

Hi @firai Thank you for replying. I visited the sandbox URL you provided above, and the :w <enter> experience in it is perfect; and is the same experience I used to have in my Notebooks. I don't know what changed. I'm using this library for vim: jupyterlab-vim==4.1.3. I'm unsure what to try next.

After :w and pressing enter, if you press j or k, does the view scroll up to the cursor, or has the cursor moved for you?
You said that "the behavior [used] to be a...one-line editor at the bottom of the display as you typed [an ex] command, then it would disappear and you were taken back to your cursor. It no longer does that." Are you saying that you're also seeing a problem with the ex prompt, or just the scrolling issue?
Just to make sure we're talking about the same issue, would it be possible for you to record a GIF of the problem you're seeing?

@firai After reading your reply, let me clarify what I wrote (because I mis-remembered how it used to work until I saw the sandbox today ). :blush:
When things worked for me, it worked just like the sandbox does. That is, when typing :w, an ex line editor opened in-place (always right where the cursor was), with absolutely no scrolling whatsoever (neither down nor up); no matter how vertically talk the cell happened to be.
Now, for some odd reason, my cursor jumps to the bottom of the cell when typing w:, no matter how tall or short the cell is. It's just less noticeable when the cell is not very tall (like, for example, one with a few Python import statements).
But, scrolling to the bottom of a cell is the wrong behavior. As with the sandbox, it shouldn't seek to scroll to the bottom of a cell under any circumstance, but that's what mine is doing now. Each time it does this, I must mouse-scroll back up to my edit location. Annoying because I like to save early & often. LoL :smile:
I hope that helps. And thank you.

PS: I noticed the GIF request too late. Let me know if you still need it after my reply, and I'll be happy to furnish one.

Thanks for the clarification. It seems like you may be comparing JupyterLab/jupyterlab-vim, which does not limit the height of the input area and therefore scrolls the document panel outside of the input area as necessary, against the codemirror-vim sandbox behavior when the input area height is limited and scrolling happens within the input area.
When the input area height is limited to be shorter than the visible page height and scrolling only happens within the input area, the ex prompt neatly displays without scrolling in the sandbox as you have mentioned.

However, when the height of the input area is longer than the visible page height, which is how very long cells are set up in JupyterLab, the sandbox page scrolls to the bottom of the input area to show the ex prompt and the cursor is no longer visible after exiting the prompt. This is the same behavior that you're seeing in JupyterLab/jupyterlab-vim.

This is the behavior that I'm seeing in JupyterLab/jupyterlab-vim.

I understand your frustration though. Just thinking out loud, it's probably not possible to show the ex prompt without scrolling to the bottom of the input area if the cell height isn't limited, unless is very significant change is made upstream in codemirror-vim. It may be possible to force the document to scroll/focus back up to the cursor after exiting the ex prompt, but this probably also needs to be implemented upstream in codemirror-vim.

@firai What would be do without GIF animations. 😊 Thank your for the comprehensive reply.
In your sandbox trials, can you enable the status bar option at the top and try again? (like in the screenshot below). Below is a screenshot of what I see with that enabled. (Apologies for having trouble creating a GIF because I'm currently booted to Fedora with Wayland, and many capture tools don't yet support the Wayland).
Although difficult to spot, when I issued the :w command, the edit-cursor is located on line-7 (under the "hi") .
That behavior would be good. It's not in-place (and probably never was LoL) but it doesn't scroll either.

Unless you're talking about different JupyterLab behavior than what I have shown above (again, recording a GIF would help here), it doesn't seem like turning on the status bar would help here. It seems like you're still looking at the sandbox behavior when the CM editor is shorter than the visible page, and the scrollbar is inside the CM editor. In order to be comparable to the JupyterLab behavior, you need to resize the CM editor in the sandbox to be taller than the page (using the drag control at the bottom right of the CM editor), such that the bottom of the CM editor is below the visible page, and the page has a scrollbar outside of the CM editor itself.

being annoyed by the same issue here. I'm now trying to have myself used to "ctrl-s" instead of "w" even in the vim mode.


paged_llm with --bs=1 exports func.func with too many kvcache arguments

What I see
Usually the kvcache arg looks like
 %arg4: !torch.tensor<[?,2662400],f16>

and is the last arg in decode_bsX and prefill_bsX
But when I export ONLY bs=1, I see 50+ arguments, most of which looking like:
 %arg3: !torch.tensor<[1,2048,32,100],f16>, %arg4: !torch.tensor<[1,2048,32,100],f16>, %arg5: !torch.tensor<[1,2048,32,100],f16>, %arg6: !torch.tensor<[1,2048,32,100],f16>,

Interestingly, --bs=1,4 produces normal looking kvcache args.
What I hoped to see
Instead of many small arrays, the kvcache should be accepted as one big array, as expected by e.g. shortfin. Having many small arrays results in an error.
Watch me replicate it
https://asciinema.org/a/UapPmn4h1wwuTxM6cptAYyXcr
Context
The cache state params are created here for export_paged_llm_v1.py
https://github.com/nod-ai/SHARK-Platform/blob/4a49a847c873f4940bb0786283c3ddf25c4c6da3/sharktank/sharktank/examples/export_paged_llm_v1.py#L120-L133
The cache state is passed to export_program here:
https://github.com/nod-ai/SHARK-Platform/blob/4a49a847c873f4940bb0786283c3ddf25c4c6da3/sharktank/sharktank/examples/export_paged_llm_v1.py#L144-L148
How to replicate
run this script
https://gist.github.com/renxida/749d6a26cf94d05ba9db6342064aaa3f
You should see the same thing as:
https://asciinema.org/a/UapPmn4h1wwuTxM6cptAYyXcr
or if you prefer pure text
https://gist.github.com/renxida/ca262a5110701bbc024359026426952a
This is found while I was debugging the kvcache nan issue in shortfin llm serving. I would really love to have bs1 so I can isolate the issue.

@aviator19941 and @archana-ramalingam because I'm hoping how this script works is still fresh in your mind

Sorry didn't see this. That's weird, have you been able to look into the issue?


Floating point precision lost

Input:
json data;
data["number"] = 11.4f;

output:
std::string dataString = data.dump();
result:
{
    "number": 11.3999996185303
}

That is because you cannot represent 11.4 as a single-precision floating-point number. Take a look into ExploringBinary - Floating Point Converter.
Here is an example having the literal number on different precisions:
Input:
json data;
data["number-float"] = 11.4f;
data["number-double"] = 11.4;
data["number-long-double"] = 11.4l;

Output:
std::string dataString = data.dump();

Result:
{
    "number-double":11.4,
    "number-float":11.3999996185303,
    "number-long-double":11.4
}

You need to use decimal floating point to solve this issue. Normal float, double, and long double are based on a base of 2 and cannot represent all base 10 floating point numbers accurately. gcc has decimal32, decimal64 and decimal128 classes as well as underlying C types defined to address this.
In your compiler try this
if((0.1+0.2)==0.3)
std::cout<<"true"<<endl;
else
std::cout<<"false"<<endl;
You will need to change the underlying types, as the library serializes the underlying types accurately.

Can this ticket be closed?


Use Aylur/ags as bar

Here refer to (or use) the configuration writing method of NotAShelf/nyx, and modify it after becoming familiar with the writing method.


Revert "Use safe_ts to determine whether the peer's data synchronizat…

…ion progress is far behind the leader. (#5866)"
This reverts commit f07fe50d19db40ee3244665213226d94288ab853.
What problem does this PR solve?
Issue Number: close #5905
Problem Summary:
What is changed and how it works?
Check List
Tests

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

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Documentation

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Changes MySQL compatibility

Release note

None

/run-check-issue-triage-complete

/run-all-tests

/merge

/merge

/run-integration-test

/run-integration-test


Crashes game on handling long character names with accented letters

I have a really bizarre bug to report, and my static spent about an hour and a half isolating it. The bug was causing me to hardcrash with no error log every time i zoned into a map. I thought at first it was the aerodrome, but it happened in the raid wing too. Long story short, it turns out it was one of our member's specific character - whenever i shared a map with this character, even at other sides of a giant open world map, my game hardcrashed immediately. I disabled all addons, testing one by one, and found that it was Squad Manager that caused it.
The character's name was "Glint Sez Gäy Rites". Other max-length names or names with the ä did not cause a crash, but consistently this character did. Said player then used an empty character slot to make another max-length name that had an umlaut character, which did cause a crash.
So there's probably something wonky with how your addon interprets accented characters in names.

https://github.com/RaidcoreGG/GW2-CommandersToolkit/releases/tag/20220918-135925 @DioVento


Add CI testing stage for OE release package on Ubuntu 18.04

Fixes 2nd bullet from checklist in https://github.com/Microsoft/Azure-DCAP-Client/issues/30 by adding a stage to test also OE release package for Ubuntu 18.04

bors try


[WIP] Refactor adding processes

Addresses #78

This PR is not really in a reviewable state. It's not even passing tests yet. However, thanks for the feedback anyway! If you want to give feedback on any of the PRs, it would be really valuable.


fix(terraform_docs): Fix non-GNU sed issues, introduced in v1.93.0

Ensure compatibility of terraform_docs hook on MacOS and Linux by using GNU sed.

[ ] This PR introduces breaking change.
[x] This PR fixes a bug.
[ ] This PR adds new functionality.
[ ] This PR enhances existing functionality.

Description of your changes
In PR #701, the usage of sed was introduced to the terraform_docs for in-file changes, resulting in #703
MacOS requires an extension for the -i parameter, unlike GNU sed.
As a result the hook fails on MacOS know with the following error:
Terraform docs..........................................................................Failed
- hook id: terraform_docs
- exit code: 1

sed: 1: "README.md": invalid command code R

I see two potential solutions for this issue.

Always pass a extension to the -i parameter, as this is compatible with GNU sed, too. As a result, a backup file would be created for each sed commands operation and needs to be deleted again.

Ensure we always use GNU sed. GNU sed is available via brew and can easily be installed on MacOS systems. Using GNU sed on both MacOS and Linux ensures consistent behaviour across operating systems.

I'm happy to change it to option 1, but wanted to show both options I see to fix the issue. Also I'm not 100% sure about Windows support for this hooks, but it seems like ( #648 ) they only work on Linux and MacOS.

@cschroer there is a much more easy solution (I use this since many years and it is proven to be portable) ...
When you use "-i" in sed you must always add the backup suffix otherwise it would not work on Mac for example. Adding and empty suffix does the trick:
# bad
infra albert$ sed -i "s/^ASDDFGFDSGHSDFG$/PIPPOPIPPO/" "MODULE-DETAILS.md"
sed: 1: "MODULE-DETAILS.md": invalid command code M

#good
infra albert$ sed -i "" "s/^ASDDFGFDSGHSDFG$/PIPPOPIPPO/" "MODULE-DETAILS.md"
infra albert$

And I suppose we need same fix in https://github.com/cschroer/pre-commit-terraform/blob/ad5d40b6686386e930560851f12b670df7110828/README.md#L585-L590

I personally ran into some other issues with sed on MacOS, therefor I personally prefer using GNU sed on MacOS, too.
But for this case it's maybe better to simply use the empty extension. 👍 Adjusted the code and also updated the README.

Also I'm not 100% sure about Windows support for this hooks, but it seems like ( https://github.com/antonbabenko/pre-commit-terraform/issues/648 ) they only work on Linux and MacOS.

@cschroer yep, you're right
From installation instructions,
https://github.com/antonbabenko/pre-commit-terraform/blob/99fceb87b07cdbb97111c3b4eb17d3f70d36e13c/README.md#L207-L213

This PR is included in version 1.93.1 :tada:


Docs: contributors guide

PR:

Add link to instructions how to install Toga prerequisites.
Updated example how to install Podium in development mode.
Removed Python2.7 instructions since it is no longer supported.

This will close issue #23.

This looks good! I am not sure why it pulled in previous commits that are merged.
@freakboy3742 can you please merge?


[CELEBORN-1445] handle NPE when open stream

What changes were proposed in this pull request?
In some case, celeborn may lost the shuffle key, and when client try to open the stream with this shuffle key. Celeborn worker will throw NPE and won't reply the open stream request.
Client will wait(hang) until reach the fetch chunk time out, so let's fast fail with return the PartitionUnRetryAbleException.
Why are the changes needed?
As the above.
Does this PR introduce any user-facing change?
No
How was this patch tested?
Add IT

In which cases will the NPE be thrown? And if shuffle key is null in these cases, Maybe better check shuffle key and throw IOException instead Wrap the NPE.

Well, seems I misjudged the issue.
First, this NPE occurs when the Celeborn Worker has a graceful shutdown and restart operation while spark applications are running. And after restart,  we observe from the dashboard that a celeborn worker has an incorrect number of running applications.
And task on spark side, will throw RPC fail with NPE(for now, I realize that this error being thrown doesn't seem to have anything to do with this PR, the error was thrown by)
https://github.com/apache/celeborn/blob/e5f09ce4e06154c3cadd1ff13a9f304b672e9cdb/worker/src/main/java/org/apache/celeborn/service/deploy/worker/storage/ChunkStreamManager.java#L197-L200

May I ask which version you are using? Are local read or hdfs read enabled?

May I ask which version you are using? Are local read or hdfs read enabled?

check out from Branch-0.4
Neither local and HDFS features enabled, just remote read and write.

I'm still finding the root cause, here we just talk about how to fast fail with fetching non exists chunks.
After reminder this PR seems not fit this goal, i will turn into draft and make some changes.


Can't change values of variables in scenes with setters

Godot version:

v3.2.3.stable.official
OS/device including version:

Windows 10
Issue description:
I expected $"Holder".setvar.somevar to be set to 3 but instead it calls the setvar setter making changing somevar to 3 impossible
If this is intentional behavior idk how to do the action I'm trying to do here
Steps to reproduce:
put a breakpoint on Node2D.gd on line 4 and step through
Minimal reproduction project:
setter  bug.zip

Can't you do something like this, i think you complicate it to much?    :D

thats not remotely similar to what I'm doing. The setvar is what needs the setter and doing so disables me from changing any properties of setvar. You can meet me on the discord if you want to see what it is I am doing in my game and how this translates

thats not remotely similar to what I'm doing. The setvar is what needs the setter and doing so disables me from changing any properties of setvar. You can meet me on the discord if you want to see what it is I am doing in my game and how this translates

This is a GDScript-specific issue, and it occurs on both 3.2 and the master branch. Master test project: setterbug4.zip
The same code does work properly in C# even though it's broken in GDScript. Here is a 3.2 C# project: setterbug-godot-cs.zip
Also, to make the problem clearer, here's a pure C# test made in .NET Core: 45404-dotnet.zip

This is a GDScript-specific issue, and it occurs on both 3.2 and the master branch. Master test project: setterbug4.zip
The same code does work properly in C# even though it's broken in GDScript. Here is a 3.2 C# project: setterbug-godot-cs.zip
Also, to make the problem clearer, here's a pure C# test made in .NET Core: 45404-dotnet.zip

@vnen I'm supposed to tag you and ask if this is taken care of for 4.0


Uncaught Error: Cannot find module "."

Runtime Error: Uncaught Error: Cannot find module "."
Version: 0.1.7

+1

+1

Have a look at issue #73 ;)

If you are still interested, please take a look at the version 1.2.3, thanks!


new resources

https://github.com/chasedooley/mostly-free-resources-for-almost-everyone

Free-Courses-For-Everyone


Problem connecting to remote node

followed instructions to make ~/.bos/mynode/credentials.js:
{
"macaroon": "mymacaroon==",
"cert": "mycert==",
"socket": "mynode.mysite.io:10009"
}

When I run bos nodes, error:
balanceofsatoshis/nodes/get_saved_nodes.js:103
          if (!credentials.macaroon) {
                           ^
TypeError: Cannot read property 'macaroon' of undefined

lnd version 0.8.0-beta commit=v0.8.1-beta
bos 5.6.2
node v10.17.0

I think the fix here is to give a better error message if you use a .js and not a .json for the credentials

Actually the new way to do this is just to use the add node functionality and not mess around directly with credential files


Pull 1.14 up to a071e8434eb695e61e4f70e8c001e775387c5e2a

Can you make sure to include 0b0bc908dffed711e59c0676d6dcbf8c90f721a0?

Replaced by https://github.com/tensorflow/tensorflow/pull/28884 since I don't know how to push to a protected branch.


Broken type validation 'string' using between

When I setup string with between like this
'name' => ['required', 'string', 'between:3,150'],
I getting wrong type
name	numeric	required	Between: 3 and 150
But when i set min, max it's ok.

The issue is fixed. The between rule automatically set the type to numeric.


Update to ccache v3.3.4, add windows build

All passing:
Linux:
OSX:
Windows:

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin , please rerender

Hi! This is the friendly automated conda-forge-linting service.
I was trying to look for recipes to lint for you, but it appears we have a merge conflict.
Please try to merge or rebase with the base branch to resolve this conflict.
Please ping the 'conda-forge/core' team (using the @ notation in a comment) if you believe this is a bug.

Hm, this PR is reallllly old, gonna close it. Looks like #5 might be tackling the windows build.


Export/apply consumer groups

I love your tool, do you plan to add functional to export/create consumer groups?

Hi @armitageee
Glad to hear it's useful!
I can certainly look into adding that functionality. I can't promise anything soon, though.

It's been a while since I've worked on this, so I just had to refresh my memory of how things work. As I understand it, consumer groups are not created via the Kafka admin APIs. I believe groups are created as a result of consumers making a request to subscribe to a topic, setting the GroupId config.
So I don't think this is something that can be centrally managed by this tool.


Address dateRange validation error

This PR fixes unwarranted validation errors by updating the date range validation schema.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Product page Fix #41

@bogas04 @twishasaraiya Please give it a review.

Great work @Nshul and @twishasaraiya. Please go through the review comments.

@bogas04 Please review again.
@twishasaraiya I have added PropTypes. Please add JSDoc and create separate components as per review by dj. If you are working on your branch, please feel free to merge this patch to your branch as and when you get time, so that we can work on skeleton framing using loading.

@bogas04 Is anybody working on #12 and #13 still?? If not I would create the components since they are already on the product page.I just have to create the components for them.

@bogas04 should i delete this branch. It is of no use now.


op-node failed to run in --dev mode

Describe the bug
op-node --dev --dev.block-time=5s failed to launch
Steps to reproduce
op-node --dev --dev.block-time=5s failed to launch
Node logs
2024-06-19T15:47:06.529267Z  INFO Starting consensus engine
thread 'tokio-runtime-worker' panicked at crates/evm/execution-types/src/execution_outcome.rs:181:9:
This should not be called in optimism mode. Use `optimism_receipts_root_slow` instead.
stack backtrace:

   0: _rust_begin_unwind
   1: core::panicking::panic_fmt
   2: reth_execution_types::execution_outcome::ExecutionOutcome::receipts_root_slow
   3: <reth_auto_seal_consensus::task::MiningTask<Client,Pool,Executor,Engine> as core::future::future::Future>::poll::{{closure}}
   4: <reth_auto_seal_consensus::task::MiningTask<Client,Pool,Executor,Engine> as core::future::future::Future>::poll
   5: <futures_util::future::select::Select<A,B> as core::future::future::Future>::poll
   6: <tracing_futures::Instrumented<T> as core::future::future::Future>::poll
   7: tokio::runtime::task::core::Core<T,S>::poll
   8: tokio::runtime::task::harness::Harness<T,S>::poll
   9: tokio::runtime::scheduler::multi_thread::worker::Context::run_task
  10: tokio::runtime::scheduler::multi_thread::worker::Context::run
  11: tokio::runtime::context::runtime::enter_runtime
  12: tokio::runtime::scheduler::multi_thread::worker::run
  13: tokio::runtime::task::core::Core<T,S>::poll
  14: tokio::runtime::task::harness::Harness<T,S>::poll
  15: tokio::runtime::blocking::pool::Inner::run
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

seems the optimism feature is not enabled in https://github.com/paradigmxyz/reth/blob/590356b3415cffec09f10189ff0ec006d9447d04/crates/consensus/auto-seal/src/lib.rs#L419-L426
Platform(s)
Mac (Apple Silicon)
What version/commit are you on?
reth Version: 1.0.0-rc.2-dev
Commit SHA: bf6696c52
Build Timestamp: 2024-06-19T03:39:59.989888000Z
Build Features: jemalloc,optimism
Build Profile: release
What database version are you on?
2
Which chain / network are you on?
--dev optimism
What type of node are you running?
Archive (default)
What prune config do you use, if any?
No response
If you've built Reth from source, provide the full command you used
make build-op
Code of Conduct

[X] I agree to follow the Code of Conduct

ugh, I can't wait until we can get rid of all the op stuff...


use react-transform instead of react-hot & fix css-modules composes & add react rules to eslint

notice:

process.env.UV_THREADPOOL_SIZE should set larger!

react-hot will be Deprecated. (react-transform solution do not support pure function component hot loading, but in progress ).

css-modules composes should use sass-loader first.

add some react rules to eslint.

It looks great! Let me test it and I'll merge

Done, great!
Do you have feedback for the documentation?

I like the structure. I will watch it carefully!


yum install broke in version 3.0.1 of cookbook

In the fix to correct an issue with the web.xml file that changed in Rundeck 2.6.10, the default attribute for ['rundeck']['rpm']['version'] was changed to include "rundeck-" in a non-passive manner.  This breaks the yum package resource in recipe::server_install that uses that same attribute for the version to install.

https://github.com/Webtrends/rundeck/pull/107 should correct this.

https://github.com/Webtrends/rundeck/pull/108


In the c# version, after adding conditional compilation custom constants in the project name.csproj file, the fields exported by [Export] cannot be assigned values in the editor, and the existing assignments will disappear after restarting the editor.

Godot version
4.1.2,4.2.beta.2
System information
wiindos11,macos14
Issue description

Steps to reproduce
1,Add conditional compilation custom constants in the project name.csproj file
2,[Export]Exported fields cannot be assigned values in the editor
Minimal reproduction project
N/A

Please post issues and comments in English, we don't all speak Chinese. In case you don't think you can clearly express yourself in English, you can always use something like a online translation service.
发布 Issue 和评论的时候请使用英文，并不是所有人都懂中文。如果你觉得自己无法用英文表达清楚，也可以发机翻后的内容。

Rough TL until the original is edited:
In the C# version, after adding a condition to compile a custom constant in the project name.csproj file, fields exported through [Export] cannot be assigned a value in the editor, and the value disappears after restarting the editor.

1,Add custom constants for conditional compilation in the project name.csproj file.
2, [Export] fields can not be assigned values in the editor.

From the screenshot, it looks like this is a duplicate of https://github.com/godotengine/godot/issues/79839.
You are replacing the constants defined by Godot.NET.Sdk. You need to use <DefineConstants>$(DefineConstants);$(OS);Test</DefineConstants> instead.


add BufBound

Problem
lots of places where we do a lot of error-prone math measuring and pushing into buffers
Summary of Changes
a utility class that encapsulates such

@andy31415 ?

@jelderton @andy31415 ?


Remove Redis (make it optional)

Hi everyone,
I'm planning to remove Redis. I don't want to integrate it natively.
Instead, I prefer make it optional.
TODO:

[x] Update schema.pptx
[ ] Update docker-compose.yml
[ ] Remove redis mention in readme.md
[ ] Add/edit the custom.md file to explain how to add Redis in this stack

Step 1: done.
schema.pptx

Great! Any plans on making ELK optional as well?

@stephanvierkant for your information, I'm working on removing redis. Its almost already done.
Concerning ELK, can you open an other issue please?


object glob found no files

Run npm run build.
Got this:
AssertionError [ERR_ASSERTION]: HtmlWebpackTagsPlugin.options.tags object glob found no files
Here is my webpack plugins config:
new CopyWebpackPlugin([
      { from: path.join(__dirname, 'library/*.js'), to: 'vendors/', flatten: true },
    ]),
...htmlWebpackPlugins,
new HtmlWebpackTagsPlugin({
    tags: [
        {
          append: false,
          path: 'vendors',
          glob: '*.js',
          globPath: path.resolve(__dirname, '../dist/vendors/'),
        },
      ],
 }),

I create a repository.
Here:
https://github.com/IMakiMaki/webpack-learning

OK.It's my fault.I should inject the file in /library instead of the /dist.


Branch 2.0

What changes were proposed in this pull request?
(Please fill in changes proposed in this fix)
How was this patch tested?
(Please explain how this patch was tested. E.g. unit tests, integration tests, manual tests)
(If this patch involves UI changes, please attach a screenshot; otherwise, remove this)
Please review http://spark.apache.org/contributing.html before opening a pull request.

Can one of the admins verify this patch?

@fjh100456 looks mistakenly open. Could you close this please?

Sorry, I made a mistake. I'll close it by now.


Colors do not change

hello, I try to change the accent, accent 2 and background colors, but remain the same, how do I do?

Hi, can you give me more details please?
Which browser do you use?
Do you try to change the colors on the live startpage or in the code?
If you use the live startpage, do you block any javascript or the use of the local storage?
If you try to change the code, what are you doing?


Unhandled rejection when doing event.preventDefault()

Using ui-router 1.0.0 rc1 and stateEvents.js with angular 1.56.
Code:
$scope.$on('$stateChangeStart', (event) => event.preventDefault())
causes error messages to be written to console: 'TransactionRejection(type 3, message: The transition has been aborted, detail: Hook aborted transition)'. I have provided a custom error handler to $state.defaultErrorHandler() that ignores type 3 transition rejections. However, it'd be nice if the built in handler itself ignored type 3 errors.
Regards,
Rostislav.

Should be fixed in rc.2 by b07a24b992aaeb8062e52e32f72f4f70a1e38d98

What's the expected release date for rc.2?

I no longer provide expected release dates because I'm always wrong.


Self contained version of the VRPN client, removing the dependence on eth-asl's version

fixed by #6


Fix hardening guide instructions for k8s config files

Fixes Path (RKE will remove files from /etc/kubernetes)
Mentions extra_binds (required to actually load in these files after they are written to the host)

Should fix https://github.com/rancher/docs/issues/1669, although this is not specific to RancherOS.
Also fixes https://github.com/rancher/docs/issues/1702

@deniseschannon @cloudnautique Please review/merge this when you can.


Add DataFormsJS

Hi @Scrum
I've resolved the conflict.
The link to https://github.com/vuejs/awesome-vue/blob/master/CONTRIBUTING.md from your message is broken because the file doesn't exist.
All the checklist items look good.

Following up I found the missing CONTRIBUTING.md file on another branch:
https://github.com/vuejs/awesome-vue/blob/refactor/CONTRIBUTING.md
It must have been deleted at some point as I find it in earlier branches as well:
https://github.com/vuejs/awesome-vue/blob/4ea433b4e5101ad03caf132f63bd37d976bc1a47/CONTRIBUTING.md

@ConradSollitt Hi, yes I fixed it, thanks


fix: revert chokidar to v3

https://github.com/nuxt/nuxt/issues/29744
https://github.com/vitejs/vite/issues/18527

Revert Chokidar to v3 temporarily (updated in v1.13.0 via #489) due to downstream issues.

won't setting usePolling to true help?

It was a hotfix to avoid ecosystem-wise issues. polling has overhad.


syntax highlighting is broken when using Code and Pre directly instead of ```

import { Pre, Code } from 'nextra/components'

# Another Page

<Pre
  filename="demo.js"
  data-language="js"
  data-theme="default"
  hasCopyCode
>
  {/* {MyComponentSource} */}
  <Code className="language-javascript">
  let a = 1 console.log(a)
  </Code>
</Pre>

```js filename="demo.js" {3} copy
let a = 1

console.log(a)
```

On a side note, how do achieve line highlighting using the jsx component syntax rather than the markdown syntax?

Found a workaround but it is a ton of code! Would love something shorter.
import { MDXRemote } from 'next-mdx-remote'
import { compileMdx } from 'nextra/compile'
import { useSSG } from 'nextra/ssg'
import { useMDXComponents } from 'nextra/mdx'

export const getStaticProps = async () => {
  // const response = await fetch('https://raw.githubusercontent.com/shuding/nextra/main/README.md')
  // const markdown = await response.text()
  const mdx = await compileMdx(['```js {3,5-8}' ,MyComponentSource ,'```'].join('\n'), { defaultShowCopyCode: true }) // 2
  return {
    props: {
      ssg: mdx.result // 3
    },
    // Revalidate at most once every 1 hour
    revalidate: 60 * 60
  }
}

import MyComponentSource from '!!raw-loader!../test.ts'

export const NextraReadme = () => {

  const compiledSource = useSSG() // 4
  const components = useMDXComponents()
  return <MDXRemote compiledSource={compiledSource} components={components} /> // 5-6
}

<NextraReadme />

there is no mention that syntax highlighting will work with Pre and Code elements
Nextra use Shiki that do syntax highlighting at the build time
https://nextra.site/docs/guide/syntax-highlighting#with-dynamic-content

It's not highlighted because it's not processed by shiki, only markdown code blocks are processed by shiki

Ah I see. What would you recommend to achieve the desired effect of highlighting code inside Pre? The use case is i'm using raw-loader to load a .ts file from disk and want to put it inside a code block but unable to put it inside the triple backtick directly because there are no interpolation possible.  That's why I'm trying to use Pre inside but running into the issue where Pre doesn't highlight.

maybe you are looking for https://github.com/kevin940726/remark-code-import (didn't tried with nextra but should works I guess)

you need to pass this plugin in similar way as I described in this page https://nextra.site/docs/guide/advanced/table#setup

Confirmed that the remark-code-import plugin works! Thanks!


Action Groups have moved

Action Groups are no longer their own blade and are found under the Monitor > Alerts blade. "Configure email notifications" section should be updated to reflect such.

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

ID: 225c9d05-83dd-b006-0025-3753f5ab25bf
Version Independent ID: 9eecef0c-b1cb-1136-faf7-542214492096
Content: Start/Stop VMs during off-hours solution
Content Source: articles/automation/automation-solution-vm-management.md
Service: automation
Sub-service: process-automation
GitHub Login: @bobbytreed
Microsoft Alias: robreed

Thanks for your comment. The feedback has been shared with the content owner for further review. Thanks for your patience.

@geekbrownbear - My apologies for the lack of timely response to your feedback.  You're correct the experience has changed in the portal and the article needs to be updated to align with the behavior of managing Action Groups in Azure.  I'm going to create a work item for this article and will update it this sprint or next month's sprint the latest.  Thank you for your patience.  #please-close.


Micropython bindings: LCD breakout - line and triangle drawing primitives fail silently

When using 'display.line' and 'display.triangle' micropython methods, these fail silently (nothing get drawn on the display), while 'display.circle' works. Tested with 'BreakoutRoundLCD' class and round LCD.
current behavior: using 'line' and 'triangle' methods renders nothing on the display
expected behavior: line and/or triangle gets drawn in the display (depending on the method used)

I have digged into the issue a little and the result is the following pull request:
https://github.com/pimoroni/pimoroni-pico/pull/344
A few unrelated notes:

there may be different ordering of R, G, B channels for the different micropython classes for the various displays (or it's a C/C++ or hardware difference) - cannot check that as I don't have the rectangular LCDs.
the error seems simple enough to fix, tests should (if they existed) have discovered the problem much sooner.

Fixed in main branch by merging https://github.com/pimoroni/pimoroni-pico/pull/344 .

Closing as I think this is now merged in and sorted - yell if not :)


Upgrade SpaCy version requirement

Type of Issue
Select the type of issue:

[x] Bug report (to report a bug)
[ ] Feature request (to request an additional feature)
[ ] Tracker (I am just using this as a tracker)

Current Behavior
When I ran pip install -r requirements.txt, it errored out while installing spacy's dependency thinc with the error:
l/miniconda3/envs/droidlet/include/python3.6m -c include/_cuda_shim.cu -o build/temp.linux-x86_64-3.6/include/_cuda_shim.o -arch=sm_30 --ptxas-options=-v -c --compiler-options '-fPIC'
  nvcc fatal   : Value 'sm_30' is not defined for option 'gpu-architecture'

The reason is that this old version of spacy/thinc aren't yet supporting CUDA 11.
We should upgrade the requirement if possible.
Expected Behavior
SpaCy/ThinC get installed smoothly
Steps to reproduce
On a machine with CUDA 11 activated, do pip install -r requirements.txt from the droidlet root directory.

The workaround that I had to use was conda install spacy==2.0.12 -c conda-forge which I believe precompiles ThinC without GPU support

The workaround that I had to use was conda install spacy==2.0.12 -c conda-forge which I believe precompiles ThinC without GPU support

Just cloned the repo from scratch and installed the requirements inside a conda env. Confirming that this version works with the assistants.

Just cloned the repo from scratch and installed the requirements inside a conda env. Confirming that this version works with the assistants.

it works if you activate a CUDA older than CUDA 11 on your machine (like your devfair).
On a machine where you have CUDA11 installed and thinc (spacy's dependency) detects it, it will fail to build with the above error.

it works if you activate a CUDA older than CUDA 11 on your machine (like your devfair).
On a machine where you have CUDA11 installed and thinc (spacy's dependency) detects it, it will fail to build with the above error.

Thanks!
I checked again and here's my nvidia-smi :

and I did not do : module load cuda/10.2 for example.
I can try reproducing this again from scratch to confirm and paste exact steps here.

Thanks!
I checked again and here's my nvidia-smi :

and I did not do : module load cuda/10.2 for example.
I can try reproducing this again from scratch to confirm and paste exact steps here.

I'm able to reproduce this issue in my machine (cuda version: 11.0).
nvcc --version:

Steps to repro:
module load cuda/11.0
git clone --depth=1 --recursive https://github.com/facebookresearch/droidlet.git
cd droidlet
conda create -n droidlet_env python==3.7.4 pip numpy scikit-learn==0.19.1 pytorch torchvision
conda activate droidlet_env
pip install --no-cache-dir -r craftassist/requirements.txt

The trick here is to use --no-cache-dir to disable pip install cache. If so, install spacy/thinc will fail given cuda version >=11.0

I'm able to reproduce this issue in my machine (cuda version: 11.0).
nvcc --version:

Steps to repro:
module load cuda/11.0
git clone --depth=1 --recursive https://github.com/facebookresearch/droidlet.git
cd droidlet
conda create -n droidlet_env python==3.7.4 pip numpy scikit-learn==0.19.1 pytorch torchvision
conda activate droidlet_env
pip install --no-cache-dir -r craftassist/requirements.txt

The trick here is to use --no-cache-dir to disable pip install cache. If so, install spacy/thinc will fail given cuda version >=11.0


Request: mark Nicholas items in item hover info

I would find it useful if I didn't have to look up every new trophy drop on the wiki to see if I should keep them or sell/salvage them.

#995 related and possibly #994

Oops, thanks!


Feat: treesitter-context integration

I'd like to add treesitter-context integration since the defaults make text very confusing.
I've added 2 variants: brighter than background and darker.

Names of options to toggle style are up to debate.

What I mean by 'confusing' is that M.defaults = { line is actually 29 lines higher than it looks:


Add "verified" flag to paper records

Add a binary "verified" flag to paper records. This flag should be set when the record for the paper is created.
When the details are entered through the interface, the flag should be FALSE
We will use this flag later to mark papers that come from moderated sources, like arXiv (once we put the integration in place)

We already have "isVerified" flag for each paper. It is a boolean value default to be false

Perfect


feat: Adds link to @Tythe in readme

Would resolve https://github.com/sqfmi/watchy-cases/issues/30 if merged

@sqfmi do you need anything else to merge this pull request?


Merging development back to master

Coverage increased (+0.01%) to 99.57% when pulling<PHONE_NUMBER>a7301d9bdd8442a4f61eb68809d3a5 on development into 256b1d79c3802a5fa9a31dafb88deec70ea87ed6 on master.

Coverage increased (+0.01%) to 99.57% when pulling<PHONE_NUMBER>a7301d9bdd8442a4f61eb68809d3a5 on development into 256b1d79c3802a5fa9a31dafb88deec70ea87ed6 on master.

Coverage decreased (-0.06%) to 99.49% when pulling d15c6b910378659117faad60fd49a3f63013de2f on development into 256b1d79c3802a5fa9a31dafb88deec70ea87ed6 on master.

Coverage decreased (-0.06%) to 99.49% when pulling cae4a6d32c58259eca092f1780f6324df7d4a694 on development into 256b1d79c3802a5fa9a31dafb88deec70ea87ed6 on master.


Use MRI Ruby

I can't let you do that Dave.
The code in this gem is intended for JVM threads. Be careful that there
aren't untested perf implications.
On Wed, 17 Feb 2016 at 13:48, David Blooman<EMAIL_ADDRESS>wrote:

You can view, comment on, or merge this pull request online at:
https://github.com/BBC-News/alephant-sequencer/pull/12
Commit Summary

Use MRI Ruby

File Changes

M .gitignore
https://github.com/BBC-News/alephant-sequencer/pull/12/files#diff-0
(1)
M .ruby-version
https://github.com/BBC-News/alephant-sequencer/pull/12/files#diff-1
(2)
M Gemfile
https://github.com/BBC-News/alephant-sequencer/pull/12/files#diff-2
(2)
M Guardfile
https://github.com/BBC-News/alephant-sequencer/pull/12/files#diff-3
(4)
M Rakefile
https://github.com/BBC-News/alephant-sequencer/pull/12/files#diff-4
(6)
M lib/alephant/sequencer.rb
https://github.com/BBC-News/alephant-sequencer/pull/12/files#diff-5
(1)
M lib/alephant/sequencer/sequence_table.rb
https://github.com/BBC-News/alephant-sequencer/pull/12/files#diff-6
(103)
M lib/alephant/sequencer/sequencer.rb
https://github.com/BBC-News/alephant-sequencer/pull/12/files#diff-7
(6)
M spec/sequencer_spec.rb
https://github.com/BBC-News/alephant-sequencer/pull/12/files#diff-8
(21)
M spec/spec_helper.rb
https://github.com/BBC-News/alephant-sequencer/pull/12/files#diff-9
(3)

Patch Links:

https://github.com/BBC-News/alephant-sequencer/pull/12.patch
https://github.com/BBC-News/alephant-sequencer/pull/12.diff

—
Reply to this email directly or view it on GitHub
https://github.com/BBC-News/alephant-sequencer/pull/12.

@kenoir I will rewrite it then.  What do you think the performance gains were from using JRuby over MRI?

Avoiding the GIL.
Native Ruby does not do multi-threading well, meaning you lose some of the benefit of multi-core systems which is basically all of them. This gem is using a mutex which I wouldn't expect unless something is using it in a threaded fashion.

Did you ever do any benchmarks, maybe it is a time to see how fast 2.3 is Vs JRuby

Meh, probably but I don't remember the outcome now (or have anything I can find).
http://www.isrubyfastyet.com/
Notice JRuby is fastest (by a tiny bit for rails requests) but has by far the bigger memory footprint and startup time. You might be better off switching to MRI if the performance in your case isn't compromised.

I'd assume that without the mutex, even we the GIL, there would be concerns about operation access because there's still non-deterministic behaviour (e.g. concurrency; process switching still occurs with the GIL) so it's likely the mutex should stay even with MRI, I guess?
I don't think we have many concerns regarding performance per se, but it's definitely something that should be benchmarked.
Dave's going to switch to latest JRuby as a precaution for now. But we'll look to move to MRI if things prove to be consistent

I'd assume that without the mutex, even we the GIL, there would be concerns about operation access because there's still non-deterministic behaviour (e.g. concurrency; process switching still occurs with the GIL) so it's likely the mutex should stay even with MRI, I guess?

I'd think so.


Lpal xxx fix build - 2cnd attempt

Purpose
Make locust tests not stop the build - second attempt
Approach
mods to github actions
Checklist

[x] I have performed a self-review of my own code
[ ] I have updated documentation (Confluence/GitHub wiki/tech debt doc) where relevant
[ ] I have added tests to prove my work
[ ] I have added mandatory tags to terraformed resources, where possible
[ ] If I have a new OPG component dependency, I have updated the metadata.json with the repo location.
[ ] If I added a package.json or composer.json, I also made sure this is included in the script in .github/workflows/dependabot-update.yml
[ ] The product team have tested these changes

PR seems to be broken


Template source code generated for a proxy service contains <outSequence>

Description:
The use of <outSequence> is deprecated and the generated code for a proxy contains the <outSequence> in it.

Follow this on: https://github.com/wso2/mi-vscode/issues/73


--vscode-multiDiffEditor-headerBackground exists but not applied to elements

Does this issue occur when all extensions are disabled?: Yes

VS Code Version:  1.86.0
OS Version: Fedora Linux 39

Steps to Reproduce:

Assign a color to multiDiffEditor.headerBackground theme token.
Observe that diff editor headers don't even use that token.

The theme color token multiDiffEditor.headerBackground doesn't seem to be used at all in the current VS Code version.
Current behaviour

Expected behaviour, after modifying background-color attribute

When I implement my custom vscode theme, I found that the diffEditor.unchangedRegionBackground color attach the property of  multiDiffEditor.headerBackground!

I hope it is helpful to fix the bug :)
I'm sorry if you already knew it.

It's fixed in the recent releases.


npm install issue

npm install fails for me (Ubuntu 15.04):
…
npm http 304 https://registry.npmjs.org/view-list
npm http 304 https://registry.npmjs.org/leveldown
npm http 304 https://registry.npmjs.org/raf
npm ERR! notarget No compatible version found: leveldown@'maxogden/leveldown#newnan'
npm ERR! notarget Valid install targets:
npm ERR! notarget ["0.0.0","0.0.1","0.0.2","0.1.0","0.1.1","0.1.2","0.2.0-b00","0.2.0-b01","0.2.0-b02","0.1.3","0.1.4","0.2.0","0.2.1","0.3.0","0.3.1","0.4.0","0.4.1","0.2.3","0.4.2","0.4.3","0.4.4","0.2.4","0.5.0","0.6.0","0.6.1","0.6.2","0.7.0","0.8.0","0.8.1","0.8.2","0.8.3","0.9.0","0.9.1","0.9.2","0.10.0","0.10.1","0.10.2","1.0.0","1.0.1","0.10.3","0.10.4","1.0.2"]
npm ERR! notarget
npm ERR! notarget This is most likely not a problem with npm itself.
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.

npm ERR! System Linux 3.19.0-15-generic
npm ERR! command "/usr/bin/node" "/usr/bin/npm" "install"
npm ERR! cwd /home/jan/friends/app
npm ERR! node -v v0.10.28
npm ERR! npm -v 1.4.9
npm ERR! code ETARGET
npm http 304 https://registry.npmjs.org/node-gyp
npm http 304 https://registry.npmjs.org/autolinker
npm http 304 https://registry.npmjs.org/webrtc-swarm
npm http 304 https://registry.npmjs.org/subleveldown
npm http 304 https://registry.npmjs.org/virtual-dom
npm http 304 https://registry.npmjs.org/cat-names
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     /home/jan/friends/app/npm-debug.log
npm ERR! not ok code 0

npm ERR<EMAIL_ADDRESS>install: `cd app && npm install`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script.
npm ERR! This is most likely a problem with the friends package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     cd app && npm install
npm ERR! You can get their info via:
npm ERR!     npm owner ls friends
npm ERR! There is likely additional logging output above.
npm ERR! System Linux 3.19.0-15-generic
npm ERR! command "/usr/bin/node" "/usr/bin/npm" "install"
npm ERR! cwd /home/jan/friends
npm ERR! node -v v0.10.28
npm ERR! npm -v 1.4.9
npm ERR! code ELIFECYCLE
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     /home/jan/friends/npm-debug.log
npm ERR! not ok code 0

Relevant parts of the debug log:
…
558 verbose addNamed [ 'raf', '2.0.4' ]
559 verbose addNamed [ '2.0.4', '2.0.4' ]
560 silly lockFile dc0b33b6-raf-2-0-4<EMAIL_ADDRESS>561 verbose lock<EMAIL_ADDRESS>/home/jan/.npm/dc0b33b6-raf-2-0-4.lock
562 error notarget No compatible version found: leveldown@'maxogden/leveldown#newnan'
562 error notarget Valid install targets:
562 error notarget ["0.0.0","0.0.1","0.0.2","0.1.0","0.1.1","0.1.2","0.2.0-b00","0.2.0-b01","0.2.0-b02","0.1.3","0.1.4","0.2.0","0.2.1","0.3.0","0.3.1","0.4.0","0.4.1","0.2.3","0.4.2","0.4.3","0.4.4","0.2.4","0.5.0","0.6.0","0.6.1","0.6.2","0.7.0","0.8.0","0.8.1","0.8.2","0.8.3","0.9.0","0.9.1","0.9.2","0.10.0","0.10.1","0.10.2","1.0.0","1.0.1","0.10.3","0.10.4","1.0.2"]
562 error notarget
562 error notarget This is most likely not a problem with npm itself.
562 error notarget In most cases you or one of your dependencies are requesting
562 error notarget a package version that doesn't exist.
563 error System Linux 3.19.0-15-generic
564 error command "/usr/bin/node" "/usr/bin/npm" "install"
565 error cwd /home/jan/friends/app
566 error node -v v0.10.28
567 error npm -v 1.4.9
568 error code ETARGET
569 verbose exit [ 1, true ]

@jancborchardt try using node v0.12 or iojs

yes you need newest iojs and npm

will add a node in readme

oh nm already there :+1:

:+1: thanks Max!


Simplify KStream Indexing Process

For the indexing that happens on the consuming side of Surge using KStreams to populate a KTable of aggregate states we had a concept of a "validation processor" which would allow an app to raise warnings based on comparing an old aggregate state to the newly discovered one (essentially determine if the state transition was an expected on on the KStreams side of things).  In theory and when initially testing the framework this is useful for continuously validating we're not seeing any corruption in the event stream - for example using sequence numbers to determine if something went backwards in time. In practice, however, this hasn't really proved to be all that useful since we've hardened the framework to the point where we never see any of these warnings based on app validation.
Even though this feature is theoretically useful, in order to grab the previous state for comparison and not need a changelog topic & duplicate data specifically for that we were extending a class internal to Kafka which pretty tightly couples Surge to the particular version of Kafka that we use rather than being flexible.  Because we're not really leveraging this anyways, this trade-off is really not something that's worth it given the fragility it introduces.

this is useful for continuously validating we're not seeing any corruption in the event stream - for example using sequence numbers to determine if something went backwards in time. In practice,

I like this idea and it could also be implemented as some sort of micro-service that sits outside the Surge apps and scans Kafka Topics used by Surge apps for corruption. What do you think ?

That makes a lot of sense to me! We could add a small utility to help with that sort of thing. It could be embedded alongside the command app (self validating in the background) or could be added to a completely separate micro-service outside of the command app specifically used for validation

Codecov Report

Merging #25 (1239da4) into main (065fd44) will decrease coverage by 0.08%.
The diff coverage is 85.71%.

@@            Coverage Diff             @@
##             main      #25      +/-   ##
==========================================
- Coverage   77.24%   77.16%   -0.09%
==========================================
  Files         162      160       -2
  Lines        2896     2855      -41
  Branches       71       72       +1
==========================================
- Hits         2237     2203      -34
+ Misses        659      652       -7

Impacted Files
Coverage Δ

...n/scala/surge/core/command/SurgeCommandModel.scala
55.00% <ø> (+0.45%)
:arrow_up:

.../core/commondsl/SurgeEventBusinessLogicTrait.scala
0.00% <ø> (ø)

...ore/commondsl/SurgeGenericBusinessLogicTrait.scala
100.00% <ø> (ø)

...cala/surge/core/event/SurgeEventServiceModel.scala
0.00% <ø> (ø)

...ore/src/main/scala/surge/internal/SurgeModel.scala
100.00% <ø> (ø)

...a/surge/internal/domain/SurgeMessagePipeline.scala
88.46% <ø> (-0.22%)
:arrow_down:

...rge/javadsl/common/DefaultAggregateValidator.scala
0.00% <ø> (ø)

...ge/scaladsl/common/DefaultAggregateValidator.scala
0.00% <ø> (-100.00%)
:arrow_down:

...a/streams/SurgeKafkaStreamsPersistencePlugin.scala
69.23% <66.66%> (-5.77%)
:arrow_down:

...afka/streams/AggregateStateStoreKafkaStreams.scala
81.57% <100.00%> (ø)

... and 4 more

Continue to review full report at Codecov.

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


🔧 generate figma variables without z-index, containers, typography

https://github.com/baloise/design-system/issues/1022

/cib

done with v16


Corrected Card resting elevation, tabs example toolbar

Fixes https://github.com/flutter/flutter/issues/411

LGTM


[Schema Change] <Shopify API Update 2022>

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the issue
I have received information that Shopify has made some updates related to changing the schema of some tables, including the Shopify customers table (as shown in the figure below).

I have checked the new ERD and found that the deprecated columns are still there and it does not affect the operation of the current dbt_shopify  too seriously. However, I want to update my data pipeline (using the dbt_shopify package) according to the latest updates, specifically update this mapping relation in shopify_customer table:

email_marketing_consent_state --> has_accept_marketing

instead of

accept_marketing -->has_accept_marketing

as I am seeing here https://github.com/ fivetran/dbt_shopify_source/blob/main/macros/staging_columns.sql.
Relevant error log or model output
No response
Expected behavior
Update this mapping relation in shopify_customer table:

email_marketing_consent_state --> has_accept_marketing

instead of

accept_marketing -->has_accept_marketing

dbt Project configurations
name: 'fivetran_shopify'
version: '1.0.0'
config-version: 2
Package versions
packages:

package: fivetran/shopify
version: [">=0.6.0", "<0.7.0"]

What database are you using dbt with?
bigquery
dbt Version
None
Additional Context
No response
Are you willing to open a PR to help address this issue?

[ ] Yes.
[X] Yes, but I will need assistance and will schedule time during our office hours for guidance
[ ] No.

hey there! so i am currently working on updates to the Shopify package that i believe capture what you're looking for.
the mapping occurs on this branch here -- what do you think? @manhitv

Oh thanks @fivetran-jamie. It looks like my problem will be solved immediately after the update but the output table schema will be changed a little (from has_accept_marketing to marketing_consent_state), isn't it?
May I know when there is a new version so I can update?
Thank you in advance.

yes and yes! will ping you hear when it's live

Thank you so much, @fivetran-jamie.


Blr automation team

merging ci improvement files

@desaimg1, Please update with highlights of work done in this PR.


SR-3467: double closing of a file descriptor from openpty

@swift-ci please test

Awesome, thanks!


git clone failed when running npm run publish-gh-pages

🐛 Bug Report
Following the tutorial
When I try and run GIT_USER=user CURRENT_BRANCH=master npm run publish-gh-pages,
I see the following error:
> docusaurus-publish

master
git@github.com:repo/docs.git
generate.js triggered...
feed.js triggered...
feed.js triggered...
sitemap.js triggered...
Site built successfully. Generated files in 'build' folder.
f6ab0b98e79cdd2fd08ad37ae4a8f754b82a88b7
fatal: Too many arguments.
Error: git clone failed

The issue is same as https://github.com/facebook/docusaurus/issues/2258
However, this is seen on Mac and the workaround mentioned there doesn't work.
Have you read the Contributing Guidelines on issues?
Yes
To Reproduce
(Write your steps here:)

Follow the documentation: https://docusaurus.io/docs/en/tutorial-publish-site
Run GIT_USER=niks3089 CURRENT_BRANCH=master npm run publish-gh-pages

Expected behavior
The site should be live on github pages
(Write what you thought would happen.)
Actual Behavior
The deployment failed
(Write what happened. Add screenshots, if applicable.)
Your Environment

Node v10.22.1
MacOs 10.15.5

Hi
This part. look suspicious to me: git@github.com:repo/docs.git
are you sure your config file has the required fields?
Otherwise we might try to clone a bad  repo, we can't guess the repo URL to clone if we don't have the  needed config  infos

Closing the issue since the repo was private. Changing to public fixed the problem.


Prevent accidental BTC retrieval from taproot: halt showing uninscribed BTC when there are pending incoming transactions to a taproot address

We show this, and a warning and advice to check every UTXO to make sure there are no inscribed sats with them before retrieving.

Sometimes these are ignored/missed and users still retrieve UTXO's with inscriptions to their bitcoin address. This enhancement can help prevent that by not showing uninscribed BTC until all pending transactions to the taproot address (likely ordinal deposits) are handled.
When transactions are not confirmed the UTXO's can falsely show as uninscribed.

Dupe of #4513


METRON-1365: Allow PROFILE_GET to return a default value for a profile and entity that does not have a value written.

Contributor Comments
Right now the profiler is a sparse system, namely if data is not written during a profile period for a given profile and entity, no values are written to HBase. Some algorithms may need non-sparse data (e.g. time series outlier detection algorithms). We should keep the default behavior as it stands, but allow the user at read time to specify a default value. This is most cleanly done by using the existing profiler config overrides (the 4rd argument to PROFILE_GET) and adding a profiler.default.value.
You should be able to validate this in the REPL in full-dev by running:
PROFILE_GET('profile1', 'entity1', PROFILE_FIXED(4, 'HOURS'), { 'profiler.default.value' : 'metron'} )

You should see a list of strings with 16 or 17 copies of metron in it.
If you run it without the overrides, you should see an empty list returned.
Pull Request Checklist
Thank you for submitting a contribution to Apache Metron.
Please refer to our Development Guidelines for the complete guide to follow for contributions.
Please refer also to our Build Verification Guidelines for complete smoke testing guides.
In order to streamline the review of the contribution we ask you follow these guidelines and ask you to double check the following:
For all changes:

[x] Is there a JIRA ticket associated with this PR? If not one needs to be created at Metron Jira.
[x] Does your PR title start with METRON-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
[x] Has your PR been rebased against the latest commit within the target branch (typically master)?

For code changes:

[x] Have you included steps to reproduce the behavior or problem that is being changed or addressed?

[x] Have you included steps or a guide to how the change may be verified and tested manually?

[x] Have you ensured that the full suite of tests and checks have been executed in the root metron folder via:
mvn -q clean integration-test install && build_utils/verify_licenses.sh

[x] Have you written or updated unit tests and or integration tests to verify your changes?

[x] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

[ ] Have you verified the basic functionality of the build by building and running locally with Vagrant full-dev environment or the equivalent?

For documentation related changes:

[x] Have you ensured that format looks appropriate for the output in which it is rendered by building and verifying the site-book? If not then run the following commands and the verify changes via site-book/target/site/index.html:
cd site-book
mvn site

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.
It is also recommended that travis-ci is set up for your personal repository such that your branches are built there before submitting a pull request.

Thanks for the review, @nickwallen I reacted to your comments. :)

+1 Looks great.


Send transaction command

Summary of work done:

Add a send-transaction command to enable sending transactions to casper networks via JSON-RPC

Areas of note for reviewers:

This PR deals with adding the send-transaction command, and fixing a runtime error that resulted from the structuring of clap commands and the generic parsing of arguments that were, in some cases, not bound to the command. This should be fixed and will prevent users from overriding runtime args generated for some transactions by the transaction builder.

Sample command input/output used when testing after development:
casper-client send-txn --transaction-path ~/casper/keys/client-dev/output_transactions/add_bid/add-bid-transaction -n http://localhost:11101/rpc

Associated output:
{
  "jsonrpc": "2.0",
  "id": -339623264891894255,
  "result": {
    "api_version": "2.0.0",
    "transaction_hash": {
      "Version1": "83efb7a61934987b788626f011e09e0394fe2910cef28b2b85aa7af2edd0fbf5"
    }
  }
}

Associated ticket(s):

#122
Client send-transaction command and backend fixes

I did not see tests but I let you manage coverage.


place kitten fix

placekitten.com/360/360 doesn't seem to work for me. 420/420 works however.

Sorry this took so long, fell under the radar. Merged in! Thanks for the fix.

You're welcome


angular-faye is not being injected

I've added angular-faye as a dependency to my proyect and installed bower, but the js file is not being injected.
The generated .bower.json file does not have a "main" property, so it does not know what to inject.
I've noticed there is a package.json file, but not a bower.json file. Why is that? From the comment of the commit 112635292b4edc246069345a9c93bb66d3c3717b I think that the project was converted to bower.

tried to install via bower but got NOT FOUND. would be ice to get this in bower form