Add Bybit datasource

Contribute a data source to the pricefeeder repo task completion for
https://nibiru.explorers.guru/validator/nibivaloper1lu60y3tjksx4srzuymrxunlp7439hda4vmnz9c

@burninxxx, please email us from the email address associated with your GitHub account so that we can tie together this profile to the one that completed on-chain tasks.

Send it do<EMAIL_ADDRESS>Use subject  ITN Dev Contribution
Include a screenshot of yourself logged in to GitHub.
Include your Discord ID
Include the nibi address you used

Superseded by https://github.com/NibiruChain/pricefeeder/pull/39
All credit goes to @burningxxx


Fix the gender of a French "variable" :)

Thank you very much; I've also given you a commit bit so that in future you can patch the tests directly.


shard durations should be as long as feasible in most cases

URL for relevant page?
http://docs.influxdata.com/influxdb/v1.0/concepts/schema_and_data_layout/
1w is a default but doesn't work for many use cases.
set the shard duration to 2x your longest typical query range
try to have at least 100k points per shard, and at least 1000 points per series

compression will be better
fixed iterator overhead per shard, the fewer
writes are faster

Durations of 50y+ are fine, dropping data is the reason to have shorter durations.

@rkuchan this is the next project we need to do. Between OSS users and commercial support, we're getting 2-3 users a day who have problems because their shard durations are far too short. Usually 24h shards on a six month retention, or similar.


fix for bug 626 - Spotify customization variables

Fix for Spotify customization variables SOUND_SPOTIFY_DISABLE_NORMALISATION and SOUND_SPOTIFY_ENABLE_CACHE. Now the variables can be defined and have no value and work correctly.
Closes: https://github.com/balena-labs-projects/balena-sound/issues/626

Nice, thanks!
It looks like the script in this container is run by bash though:
CMD [ "/bin/bash", "/usr/src/start.sh" ]
So the shebang would be:
#!/usr/bin/env bash
With the correct shebang in place, you can then paste the whole script in to this awesome tool to take care of any other syntax: https://www.shellcheck.net

Thanks for reviewing and pointing me to shellcheck.net, @maggie0002! Great resource.
I've updated the code based on your comments, rebased, and pushed.

Looks good to me, thanks.
Have you been able to test it all? I am not able to on my end, but if you are happy with the fix and to take the wrath of the balenaSound community then I will go ahead and merge.

Closes: https://github.com/balena-labs-projects/balena-sound/issues/626
lgtm

@maggie0002 - I've tested it on two devices with all variable permutations and had no issues. I'd rather not face the wrath ;)
I haven't added a fix for #620 but I imagine it's a similar fix. I can have a look after this is merged in. Thanks for reviewing!

I'd rather not face the wrath

Merges only impact new deploys, not old ones, so it's relatively low risk in the sense we can always go back if someone raises an issue. 👍

Hello, did this end up fixing #620 or has there been a fix for #620?
It's quite important to me since I'm trying to run the software on the Pi Zero and without the possibility to disable all these services the Pi is not powerful enough.


chore: add IsROrC.toDecidableEq

We already have noncomputable DecidableEq instances for Real and Complex; putting them here too reduces friction in code generalized to IsROrC K.

Thanks!
bors r+


Write to SD card: how to?

Hi,
Thanks for sharing your great work.
How can we have the mjpeg file on the sdcard?
I tried with below steps:

inserted a sdcard
turned on the esp
On monitor, it shows the expected output
wait a few seconds
turn off the esp
checking the sd card, but no files created.

(Not related but, is there any chance to use your logic to have better FPS to be sent to a browser/video program?)
Thanks in advance,

Hi, recording is started from the ground station. There is a window with various controls - quality, resolution, etc, and a button to start recording. When started, the big white LED will flash (if using the Ai Thinker camera board).
Make sure you stop recording before removing the sdcard, otherwise the file will not be closed properly and you'll not get the video.


无法用https://github.com/Chimeejs/chimee js 播放器播放本项目的http-flv

When you meet a bug, please open the issue including a title prefixed by '[bug]' and describe it as follows:
Expected behavior
Actual behavior
Steps to reproduce the behavior

OBS，VLC和flv.js都已经测试支持本模块推送的HTTP-FLV流，不打算兼容不太常见的播放器，如果你想支持，可以自行修改


Stream results

Is it possible to have the implementation returns each row using yield rather than filling a List in memory and returning that?
This would really help me out as I am working with very large excel files.

I've been tinkering with streaming in my laziness branch over here.
You can set Lazy to true on ExcelQueryFactory in order to bypass the default behavior, which used ToList() to bring everything into memory.
I haven't yet put together a PR because I'll want to build some tests around it, but preliminary ad-hoc testing seems ok.
Comments and suggestions are welcome!

I've had success running my laziness experiment for a few months, so I've opened a PR here: https://github.com/paulyoder/LinqToExcel/pull/155


add xquad_r dataset

looks like this PR includes changes in many files than the ones for xquad_r, could you create a new branch and a new PR ?

Sure, I will close this then.


Minimal changes for Material with AppCompat

This is minimal change PR for moving to using Material via the AppCompat library.
There's lots more we can do here - but this is both usable and a step in the right direction.
Main changes:

Using v7 ActionBar
K9ListActivity now implements the List functionality and extends K9Activity.
A few action bar actions are now 'ifRoom' instead of 'always so that there's space for the account name on the Folder list

Screenshots:
https://photos.app.goo.gl/0NoJuo75jkh5U9Tw2

Hey @philipwhiuk -- I got a little carried away with the stuff I was doing for my Chromebook and kept going with this.  I won't submit it officially because yours is already here, but for reference if you want to incorporate any of it, please feel free.  It's basically what you were doing, just w/a few more XML files and the dialogs and a few other things-- it's meant to go over my Android Studio 3.1 commit #3159.  I'll add a note there too in case anyone wants it.
Material with AppCompat (building on commit from @philipwhiuk)

Closing in favour of PR from K-9 repository.


Removed webpack build warnings… no more walkDecls

This commit was just a dep change, and is included in #44. Closing in favor of that PR>


Update DG for Logic & Find

Not much to change for Logic diagrams/descriptions since the basic structure is largely unchanged from AB3

Apologies, accidentally made a PR to the upstream repo!


UI improvements for sorting on Columns

Tell us where you are using Dejavu (Hosted web app, Chrome extension, Docker Image, Within appbase.io)
appbase.io
What is the version of Dejavu that you are using?
1.2
Describe the issue that you are seeing, or the feature request :-), include any screenshots as necessary.
The sort icons should be more expressive and change depending on the sort order. The sort action should only be allowed on fields which give predictable results eg - not on boolean, geo_point, geo_location or string or text field having no sub-field with a not_analyzed index

Resolved in https://github.com/appbaseio/dejavu/commit/b1f34db2d254233cbdd2b47899c39badd2e15eb1 https://github.com/appbaseio/dejavu/commit/c93a40bb50f690fe5380ceb865deab5a94bf88d7 https://github.com/appbaseio/dejavu/commit/a26e8fa4c2f44a06aa567cc357b206b93a5cb634 https://github.com/appbaseio/dejavu/commit/c157551d7d59a237d54f560a4620340f17381768 https://github.com/appbaseio/dejavu/commit/794ee3866dc512514bd001bb010ffc6eb925f2bc


React 16 lifecycle errors appearing in a React 15 project

I'm getting react/no-deprecated componentWillReceiveProps errors in a React 15 project 😢

Build log: https://travis-ci.org/swagger-api/swagger-ui/builds/378016142#L506
<EMAIL_ADDRESS><EMAIL_ADDRESS>

https://github.com/swagger-api/swagger-ui/blob/d256ae87d310b40fb9fd5cc52ec2aa7db55b28ca/.eslintrc Doesn’t specify a react version pragma, so as far as eslint is concerned, it’s a React 16.3 project.
If you specify your react version, you’ll get appropriate error messages.

Thanks @ljharb, I wasn't aware of the pragma setting!
From my perspective, having my linter (and therefore, my build) break due to a changing default in this plugin was not a fun thing to discover. I do see that the plugin documents its changing default React target version (React version, default to the latest React stable release).
Perhaps a warning if a pragma is not present would provide a better experience than finding out the hard way when something like this happens?

Adding a warning for that sounds like a great idea.

We have faced same error messages with react 16.2. Adding react version to .eslintrc file fixed the problem.
{
...
  "settings": {
    "react": {
      "version": "16.2.0"
    },
  }
...
}

Adding the react version is good to know, however like @shockey said, this isn't great behaviour. Ideally, any rules that are modified to break where they didn't before should be breaking changes rather than something that gets picked - usually automatically with a minor bump

@alasdairhurst there's always cases, however, where that constitutes a bugfix - ie, the bug was "it wasn't warning" and now it is.


Sequencer API impl: zk & standalone redis

What would you like to be added:
Add Sequencer API component: zk & standalone redis
See #108
Why is this needed:

This task will be assigned to @ZLBer


Introduction to plain language: remove June 20 course

The page lists all offerings of the course through the end of June. This issue is to:

Remove the June 20 course once it has taken place
Add any new course offerings. If none, remove this page.

Page removed and associated edits made.


Add DecorationMaster

i need to know that you have an OK from both Mickely (DeathCounter) and sawyer (DecorationMaster). Can't just blindly add ports of mods without the original authors approval.

emmm,sawyer approve me to do that,but I havent get Mickely approval,sorry for that.

DeathCounter was actually added in #78

emmm,sawyer approve me to do that,but I havent get Mickely approval,sorry for that.


不能正常解析

Contents.zip

不能正常解析，报错如上图。其他工具可以解析，文件格式没有问题。

Please post your problem in English.

Can not be resolved normally, error as shown in the above figure. Other tools can parse, file format no problem.

Please post your problem in English.

Can not be resolved normally, error as shown in the above figure. Other tools can parse, file format no problem.

#1

Duplicate of #1


Small typo in documentation

In the code example in https://www.tensorflow.org/versions/r0.11/api_docs/python/train.html#replica_device_setter tf.replica_device_setter is used instead of tf.train.replica_device_setter.

Thanks!  Want to submit a quick PR?

This issue has been fixed. It can be closed. :)

@hholst80 This issue could be closed now as it's been solved.


Replace all MathHelper.Clamp usages with Math.Clamp

.NET Standard 2.1 implements Math.Clamp , use it instead of MathHelper.Clamp from osuTK.
During quick testing I noticed that now an exception is thrown during the DelayedLoadWrapper visual test.
Exception
I've added a commit that fixes the test, but I'm not completely sure if this is the correct fix.

Reverted the behavior of ScrollContainer.Clamp, it now uses the old Clamp implementation from osuTK again.


Configuring wrappers as Swift Package

Making swift wrappers as a swift package.

Merging bypassing the MacOS related CI tests. The MacOS VMs are upgraded in GitHub, and build is not successful in latest version.


should be able to access scope that function call was made on

rspec-puppet for functions does not support accessing the scope object on which the function was called.
This is required for cases where the function calls another function and you want to stub the results of that function. (b/c you have to stub that function call on the same scope object used for the function call being tested)

This is implemented in 2.2.0: https://github.com/rodjek/rspec-puppet#accessing-the-parser-scope-where-the-function-is-running


Custom durations & settings lost after restart

I've found that rebooting my machine (Big Sur) causes the settings to be lost. Custom durations are no longer showing, and the "Start at Login" button is unchecked, despite the app starting at login.
I'm using 1.6.0 via homebrew.

Sounds like something went wrong with the preferences file. This should never happen and is sadly system behavior and out-of-reach of the app itself.
Can you please try if the following steps solve this problem?

quit KeepingYouAwake
open the Finder, open the Go to Menu and select Go to folder….
type in ~/Library/Containers/ and hit Open
look for a KeepingYouAwake or info.marcel-dierkes.KeepingYouAwake folder and throw it into the trash
restart KeepingYouAwake and apply your settings, toggle the launch at login checkbox a couple of times to make sure the app is properly re-registered to launch at login
reboot and check if the problem still occurs

Hopefully this solves the problem.

Thanks. I've run through the steps (without the reboot as of yet). Since there's not much you can do from the app, I'll close this ticket. Might be good to have these steps in the README or a troubleshooting file.

Unfortunately, the issue persists after running through the process and doing a restart.

I have no clue what might be causing this. I'm closing it again for now. If this re-appears please also list any unusual configuration that your Mac might have… e.g. if you are enrolled in MDM, if your user account is not an admin account of even if you have multiple user accounts.


Make properties of window, frame etc

Hello,
if there is a way to access properties of e.g a window such as its size, I was unable to find how to do that.
This would be useful e.g for making an UI that reacts to the window being resized.
A possible API might be to integrate this into the existing builder pattern:
    let mut size = (0.0,0.0);
    ui.window(im_str!("Hello world"))
        .size((900.0, 500.0), ImGuiCond::FirstUseEver)
        .get_size(&size).
        .build(|| {
            // ...
        });

Or the window might be passed to its inner function (which might be weird with the way the API currently works, but might be made ok by passing an immutable object (see also #90):
    let mut size = (0.0,0.0);
    ui.window(im_str!("Hello world"))
        .size((900.0, 500.0), ImGuiCond::FirstUseEver)
        .build(|it: &Ui::Window| {
            // ...
            let zesize = it.get_size();
        });

I don't think there's a way to do what you want but it's a good idea! But first, I think we need to split properties into two groups: defined properties and calculated properties.
Defined properties IMHO don't need to be accessible through the API, because they are always passed by the library user and therefore the user already has all the values. For example:
let use_borders = true;
ui.window(im_str!("Hello world"))
    .show_borders(use_borders)
    .build(|w| {
      w.has_borders(); // <- no point in having this, because use_borders is already easily accessible
    });

Calculated properties such as size are a different story. For example, window position and size could be accessible using some API using the style in your second example. Remember that the position and size passed to the builder are not necessarily the real values that the window ends up having.
It's also not just properties...there's some "window APIs" in imgui that are currently not exposed at all in the imgui crate but could be added. For example:
ui.window(im_str!("Hello world"))
    .build(|w| {
        if w.is_appearing() {
            w.focus();
            println!("Content region width: {}", w.content_region_width());
        }
    });

Hey, can't say much about this except that I think you're right on all points :)

Closing old ticket
Not sure what the state of the lbirary was at the time, but the initial problem (getting window size) is doable now via
ui.window("Hello world")
    .size((900.0, 500.0), FirstUseEver)
    .build(|| {
        // ...
        let zesize = ui.window_size();
    });

Would be nicer if that method was through some more explicit "Window" object passed in, but.. that would be a somewhat drastic change, and the current approach is basically direct mapping of the C++ API which is also nice


Email Notifications Part Deux

🐴 Considerations

User needs to be subscribed
Don't want to send 30 emails when Amy creates a recurring event for an entire month
Send reminder emails when she doesn't have enough people to fill slots
Should be able to add a string to the email for reminders so she can customize message like "🐴 Hey we need 2 more people for this 🐴"
When creating a new event, allow admin to not send email for event creation
Email specifically for Lesson Assistant attribute or everyone (a checkbox that shows all roles, with them all defaulted, and Amy can select which specific ones she wants to send emails to)

🐴 Emails needed
Generic email functionality:
1."Coming Soon" events with the events in the next month
Nice to have:
2. Event creation when a new event is made
3. Reminder email for event if event is not full
Code Pointer: https://github.com/opportunity-hack/evs/blob/e9487a3663e9989fcb958b7c6d4aaef57cd131ba/app/routes/resources%2B/event-register.tsx#L193C2-L193C77

Slack Notes:

Must have: tell everyone that a new event is created
FYI Amy keeps separate SignUp for Lesson Assistant Positions
Since we’re getting into October and starting lessons, Amy would create lessons next week, week after that
Biggest things to for us to add:
1/ Notification when a new event is created (use the user-level details Instructor or Lesson Assistant or Horse Leader to send an email to these folks when an event is created that matches their type

3 distinct lists of people

Everyone (cleaning crew is the current list of all volunteers)
People with horse knowledge
Lesson Assistants are automatically a horse leader as well

Made some small updates to @parkerdavis1 's PRs

Added upcoming events right in the email
Made the link point to /calendar
Added FANCY gray box

This is good to go! All code merged and tested - MVP of email is lookin good


build_solution

Small update according to https://github.com/control-toolbox/CTDirect.jl/issues/115#issuecomment-2192171031
linked to the PR in CTDirect https://github.com/control-toolbox/CTDirect.jl/pull/154
Have a nice weekend !

It is written that build_solution is not found:
https://github.com/control-toolbox/OptimalControl.jl/actions/runs/9826313682/job/27127615878?pr=207#step:7:21

It is written that build_solution is not found:
control-toolbox/OptimalControl.jl/actions/runs/9826313682/job/27127615878?pr=207#step:7:21

Yes, I haven't updated CTDirect yet, I wondered if it could interfere with the registration process. If not, I can do the release for CTDirect and you can relauch the tests here !

The process for registration is stopped at very early stage. No PR has been launched like for CTBase.jl. i think you can update and make a new release. I will update for the registration into yhe general registry.

The process for registration is stopped at very early stage. No PR has been launched like for CTBase.jl. i think you can update and make a new release. I will update for the registration into yhe general registry.

Ok, 0.9.3 is out for CTDirect, doc builds now :-)
You can merge this one when ready.


Add relative template path support

@harikt @koriym and others: please take a look to see if you find any problems.
@koriym especially: note the documentation change; the docs-ja folks will want to update the translation.

Update the translation with #15

That was very fast @koriym thank you!
I have discovered a bug related to named collections (e.g. email:...) and need to delay merging until a fix is in.


removing duplicates

Hi, When I run annovarToMaf using the txt file generated by ANNOVAR, I got the message that 693 duplicates were removed. I am wondering what are the standards for removing duplicates here and if there is any way to prevent it from removing the so-called duplicates if I don't want it to since there are not exactly the duplicates based on my criteria.
Thank you.

Hello,
Duplicates are removed based on variants occurring at same position in the same sample. If you dont want to remove them, then just convert your txt files to maf data.frame with MAFobj = FALSE. Then pass the resulting data.frame to read.maf function with argument removeDuplicatedVariants = FALSE. Hope this helps.

Thank you for your quick response. It works! But I am still a bit confused since I looked back to the original dataset generated by ANNOVAR and actually I didn't see the removed rows were duplicated based on the definition you gave here. So the sample here is the subject, right?
Thank you for your help.

And also, do you know how to change the margin of the figure (either for oncogenic pathways) and oncoplot with gene names cropped.

Hi,
Yes, sample here means the subject. For oncoplot you can use gene_mar argument to increase the default space. See ?oncoplot for more details.


Updates rsocket broker to 0.3.0

I'd like to get this merged before you release function for 2021.0.0. Having an issue releasing to sonatype, that's why it's still 0.3.0-SNAPSHOT

As soon as rsocket-broker-spring hits maven central this will be good to go.

Done https://repo1.maven.org/maven2/io/rsocket/broker/rsocket-broker-spring/0.3.0/


Gerkin: Paramater type {float} not matching 0 (zero).

Summary
The Gerkin parameter {float} does not match a simple 0 value. It seem to be treating this as an integer and thus looking for an integer step to match with. Any {float} steps are ignored as potential matches.
This is manly a problem as the Business stakeholders that are preparing Features and Scenarios do not understand that the difference between a 0 integer value and a 0.0 float value. They're mathematicians and consider 0 (integer) to belong to the domain of Real numbers and thus a valid value identical to the 0.0 (float) (likewise 1 is identical 1.0, and so on for all Integer values).
The Step where this is an issue has five parameters that are all likely float values yet are also possible Integer numbers. Supporting variations for all five possible matches would be somewhat cumbersome. (The other alternative of providing a custom type using a regular expression also isn't ideal.)
Expected Behavior
If matching on  an Integer parameter and no {int} steps is found yet a matching {float} step exists then this will be used.
Current Behavior
If matching on an Integer and no {int} exist no matching takes place even if an acceptable {float} match is available.
Possible Solution
Accept that Integer values are acceptable subset of Real numbers and thus also acceptable matches for {float} parameter type iff no acceptable {int} step exists.
Context & Motivation
Features are intended to be prepared by domain experts that have no specialized understanding of computing environments. With this in mind interpretations of specific types of information provided in scenarios need to be aligned with the "common" understanding familiar to the domain experts.

Thanks for the detailed report @alcarwk!

This is a little tricky to implement, but not impossible.
The first step is to change FLOAT_REGEXPS / FLOAT_PATTERN in ParameterTypeRegistry to -?\d*(?:[.,]\d+)?. That will recognise integers as floating points.
The tricky part is in the expression generation. We still want 0 in an undefined step to suggest {int} for the parameter. So we need to add some more smarts to the CucumberExpressionGenerator to make all tests pass.
Would you be interested in helping us with a PR for this?

Thanks for the response to this. At the moment I'm using a parameter type definition defined as {number} that matches both integer and float returning a Double.
This would provide a nice bases to work up a generalized (polymorphic) number matcher that works as suggested.
Time permitting I would like to help with adding this as a new feature.
There are a couple of other ideas based on what our Business experts are putting in features that might also be useful; i.e. lists in step definitions' "And applying adjustments 1, 1.32, 2.67, 3, 3.86, 4.2"

Give us more time stalebot!


Allow building with the free VS 2017 build tools.

This aims at solving issue #16 .  The added scripts require local admin rights.  The new Windows native docker support may solve this limit.
Attempting to install build tools locally (--user2017) without admin rights results in an exit code 138 from the installer.
Using /m speeds up msbuild but conflicts with HP Fortify's sourceanalyzer.

Thanks for your pull request :)


Different rules for V2 and V3

@darrelmiller
There are places where the V2 and V3 specs may be slightly different. For example, V2 doesn't enforce XML.namespace to be absolute URI.
It seems to me that we may need different rulesets per version. Most default rules will be shared, but certain rules only belong to certain versions of the spec.

@PerthCharern This comes back to parsing errors verses validation.  Once we are loaded into the DOM we are no longer V2, we are V.Current.  If the we can't make it V3 compliant then I think we have to reject when parsing, or flag it with our validation errors.  Anyway, I'm pretty sure a namespace URI can't be relative anyway.  At least I can't say I've ever seen a relative namespace.

Same effect can be achieved by adding or removing rules from the default set when validating, so we'll close this for now.

We are seeing this issue in #254. Even though the DOM is universal, there are certain restrictions on some strings in V3 that were not the case in V2.
Customers can remove the rule themselves, but then that seems very inconvenient. Should we provide rulesets based on Versions?

We decided not to do this. Whatever is in the DOM must be "V3-valid".


Tooltip size recalculated by browser

There is an issue (probably related somewhat to our internal css in the project) that the tooltip after all the position calculations are done changes it's width and then renders incorrectly. Unfortunately I can't reproduce it easily without our source code. Do you still take pull requests for v3? I'm not sure if the fix is pull request material (I'm forcing min-width if it's not set already). The change in size happens when we call 'applyPlacement' method.

Do you still take pull requests for v3?

In general, we still accept bugfix pull requests for it, but we've mostly given up on v3 tooltip positioning bugs; see https://github.com/twbs/bootstrap/issues/15590#issuecomment-113321235


Enable EssenceDescriptor node ignore set for virtual track conformanc…

…e validation

@svenkatrav Per communication with 35PM editor/chair, it appears that properties that are ignored in the IMF layer, ought to conform to the MXF specification (in other words, they should be treated just like other properties). Perhaps, this pull request should be declined?

FYI. "ignored" properties are not intended to be removed and/or absent. These properties were in fact designated "ignored" instead of "shall be absent" since they are required by MXF.
So I would argue that:

the values of "ignored" properties in the MXF file must conform to ST 377-1
the values of "ignored" properties in the CPL Essence Descriptor elements must match the values of the underlying Track File
when comparing CPLs or Track Files, the values of "ignored" properties can be ignored
the values of "ignored" properties is never used in IMF for processing


Skip glob not working in 4.2.0

Skip glob is no longer working in 4.2.0 due to a missing import of fnmatch

see: https://github.com/timothycrosley/isort/commit/17e61ff807a2d1462637df505aa0dcefe61c8bff#commitcomment-13330858

Fixed in release 4.2.1


contribute how to stop an actor docs

@skotzko link on this page is broken http://getakka.net/docs/working-with-actors/Actor lifecycle
Need to submit an updated PR.
On top of that the embedded image is also broken.

Also please update the relevant section on this page http://getakka.net/docs/Working with actors


Show all projects on grid

Context: https://centrepopgen.slack.com/archives/C020PDNH3N0/p1683008346969449?thread_ts=1682923952.982739&cid=C020PDNH3N0

Closing as we improved the speed of project membership lookups


dev server not running

https://github.com/ccrsxx/twitter-clone/issues/9#issue-1510281366
After running npx next dev, it is  not working.

.env.development
// Import the functions you need from the SDKs you need
import { initializeApp } from "firebase/app";
import { getAnalytics } from "firebase/analytics";
// TODO: Add SDKs for Firebase products that you want to use
// https://firebase.google.com/docs/web/setup#available-libraries

// Your web app's Firebase configuration
// For Firebase JS SDK v7.20.0 and later, measurementId is optional
const firebaseConfig = {
  apiKey: "AIzaSy****************8",
  authDomain: "twitter-cl*******.firebaseapp.com",
  projectId: "twitter-clone-*****",
  storageBucket: "twitter-clo****appspot.com",
  messagingSenderId: "1********99",
  appId: "1:1069671**********************de",
  measurementId: "G-J******FL8"
};

// Initialize Firebase
const app = initializeApp(firebaseConfig);
const analytics = getAnalytics(app);

also used this config but not working
# Dev URL
NEXT_PUBLIC_URL=http://localhost:8080/

# Firebase
NEXT_PUBLIC_API_KEY=AIzaSyB09J98vGekeqAnxtW2Nd6l1ow_UvQsLM8
NEXT_PUBLIC_AUTH_DOMAIN=twitter-clone-72050.firebaseapp.com
NEXT_PUBLIC_PROJECT_ID=twitter-clone-72050
NEXT_PUBLIC_STORAGE_BUCKET=twitter-clone-72050.appspot.com
NEXT_PUBLIC_MESSAGING_SENDER_ID=1069671531899
NEXT_PUBLIC_APP_ID=1:1069671531899:web:2e3827d7e2935369bde9de
NEXT_PUBLIC_MEASUREMENT_ID=G-JLKLB4GFL8

Oh, Hi! To fix this issue, try my own solution.
 Then put all your token/secret in Tokens/Secrets section. Make sure you use the api name.

Thankyou @TBNRDev for guiding me.....
https://github.com/piyush168713/twitter-clone
Can you please check the configuration or where eroor occurs in my repo.
Deployement is getting failed in vercel.app
Kindly guide me.

Try reinstalling the dependencies again. Delete the node_modules and .next folder first before installing it.


vid is being set to NaN in recent tracker version

Describe the bug
Tracking events sent using this tracker are failing in enrichment with the following failure message
{
  "expectation": "cannot be converted to java.lang.Integer",
  "field": "vid",
  "value": "NaN"
}

I suspect this commit causes the issue: https://github.com/snowplow/snowplow-javascript-tracker/commit/b212eb7a15fc4fe0248dacfbc4e592277fe58b75#diff-e1e232ecf4c494ec3be5f942f973200db624f9569d1776b35781614dcf2a97a8R97
To Reproduce

Send a tracking event without calling setSessionIndex or setSessionId
Observe the vid p is set to NaN

Expected behavior
vid is not set if sessionIndex is undefined
Desktop (please complete the following information):

OS: Linux/ubuntu
Browser: Node.js
Version: v3.12 (though it seems the bug may have been introduced in 3.11)

Additional context
We are using this package server-side in a node.js application.

Hey @jakeberesford-palmetto , thanks for spotting that, we released v3.12.1 which hopefully resolves this issue !

Thanks for the quick turnaround @igneel64 - much appreciated!


contracts: use uint96 for claim id and nonce

Optimization for storage
WithdrawClaimId and filler now fit into one slot
this results in 79e18 requests and claims combined

WithdrawClaimId and filler now fit into one slot

I am curious: how can one easily verify that?
I know there's --storage-layout option to solc, but it's tedious to invoke it manually because of the paths...
Would be nice to have Makefile target that outputs storage information so we could also use this in PRs, like we use the gas profiles...

WithdrawClaimId and filler now fit into one slot

I am curious: how can one easily verify that? I know there's --storage-layout option to solc, but it's tedious to invoke it manually because of the paths... Would be nice to have Makefile target that outputs storage information so we could also use this in PRs, like we use the gas profiles...

I looked briefly for tools, found this one, but looks outdated. Indeed I tried to run it, but it failed on the RequestManager. It's basically doing a static analysis on the source code.
I consider this out of scope for now, but sounds like a good idea to have it in the future. Please create an issue for it.

This PR is part of #1170.

We seem to have went from 288 down to 256 bytes for Request:
-      "numberOfBytes": "288"
+      "numberOfBytes": "256"

Nice!


Excessive Memory Consumption by Extension in vscode-server

Environment data

Language Server version: XXX
OS and version: Linux
Python version (& distribution if applicable, e.g. Anaconda): XXX

Code Snippet
xx-xxx-xxx:/space/user/.vscode-server/extensions$ du -sh -- ms-python.vscode-pylance-2024.2.2
390G	ms-python.vscode-pylance-2024.2.2

Repro Steps

Vscode Version: 1.86.2
Install the pylance extension 2024.2.2.
Monitor the vscode-server's memory usage.
Identify the extension(s) responsible for the excessive memory consumption.

Expected behavior
Extensions should operate within reasonable memory limits to ensure optimal performance and stability of Visual Studio Code.
Actual behavior
One extension is consuming an alarming 390GB of memory, causing significant performance degradation and potential system instability.
Logs
xx-xxx-xxx:/space/user/.vscode-server/extensions$ du -sh -- ms-python.vscode-pylance-2024.2.2
390G	ms-python.vscode-pylance-2024.2.2

du -sh shows disk space usage not memory usage?

Could you also try and create a core dump for our investigation?

I find the same question in this extension.

hey @Franky-in, thanks for the reporting this issue. Could you mind sharing the core dump?

hey @Franky-in, thanks for the reporting this issue. Could you mind sharing the core dump?
They may not easy to share as every  of them got more than 5GB.
They show up when I'm running .py using Ctrl+F5.

Thanks for your reply, I tried 2.1 2.2 2.3, and the issue always exists. "It seems ok on the next version 2.3." is not true. The core does not show up when my code ends, but a few times later (about 20s). Also, the name of the core is not the same one shows up when I'm running my code.
import os

files = os.listdir('dist')
for file in files:
    if file.startswith('core'):
        os.remove(f'dist/{file}')

Other code may also cause this issue.
After I run like this:
root@273e04153108:~/.vscode-server/extensions/ms-python.vscode-pylance-2024.2.1#  cd /root/.vscode-server/extensions/ms-python.vscode-pylance-2024.2.1 ; /usr/bin/env /usr/local/bin/python /root/.vscode-server/extensions/ms-python.debugpy-2024.2.0-linux-x64/bundled/libs/debugpy/adapter/../../debugpy/launcher 52375 -- /root/.vscode-server/extensions/ms-python.vscode-pylance-2024.2.1/dist/clean.py
The core is like:
/root/.vscode-server/extensions/ms-python.vscode-pylance-2024.2.1/dist/core.19913
I try to find the 19913 process but it's nowhere in my running history.
Here is my log.txt. Hope that will help.
log.txt

I don't think we actually need the core dump. A log of when the crash occurs would be better. Instructions for gathering a log can be found here: https://github.com/microsoft/pylance-release/blob/main/TROUBLESHOOTING.md#filing-an-issue
That should be a lot smaller (just a block of text).
The reason 2024.2.3 is better is because there haven't been any core dumps yet. If you go into the 2024.2.1 extension's dist folder, there should be a whole bunch of core.<processid>.dmp files. These are memory dumps of the Pylance server when it crashes. Given you have 5GB versions of these, I'd hazard a guess you're running out of memory.
What we really need is to find out what's causing the out of memory condition. The logs (and/or your source code) should help us figure out that out.

Thanks for your reply.
I tried 2.1 2.2 2.3, and the issue always exists. "It seems ok on the next version 2.3." is not true. The core does not show up when my code ends, but a few times later (about 20s). Also, the name of the core is not the same one shows up when I'm running my code.
import os

files = os.listdir('dist')
for file in files:
    if file.startswith('core'):
        os.remove(f'dist/{file}')

Other code may also cause this issue. It may not cause  "out of memory".
After I run like this:
root@273e04153108:~/.vscode-server/extensions/ms-python.vscode-pylance-2024.2.1#  cd /root/.vscode-server/extensions/ms-python.vscode-pylance-2024.2.1 ; /usr/bin/env /usr/local/bin/python /root/.vscode-server/extensions/ms-python.debugpy-2024.2.0-linux-x64/bundled/libs/debugpy/adapter/../../debugpy/launcher 52375 -- /root/.vscode-server/extensions/ms-python.vscode-pylance-2024.2.1/dist/clean.py
The core is like:
/root/.vscode-server/extensions/ms-python.vscode-pylance-2024.2.1/dist/core.19913
I try to find the 19913 process but it's nowhere in my running history.
Here is my log.txt. Hope that will help.
log.txt

Why are you running a python file in the same directory as where the pylance extension exists? Was that just an example?
The core.19913 file is written by the operating system after a process crashes. It looks like you were debugging a file you wrote to the dist folder? (See this for more information https://access.redhat.com/solutions/4896)
If you're running python files using python that can also cause core dumps if the process crashes. That wouldn't have anything to do with pylance though.
Sorry but I'm confused as to whether or not you're running python and seeing core dumps or if you're opening python files in VS code and seeing core dumps. Or maybe both.
The log you sent looks like you opened the dist folder in VS code. Is this the only code you had in that folder?
import os

files = os.listdir('dist')
for file in files:
    if file.startswith('core'):
        os.remove(f'dist/{file}')

I wonder if it's possible you're getting a core dump when VS code exits. If the extension host is too slow in shutting down, I know VS code just kills the extension host process. That might generate a core dump.
You could try deleting all the core dmp files, opening VS code like you normally do and then close VS code and see if a core dump appears on disk.

Thanks for your time again.
This is just an example, the core dumps are too many so I wrote this to delete them all. The other codes are not running in this folder  and also cause this issue. I'm just trying to explain the issue shows up maybe not related to the text of my code.
I wasn't doing anything else as using the ctrl+f5 to run my code on Vscode. I thought the core dump might show up as soon as my run finished. I kept refreshing the dist folder but it didn't show up until 20s later. I'm also confused about what's happening.
Make a guess, maybe the process does not end properly, and after running my code, takes a few times to generate the core dump?
---Original---
From: "Rich @.>
Date: Fri, Mar 8, 2024 01:04 AM
To: @.>;
Cc: "Franky<EMAIL_ADDRESS>Subject: Re: [microsoft/pylance-release] Excessive Memory Consumption byExtension in vscode-server (Issue #5531)
Why are you running a python file in the same directory as where the pylance extension exists? Was that just an example?
The core.19913 file is written by the operating system after a process crashes. It looks like you were debugging a file you wrote to the dist folder? (See this for more information https://access.redhat.com/solutions/4896)
If you're running python files using python that can also cause core dumps if the process crashes. That wouldn't have anything to do with pylance though.
Sorry but I'm confused as to whether or not you're running python and seeing core dumps or if you're opening python files in VS code and seeing core dumps. Or maybe both.
The log you sent looks like you opened the dist folder in VS code. Is this the only code you had in that folder?
import os files = os.listdir('dist') for file in files:     if file.startswith('core'):         os.remove(f'dist/{file}')
I wonder if it's possible you're getting a core dump when VS code exits. If the extension host is too slow in shutting down, I know VS code just kills the extension host process. That might generate a core dump.
You could try deleting all the core dmp files, opening VS code like you normally do and then close VS code and see if a core dump appears on disk.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

If your code is crashing, it would generate a core dump (after hitting CTRL+F5). It would be weird that it would be in the pylance extension dist folder though. Perhaps your python interpreter is actually crashing itself. That would explain core dumps in the pylance dist folder because we run python there.
This stack overflow response shows how to parse the dump files and see what process was being run:
https://stackoverflow.com/questions/62373716/retrieve-executable-from-core-dump

Hey,
Thanks for looking into the issue. At the end of this message, you can see the log output of an instance that caused a core file to be created. It seems that excluding a large subdirectory by creating a pyrightconfig.json file with the content below solves the issue.
{
    "exclude": [
        "results/**"
    ]
}

The directory was already on vscode's exclude list, i.e., part of the  files.exclude array. I wonder whether pylance should honor this exclude list. Notably, none of the files in the (excluded) directory are referenced by the actual Python code, nor should there be any Python code in the excluded directory.
Also, is crashing, in this case, considered expected behavior? If yes, it would be nice if there was some error dialog since nobody knows where to look for a helpful error message since there are so many different logs around.
Thanks :)
Nils
<--- JS stacktrace --->
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
2024-04-02 09:47:38.152 [info]  1: 0xb881c0 node::Abort() [/home/user/.vscode-server/bin/863d2581ecda6849923a2118d93a088b0745d9d6/node]
2024-04-02 09:47:38.152 [info]  2: 0xa92a26  [/home/user/.vscode-server/bin/863d2581ecda6849923a2118d93a088b0745d9d6/node]
2024-04-02 09:47:38.153 [info]  3: 0xd73d50 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [/home/user/.vscode-server/bin/863d2581ecda6849923a2118d93a088b0745d9d6/node]
2024-04-02 09:47:38.153 [info]  4: 0xd740f7 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [/home/user/.vscode-server/bin/863d2581ecda6849923a2118d93a088b0745d9d6/node]
2024-04-02 09:47:38.154 [info]  5: 0xf51a95  [/home/user/.vscode-server/bin/863d2581ecda6849923a2118d93a088b0745d9d6/node]
2024-04-02 09:47:38.154 [info]  6: 0xf52998 v8::internal::Heap::RecomputeLimits(v8::internal::GarbageCollector) [/home/user/.vscode-server/bin/863d2581ecda6849923a2118d93a088b0745d9d6/node]
2024-04-02 09:47:38.155 [info]  7: 0xf62e33  [/home/user/.vscode-server/bin/863d2581ecda6849923a2118d93a088b0745d9d6/node]
2024-04-02 09:47:38.156 [info]  8: 0xf63ca8 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/home/user/.vscode-server/bin/863d2581ecda6849923a2118d93a088b0745d9d6/node]
2024-04-02 09:47:38.156 [info]  9: 0xf3e65e v8::internal::HeapAllocator::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/home/user/.vscode-server/bin/863d2581ecda6849923a2118d93a088b0745d9d6/node]
2024-04-02 09:47:38.157 [info] 10: 0xf3fa17 v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/home/user/.vscode-server/bin/863d2581ecda6849923a2118d93a088b0745d9d6/node]
2024-04-02 09:47:38.157 [info] 11: 0xf20e7a v8::internal::Factory::NewFillerObject(int, v8::internal::AllocationAlignment, v8::internal::AllocationType, v8::internal::AllocationOrigin) [/home/user/.vscode-server/bin/863d2581ecda6849923a2118d93a088b0745d9d6/node]
2024-04-02 09:47:38.158 [info] 12: 0x12e84bf v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long*, v8::internal::Isolate*) [/home/user/.vscode-server/bin/863d2581ecda6849923a2118d93a088b0745d9d6/node]
2024-04-02 09:47:38.158 [info] 13: 0x1724e39  [/home/user/.vscode-server/bin/863d2581ecda6849923a2118d93a088b0745d9d6/node]
2024-04-02 09:47:45.998 [info] [Error - 9:47:45 AM] Server process exited with signal SIGABRT.
2024-04-02 09:47:45.999 [info] [Info  - 9:47:45 AM] Connection to server got closed. Server will restart.
2024-04-02 09:47:45.999 [info] true
2024-04-02 09:47:46.400 [info] [Info  - 9:47:46 AM] (3097319) Pylance language server 2024.3.2 (pyright version 1.1.351, commit 87171fbf) starting
2024-04-02 09:47:46.400 [info] [Info  - 9:47:46 AM] (3097319) Server root directory: file:///home/user/.vscode-server/extensions/ms-python.vscode-pylance-2024.3.2/dist
2024-04-02 09:47:46.407 [info] [Info  - 9:47:46 AM] (3097319) Starting service instance "eval"
2024-04-02 09:47:46.412 [info] [Info  - 9:47:46 AM] (3097319) Auto format for strings enabled
2024-04-02 09:47:46.433 [info] (3097319) No configuration file found.
2024-04-02 09:47:46.433 [info] (3097319) No pyproject.toml file found.
<...>
2024-04-02 09:47:46.433 [info] [Info  - 9:47:46 AM] (3097319) Setting environmentName for service "eval": "3.11.4 (env-container venv)"
2024-04-02 09:47:46.458 [info] [Info  - 9:47:46 AM] (3097319) Assuming Python version 3.11
2024-04-02 09:47:46.458 [info] (3097319) Assuming Python platform Linux
<....>
2024-04-02 09:47:56.509 [info] [Error - 9:47:56 AM] (3097319) Enumeration of workspace source files is taking longer than 10 seconds.
This may be because:

You have opened your home directory or entire hard drive as a workspace
Your workspace contains a very large number of directories and files
Your workspace contains a symlink to a directory with many files
Your workspace is remote, and file enumeration is slow
To reduce this time, open a workspace directory with fewer files or add a pyrightconfig.json configuration file with an "exclude" section to exclude subdirectories from your workspace. For more details, refer to https://github.com/microsoft/pyright/blob/main/docs/configuration.md.


Inferred recursive types

I'm working on a library that needs type definitions at runtime, and I wanted to use Zod as it's the “lingua franca” of runtime type definitions. However, my library will make heavy use of recursive types, and working with these is currently very cumbersome in Zod. The Recursive types section of the documentation reads:

You can define a recursive schema in Zod, but because of a limitation of TypeScript, their type can't be statically inferred. Instead you'll need to define the type definition manually, and provide it to Zod as a "type hint".
Unfortunately this code is a bit duplicative, since you're declaring the types twice: once in the interface and again in the Zod definition.

I wonder if such a limitation is necessary, since TypeScript supports recursion even on anonymous types. For example, if we define the following helper types...
const TAG = Symbol('TAG');
type Tag<N extends string> = { [TAG]: N };
type RecursiveType<Name extends string, Self extends object, O = Self>
    = O extends Tag<Name> ? RecursiveType<Name, Self>
    : O extends Array<infer V> ? Array<RecursiveType<Name, Self, V>>
    : O extends object ? { [K in keyof O]: RecursiveType<Name, Self, O[K]> }
    : O;

... we can create the Category type without having its definition reference itself:
type Category = RecursiveType<'Cat', {
  name: string;
  subcategories: Tag<'Cat'>[];
}>;

const x: Category = { name: "foo", subcategories: [42] }; // error
const y: Category = {
  name: "bar",
  subcategories: [
    { name: "qux", subcategories: [] }
  ]
}; // ok

Link to TS Playground.
It is then hard to imagine that Zod couldn't support recursive types with full static inference using an API like this:
const Category = z.label('Cat', z.object({
  name: z.string(),
  subcategories: z.ref('Cat').array(),
}));

Is there a good reason why this isn't a part of Zod already? Or should I try to make a PR for this?

EDIT: Changed the last code snippet, so that it uses methods z.label and z.ref instead of z.recursiveType and z.tag, becaue I think the new methods are easier to understand.

In your examples, the type is not being inferred or extracted from a self-referencing runtime construct. It's trivially easy to write a recursive type. I didn't fully follow your code but this is all you actually need:
type Cat = {
  name: string;
  subcategories: Cat[];
};

I'm very dissatisfied with this limitation of Zod though, and overcoming this will likely be a major design goal of a hypothetic Zod 4. Anyway - you're certainly welcome to attempt a PR but I'm pretty confident this is not possible atm.

I'm sorry for not being clear enough. What I wanted to say was that it is possible to declare a self-referencing schema whose TS type is correctly inferred.
While TS can't infer if from the z.lazy pattern, it works if we introduce the label-ref pattern that I propose.
See my minimal implementation on the TS playground.
In my proposal, the following code:
const Category = z.label('Cat', z.object({
  name: z.string(),
  subcategories: z.ref('Cat').array(),
}));

would be the dry alternative to this code:
interface Category {
  name: string;
  subcategories: Category[];
}

// cast to z.ZodType<Category>
const Category: z.ZodType<Category> = z.lazy(() =>
  z.object({
    name: z.string(),
    subcategories: z.array(Category),
  })
);

I'm pretty confident this is not possible atm.

I hope to have proven you wrong and look forward to further collaboration :^)

I think I found something even better. It's possible to have static inference even with the z.lazy pattern, if we modify it slightly. The following code would do the same as the two snippets in my previous comment:
const Category = z.lazy(self => z.object({
  name: z.string(),
  subcategories: self.array(),
}));

See it on the TS playground!
The key here is the self argument, which does all the heavy lifting. While at runtime it would hold the exact same value as the Category variable, in the TypeScript's type system it has a special non-transparent type, so that it's still possible to statically infer the return type of the lambda.

I think this is a really cool idea. Do you think you would be able to make a PR?

I started working on it, but then got stuck on the fact that Zod types have both a _def property and In & Out type parameters, ie. the actual resulting type is described in multiple places. I finished the transformer for _def, but I haven't implemented the transformers for In & Out yet.
However, I realized that this makes Zod quite cumbersome for my original use case¹ – therefore I won't be using Zod in my codebase and cannot guarantee I'll find time to finish the PR. If anybody wants to tackle this in the meantime, here's my work in progress.
¹) I need to do a lot of deep mapping on the runtime types, and this doesn't go well with the fact that Zod schemas have three different places where they store type information (_def, In, Out).

thanks for your honesty and all your hard work.


Bring back Storybooks

Migrates a lot of the setup inside reaction-force into Emission, as Storybooks were removed in #453
Note: this include the fusebox manager, should we keep this? I'm close to having the webpack setup down. So once that's working I could look at fusebox instead.
TODO:

[x] Fix Dangerfile
[x] Port rest of books to TS
[x] Clean up the folder structure
[ ] Figure out if webpack is fast enough
[ ] Fusebox?
[ ] Storysnaps?

Fails

:no_entry_sign:
Running your Dangerfile has Failed

Danger has errored
Error: TypeError
TypeError: Cannot read property 'length' of null
    at reactComponentForPath (/home/travis/build/artsy/dangerfile.ts:87:12)
    at Array.map (native)
    at Object.<anonymous> (/home/travis/build/artsy/dangerfile.ts:94:52)
    at Runtime._execModule (/home/travis/build/artsy/emission/node_modules/jest-runtime/build/index.js:447:13)
    at Runtime.requireModule (/home/travis/build/artsy/emission/node_modules/jest-runtime/build/index.js:295:14)
    at /home/travis/build/artsy/emission/node_modules/danger/source/runner/DangerfileRunner.ts:92:13
    at ensureCleanDangerfile (/home/travis/build/artsy/emission/node_modules/danger/source/runner/DangerfileRunner.ts:129:3)
    at Object.<anonymous> (/home/travis/build/artsy/emission/node_modules/danger/source/runner/DangerfileRunner.ts:91:3)
    at step (/home/travis/build/artsy/emission/node_modules/danger/distribution/runner/DangerfileRunner.js:32:23)
    at Object.next (/home/travis/build/artsy/emission/node_modules/danger/distribution/runner/DangerfileRunner.js:13:53)

  Generated by :no_entry_sign: dangerJS

OK, storybooks are back in and I've added a few more

Gonna bail on fusebox etc for now, and have a separate PR for Danger checking that people are including stories for new components.

This may already be clear to you, but we’re no longer using fusebox in reaction-force. So this look great to me, good stuff :clap:

I didn't look :D


Sync with groups created manually

We can create a group manually by right-clicking on the tab. But the extension doesn't record that group now

Add a new type for new group created manually
Record in tabGroupMap
Merge group if there is already a group with that type

In addition to recording the group name, is it necessary to record the behavior of manual or automatic creation?

Is anyone following up on this issue now? I want to go and solve it.

Is anyone following up on this issue now? I want to go and solve it.

Just assigned this issue to you. You can check the latest updates on main branch, here is a new variable called tabMap to record all the tabs state manully

When tabGroup be updated, I added logic. At this time, if the configurations saved in title and popup are different, the tabGroup will be stored and synchronized to the configuration of popUp.
And next time when clicking "Group Existing Tabs", it will query all tabsId under tabGroup, then filter them out from the group event after openai.


Fixes an issue with favorited web CARs

There's a missing piece of information in the current car by name selection, which looks unintentional. This adds in the account number to the function call and uses that for matching as well as the CAR name.

Closing in favor of https://github.com/kionsoftware/kion-cli/pull/19


Modified Datapath_test to support PacketGen

Codecov Report

Merging #266 into master will decrease coverage by 1.09%.
The diff coverage is 0%.

@@            Coverage Diff            @@
##           master     #266     +/-   ##
=========================================
- Coverage   52.76%   51.66%   -1.1%
=========================================
  Files          39       39
  Lines        4325     4343     +18
=========================================
- Hits         2282     2244     -38
- Misses       1846     1902     +56
  Partials      197      197

Impacted Files
Coverage Δ

enforcer/utils/packetgen/packet_gen.go
0% <0%> (ø)
:arrow_up:

enforcer/utils.go
71.87% <0%> (-15.63%)
:arrow_down:

monitor/linuxmonitor/linuxMonitor.go
58.94% <0%> (-7.37%)
:arrow_down:

enforcer/datapath_tcp.go
57.11% <0%> (-5.69%)
:arrow_down:

enforcer/datapath.go
70.19% <0%> (ø)
:arrow_up:

enforcer/nfq.go
0% <0%> (ø)
:arrow_up:

cmd/remoteenforcer/remoteenforcer_linux.go
0% <0%> (ø)
:arrow_up:

enforcer/utils/packet/packet.go
26.28% <0%> (+0.53%)
:arrow_up:

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 95e36b1...62897be. Read the comment docs.


Update nip05.ts

Added support for hieroglyphs and emoji domains for nip05 verification<EMAIL_ADDRESS>should pass)

I like your idea! But I don't think this is the right place for it<EMAIL_ADDRESS>should not pass, although<EMAIL_ADDRESS>should pass. It should be up to the client to parse punycode in URLs and render the emoji during display. Allowing anything except strict URL characters here could open the door to potential security issues.

I understand your point completely! However, requiring clients to adopt this might compromise the functionality of NIP05 in many instances where the library is being used, mainly because a large number of users are unaware of this feature's existence.
As it stands, the criteria for URL characters remain stringent, permitting only the use of emojis and hieroglyphs that do not resemble or mimic standard characters, thereby preventing possible security vulnerabilities.
Please reconsider 🙏🍄

@alexgleason, @fiatjaf
Additionally, as per the guidelines outlined in NIP-05, it is specified that:
NIP-05 presumes that the <local-part> will strictly adhere to a character set comprising of a-z, 0-9, and the symbols -_., with no regard to case sensitivity.
This restriction should exclusively apply to the  and not extend to the domain section of the identifier. Moreover, the responsibility of translating glyphs to punycode rests with the browser client, not with every other client being developed within the ecosystem.
Therefore, an identifier like<EMAIL_ADDRESS>is in full compliance with the standards set forth in the NIP-05 document.
It's worth noting that the regex pattern  /^[A-Za-z0-9-_]+$/ was established in an earlier iteration of nostr-tools and has been operational across various clients, with metadata being a notable example.
However, the recent modifications made to the regex pattern through the pull request  207 have unfortunately led to compatibility issues in certain clients. It's vital to consider the implications of such changes to ensure a seamless user experience across all platforms.

This fails every IDN domain for NIP-05 Verification.
Such as every .世界 domain. or anything with non-english characters.

It's not just about security, but compatibility.
On the DNS/HTTP protocol level, 𓂀.cc is not compatible, only xn--ts7d.cc is. I've already told you how to make it work. What is the blocker?
Clients will need to handle IDNs regardless, so it should be up to clients to display it correctly.
See also: https://en.wikipedia.org/wiki/Emoji_domain#Issues

At present, only Punycode encoding is advised in e-mail addresses,[31] e.g<EMAIL_ADDRESS>as many MTAs and MUAs don't support SMTPUTF8[32] which would allow SMTP commands with non-ASCII characters.

I'm open to the idea I'm wrong about this, but at the very least some other Nostr developers should chime in here on problems it would solve to support IDNs directly. And developers should be aware of this, because it creates two possible ways to represent the same nip05. It just seems like an unnecessary extra layer of complexity. The thing I don't like about it are the problems I haven't even anticipated.

It's not just about security, but compatibility.
On the DNS/HTTP protocol level, 𓂀.cc is not compatible, only xn--ts7d.cc is. I've already told you how to make it work. What is the blocker?
Clients will need to handle IDNs regardless, so it should be up to clients to display it correctly.
See also: https://en.wikipedia.org/wiki/Emoji_domain#Issues

At present, only Punycode encoding is advised in e-mail addresses,[31] e.g<EMAIL_ADDRESS>as many MTAs and MUAs don't support SMTPUTF8[32] which would allow SMTP commands with non-ASCII characters.

I followed your advice and everything seems to work fine, thank you! 🙏
However, I've noticed that the web browser itself takes care of the necessary punycoding, making additional client-side efforts redundant. This became clear to me when I was testing things on metadata.nostr.com network request and comparing it with my own setup.
While looking into pull request 207, I realized that we might not need to limit this in the regex, especially if we want to stay compatible with NIP-05. I totally get that the thing you don't like about it are the things you haven't anticipated, but it seems this goes beyond just the technical aspects of unicode, punycode, ASCII or the internet.
The browser, acting as a sort of super-client, is already handling the necessary conversions. This means we don't really need to enforce these changes at the client level, which could make things a lot easier and straightforward for everyone involved.
It doesn't essentially lead to two representations of the NIP-05 on the backend, as it ultimately gets converted to the respective punycode regardless.
Thus, it solely affects the frontend, allowing developers the discretion to choose whether to display a 'xn--' sequence or a glyph/emoji. Hopefully, a consensus will emerge favoring the more visually appealing emojis over 'xn--' strings.
Additionally, if you attempt to ping 𓂀.cc, it functions correctly, and there's no requirement to personally convert it to punycode, since the OS's punycode.c handles that task automatically.
Remaining receptive to additional feedback from developers. 🥳


TypeError: appFn is not a function message when running the probot run command

Bug Report
Current Behavior
Starting a probot app with the command probot run on a local machine in production mode (not a local development mode) will print out TypeError: appFn is not a function error.
Following is the full error log that is relevant to this issue:
INFO	 (server): Running Probot v11.0.0 (Node.js: v14.4.0)
INFO	 (server): Listening on http://localhost:3000
(node:8029) UnhandledPromiseRejectionWarning: TypeError: appFn is not a function
    at Server.load (/home/hoonkim/Projects/unity-push-checker/node_modules/probot/lib/server/server.js:49:15)
    at combinedApps (/home/hoonkim/Projects/unity-push-checker/node_modules/probot/lib/run.js:87:20)
    at async Server.load (/home/hoonkim/Projects/unity-push-checker/node_modules/probot/lib/server/server.js:49:9)
    at async Object.run (/home/hoonkim/Projects/unity-push-checker/node_modules/probot/lib/run.js:90:9)

// app.ts
import { Probot } from 'probot';
import * as controller from './controller';

const pullRequestChangeCheckApp = async (app: Probot) => {
    app.on(['pull_request.opened', 'pull_request.reopened', 'pull_request.synchronize'], async (context) => {
        try {
            const pr = context.payload.pull_request;

            app.log(
                `Pull request number ${pr.number} from ${pr.base.repo.owner.login}/${pr.base.repo.name} emitted a new event`,
            );

            await controller.PullRequestHandlers.handlePullRequest(context);
        } catch (e) {
            app.log.error(e);
        }
    });
};
export default pullRequestChangeCheckApp;

The full repository can be found here: https://github.com/TeamSTEP/unity-push-checker/tree/7f788c12bfa3d74dea9e6cf2434d4fe12820439c
This issue may be related to https://github.com/probot/probot/issues/1371
In my case, the project itself will operate correctly minus the aforementioned UnhandledPromiseRejectionWarning.
So I can't say this is a critical project-breaking bug, but more of a minor annoyance.
Having said that, running the app in development mode without a registered github app ID will not print out this error because of this check.
https://github.com/probot/probot/blob/15e4b007022ee74af8c9ff272dab954879b0ac25/src%2Frun.ts#L84
Expected behavior/code
There shouldn't be any unhandled rejections when running the code when I'm only loading one app function.
Environment

Probot version(s): 11.0.0
Node/npm version: node - v14.4.0/npm - 6.14.8
OS: Ubuntu LTS

Possible Solution
From what I can see, the issue is stemming from this block in the run script https://github.com/probot/probot/blob/15e4b007022ee74af8c9ff272dab954879b0ac25/src%2Frun.ts#L107-L120
There are a total of three application function loading points (L-108, L-113, L-119), but unlike the second load that checks if an app package config was passed, the third loading point will try to find an application function even if no script arguments were passed, which means a non-function type object could be passed to the loading method. This could be related to the file resolution function as well.
https://github.com/probot/probot/blob/072b8c26b56f1c78c057f09b848b021d0f91b825/src%2Fhelpers%2Fresolve-app-function.ts#L5-L11
The simplistic solution I can think of on top of my head is to add a type check before loading the function to the server.
      const [appPath] = args;
      const appFn = resolveAppFunction(appPath);
      if (typeof appFn === 'function') {
        server.load(appFn);
      }

I hope this helps

Thanks! I was able to reproduce the problem, I'm looking into it

It looks like the problem is the usage of dynamic require calls. Because you use TypeScript and you export the default function as default export, the resolveAppFunction helper returns an object: { default: [AsyncFunction: pullRequestChangeCheckApp] } instead of the function pullRequestChangeCheckApp.
I guess the workaround could be to check if the result of require(resolver(appFnId, { basedir })) is an object with a default property instead of function, in this case we would return the value of { default }. Or better, we use the same import helper that TypeScript uses when transpiling to JavaScript.
Could you edit node_modules/probot/lib/helpers/resolve-app-function.js and replace its content with
"use strict";
Object.defineProperty(exports, "__esModule", { value: true });
exports.resolveAppFunction = void 0;
const resolve_1 = require("resolve");
const defaultOptions = {};
const resolveAppFunction = (appFnId, opts) => {

    opts = opts || defaultOptions;
    // These are mostly to ease testing
    const basedir = opts.basedir || process.cwd();
    const resolver = opts.resolver || resolve_1.sync;

    const path = resolver(appFnId, { basedir })
    const mod = require(path)
    if (typeof mod === 'function' ) {
        return mod
    }

    // handle ES Module export transpiled to JS
    if (mod.__esModule && typeof mod.default === 'function') {
        console.log(`mod.__esModule`);
        console.log(mod.__esModule);

        return mod.default
    }

    throw new Error(`[probot] now app function found at ${path}`)
};
exports.resolveAppFunction = resolveAppFunction;
//# sourceMappingURL=resolve-app-function.js.map

and see if that works?

I've a PR ready with the fix: https://github.com/probot/probot/pull/1448. I'll merge & release once you confirm it resolves the problem for you

I'll go ahead and merge it in, as I was able to reproduce the problem and the change fixed it for me. Let me know if the problem isn't resolved with 10.0.1

sorry for the late response. This seems to work for my build too, thank you!


ECR.embed won't take a variable as a parameter

I'm creating a simple web framework as a means to learn crystal - and whilst creating a function to render ECR I'm encountering this error;
in macro 'embed' /usr/share/crystal/src/ecr/macros.cr:69, line 1:
  1.     {{ run("ecr/process", embedded, "io") }}
  2.
undefined macro variable 'embedded'

This is occurring when I run this;
def execute
    embedded = self.get_template
    io = IO::Memory.new
    ECR.embed "embedded", io
    io.to_s
end

I've tried the above with and without string interpolation and it always fails unless passed as a string literal.

Yes, this is impossible. ECR is a macro, and compiles the templates at compile-time so you can only use constant strings for the path of the template.

Thanks for the fast response. Is there an alternative that is is available at run time?
I'm aware this can probably go on stack overflow now, but I thought I'd try my luck.

If you need runtime templates you'll need to use another templating engine, not compile time ones.

There are some other template engines shards, checkout: http://crystalshards.xyz/?filter=Template

Not all of them evaluate templates at runtime, though.
For runtime engines there are crustache, liquid.cr and crinja (I'm the author of the latter). This order roughly resembles the feature set and complexity of the template language and engine.

you can also reevaluate whether you need to load the template at runtime.

Closing, since this is a question and not an issue about ECR.


OverflowError with Numpy 2

I've upgraded to Numpy 2.0 and am now encountering the following error. I confirmed that if I downgraded this error goes away so this is definitely a new behavior in the new version of Numpy.
File ~/opt/anaconda3/envs/padre_meddea/lib/python3.10/site-packages/ccsdspy/decode.py:290, in _decode_variable_length(file_bytes, fields)
    288 while offset < len(file_bytes):
    289     packet_starts.append(offset)
--> 290     offset += file_bytes[offset + 4] * 256 + file_bytes[offset + 5] + 7
    292 if offset != len(file_bytes):
    293     missing_bytes = offset - len(file_bytes)

OverflowError: Python integer 256 out of bounds for uint8

I get a similar overflow with FixedLength packets. This may be related to NEP 50.
The easiest way to reproduce these errors is to try to run the test suite with numpy 2. Some of the output is below.
collected 205 items

ccsdspy/tests/test_byte_order.py FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF [ 19%]
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF                           [ 41%]
ccsdspy/tests/test_converters.py ..................................FF    [ 59%]
ccsdspy/tests/test_hs.py FFFFFFFFFFFFF                                   [ 65%]
ccsdspy/tests/test_packet_fields.py ......                               [ 68%]
ccsdspy/tests/test_packet_types.py ............FFFFFFFFFFFFFFFFF...F     [ 84%]
ccsdspy/tests/test_primary_header.py .F....                              [ 87%]
ccsdspy/tests/test_regression.py FFFFFFFFF                               [ 91%]
ccsdspy/tests/test_split.py .FF                                          [ 93%]
ccsdspy/tests/test_utils.py .....FFF                                     [ 97%]
ccsdspy/tests/test_var_length.py FFFFFF                                  [100%]

The numpy version should be pinned in the project toml file ASAP because anyone trying to install ccsdspy will run into these errors.

Note that on 30-Jul-2024, the pyproject.toml file was updated to pin the numpy version to <2. Users may run into this bug if they are using Numpy 2. We will work on a new release that supports Numpy 2 soon!

@ddasilva I did some testing to try to figure out what is the issue here. The primary problem is that the packet data is in bytes which includes the packet length. This packet length value which is also a uint8 is then used to calculate offset values to index in the packet in various places in the code. Calculating packet offsets requires ints and not uint because in some places the values become larger than a uint8 and in others negative packet offsets are used. Since these offsets are frequently initialized with data from the packet (therefore bytes) they are set to uint8 and then the calculations to update the offsets fail.

Hi @ehsteve, thanks for your help! I pushed a patch for NumPy 2 in PR #128 (branch name npy2_patch). Can you try it with your code and verify it works before I merge?
The patch should make the code work with both NumPy 1 and 2


Building course Date not loading

(https://user-images.githubusercontent.com/83554412/124438053-667db980-dd80-11eb-8b79-59ee60abcdc3.png)

Guys, please be a good guy, and use the fk*g search function - or use your eyes - check the Pinned issue! there are hundreds of issues related to the same - download stucked at "building course data" problem,
goto #609 and you will find the answer from the author

Check the new alternative version:
https://github.com/FaisalUmair/udemy-downloader-gui/pull/631


Rename manage/release to activate/deactivate.

The terms activate and deactivate seemed more appropriate than manage and release, as became apparent during the Distributed Tracing workshop in Berlin.
I think it is wise to tackle unclear naming while the library still is in the 'work in progress' stage.

Tagging @adriancole and @wu-sheng as I can't seem to add you as official 'reviewers' for this PR, but I'm curious about your opinions.
Btw, no problem if you don't have any time..

@objectiser I guess this would have impact on your code?
Interested in all opinions on this, I just t.ry to take advantage of what felt like consensus on monday 😉 .

@sjoerdtalsma LGTM - once merged if you can release then I'll update my code.

@objectiser Merged and release 0.0.3 was created.
It may take a while before maven central mirrors pick it up though.

@sjoerdtalsma Thanks


Problem signing based on tutorial code

I've been trying to use this library for the past several weeks and keep hitting problems with signing. I can't seem to get kbpgp to simply sign a message. Using the "sign" method provided, the box method always encrypts the message, even when explicitly told to only sign. I've created a testcase that fails:
var kbpgp = require('kbpgp');
var expect = require('chai').expect;

function gen( callback){
  var F = kbpgp["const"].openpgp;

  var opts = {
    userid: "User McTester (Born 1979<EMAIL_ADDRESS>    ecc:    true,
    primary: {
      nbits: 384,
      flags: F.certify_keys | F.sign_data | F.auth | F.encrypt_comm | F.encrypt_storage,
      expire_in: 0  // never expire
    },
    subkeys: [
      {
        nbits: 256,
        flags: F.sign_data,
        expire_in: 86400 * 365 * 8 // 8 years
      }, {
        nbits: 256,
        flags: F.encrypt_comm | F.encrypt_storage,
        expire_in: 86400 * 365 * 8
      }
    ]
  };

  kbpgp.KeyManager.generate(opts, function(err, alice) {
    if (!err) {
      // sign alice's subkeys
      alice.sign({}, function(err) {
        console.log(alice);
        // export demo; dump the private with a passphrase
        alice.export_pgp_private ({
          passphrase: 'booyeah!'
        }, function(err, pgp_private) {
          // NOTE: there is a bug in the tutorial, a variable "priv"
          //  (which I've replaced below with pgp_private), isn't
          //  defined anywhere)
          console.log("private key: ", pgp_private);
          alice.export_pgp_public({}, function(err, pgp_public) {
            console.log("public key: ", pgp_public);
            callback( pgp_private, pgp_public, alice);
          });
        });
      });
    }
  });
}

function sign( alice, callback){
  var params = {
    msg:        "Here is my manifesto",
    sign_with:  alice
  };

  kbpgp.box (params, function(err, result_string, result_buffer) {
    console.log(err, result_string, result_buffer);
    callback( result_string);
  });
}

describe( 'kbpgp ecc', function(){
  it( 'should be able to sign a message', function(done){
    this.timeout(20000);
    gen( function(apub, apriv, alice){
      gen( function(cpub, cpriv, chuck){
        sign( alice, function( signed){
          expect(signed).to.contain("Here is my manifesto");
          expect(signed).to.contain("PGP SIGNATURE");
          done();
        });
      });
    });
  });
})

For some reason it's always encrypting. Am I doing something wrong here? I've simply pulled the tutorial code, so maybe I'm missing something that hasn't been updated in the documentation. Or possibly it's just not outputting the standard "PGP SIGNED MESSAGE" first part of the messge, which usually appears?

After some research, it looks like kbpgp produces detached signatures, when I was expecting cleartext signatures. From the spec:
  BEGIN PGP SIGNATURE
   Used for detached signatures, OpenPGP/MIME signatures, and
   cleartext signatures.  Note that PGP 2.x uses BEGIN PGP MESSAGE
   for detached signatures.

Perhaps confusing from a documentation standpoint, but this does appear to be proper behavior, so I'm closing this.


make progress transferable between devices

I play on different devices and want my grind stats to show up when i switch device. I assume data is stored locally and that there's no access to the in game account but it would be a nice feature

yeah, this would require hosting the data.
I can make it so you can put the data wherever you want; like in OneDrive, so then it could be accessed on multiple devices.

That is a great idea, I will definitely use it if you do. Really nice feature, great work!

Somewhat related; I am really struggling to find the location that the data gets saved on my device. I was hoping to write a script that parses it and combines all of the data into some usable form -- to see how much time I spend across different categories for example. A way to define where that data is saved works!

sorry for the delays, I've been getting ready to move back to uni so my computer is all packed up.
for tm2020 the data is saved in C:/Users/NAME/OpenplanetNext/Grinding Stats
(for MP4 or turbo it would be the openplanet directory for those games)

How much effort would it take to host the data?  I think it would be great to be able to browse the stats and see who has grinded certain tracks the longest, etc.

@drekdrek I can help on the Backend/Admin side of things if you plan on implementing that feature as well as the frontend ;)


[GPT-41] Featured Articles View is Ugly

GPT-41

This bug can be replicated by resizing the webpage in inspector mode, and letting the carousel autoscroll


GitHub Pages deployment not turned on

I see that GitHub Pages deployment isn't working because GitHub Pages isn't enabled:

Error: Failed to create deployment (status: 404) with build version 99b960fa2cf57ac3168d2933cd36c432eb8178d8. Ensure GitHub Pages has been enabled: https://github.com/hjvoid/WolfiesWar3/settings/pages

I believe that it needs to be set to the GitHub Actions "source"

Nice! It builds, but now there's an error with module references in the build...

Also, we seem to be using the jekyll-build-pages action. Is the source set to GitHub Actions?


0001-perf-Correct-the-substitution-of-python-shebangs.patch - quotes

@mwallnoefer sorry, I forgot to mention I force pushed. The initial patch where the perf recipe from master is introduced has been refreshed, so includes this fix. Therefore I dropped the 2nd 'correct the substitution..' patch.

Ah, sorry a a bit lost, where did you do that :thinking::? I guess this is still the old one: https://github.com/htot/meta-intel-edison/commit/c160c737846fb511d2ee61b7ba858236fdf02bdd

Was buried deep f5ac9454e0820bda9817173d3ba99467f2b56964 so affected master, zeus, btrfs, oobe.


Start Time not working for post 12 hours work

Describe the bug
If start time is post 12:00 AM 16:00:00 is not matching with 4:00 PM
Expected behavior
extension should start when start time is matched.
Desktop (please complete the following information):

OS: [e.g. iOS] Windows 10
Browser [e.g. chrome, safari] Chrome
Version [e.g. 22]

This issue is fixed in v3.1.3 currently in Beta version


doc: generate README.md from nodejs-repo-tools

Fixes #3
Quick start guide is TBD in README.md (populated from quickstart.js, using nodejs-repo-tools).

Codecov Report

Merging #5 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master     #5   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           1      1
  Lines           4      4
=====================================
  Hits            4      4

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 a2379f1...8ad1902. Read the comment docs.


Fix issue with tailwind class escaping

tailwind.e was being used incorrectly, causing classnames to be incorrectly escaped. This caused @apply to not work. I believe this is what causes #25
See below for the generated css:

The input for tailwind.e needs to be the whole class name. Prior to this PR, the input was only the colour modifier (100, 200, 300, ect). As classnames cannot begin with a number, this gets escaped.

Looks good! Thanks!


Demo manifest not valid for Sequential workflow adaptive cards C# and Node sample

We need to change the demo manifest for Sequential workflow adaptive cards C# and Node sample.
Currently, it is displaying the 'bot-adaptivecards-user-specific-views' sample demo manifest when downloading the manifest.
Sample Link-1. https://github.com/OfficeDev/Microsoft-Teams-Samples/blob/main/samples/bot-sequential-flow-adaptive-cards/csharp/demo-manifest/bot-adaptivecards-user-specific-views.zip
2. https://github.com/OfficeDev/Microsoft-Teams-Samples/blob/main/samples/bot-sequential-flow-adaptive-cards/csharp/demo-manifest/bot-adaptivecards-user-specific-views.zip

@Prithvi-MSFT -Could you please help us to update the sample manifest.


[bug] did not change any but http.serve just not woking in windows now

it works well before, but today

don't know why =.=

It's hard to see what's the problem. We suggest to use node --inspect .. to debug the real filename is expected or not.
Note: cwd is the path where node.js start at, it's not the dirname of current file. Try http.serve('/static', path.join(__dirname, '..')) instead. It's better not to serve static directory in root path /, it's dangerous and often error-prone.

I get the error. And I find it is caused by the basename matching process bug: '/'.split('/') === ['', '']. I will fix it.

https://www.npmjs.com/package/farrow-http/v/1.10.12


Add sweepID, occurrenceID, and scheduleID to transfer model

Related platform-api PR

Ty for merging and minting the release @adamdecaf


Update to use RTSPATT for testing

CES became RTSPATT. The new version is way cooler and can be used with a docker image, which would avoid the ugly binary in the repo.

Done in https://github.com/EtixLabs/cameradar/pull/93


play-grpc-* samples fail on Java 8 dues to 8u252+ALPN

Originally posted in https://github.com/playframework/play-samples/pull/97#issuecomment-629430965
Once upstream projects (and play itself) have been patched and released we can the JDK8 versions of the jobs back online again.

Fixed in #111


Exit channel without specifying the channel name

Exit the channel without needing to specify the channel name

Thanks, makes sense 👍🏽


Xnero: Watch fratres(?!.net)

Xnero requests the watch of the watch_keyword fratres(?!\.net). See the MS search here and the Stack Exchange search in text, in URLs, and in code.

fratres(?!\.net) has been seen in 2 true positives, 0 false positives, and 0 NAAs.

Approved by Ryan M in Charcoal HQ


u256 sqr mod

Pull Request type

Please check the type of change your PR introduces:

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no API changes)
[ ] Build-related changes
[ ] Documentation content changes
[ ] Other (please describe):

What is the current behavior?
No dedicated u256 sqr, which can be done with one less u128 mul.
What is the new behavior?
Instead of mult_mod(x, x), call the more efficient sqr_mod(x)
A new u256_wide_sqr which is largely identical to u256_wide_mul is added,

Does this introduce a breaking change?

[ ] Yes
[x] No

Resolved!

Closing in favor of #304


Possible Blog Article on Scientific Software Projects and Their Communities

Rene Gassmoeller is going to write a blog on Scientific Software Projects and Their Communities, as part of the BSSW fellowship. This article is invited article and already has votes for it.
The blog article will focus on improving the state of scientific software requires focusing on the people behind the software.

Already has required votes from David, Lois and Rinku

Please refer to PR #493 for further discussion


kit import fails (script-refactor branch)

When using the script-refactor branch, the import CLI command fails. Here the logs:
rgb -n regtest --electrum localhost:50001 -d data0 import -w wallet_1 ./rgb-schemata/schemata/NonInflatableAssets.rgb
RGB: command-line wallet for RGB smart contracts
     by LNP/BP Standards Association

Loading stock ... success
Error: unsupported value `136` for enum `Bool` encountered during decode operation

The error seems to be triggered by the call to let content = UniversalFile::load_file(file)?; and is raised by strict-encoding.

Huh, I spent hours trying to detect why this happens - and just accidentally notice that the bug goes away after cargo update -p rgb-std (on script-refactor branch).
Huh

Sorry to hear that. Anyway I've retried and I confirm this is not an issue anymore. Closing this


docs(gateway): add TCP route docs

@michaelbeaumont as you mentionned I removed TCP from 1.8 so please remove it from the docs of 1.8


Fix deadlock when secor.upload.on.shutdown=true

The secor.upload.on.shutdown feature worked fine if we were shutting down
because we received a signal, but not if we were shutting down because a
Consumer thread had crashed and the UncaughtExceptionHandler had called
System.exit(1). In that case we'd get a deadlock and the program would never
exit.
Change the shutdown hook to do nothing if any Consumer thread called
System.exit.
The simplest way to implement this is to move the UncaughtExceptionHandler into
the Consumer thread itself as a big try block, so I did that.

CI failure is maven.twttr.com being down: https://github.com/twitter/commons/issues/418

Thanks for fixing the twitter maven issue.


[MPWG Membership- Legal ] Tomitribe

Signature of the MPWG agreements by Oct 12th

MPWG signed agreement signed and sent to Paul B. on Oct 5th, 2020!


Added memory access for system RAM.

Added memory access for system RAM.
Fixed bug where no core options JSON is present.

Added sort of similar behavior in c97a8c87a4c7eafeabc6e92aa11ba25a198f599b


multiple target folder for minified css and js files

I am working on a project where I need to minify multiple js and css files and copy to different directories. How do I achieve it? I used "cssTargetDir" but all the minified will be moved to one directory instead, I need the minified to copy to different folders.
src/main/resources/static/css/1.css
src/main/resources/static/css/2.css
src/main/resources/static/js/1.js
src/main/resources/static/js/2.js
Final out directory
target/web-resources/assets/js/1/1.min.js
target/web-resources/assets/js/2/2.min.js

any idea on this?


nim-base: add arm32v7 image

experimental, thus a little different from the existing two-build setup.. can optimize if it becomes popular - will also need a wee bit of refactoring to scale to other arches

will also need a wee bit of refactoring to scale to other arches

I've recently done some refactoring in my nim-docker repo, it allows to define "layers" and combine them arbitrarily.

How is travis going to execute arm dockers? Does docker use qemu under the hood?

yeah, that's the idea. on my fedora at least, simply having qemu installed makes linux pick up arm emulation through the binfmt mechanism such that the whole image can run.. some guides also copy the qemu-user-static binary into the docker and register it somehow so that it's available in-image (it's kind of weird, you get an arm image with an x86 binary inside - I don't claim to understand how this works exactly) - trying to see if that's needed here also

I've recently done some refactoring in my nim-docker repo, it allows to define "layers" and combine them arbitrarily.

suggestions welcome here, this is the first time I try docker.. I think the issue here is that I want to derive the same image from different source images.. ie the only difference between arm64 and arm32 is the FROM part - the rest should be the same.. it's kind of ugly for example to copy bootstrap.sh into the image folder for every image as part of "build"