README.md files sometimes identified as video/m2ts

README.md files are sometimes identified as Mime Type: video/m2ts. Behaviour seems to vary, but here is an example:
https://scholarsphere.psu.edu/concern/parent/bnz805z66z/file_sets/mpg15bf61m

FITS is identifying this file as video/m2ts which is triggering the video derivative creation process. It doesn't seem to affect the rendering of the readme, which is nice, but the characterization metadata is incorrect. I haven't been able to replicate this on the jobs server. It's possible it's something to do with certain Readme files, or their character encoding, or it's an issue with fits. I don't believe we've update it's version at all in the past year or more.

For this version of SS let's handle it by a local fix. The files are not consistently being added to the work.

looks like we can add the following into fits.xml to resolve the issue with markdown files
<tool class="edu.harvard.hul.ois.fits.tools.exiftool.Exiftool" exclude-exts="md,txt,wps,vsd,jar,avi,mov,mpg,mpeg,mkv,mp4,mxf,ogv,mj2,divx,dv,m4v,m2v,ismv,m2ts,mpeg4" classpath-dirs="lib/exiftool" />
we currently aren't managing this file, but if this seems like a sane approach, i can vendor the configuration and have chef manage it.

I've updated the configuration on the qa jobs box, with the readme file above it's now being classified as plain text.
/fits.sh -i /tmp/README.md
<?xml version="1.0" encoding="UTF-8"?>
<fits xmlns="http://hul.harvard.edu/ois/xml/ns/fits/fits_output" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://hul.harvard.edu/ois/xml/ns/fits/fits_output http://hul.harvard.edu/ois/xml/xsd/fits/fits_output.xsd" version="1.2.2" timestamp="7/8/19 11:17 AM">
  <identification status="SINGLE_RESULT">
    <identity format="Plain text" mimetype="text/plain" toolname="FITS" toolversion="1.2.2">
      <tool toolname="file utility" toolversion="5.28" />
    </identity>
  </identification>
  <fileinfo>
    <filepath toolname="OIS File Information" toolversion="0.2" status="SINGLE_RESULT">/tmp/README.md</filepath>
    <filename toolname="OIS File Information" toolversion="0.2" status="SINGLE_RESULT">README.md</filename>
    <size toolname="OIS File Information" toolversion="0.2" status="SINGLE_RESULT">3257</size>
    <md5checksum toolname="OIS File Information" toolversion="0.2" status="SINGLE_RESULT">18bb526f0a2a09989c0af7334588391c</md5checksum>
    <fslastmodified toolname="OIS File Information" toolversion="0.2" status="SINGLE_RESULT">1562595576000</fslastmodified>
  </fileinfo>
  <filestatus />
  <metadata>
    <text>
      <charset toolname="file utility" toolversion="5.28" status="SINGLE_RESULT">US-ASCII</charset>
    </text>
  </metadata>
  <statistics fitsExecutionTime="400">
    <tool toolname="MediaInfo" toolversion="0.7.75" status="did not run" />
    <tool toolname="OIS Audio Information" toolversion="0.1" status="did not run" />
    <tool toolname="ADL Tool" toolversion="0.1" status="did not run" />
    <tool toolname="VTT Tool" toolversion="0.1" status="did not run" />
    <tool toolname="Droid" toolversion="6.3" executionTime="75" />
    <tool toolname="Jhove" toolversion="1.20" status="did not run" />
    <tool toolname="file utility" toolversion="5.28" executionTime="389" />
    <tool toolname="Exiftool" toolversion="10.00" status="did not run" />
    <tool toolname="NLNZ Metadata Extractor" toolversion="3.6GA" status="did not run" />
    <tool toolname="OIS File Information" toolversion="0.2" executionTime="73" />
    <tool toolname="OIS XML Metadata" toolversion="0.2" status="did not run" />
    <tool toolname="ffident" toolversion="0.2" executionTime="346" />
    <tool toolname="Tika" toolversion="1.10" executionTime="165" />
  </statistics>
</fits>

@whereismyjetpack Great! However, don't we only need to exclude the md extension? We want Exiftool to run for all the other types of files, I believe.

I should have been more clear. the default fits.xml that we get has <tool class="edu.harvard.hul.ois.fits.tools.exiftool.Exiftool" exclude-exts="txt,wps,vsd,jar,avi,mov,mpg,mpeg,mkv,mp4,mxf,ogv,mj2,divx,dv,m4v,m2v,ismv,m2ts,mpeg4" classpath-dirs="lib/exiftool" /> I just tacked md in the front. i think for the other file types, there are other classes that do run on them. for example,         <tool class="edu.harvard.hul.ois.fits.tools.mediainfo.MediaInfo" include-exts="avi,mov,mpg,mpeg,mkv,mp4,mxf,ogv,mj2,divx,dv,m4v,m2v,ismv,m2ts,mpeg4" classpath-dirs="lib/mediainfo" /> so, mp4's will use the MediaInfo class, but ignore Exiftool

@whereismyjetpack Sounds good. There's a config file in this repo under fits_conf/fits.xml. Can you put in a PR for an updated config file with these changes that matches what will go into qa and production? This is similar to the way we keep our solr configs between repo and deployment in sync.

@awead https://github.com/psu-stewardship/scholarsphere/pull/1592

This configuration was placed on the servers today. Please let me know if something needs mended

Thanks! I'll try it out.

Works as expected when I upload the README.md in the OP to a new work. I also re-uploaded the README to the existing work and the mime type was correctly updated to text/plain.
Thanks! @whereismyjetpack


[DO NOT MERGE] Backport some fixes from master to ozone-1.4

What changes were proposed in this pull request?
Backport the following fixes from master to ozone-1.4 for 1.4.1.

HDDS-9846. Datanode should not persist cluster ID to global version file until loading all volumes. (#5757)
HDDS-9913. Reduce number of times configuration is loaded in Ozone client (#5789)
HDDS-9943. TokenRenewer should close OzoneClient after use (#5809)
HDDS-9986. Log if there is a failure in closing RocksDB (#5852)
HDDS-10028. Simplify Maven cache for dependencies in CI (#5889)
HDDS-9683. Containers present on decommission nodes are reported as mis-replicated (#5726)
HDDS-10001. Options not closed properly in rocksdb-checkpoint-differ (#5890)
HDDS-9527. Race condition in RocksDatabase (#5947)
HDDS-10113. UNHEALTHY replicas of QUASI_CLOSED container with unique origins should be handled during decommission (#5984)
HDDS-10157. Download zlib fails with 403 Forbidden in CI (#6029)
HDDS-10138. NPE for SstFilteringService in OMDBCheckpointServlet.Lock (#6015)
HDDS-10174. Enable Surefire process checker (#6075)
HDDS-9528. Managed objects should not override finalize() (#5853)
HDDS-10184. Fix ManagedStatistics not closed properly (#6055)

If approved, I'll push to the ozone-1.4 branch directly.
How was this patch tested?
CI:
https://github.com/adoroszlai/ozone/actions/runs/7657035459

/pending DO NOT MERGE

@ashishkumar50 @duongkame @hemantk-12 @ivandika3 @siddhantsangwan @sumitagrawl @whbing @xBis7 @xichen01 please take a look at your commit(s)

@adoroszlai Thanks for the work on this. LGTM!

Thanks @adoroszlai.
Can we back port these jiras as well?

https://issues.apache.org/jira/browse/HDDS-10103
https://issues.apache.org/jira/browse/HDDS-9486 (PR is in review)

Can we back port these jiras as well?

https://issues.apache.org/jira/browse/HDDS-10103
https://issues.apache.org/jira/browse/HDDS-9486 (PR is in review)

This PR is not a comprehensive list of Jiras to be backported, just an initial batch.  I thought one PR per backported commit would be too much overhead now, as more than a month has passed since the branch was cut.
Once this is completed, we can follow-up with another batch.  If we catch up, we may start backporting each fix right after it is merged to master.
We don't have a timeline for release yet.  The idea is to try to keep ozone-1.4 in good shape until then.

@adoroszlai Thanks for working on this. LGTM +1 for my patch.

@adoroszlai Thanks ! LGTM +1 for my patch.

LGTM +1

Thanks everyone for the review.
FYI, I pushed this via CLI as:
git checkout ozone-1.4
git pull
git merge --ff-only ozone-1.4.1-backports
git push

GitHub seems to recognize that as a "merge" of the PR, which is good.


added auth to config.js

Pushed to the wrong branch for the auth additions before this commit - let me know if you would like me to rollback the changes and republish through a PR!


Missing enctype on form using upload field in v6

Bug report
What I did
By using setFromDb() and modifying the type of a field to upload with the modifyField function the form does not apply the enctype.
What I expected to happen
The modifyField method should add the enctype to the form if it is an upload, upload_multiples, image, ... type.
What happened
Currently, the form does not send the file in POST request.
What I've already tried to fix it
If we rewrite the field with CRUD::field instead of modifying it with CRUD::modifyField it works and the enctype is defined
Is it a bug in the latest version of Backpack?
This is indeed the latest version of Backpack v6 and I confirm after running ``composer update backpack/crud``` the bug is still there.
Backpack, Laravel, PHP, DB version
When I run php artisan backpack:version the output is:
BACKPACK PACKAGE VERSIONS:
backpack/basset: 1.2.1
backpack/crud: 6.2.4
backpack/devtools: 3.0.0
backpack/editable-columns: 3.0.2
backpack/generators: v4.0.2
backpack/logmanager: v5.0.1
backpack/pro: 2.0.16
backpack/settings: 3.1.0
backpack/theme-tabler: 1.1.1
The code:
    protected function setupCreateOperation()
    {
        CRUD::setValidation(AccountDocumentRequest::class);
        CRUD::setFromDb();

        // This not add enctype on form
//        CRUD::modifyField('path', [
//            'type' => 'upload',
//            'withFiles' => true,
//            'tab' => trans('admin/account_address.tabs.general')
//        ]);

        // Redeclaration of field add enctype on form
        CRUD::field([
            'name'=>'path',
            'type' => 'upload',
            'withFiles' => true,
            'tab' => trans('admin/account_address.tabs.general')
        ]);
    }

The Backpack\CRUD\app\Library\CrudPanel\Traits\Fields@hasUploadFields check that the field has the upload attribute as true value. If we add it in the modifyField the enctype is added well. I think that it is related to the registered attribute macros function.
What do you think ?

Hey @dimer47 thanks for the report and the additional information.
I think I got the issue here. The upload => true was a requirement since forever, even before the Uploaders were a thing.
I am not sure about the real intent of it, I am guessing that by the time it was added (very long time ago), was to don't rely on the field types to add the enc-type.
Behind the scenes the Uploaders add this automatically in the field for you.
The Uploader macro is activated with withFiles attribute or method, when addField() or field() are called.
When you do setFromDb, the addField() method generated from your db columns will not have the macro.
The macros should not be ran on field modifications, they should only run when explicitly defined in the addField, or via macro method on the field instance.
Your scenario would work just fine if you do:
CRUD::setFromDb();
CRUD::field('path')->withFiles();

Let me know if it worked for you.
Cheers

Hey pxpm 👋🏻
Thanks for your return,
I confirm that by doing CRUD::setFromDb(); and CRUD::field('path')->withFiles(); this works perfectly 👍. The enctype is correctly added to form.
Do you think it would be possible to add the macro in the modifyField method to prevent this bug?
Cheers

Maybe I can work around it by checking if the field don't contain the macro in the previous attributes, only in the ones provided by modifyField(), and in that case, run the macro.
It may work non-BC like that. I will investigate that possibility. I don't think at the moment we have a way to run a specific macro on the field, either run all field macros or specifically call the ->macro() to run it.
I can't prioritize this rigth now, but I will keep this open so I don't forget.
Thanks again for the report 🙏

Thank you @pxpm for your feedback and your help.
Even if this problem is not corrected, I think it is a good idea to leave the issue open to help developers who notice the same problem.
Thanks again @pxpm


Question about --Save-Name

Hello,
When i save a file as for example: Good Video sometimes i get an error and sometimes the application just closes.
But if i save it as GoodVideo then it works normally, and i don't get any errors.
Is this expected? if yes, can you also add support for spaces in the name?
Thanks.

Add " like:
N_m3u8DL-RE --save-name "Good Video" https://example.com/master.m3u8

Yes, but in my batch file on Windows it works only if i use ExampleName, it doesn't work if i use "Example Name", i don't know why?
This is my file:
@echo off
set /p URL=Video Link:
set /p arguments=More commands?:

if not "%arguments%"=="" echo More arguments provided!

N_m3u8DL-RE %arguments% "%URL%"
pause

More commands?: --save-name "Example Name"
After i enter this, the terminal just closes, but if i use --save-name ExampleName then it works well, i don't know why?
Can you please try it?

Delete line 5.

Please, i need this line, is it a bug in N_m3u8DL-RE?

@54m4d That's not a bug, your bat script thrown an error when input contains ".
@echo off
set "arguments="
set /p URL=Video Link:
set /p arguments=More commands?:

if defined arguments echo More arguments provided!

N_m3u8DL-RE %arguments% "%URL%"
pause

I'm sorry, it was really a problem with my bat file, it conflicts when using "
Also, no need line 2.
Thank you very much Man.


Refactor types generation

Description of changes:

Follow DirectedCodegen's golden-path when generating shapes
Remove the use indirection and visitor in some generators
Create specific generators to handle each shape directive
Configure DirectedCodegen to "feed" shapes in alphabetical ordering based on shape name

This helps avoid having to store shapes in a list/collection temporarily + sort them before writing them to files

Upgrade Smithy version

Note: Build fail due to unreleased Smithy changes
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Tests are failing due to a dependency on unreleased smithy changes.  We're holding merging the PR until those have been released.


chore(master): release 0.24.0

:robot: I have created a release beep boop
0.24.0 (2023-08-11)
Features

add stamp dilute and topup (#619) (055a300)

This PR was generated with Release Please. See documentation.

🐝 PR preview in Swarm
Preview URL: https://bah5acgzaotws2fjzmeycdvmfpclfpewmjljeqhaue2hgfl3pqtvq6f46ujda.bzz.link
Swarm Hash: 74ed2d1539613021d58578965792cc4ad2481c14268e62af6f84eb0f179ea246
Commit Hash: a53d159ab91f4316b4f78b4b0af846d6ebe3d3a7
Commit Message: chore(master): release 0.24.0

:robot: Release is at https://github.com/ethersphere/bee-dashboard/releases/tag/v0.24.0 :sunflower:


Create the authentication mechanism

https://github.com/devkishore/react-practice/blob/main/README.md

hello @devkishore assign the task to me


Evgenios/feature/proportional size on demand

We discussed about the benefits of offering different visualisations on demand.
Some developers might want to see how big a component is by colour, while others by size.
The label_hash is now proportional_size and it offers scaling based on size while keeping the label_hash colour, to make it easy to spot same components that are used many times. In the proportional size mode, when the tree layout is vertical, component nodes scale based on lines of code horizontally, and when it's horizontal, they scale vertically.
Then there are the "white" and the "colorisation based on lines of code" versions that use a static component size.
Also fixed a bug, implemented async functionality on the "Change Layout" buttons, to fit the tree instance in the screen on click and implemented open component details on double click.

Hey guys,
Just want to let you know that it looks super cool with all the updates you are adding. Great job 🔥
(I still get notifications so I am following along 😄)

Hey guys,
Just want to let you know that it looks super cool with all the updates you are adding. Great job 🔥
(I still get notifications so I am following along 😄)

@stephanboersma Thanks Stephan <3


Bug always render existing assignments

Description

Fixes #41

Reviewers

Primary:
Secondary:

Checklist

[ ] Added/Updated related documentation (if applicable).
[ ] Added/Updated related unit tests (if applicable).

Screenshots (if applicable):

@raphaellaude I'm missing some context here -- does this mean a problem with re-rendering already painted areas when painting an unrelated area/color?
If so, it is possibly worth integrating with Deck.gl that has more granular controls over rendering update triggers? Especially for the case of separate geometry rendering (eg. on tile load or zoom) from color rendering (eg. on zone paint)


Geo search integration tests

In gitlab by @sfalquier on Apr 26, 2017, 15:41

In gitlab by @sfalquier on Apr 27, 2017, 10:00
closed

In gitlab by @sfalquier on Apr 27, 2017, 09:02
added ~1918368 and removed ~1918367 labels

In gitlab by @sfalquier on Apr 27, 2017, 10:00
removed ~1918368 label


Cannot execute "embark run" because module hdkey is missing

Apologies, this is my first submitted issue.  When trying to execute "embark run" I receive the error
Error: Cannot find module 'ethereumjs-wallet/hdkey'
I have installed ethereumjs-wallet and hdkey via npm and still receive this message.  This is my first experience with javascript so, again, I am sorry if this is just be being stupid with npm.

Please see https://github.com/embark-framework/embark/issues/654. If this is not fixed in the originating package very soon (next 9 hours roughly), we will create a 3.1.6 patch.

Also - thanks for submitting an issue and trying out Embark!! 🥇

@walletdude Thanks for reporting this. We released 3.1.7 which should fix this.


PIXI.AUTO_PREVENT_DEFAULT = false and mousedown events on mobile

The issue
Setting PIXI.AUTO_PREVENT_DEFAULT = false seems to cause mousedown events to fire alongside touch events.
If you take a look at the console output of this example I made using a mobile device or equivalent you'll see that tapping on the canvas will produce output that looks something like this:
onTouchStart
onTouchEnd
onMouseDown

(Note that I added a couple console.logs to pixi.js to produce this output.)  If you look at the sample example without that line you'll see that this doesn't happen.
I'm seeing this issue in Chrome mobile emulation, the iOS simulator, and my Droid Mini running Android 4.4.4.
Why this is a problem
I need to set AUTO_PREVENT_DEFAULT to false in order to enable scrolling while swiping on an interactive canvas, as recommended elsewhere.  The problem arises when I attach event handlers with something like mysprite.click = mysprite.tap = someCallbackFunction.  On desktop this works as-needed, but on mobile the unnecessarily triggered mousedown event causes the callback to fire a second time.  Any help with this would be greatly appreciated.

One of my coworkers pointed out that I can use underscore's _.throttle or _.once (since I'm also using underscore in my project) , which will work for now — although it would be great if this erroneous event would go away!

Note that we will be rewriting the interaction manager here soon, see #1296 and #241 for more info. We will keep these issues in mind when we get to that part.

Can you test this in v3 and see if this is still an issue?

Any update on this issue?  I'm having the same issue where I need to enable the default pan and zoom of the page.

See: #2071

This should be fixed in the latest dev branch.


added wstETH related addresses

superseded by https://github.com/bgd-labs/aave-address-book/pull/102


dependency refresh

updates all dependencies to latest versions
fixes all security issues flagged via yarn audit
fixes benchmarks by adding benchmark module as dev dependency

migrated changes to 0.10.0 pr #20


untimeWarning: invalid value encountered in greater_equal

untimeWarning: invalid value encountered in greater_equal
keep = (tmp_a >= first_edge)

@davidsandberg,
Same issue, please help.

I have small training data set and had the same issue.
It seems like decreasing "Number of batches per epoch" helps (default value = 1000).
--epoch_size 150


Fix Adjustment Factors prefix for pysam

Pull Request Template
Fixes https://github.com/NREL/pysam/issues/164. https://github.com/NREL/ssc/pull/1196. Branch for PySAM upcoming.
Doesn't exactly address https://github.com/NREL/SAM/issues/1661, but that one will require some more effort, and I'm not sure if it's really needed
Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes # (issue)
Type of change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
[ ] This change modifies variables in existing compute modules. Please see Checking for PySAM Incompatible API Changes.

@cpaulgilman Yes, fixed, thanks!


Add test for pods number not updating

Follow-up to #2728

@fbarl good suggestions, mind taking another look?


Add detection example from image

Addresses https://github.com/szagoruyko/cifar.torch/issues/11

Removed the unnecessary code

thanks Francisco, one more thing, can you do
local model_path = arg[1]
local image_paths = tablex.sub(arg, 2, -1)

for readability

Sure, no problem.
Just pushed the changes

Wait, forgot to import pl

Done

thanks!


several build issues (nightly-x86_64-pc-windows-msvc/rustc 1.25.0-nightly (27a046e93 2018-02-18))

I tried building the webgl demo of the current commit (82be5d12d16eb14fa81fbc70a32744141b4bf36d)
First, npm run build fails with the following output
><EMAIL_ADDRESS>build D:\development\pathfinder\demo\client
> webpack

'webpack' is not recognized as an internal or external command,
operable program or batch file.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>build: `webpack`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

After calling npm install --save-dev webpack, the client build succeeds. However, building the server with cargo run --release fails with the following:
   Compiling pathfinder_path_utils v0.1.0 (file:///D:/development/pathfinder/path-utils)
error: expected outer doc comment
  --> font-renderer\src\directwrite\mod.rs:39:1
   |
39 | //! Font loading using Windows DirectWrite.
   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |
   = note: inner doc comments like this (starting with `//!` or `/*!`) can only appear before items

If I remove the (erroneous?) doc comment, the build fails with several errors like
   Compiling pathfinder_font_renderer v0.1.0 (file:///D:/development/pathfinder/font-renderer)
error[E0432]: unresolved import `pathfinder_path_utils`
  --> font-renderer\src\directwrite\mod.rs:16:5
   |
16 | use pathfinder_path_utils::PathCommand;
   |     ^^^^^^^^^^^^^^^^^^^^^ Maybe a missing `extern crate pathfinder_path_utils;`?

Yeah, the DirectWrite support hasn't been updated to use Lyon yet.

Is there a specific commit that should still work?
Should I add a separate issue due to webpack being in the wrong category (it should be a dev dependency)?

Let's see if 45a812d fixes the latter.
I'm working on upgrading DirectWrite. Earlier commits prior to the Lyon change should work for now.


Proposal: Replace pyBarcode with your project at awesome-python

Not a bug, just a proposal ;)
https://github.com/vinta/awesome-python#image-processing lists the unmaintained pyBarcode project, Maybe it would make sense to open an issue an suggest to list python-barcode instead.

Appreciate the hint. I've addressed it in https://github.com/vinta/awesome-python/pull/1606.


Vera integration with HASS broken in 0.83.X

Home Assistant release with the issue:

Last working Home Assistant release (if known):
Operating environment (Hass.io/Docker/Windows/etc.):

Component/platform:

Description of problem:
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

Traceback (if applicable):

Additional information:

Home Assistant release with the issue: 0.83.X
Last working Home Assistant release (if known): 0.82.1
Operating environment (Hass.io/Docker/Windows/etc.): Docker
Component/platform: Vera
Description of problem:
Discovered lights are not responding when turning them "on". Turn "off" works for some modules

Any errors in the HA log when you try to turn lights on?


Feature request: run/test ETL-packages on a remote server

Right now, ETL packages can be tested on the same server on which NBi runs.
When deploying ETL packages to a productive environment while the NBi-instance runs on a test-server it would be nice to enable running tests for the productively deployed ETL-packages without deployment of a second NBi/NUnit-instance.
It's a nice to have, low priority from my point of view.
reference: http://www.nbi.io/docs/etl-define/

The blocking point at the moment is the need that I open-source another project to "remotely execute a package" ... but it's planned.


Facebook login - Redirect issue

Hello,
I've tried to implement a facebook login and first started by adding a button :
<button ng-click="authenticate('facebook', {params: oAuthForm})" class="btn btn-primary">Facebook</button>

And have my app configured like so :
config(['$authProvider', function($authProvider) {
      $authProvider.configure({
        apiUrl: '/api/v1',
        authProviderPaths: {
          facebook: '/auth/facebook',
          google:   '/auth/google'
        }
      });

Have my onmniauth.rb initializer setup like so :
Rails.application.config.middleware.use OmniAuth::Builder do
  provider :facebook,      ENV['FACEBOOK_KEY'], ENV['FACEBOOK_SECRET'], :scope => 'email,user_birthday'
end

And Facebook configured like I normally do, with app turn on for everyone to see with right key/secret,  domain etc.
So when I click the Facebook button I pasted html for previously, the new tab opens (tested in chrome) and I'm prompted for facebook login.
I enter the facebook credentials (I wasn't logged in before), and I get redirected to this url:
http://api/v1/auth/facebook/callback#_=_

A log snippet :
Redirected to //api/v1/auth/facebook/callback
Completed 302 Found in 2365ms (ActiveRecord: 0.0ms)

Which lead me back to DeviseTokenAuth::OmniauthCallbacksController#redirect_callbacks . To be more precise this part :
redirect_route = "/#{Devise.mappings[devise_mapping].as_json["path"]}/#{params[:provider]}/callback"

Which is ok, but since the facebook login opened in a new tab, and there was no application running here, the redirect was wrong, so I changed it to this (might not be the best thing) :
redirect_route = "#{request.protocol}#{request.host_with_port}#{Devise.mappings[devise_mapping].as_json["path"]}/#{params[:provider]}/callback"

Which then redirects me to (lvh.me is localhost):
Redirected to http://lvh.me:3000/api/v1/auth/facebook/callback

Which then unveils the new issue which should be treated as a separate issue. I'll just mention what it is (from the log) :
Started GET "/api/v1/auth/facebook/callback" for <IP_ADDRESS> at 2015-02-28 19:21:01 -0500
Processing by DeviseTokenAuth::OmniauthCallbacksController#omniauth_success as HTML
  Parameters: {"provider"=>"facebook"}
  User Load (0.0ms)  SELECT  "users".* FROM "users" WHERE "users"."uid" = '1386467908335711' AND "users"."provider" = 'facebook'  ORDER BY "users"."id" ASC LIMIT 1
Completed 500 Internal Server Error in 190ms

ActiveRecord::UnknownAttributeError (unknown attribute 'nickname' for User.):
  activerecord (4.2.0) lib/active_record/attribute_assignment.rb:59:in `_assign_attribute'

But assuming that my model has nickname, how would I got about solving the redirect issue described above?  (The one that's commented out)

@lynndylanhurley I had issues before with this(nested version of mount..), but the workaround got to work and I just continued with that. Not able to find it now, not sure if you recall or not I've opened a issue for that case.

Oh right, I remember now. The routing system was refactored to support namespacing and scoping, and I'm wondering if the refactor may have broken the previous method of mounting the routes.
Can you try using the nested version and see if it resolves the issue?

hey @lynndylanhurley good catch. Tried this :
namespace :api, defaults: { format: :json } do
    scope :v1 do
      mount_devise_token_auth_for 'User', at: 'auth'
    end
  end

The login with username/password works now.
However if I try to login with facebook I get this error :
undefined method `[]' for nil:NilClass

In this bit :
# before authentication.
      devise_mapping = request.env['omniauth.params']['resource_class'].underscore.to_sym
      redirect_route = "/#{Devise.mappings[devise_mapping].as_json["path"]}/#{params[:provider]}/callback"

The log :
NoMethodError (undefined method `[]' for nil:NilClass):
  devise_token_auth (0.1.32.beta5) app/controllers/devise_token_auth/omniauth_callbacks_controller.rb:12:in `redirect_callbacks'
  actionpack (4.2.0) lib/action_controller/metal/implicit_render.rb:4:in `send_action'
  actionpack (4.2.0) lib/abstract_controller/base.rb:198:in `process_action'
  actionpack (4.2.0) lib/action_controller/metal/rendering.rb:10:in `process_action'
  actionpack (4.2.0) lib/abstract_controller/callbacks.rb:20:in `process_action'

@lynndylanhurley I just debugged this bit and here is the problem :)
devise_mapping = request.env['omniauth.params']['resource_class'].underscore.to_sym is :user but the Devise.mappings is this :
Devise.mappings
=> {:api_user=>
  #<Devise::Mapping:0x53dbb696
   @class_name="User",
   @controllers={:sessions=>"devise_token_auth/sessions", :registrations=>"devise_token_auth/registrations", :passwords=>"devise_token_auth/passwords", :confirmations=>"devise_token_auth/confirmations"},
   @failure_app=Devise::FailureApp,
   @format=nil,
   @klass=#<Devise::Getter:0x54ef43b1 @name="User">,
   @modules=[:database_authenticatable, :recoverable],
   @path="auth",
   @path_names={:registration=>"", :new=>"new", :edit=>"edit", :sign_in=>"sign_in", :sign_out=>"sign_out", :password=>"password"},
   @path_prefix="/api/v1",
   @router_name=nil,
   @routes=[:session, :password],
   @scoped_path="api/users",
   @sign_out_via=:delete,
   @singular=:api_user,
   @strategies=[:database_authenticatable],
   @used_helpers=[:session, :password],
   @used_routes=[:session, :password]>}

so the :api_user is supposed to be :user

Oh interesting. That does look like a bug. It's strange though, because the test case is almost identical to yours and the tests are all passing.
What version of Devise do you have installed?

Yes indeed very strange.
Devise version is devise (3.4.1)

The question is, why does the Devise mapping represent the User model as :auth_user in the mappings hash. Is your User model nested within an Api module?

@lynndylanhurley Actually its represented it as :api_user when the routes are nested :
namespace :api, defaults: { format: :json } do
    scope :v1 do
      mount_devise_token_auth_for 'User', at: 'auth'
    end
  end

When routes are not nested :
namespace :api, defaults: { format: :json } do
    scope :v1 do
      #mount_devise_token_auth_for 'User', at: 'auth'
    end
  end

mount_devise_token_auth_for 'User', at: '/api/v1/auth'

Then the devise mappings use :user

@c0mrade - thanks for your patience with this issue. I'll dig in tomorrow morning and see if I can replicate the behavior.

no problem, thank you for developing the wonderful gems.
I just got back to developing my app, first time creating angular app. Surely will be fun.
thanks for your time, let me know if you want me to try something else

Hi, I'm trying this gem with twitter and I'm getting the same error.
I'm using this routes:
namespace :api do
  namespace :v1 do
    mount_devise_token_auth_for 'User', at: 'auth'
    resources :supermercados, :defaults => { :format => :json }
  end
end

with these nested routes the devise mapping uses :api_v1_user
so I use the devise methods like this before_action :authenticate_api_v1_user!, but I don't know how to solve the problem with the NoMethodError in DeviseTokenAuth::OmniauthCallbacksController#redirect_callbacks.
I hope you could help me, thanks :)

I'm still hitting the username issue. Has a fix been found for this?

Hello! Any updates on this one?

Having the same problem, with the namescope in routes or without it. Rails 5 and the latest code in master.

Hi there @c0mrade   ,
In an effort to cleanup this project and prioritize a bit, we're marking issues that haven't had any activity in a while with a "close-in-7-days" label. If we don't hear from you in about a week, we'll be closing this issue. Obviously feel free to re-open it at any time if it's the right time or this was done in error!
If you are still having the issue (especially if it's a bug report) please refer to our new Issue Template to provide some more details to help us solve it.
Hope all is well.

hey @zachfeldman no, not having problems anymore, this is good to close, it's an old issue.

guys, some response about the problem? i 'm very confused about how a setting a omniauth provider with this gem.
Someone can help me?

Hi @gustavosantiago this is a closed issue. If you are having an issue, please open a new one and follow the issue template. We'll try to help you troubleshoot there - keep in mind that this is a volunteer run project.


[8.x] Revised FactoryMakeCommand to suffix generated filename with "Factory"

Resolves a filename bug when a new factory is created. When executing the make factory command, the class name is suffixed with "Factory" and the filename is not. This becomes a problem for autoloading, etc.
For example:
php artisan make:factory Test --model=Test
results in:

database/factories/Test.php

<?php

namespace Database\Factories;

use App\Models\Test;
use Illuminate\Database\Eloquent\Factories\Factory;
use Illuminate\Support\Str;

class TestFactory extends Factory
{
    /**
     * The name of the factory's corresponding model.
     *
     * @var string
     */
    protected $model = Test::class;

    /**
     * Define the model's default state.
     *
     * @return array
     */
    public function definition()
    {
        return [
            //
        ];
    }
}

Is this bug only present in 8.x and higher?

Is this bug only present in 8.x and higher?

Well, I would not call it a bug pre-8.x. In earlier versions the file was not suffixed with "Factory" but that was fine because earlier versions also did not contain a class.

Right, thanks for clarifying.

It's not a bug. It's expected to include the Factory suffix in the generator command atm.

@driesvints agreed, but it is not including the suffix for the filename so the class literally doesn't work with autoloading.

@aidan-casey yeah I can definitely see the benefit of this PR. Just wanted to clarify that the current behavior is expected.

@driesvints Looking at this further, it looks like the model name is used for the class name but the name parameter is used for the filename. So basically, unless I pass the model name suffixed by "Factory" to the make command, stuff wouldn't match up at all.
Would be helpful to put in another commit to address that?

@aidan-casey can you clarify? So this PR isn't ready?

@taylorotwell - This PR is ready, it would simply tack on "Factory" to the filename allowing it to be compliant for autoloading.
I just noticed, however, that a different variable is used for the class name vs. filename. The class name is determined from the model passed to the command, the filename is determined by the name parameter passed to the command. I would be happy to update this PR to address that as well.

Fixed.


SSD detection model

Hello. Thank you for providing the ncnn converter tools.
Could you provide the code and/or the base pytorch model you used to parse SSD detection?  SSD support is listed in the readme and in one of the past commit messages but there is no ModelFiles for it.
If you're too busy, please just provide me the model you used as base and so I can adapt and make a PR afterwards.
Thanks

Hi, great thx for your interests on this project:)
The pretrained model I'm afraid is not being able to release at present, because the demo code and model are actually belonging to other developers. I will help you by asking them for the permission.


Should Lisplate parse strings files

Would still require the user to load the strings files however they wish, but should Lisplate be capable of parsing a format for them? Would require less effort on the end user. Does limit options of how strings files should be represented, but does remove the burden of figuring it out.
Two formats are possible:
Props file style. Split based on equals, trim endings. Allow quotes to maintain trailing spaces or = signs. Allow standard escapes (t, n, r, backslash, quote).
My Key=My Value
"A = String "=" maintained spacing    "

JSON style. Rules are well defined and well known.
{
  "My Key": "My Value",
  " A = String ": " maintained spacing    "
}

I feel the JSON is the recommended way, but not going to enforce anything on the user. I don't enforce how templates should be read in. Right now, Lisplate lacks a proper template format and loading of pre-compiled templates entirely.


Add an optional note_description:string field to change_history

https://trello.com/c/qzHbv9S9/181-show-change-notes-and-page-history-at-the-bottom-of-guidance-page
In Service Manual, we're going to have two fields for change notes.
The current form of change history only stores "note" and no second value.
Because other teams use this type, we have made the newer field
optional.
In Service Manual we store change notes like this:

Could you give a bit more detail on the semantic difference between the two fields? From the change along it's not super clear why there are two fields, and what different purposes they support.
At a guess, note is intended to be a short (one line?) summary of the change and note_description is for longer form (multi-line? supporting markup?) description of the change.
Apologies for the semantic nit-picking, but we want content items to be as self-documenting as possible, and avoid confusion down the line - so it's worth investing a bit up front :)

Exactly that - the note_description is the longer form.
@elliotcm mentioned that existing uses of note tend to be short / summaries, so we've tried to make note_description sound like the longer form of note without renaming it. In a perfect world we'd probably rename them into summary and description but that would require other apps to conform.
How about adding descriptions to each field? eg.
"note": {
  "type": "string",
  "description: "A summary of the change"
},
"note_description": {
  "type": "string",
  "description": "A more detailed description of the change"
}

Using the description attributes for the fields is a huge help, thanks. I'm still not sure on the name, and it doesn't help clarify if the longer field has formatting, or is multiline.
(CC @boffbowsh who had an opinion on this from another discussion.)

Can you please explain more about what value this adds? What restriction is in place on the note field that you can't just use that?

An example somewhere might be useful

@boffbowsh Added a screenshot of what we do in service manual

Sorry, I mean an example in one of the format examples. I see why it's necessary now, and think it's fine. But I'm not sure about the name of it. We're in the context of an item of change_history, so maybe something like full_description?

@boffbowsh Added an example https://github.com/alphagov/govuk-content-schemas/pull/280/commits/e71a3110e813499559af578b48a43b8a3fd9d74d

The reason we went with note_description is because we already have note, and _description felt like the natural progression.

I think note_description is a bit non-sensical. It's not a description of a note, it's a description of why a change was made.

Naming! :sweat_smile:
full_description might be good @boffbowsh. It ticks the box of sounding longer than note to me. However it does make note, like a notes field, sound optional to me. note is the required field.
I agree note_description doesn't make much sense by itself but it does sound secondary to note.
My guess is that without renaming note there won't be a really good answer. Y'all have seen more schemas than me so will have a better feel for what is "right".
Amending the descriptions to mention formatting / multiline is good suggestion @dsingleton :+1:

@thehenster @boffbowsh Done.

full_description wouldn't actually be my choice. But I'm wedded to none of them.

I get we're in danger of bikeshedding here, but also this is the first time this has been brought up, and this PR will essentially codify a standard that will be used across all government publishing. It's not an easy thing to change later, either. The name of it needs to make sense to developers in GDS, but also eventually developers in wider government with less readily-available context. I'd like to get the thoughts from someone who's been working full time on the pub API and has done naming of things in this context so far, so maybe @elliotcm, @tuzz, @danielroseman, @steventux or even @heathd would like to comment?

Hey @boffbowsh.  I had a chat with this team when they brought this issue up with us.  The proposed solution here is what we settled on precisely because it doesn't codify a standard for the whole of gov.uk, because it's an optional field that we don't do anything special with.
One thing that could be done to reduce the scope of this is just to add it to the service manual formats rather than all of them, but in any case we have a ticket to address change notes across gov.uk and bring them all together.  Service Manual are aware that this might mean the removal of their extra field if that's the way the research and discussions come out.
https://trello.com/c/we9wSH0S/622-spike-investigate-if-anything-we-want-to-migrate-is-blocked-by-the-way-we-currently-model-change-notes-and-update-types

I agree with @ecm; it might be worthwhile making this change bespoke to the service manual format in the short term, when we address change notes ftw this and other definitions will inform the global definition.

Hello!
Regarding the naming of the field
given that the user input field is labelled "Why the change is being made", perhaps rationale would convey purpose of the field better (or reason_for_change or justification_for_change)?
Regarding the approach of adding an optional field
that seems fine to me, provided that the note field retains the same semantic purpose in both contexts. If not, perhaps consider whether the change_history in a service_manual_guide should actually be a different type such as detailed_change_history. I don't have enough context to say which is more appropriate. I guess it's preferable to avoid diverging if you can, however.
Hope that helps!

I think it's ok to introduce this optional field across all formats as it seems like a sensible addition. It isn't particularly unique to one format and I'd rather we have one way of doing this rather than each publishing app independently arriving at different solutions for this problem.
That being said, I don't think the full_description name is representative of what this field is for and I think @heathd's suggestions are more appropriate. I'd personally prefer reason_for_change, but I'm not opposed to the others.
I will also leave a couple of comments on the file changes that I think should be addressed.

I like reason_for_change too.
I still believe the semantics of note change in the context of the extra field, optional or not. We are changing it's meaning without changing the field. Maybe that's just life though and will be addressed when the publishing team look at their change history story.
Thanks to all for helping out btw :+1:

Can we have a vote on reason_for_change please? I've rebased this thing more times than there are lines of code....

Please add reactions to that comment ^^^ :)

@tuzz Did you want me to mention that the field doesn't support govspeak, in the description?

reason_for_change sounds good to me. Thanks for chiming in, @heathd :)

@elliotcm @tuzz @boffbowsh @heathd Could someone click that merge button please :)

@AndrewVos: @tuzz Did you want me to mention that the field doesn't support govspeak, in the description?

No, that's ok. The example has a newline character so I think that's fine.
:tada: :star:


[BUG] Wrong order of columns

Prerequisites

[ ] Able to reproduce the behaviour outside of your code, the problem is isolated to Laravel Excel.
[x] Checked that your issue isn't already filed.
[x] Checked if no PR was submitted that fixes this problem.

Versions

PHP version: 7.2.20
Laravel version: 5.8.31
Nova version: 2.0.10
Package version: 3.1.15 / 1.1.5

Description
Wrong order of columns in exported excel
Steps to Reproduce

Config Excel Export as following:

(new DownloadExcel)
                ->only([
                    'title',
                    'first_name',
                    'last_name',
                    'email'
                ])
                ->withHeadings([
                    'Title',
                    'Vorname',
                    'Nachname',
                    'E-Mail'
                ])
                ->askForWriterType()

Export as XLS in Nova

Expected behavior:
Order of Data Excel file is: title, first_name, last_name, email
Actual behavior:
Order of Data Excel file is: first_name, last_name, title, email
Additional Information
Order of headings is correct though.
I think the problem is in vendor/maatwebsite/laravel-nova-excel/src/Actions/ExportToExcel.php in replaceFieldValuesWhenOnResource() where the 'resourceFields' are always used first and then the 'only' fields.
Possible solution
 protected function replaceFieldValuesWhenOnResource(Model $model, array $only = []): array
    {
        ...

        // Fix sorting
        $row = array_merge(array_flip($only), $row);

        return $row;
    }

or
 protected function replaceFieldValuesWhenOnResource(Model $model, array $only = []): array
    {
        ...

        // Fix sorting
        uksort($row, function($key1, $key2) use ($only) {
            return (array_search($key1, $only) > array_search($key2, $only));
        });

        return $row;
    }

Feel free to PR a solution that takes the order of columns into account when using the only method

Fixed in next release


update Some Python codes

I have made changes in the python script and before the result is displayed, a preview is shown.

Thanks for contribution. ❤


KAFKA-4779: Fix security upgrade system test to be non-disruptive

The phase_two security upgrade test verifies upgrading inter-broker and client protocols to the same value as well as different values. The second case currently changes inter-broker protocol without first enabling the protocol, disrupting produce/consume until the whole cluster is updated. This commit changes the test to be a non-disruptive upgrade test that enables protocols first (simulating phase one of upgrade).

Started system test run here: https://jenkins.confluent.io/job/system-test-kafka-branch-builder/736/

@apurvam The goal of the test was to verify non-disruptive upgrade from non-secure to secure mode by adding a new protocol and making updates with incremental bounces. But somewhere along the line the test was modified and the test ended up not testing our recommended upgrade path. Instead it tests a path where the cluster is unavailable while is being upgraded. I don't think we need to test that path when there is a recommended alternative.
I think this change to the test is necessary to test the right upgrade scenario and avoid consumer timeouts. But I am not entirely sure it fixes the specific issue in the JIRA.

The system test run https://jenkins.confluent.io/job/system-test-kafka-branch-builder/736/ has passed all tests.

Thank you very much for the PR @rajinisivaram. I am trying to understand where we do the disruptive change. We currently start the broker with the plaintext and client protocol ports open:
        self.kafka.security_protocol = client_protocol
        self.kafka.interbroker_security_protocol = "PLAINTEXT"
        self.kafka.start()

We then start to produce and consume via client_protocol and do the following:
       # Roll cluster to include inter broker security protocol.
        self.kafka.interbroker_security_protocol = broker_protocol
        self.kafka.open_port(client_protocol)
        self.kafka.open_port(broker_protocol)
        self.bounce()

We change the inter-broker protocol, open the ports for client (which seems unnecessary) and broker protocol and then bounce the brokers. The changes should only take effect when we bounce the brokers, right? So, I don't see any period where the we do a disruptive change, but I could be missing something.

Oh, I see. We need to open port with broker protocol for every broker before we change the inter broker protocol and bounce the broker. Got it, thanks.


Progess on iOS port?

It looks like it's been a while since your last update. Have you made any further progress on the iOS version?

Thanks for reminding me. I have everything ready for IOS. I was just not getting a proper time to provide new updates on this repo. Soon I will upload new code for both platform. Thanks for your patience.

Hey, Thanks for patience . I had updated repo for IOS as well. Please use plugin and submit report for errors (if any).


Pagebreak only works with -f markdown (default)

I was trying the filter and didn't work using commonmark_x, until I use -f markdown.
I did use input.md from test samples:
$ pandoc --lua-filter pagebreak.lua input.md -f markdown -t ms > expected.ms
$ pandoc --lua-filter pagebreak.lua input.md -f commonmark_x -t ms > not_expected.ms
$ diff --unified --suppress-common-lines expected.ms not_expected.ms
--- expected.ms 2024-02-21 00:05:06.881878556 -0300
+++ not_expected.ms     2024-02-20 23:40:30.712961487 -0300
@@ -2,7 +2,8 @@
 Lorem ipsum dolor sit amet, consectetuer adipiscing elit.
 Donec hendrerit tempor tellus.
 Donec pretium posuere tellus.
-.bp
+.PP
+\[rs]newpage
 .PP
 Cum sociis natoque penatibus et magnis dis parturient montes, nascetur
 ridiculus mus.

As you can see they're not the same, for -t ms pagebreak should be in both cases .bp.
Same mismatch happens using:

gfm
commonmark
markdown_strict
...

And not just -t ms output, also:

context
asciidoc
html
...

I din't use "expected" files to compare, because clearly they have errors and need to upload again, problems like:
input.md > 1 page break (corrupted maybe?)
expected.adoc > 0 page break
expected.html > 2 page break
expected.context > no exist to compare

$ pacman -Qs pandoc | head -1
local/pandoc-bin 3.1.11-1
$ neofetch --off distro kernel
distro: Arch Linux x86_64
kernel: 6.1.52-1-lts

commonmark_x doesn't support the raw_tex extension for CommonMark input, so (with commonmark_x) it's parsed as a Para, not as a RawBlock (and I guess the filter doesn't recognise this as a page break).
You could set the pagebreak.break-on.form-feed option to allow literal ^L paragraphs to trigger page breaks (see the README).

Thanks 4 the quick answer!
I did search for raw_tex in every markdown variant that pandoc has:
$ pandoc --list-extensions=markdown | grep raw_tex
+raw_tex
$ pandoc --list-extensions=markdown_mmd | grep raw_tex
-raw_tex
$ pandoc --list-extensions=markdown_phpextra | grep raw_tex
-raw_tex
$ pandoc --list-extensions=markdown_strict | grep raw_tex
-raw_tex

This other ones didn't show any output:
$ pandoc --list-extensions=commonmark | grep raw_tex
$ pandoc --list-extensions=gfm | grep raw_tex
$ pandoc --list-extensions=commonmark_x | grep raw_tex

I get from all of this:

-f markdown is the only one enabled by default.
Is possible to enable it with `+raw_tex' in some.
Makes sense because -f markdown has a lot more +extensions, and if I need other one that is disabled, just need to enable it.
Last 3 are not supported, I understand that commonmark and gfm are not supported, but commonmark_x don't makes sense to me.
I will try your suggestion with pagebreak.break-on.form-feed, my .mds are rather small and don't think performance is an issue for now.
Maybe is a good idea to add some of this "markdown variant" compatibility info in the README.

My last resort is to create my own shell script to process ms output and replace \newline to (raw break page ms):
`.bp`{=ms}

then gropdf, to get final pdf. But is just too specific, and I need to change it if I want another output format.

If you go to the extension in the manual and hover over the ± you can see which formats support the extension (I guess this refers to the reader?).

Maybe is a good idea to add some of this "markdown variant" compatibility info in the README.

Yes. A pull request would be welcome!

My last resort is to create my own shell script

I think it would be reasonable to have an option that allows a paragraph consisting only of \newpage. This wouldn't depend on supporting the raw_tex extension, and is actually a variant of the pagebreak.break-on.form-feed option. A pull request for this would be welcome too!

If you go to the extension in the manual and hover over the ± you can see which formats support the extension (I guess this refers to the reader?).

I went to your link and I didn't see the symbol, because your answer, now I did click this one in the same topic and yes, you're right. And I did learn that markdown_github (deprecated) can use it.

Maybe is a good idea to add some of this "markdown variant" compatibility info in the README.

Yes. A pull request would be welcome!

I'm no programmer and did this account just to make Issues 4 software that I like 2 use. Maybe later I'm gonna try to do that, because I previously never did a PR, and English is not my 1st language, but to edit README.md should be easy.

My last resort is to create my own shell script

I think it would be reasonable to have an option that allows a paragraph consisting only of \newpage. This wouldn't depend on supporting the raw_tex extension, and is actually a variant of the pagebreak.break-on.form-feed option. A pull request for this would be welcome too!

If I can get working my shell script, I can leave it here.

PR #5 updated README.md.

Issue #6 proposes adding an option that allows a paragraph consisting only of \newpage (even if not parsed as raw TeX) to indicate a page break.


mattermost: Handle duplicate dm-groups.

Observed in the wild, cause unknown.
Partially fixes: #24131.

Merged and marked as a backport candidate, thanks @alexmv and @mateuszmandera!

Backported to 9.x in https://github.com/zulip/zulip/pull/31584, along with the renames in #30766 to avoid merge conflicts.


Calibration using evaluation - using cartographer autogenerate ground truth and compute  relations metrics for automatic calibration tool

I would like to create a system for automatic calibration of the lua parameters using the above tool:
The method will be as follows:

First creating a ground truth pbstream by using optimization and view by eye that a good map created (optimize_every_n_nodes = 60)
Running on the same bag but change the parameters (optimize_every_n_node = 0)
Run cartographer_compute_relations_metrics between ground truth and the created pbstream
Get the minimum as possible for the sum of : (Abs translational error + Sqr translational error + Abs rotational error + Sqr rotational error).

Does this way make sense?

How would you recommend creating the best ground truth?

For example today for creating ground truth I put parameters in the lua file that consume a lot of resources(high CPU) - include "optimize every_n_node"

As I understood this tool can only help calibrating the trajectory builder parameters(is it true?)
Which parameters would you recommend calibrate using this automatic tool?

Thanks in advance,
Shir

Did you see the documentation for this tool already? It might help to answer some of your questions. https://github.com/cartographer-project/cartographer/blob/master/docs/source/evaluation.rst


Get rid of IP checks in API

Since we've moved to docker, the IP of node container may change, so it is not reliable anymore to check the IP.
The only source of truth for us is a signature.

Solved in scope of https://github.com/Mehonoshin/smartvpn-billing/pull/127


geoNear with GeoJSON should expect maxDistance in metres

The documentation for mongo's geoNear defines maxDistance as being in radians for legacy coordinate pairs and metres for GeoJSON data.
Mongoose's geoNear strips the coordinates from the GeoJSON object (see model.js#L1775) so all calls to mongo's geoNear use legacy coordinate pairs, which isn't what you expect as a developer.
What I expected
Given the following JavaScript:
var location = {
  type : "Point",
  coordinates : [53.123578, -4.102395]
};
var searchOptions = {
  maxDistance : 10,
  spherical : true
}
MyThing.geoNear(location, searchOptions, function (err, results, stats) {
  console.log(results);
})

The results should be limited to those within a radius of 10m.
What happened
The results were limited to those within a radius of 10radians, or 63,710m.

If someone could confirm this as a valid bug I'm happy to have a crack at fixing it.

Please at least mention it in the documentation, I wasted some time because of this. Thanks!


Can't add sources to RunnableWithMessageHistory

Checked other resources

[X] I added a very descriptive title to this issue.
[X] I searched the LangChain documentation with the integrated search.
[X] I used the GitHub search to find a similar question and didn't find it.
[X] I am sure that this is a bug in LangChain rather than my code.
[X] The bug is not resolved by updating to the latest stable version of LangChain (or the specific integration package).

Example Code
python

from langchain_openai import ChatOpenAI, OpenAIEmbeddings
from langchain.chains import create_retrieval_chain
from langchain.chains.combine_documents import create_stuff_documents_chain
from langchain_core.prompts import ChatPromptTemplate, MessagesPlaceholder
from langchain_core.runnables.history import RunnableWithMessageHistory
from langchain_core.runnables import ConfigurableFieldSpec, ConfigurableField
from langchain_community.vectorstores.azuresearch import AzureSearch
from langchain_community.chat_message_histories import RedisChatMessageHistory
from langchain.chains import create_history_aware_retriever
from typing import Any, Callable, Dict
import os
import re

embeddings = OpenAIEmbeddings(
    openai_api_key=os.environ["OPENAI-API-KEY"],
    model="text-embedding-3-small"
)

llm = ChatOpenAI(
    model_name="gpt-3.5-turbo-0125", temperature=0,
    openai_api_key=os.environ["OPENAI-API-KEY"]
)

vector_store = AzureSearch(
    azure_search_endpoint=os.environ["VECTOR-STORE-ADDRESS"],
    azure_search_key=os.environ["VECTOR-STORE-ADMIN-KEY"],
    index_name="products",
    embedding_function=embeddings.embed_query,
)

def _is_valid_identifier(value: str) -> bool:
    """
    Validate an identifier such as user_id or conversation_id.

    Args:
    - value (str): The identifier to be validated.

    Returns:
    - bool: True if the identifier is valid, False otherwise.
    """
    valid_characters = re.compile(r"^[a-zA-Z0-9-_]+$")
    return bool(valid_characters.match(value))

def create_session_factory() -> Callable[[str, str], RedisChatMessageHistory]:
    """
    Create a session factory for Redis based chat history storage.

    Returns:
    - Callable[[str, str], RedisChatMessageHistory]: A function to get chat history based on user_id and conversation_id.
    """
    def get_chat_history(user_id: str, conversation_id: str) -> RedisChatMessageHistory:
        if not _is_valid_identifier(user_id):
            raise ValueError(
                f"User ID {user_id} is not in a valid format. "
                "User ID must only contain alphanumeric characters, "
                "hyphens, and underscores."
            )
        if not _is_valid_identifier(conversation_id):
            raise ValueError(
                f"Conversation ID {conversation_id} is not in a valid format. "
                "Conversation ID must only contain alphanumeric characters, "
                "hyphens, and underscores."
            )

        return RedisChatMessageHistory(
            session_id=f"user:{user_id}:conversation:{conversation_id}",
            url="redis://<IP_ADDRESS>:6379",
            key_prefix="qna-rag"
        )
    return get_chat_history

contextualize_q_system_prompt = """Given a chat history and the latest user question \
which might reference context in the chat history, formulate a standalone question \
which can be understood without the chat history. Do NOT answer the question, \
just reformulate it if needed and otherwise return it as is."""
contextualize_q_prompt = ChatPromptTemplate.from_messages(
    [
        ("system", contextualize_q_system_prompt),
        MessagesPlaceholder("chat_history"),
        ("human", "{input}"),
    ]
)

history_aware_retriever = create_history_aware_retriever(
    llm,
    vector_store.as_retriever(
        search_kwargs={"k": 2}
    ).configurable_fields(
        search_kwargs=ConfigurableField(
        id="search_kwargs_retriever",
        name="Search Kwargs",
        description="The search kwargs to use",
    )
),
    contextualize_q_prompt
)

qa_system_prompt = """Answer the user's questions based on the below context.
If the context doesn't contain any relevant information to the question, don't make something up and just say "I don't know":

<context>
{context}
</context>"""
qa_prompt = ChatPromptTemplate.from_messages(
    [
        ("system", qa_system_prompt),
        MessagesPlaceholder("chat_history"),
        ("human", "{input}"),
    ]
)

question_answer_chain = create_stuff_documents_chain(llm, qa_prompt)

rag_chain = create_retrieval_chain(history_aware_retriever, question_answer_chain)

conversational_rag_chain = RunnableWithMessageHistory(
    rag_chain,
    create_session_factory(),
    input_messages_key="input",
    history_messages_key="chat_history",
    history_factory_config=[
        ConfigurableFieldSpec(
            id="user_id",
            annotation=str,
            name="User ID",
            description="Unique identifier for the user.",
            default="",
            is_shared=True,
        ),
        ConfigurableFieldSpec(
            id="conversation_id",
            annotation=str,
            name="Conversation ID",
            description="Unique identifier for the conversation.",
            default="",
            is_shared=True,
        ),
    ],
    output_messages_key="answer"
)

Error Message and Stack Trace (if applicable)
No response
Description
I do not know how to add sources to the rag chain up above, I tried multiple solutions like using load_qa_with_sources chain but that doesn't seem to work. I also tried this but am unable to figure out how to add it into my conversational_rag_chain above. All I want to do is return sources along with the answer for the conversational_rag_chain. I did try out what was recommended in this discussion still not able to make it work. No help on discussions, kapa_ai_bot or dosubot or the community, hence the issue here
System Info
System Information
------------------
> OS:  Linux
> OS Version:  #1 SMP Wed Mar 2 00:30:59 UTC 2022
> Python Version:  3.11.8 (main, Feb  7 2024, 22:38:59) [GCC 12.2.0]

Package Information
-------------------
> langchain_core: 0.1.35
> langchain: 0.1.13
> langchain_community: 0.0.29
> langsmith: 0.1.31
> langchain_cli: 0.0.21
> langchain_openai: 0.0.8
> langchain_text_splitters: 0.0.1
> langchainhub: 0.1.15
> langserve: 0.0.51

Packages not installed (Not Necessarily a Problem)
--------------------------------------------------
The following packages were not found:

> langgraph

I am not trying to modify conversational RAG chain, it is just a variable name and not a chain within Langchain's documentation. Can you please take that into consideration and then respond. FYI conversational_rag_chain is just one variable placeholder for the custom chain that I have created

Let me see

@liugddx Were you able to find anything?

@liugddx Were you able to find anything?

Sorry, I'm busy now, I will deal with this problem as soon as possible

Any update @liugddx

I have been able to verify that sources are shown in the above chain but langserve's RemoteRunnable isn't displaying the sources and hence closing this issue


As a user I can sort and filter based on user input data

This was requested by Eli Johnson
Is it possible to sort and filter on output buttons? For example, if I mark 10 of 15 plots as correct, can I then filter out the 10 panels I marked as correct so I can just display and talk about the bad plots with colleagues?

duplicate


Language file problem

Hello,
I want to switch my server to 1.13 (currently 1.12.2) we put the last update of your plugin with the new configuration files. I have selected the default language on FR for French but basic in the plugin there is no corresponding file while in your old version though. On the other hand the plugin create a file Words_fr but everything is in English. Could you help me ? Moreover, when I modify the last part of the plugin on the form of the GUI menu with the / jobs join it does not work. I have no major error in the console.
Thank you very much, congratulations on your plugin, which remains very good!

It's all in English because you have not seen the latest version of the file yet. We recently updated the files with new methods, in this comment you will find: https://github.com/Zrips/Jobs/issues/283#issuecomment-436291200
Send the configuration where your problem is.

163af81253e966d6e8408934442ea7782e591b54


configure use of builtin LED

Use of a port conflicted with the LED in this lib. So added an option to configure use of builtin LED.

LGTM. Can you also add the option into the other example ESPAsync_WiFi_MQTT to save me some time. Then I'll merge.
Thanks,

Sure. Done. :-)

Merged. Will be in next release.
Thanks

Your last commit f8eb24c12d0a1f1badffa52022d91f798fc1ddaf reverted this merged PR. It looks like you took old sources when applying the allman astyle ...


Inconsistent argument names.

Just find it a wee bit odd that in the transformers library predictions are those made by the model:
https://github.com/huggingface/transformers/blob/master/src/transformers/trainer_utils.py#L51-L61
While in many datasets metrics they are the ground truth labels:
https://github.com/huggingface/datasets/blob/c3f53792a744ede18d748a1133b6597fdd2d8d18/metrics/accuracy/accuracy.py#L31-L40
Do you think predictions & references should be swapped? I'd be willing to do some refactoring here if you agree.

Also for the Accuracy metric the accuracy_score method should have its args in the opposite order so accuracy_score(predictions, references,,,).

Thanks for pointing this out ! 🕵🏻
Predictions and references should indeed be swapped in the docstring.
However, the call to accuracy_score should not be changed, it signature being:
sklearn.metrics.accuracy_score(y_true, y_pred, *, normalize=True, sample_weight=None)

Feel free to open a PR if you want to fix this :)


Added ifremer

I have added functionality in the GliderDataFetcher class to specify the server. Defaults to IOOS.
If the user supplies the ifermer ERDDAP, a different set of variables is requested so satisfy ifremer's naming conventions (TEMP rather than temperature etc.)
Ifremer stores all glider data in one big table, so I have added a method where the user can specify the glider deployment with a string.
Finally I have made a new notebook demonstrating the above functionality.

Thanks @callumrollo! I'll work on the CI failures now to avoid merging failing PRs in the future.
(It is the docs and some pre-commit stuff that are failing.)


Create a second expandable auxiliary array

Some cards require storing multiple large arrays such as polytheism needing a card id array and a color count array.

Many of these cards need an auxiliary array which only gets reset at the end of each action (e.g. Polytheism, Legend, Dancing Girl, Democracy). So we will want it to be keyed by card ID and player at least.

Maze needs something similar but it can't be action-scoped.

Oh I don't think Maze needs this after all! I'll give that card a shot.


Add IIIF schema.

Work towards #50
What this doesn't include is validation and any form work.

Should we consider adding it to the RDF::Vocab gem once IIIF/iiif.io#551 is fixed?

@jpstroop https://github.com/ruby-rdf/rdf-vocab/blob/develop/lib/rdf/vocab/iiif.rb The ontology is there already, this is more like the accessors for mapping from instance methods to predicates.

I added a spec in there to make sure the viewing hint on GenericFile would update, and it appears to - maybe I should just delete that spec?

I guess you're technically testing the behavior of GenericFile here and therefore shouldn't have to, but I'm not going to complain about an extra spec.

@jpstroop I'm gonna remove it and trust our layers. Extra second of spec for something I can't make fail doesn't seem worth it.

Heh, fair enough. But did we decide that we're storing the literals instead?
https://github.com/pulibrary/plum/blob/iiif_properties/spec/models/generic_file_spec.rb#L8

(Maybe I don't understand what that code is doing well enough....)

@jpstroop That's just making sure that the method #viewing_hint maps to the viewingHint predicate. The literals stuff will come in for the validation PR.


wasm-encoder: Change the I64xLeS instruction encoding

Change the u32 field of the I64x2LeS instruction from 0xDD to 0xDA (decimal 218) to match the spec.

This should fix https://github.com/bytecodealliance/wasm-tools/issues/812.

Thanks for taking a look. By the way, any idea when the next release would be?

I'm preparing that in https://github.com/bytecodealliance/wasm-tools/pull/815


Fix: Removing quotes for prependCommand

Fixed bug with https://github.com/Voxelum/x-minecraft-launcher/issues/857

Like I suggested, you can make this support passing array.
Though, on the launcher side (or UI layer). You need to parse the user input textbox string into a string array.
The splitting algorithm can be found in https://github.com/Voxelum/x-minecraft-launcher/blob/626058eefd4ff23762ee3d17897e6e2426ffadf3/xmcl-runtime/instanceIO/parseVanillaInstance.ts
There is a function named function splitCommandLine(command: string): string[].
You can use that function to handle the prepend commands like "some/path/with space/some/exe" --argument

I fixed in other branch. You can try it.


About fine-tuned detector

Hi, I wonder after fine-tuning the object detector on HICO-DET, whether you retrain your hoi classification model or just replace the object detector at the test time.

Hi, @hoyeYang
As shown in the table of performance on the front page, all results correspond to a single model, which we trained using a pre-trained object detector. So to answer your question, we did not re-train our model after fine-tuning the detector. This is out of concerns for fair comparison, since other works that used fine-tuned detectors also did not re-train their models (or at least we think so).
Let me know if you have other questions.
Cheers,
Fred

Hi, @hoyeYang
As shown in the table of performance on the front page, all results correspond to a single model, which we trained using a pre-trained object detector. So to answer your question, we did not re-train our model after fine-tuning the detector. This is out of concerns for fair comparison, since other works that used fine-tuned detectors also did not re-train their models (or at least we think so).
Let me know if you have other questions.
Cheers,
Fred

Thanks a lot. I'll close this issue.

Thanks a lot. I'll close this issue.


Added copy of the code here

added duplicate of my code here

Hello @shuhad786
Good job so far 👍
JavaScript best practices
type checks.✔
naming.✔
simplicity.✔
DRY.✔


About sequence formulation for instance segmentation

Excuse me,
I am interested in Pix2Seq, and trying to better understand it.
I wonder how instance segmentation targets are formulated for training. To be more specific,

How to convert coco annotations into target sequences? (especially those with more than one polygon)
Do the starting point and direction matter?
Is there any design handling the varying length of target sequences?

It would be nice if you can provide these details at your convenience.
Thank you!

How to convert coco annotations into target sequences? (especially those with more than one polygon)

we use a separator to indicate different polygon.s

Do the starting point and direction matter?

we randomly pick the starting point, and follow the same direction as in the annotation.

Is there any design handling the varying length of target sequences?

We use ending token to indicate the end of the sequence. We simply truncate the sequence if it turns out to be longer than predefined max seq len (which is rare and happens when the annotation is very fine-grained).
Hope this helps.

Thank you for detailed response. I have got it now!
It's really surprising that such a simple solution achieves these good results.

How to do it, in more detail？


hie-bios --help now works even with a faulty hie.yaml

Running hie-bios --help in a folder with a faulty hie.yaml would crash
straightaway with for instance:
hie-bios: AesonException "Error in $.cradle.cradle: Not a known cradle type. Possible are: cabal, stack, bios, direct, default, none, multi"

without displaying the help. This should not happen.
NB: Would you mind if I opened a PR to add a flake.nix ? like haskell-language-server does.

LGTM, thanks!

NB: Would you mind if I opened a PR to add a flake.nix ? like haskell-language-server does.

What would be the guarantees (e.g. you can build the executable, etc...)?
I am not generally opposed to it, but even as a nix user, I often feel the cost of supporting builds with nix outweigh the benefits. We need CI, an experimental nix feature, and I worry nix pushes away new contributors.

I wanted to provide just enough to run nix develop, I dont want to commit to install a CI etc. I usually use nix just to get some system libraries + ghc since it is indeed hard to build haskell stuff via nix (I gave haskell.nix a try but it has its own issues)

If we don't commit to maintain it, I personally see little value in it. You can open a PR so others can see and use it, but I don't think we would merge it then


datatables editor select2 - Uncaught Error: Error adding field - unknown field type select2

Summary of problem
I've a Laravel 9 installation, in dev console show Uncaught Error: Error adding field - unknown field type select2.
Before working but after asset build with mix not!
Can you provide a guideline to check my integration ? Select2 before work perfectly,  in my laravel project not commits changing anything!!!

Operating System win11 pro dev
PHP Version 8.1
Laravel Version 9
Laravel-DataTables Version 9

I have the same problem and haven't been able to solve it yet


EM27 sensor panel needs a minimum width for sensor values

Tagging @dc2917.
Currently on my machine it looks like this:

Ideally we want to be able to see the sensor values, whatever the size of the window. I'm not sure what the right fix is. Either we need to set a minimum width (in pixels) for the QGridLayout's column or for the QLineEdits themselves. Alternatively there may be an option to keep a QLineEdit wide enough that its text is always visible.

Yeah, I had a go at sorting out the row sizes and scaling as I tried to line up the LED with the QLineEdits now that they're in separate layouts, but to no avail. Qt is quite annoying in this regard. I need to work out the right combination of setting geometry, sizeHint, columnMinimumWidth, columnStretch, as well as setSizePolicy.


Move enzymeMap to package level, compile regular expressions only once

I think that this might be useful and perform better if you're calling getBaseRestrictionEnzymes multiple times in the same function. Before this change, getBaseRestrictionEnzymes would compile the same regular expressions over and over.

@matiasinsaurralde it looks like @Koeng101 defined enzymeMap as a function so that it'd behave as a constant.
https://qvault.io/2019/10/21/golang-constant-maps-slices/
Do you remember the reasoning behind this @Koeng101?

Thanks for the PR @matiasinsaurralde! It looks like @Koeng101 defined enzymeMap as a function so that it'd behave as a constant but maybe it's no longer necessary that it does.
https://qvault.io/2019/10/21/golang-constant-maps-slices/
Do you remember the reasoning behind this @Koeng101?

The reason was I just wanted an easy way to see default enzymes. However, the reasoning to put it behind a function makes sense to me.


Doc request: CONTRIBUTING.md

Hey,
I have just opened a small PR against this repo to fix some incorrect documentation. I basically had to look up what other people were doing in terms of naming branches and pull requests, although there is no particular consensus.
We should add a CONTRIBUTING.md which either includes how you would like this information delivered like the main repo has, or some text saying that it can come however the individual likes.

Closing this as we have a contributing guide now.


[gui error report] Error: ipfs daemon failed to start and produced no output (see error.log

 ipfs daemon failed to start and produced no output (see error.log for details)

Desktop: 0.39.0
OS: darwin 22.6.0 x64
Electron: 32.2.0
Chrome: 128.0.6613.178

Error: ipfs daemon failed to start and produced no output (see error.log for details)
    at errorTemplate (/Applications/IPFS Desktop.app/Contents/Resources/app.asar/src/daemon/migration-prompt.js:78:49)
    at loadWindow (/Applications/IPFS Desktop.app/Contents/Resources/app.asar/src/daemon/migration-prompt.js:129:26)
    at showMigrationPrompt (/Applications/IPFS Desktop.app/Contents/Resources/app.asar/src/daemon/migration-prompt.js:134:3)
    at startIpfsWithLogs (/Applications/IPFS Desktop.app/Contents/Resources/app.asar/src/daemon/daemon.js:193:9)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async startDaemon (/Applications/IPFS Desktop.app/Contents/Resources/app.asar/src/daemon/daemon.js:216:27)
    at async startIpfs (/Applications/IPFS Desktop.app/Contents/Resources/app.asar/src/daemon/index.js:49:17)
    at async setupDaemon (/Applications/IPFS Desktop.app/Contents/Resources/app.asar/src/daemon/index.js:116:3)
    at async Promise.all (index 1)
    at async run (/Applications/IPFS Desktop.app/Contents/Resources/app.asar/src/index.js:68:5)

@RastaDjuss can you please provide the log files you have in ~/Library/Application Support/IPFS Desktop/? (Log locations for different OS are defined at https://github.com/ipfs/ipfs-desktop#where-are-my-ipfs-configuration-and-log-files)


Nuclearcraft Radiation Crashes Essentia Brazier

Placing a brazier in a world with Nuclearcraft Radiation enabled causes the game to crash. The related crash report is attached.
crash-2019-07-11_20.31.02-server.txt

Glad this was resolved, thanks!


Test for inaccuracy?

Hi,
I was looking through your README and I saw this statement:
Deep-space calculations appear to be slightly off. Cause is currently unknown
How are you arriving at this conclusion? I've run the tests but they all pass. There is one test under dpper where you do an assert_similiar-- is this what you mean by the accuracy being slightly off?
I would like to investigate this issue and fix it if possible. If I know how to validate the precision, I can work to resolve it.

There's a couple tests (where I used assert_similar) where they're off by a bit more than I expected due to floating-point math errors, and still haven't quite figured out the source yet. I'm not a subject-matter expert so I'm not too sure the impact of this on actual use
It's possible they're all working fine - the test cases were generated using the javascript implementation so the issue may be on that end and not in this library at all


Pandas Key Error

When I try to get data from differentl technical indicators for a specific timestamp for the 1min interval (say '2020-03-27 15:56'), it works perfectly for the MACD. However, when I try querying RSI, VWAP, or SMA with the same timestamp I get KeyError: '2020-03-27 15:56' despite the code being very similar for the two.
    if req is 'ta':
        indicator = reqExtra[0]
        interval = reqExtra[1]
        if reqExtra[2] is None:
            timestamp = datetime.now().strftime("%Y-%m-%d %H:%M")
        else:
            timestamp = reqExtra[2]
        if len(reqExtra) > 3:
            time_period = int(reqExtra[3])
        else:
            time_period = 20
        ti = TechIndicators(key=api_key, output_format='pandas')
        if indicator is 'macd':
            data, meta_data = ti.get_macd(symbol=stock, interval=interval)
            return data[timestamp]
        elif indicator is 'rsi':
            data, meta_data = ti.get_rsi(symbol=stock, interval=interval, time_period=time_period)
            return data[timestamp]
        elif indicator is 'sma':
            data, meta_data = ti.get_sma(symbol=stock, interval=interval, time_period=time_period)
            return data[timestamp]
        elif indicator is 'vwap':
            data, meta_data = ti.get_vwap(symbol=stock, interval=interval)
            return data[timestamp]

Do you have any suggestions for why this is the case? For the other indicators, I am able to query up to the hour timestamp, but after that I get this key error from pandas, but with MACD it works even with the minute timestamp.

This is the output I get in console:

could you try adding a breakpoint at one of the offending lines to manually search the data frame for your desired timestamp?
e.g.
elif indicator is 'rsi':             data, meta_data = ti.get_rsi(symbol=stock, interval=interval, time_period=time_period)  breakpoint here>>           return data[timestamp]

The timestamp does appear to be in the dataframe:

Fixed by using: data.loc[timestamp]


data set is too big (which is too big to be held in one machine's mem), and I should break it to small daily set

Thanks for the excellent code.
and I met one question, my data set is too big (which can not be held in one machine's mem), and I should break it to small daily set.
so I should first generate each day's walk result (sequence) and then train by other code(suan as Gensim) as word2vec.
All I want is the random walking result
as for the walking result, should I just return before the part listed as following?
and then save dw_rw to disk for latter training?

You will need to deal with multiprocessing slightly better than I do in the training loop. One option would be to just run the random walk generation and write to the file in the single thread. As for the place, it is correct.

Thanks very much.
Is there any other repo that is available to generate random walk sequence for big data set?
I found when I use data set bigger than 10 million  edge, the memory required would be bigger than my memory capacity(200G)


fix(deps): update module github.com/tubenhirn/dagger-ci-modules/v5 to v5.3.9

This PR contains the following updates:

Package
Change
Age
Adoption
Passing
Confidence

github.com/tubenhirn/dagger-ci-modules/v5
v5.3.8 -> v5.3.9

Release Notes

tubenhirn/dagger-ci-modules (github.com/tubenhirn/dagger-ci-modules/v5)
v5.3.9
Compare Source
Bug Fixes

deps: update module dagger.io/dagger to v0.11.0 (#274) (ae1d184), closes #274
deps: update module github.com/tubenhirn/dagger-ci-modules/v5 to v5.3.8 (#271) (f7c630b), closes #271

Miscellaneous Chores

deps: update goreleaser/goreleaser docker tag to v1.25.1 (#272) (44b649c), closes #272
deps: update renovate/renovate docker tag to v37.269.3 (#270) (f0108f6), closes #270
deps: update renovate/renovate docker tag to v37.295.0 (#273) (8de1f5b), closes #273

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

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


Fix Docs (Github Pages)

https://mkdocs-mdpo.ga/ currently says "Server not found"

I've now disabled the redirection, so it should be soon available at https://mondeja.github.io/mkdocs-mdpo-plugin/, when DNS will update.
Sorry, this project has been on hold for two years. Don't expect the translations of plugins work at all, maybe nothing works because is outdated. The temporary abandonment was started because in those days, the ecosystem was rapidly changing, so it quicly became a nightmare to maintain, especially plugins like mkdocstrings.
I expect to restart the development in a couple of years or so, when the ecosystem is in a more advanced state of maturation and probably offering a slightly different way of solving this problem, which should be  more stable and maintainable thanks to the new features of Mkdocs >= 1.5.


Python floor division operator (//)

During my work with cpmpy library I have to use two different operators for a division

Single slash for intvar() objects
Double slash (aka floor division) for Python3 int() - as normal division generates float value instead of int

It will be convenient if cpmpy implements both in the same way for simplicity - then we can have the same code for int() and intvar()

Actually since we only support integer variables, we conceptually only support floordivision...
Adding floordivision is trivial and we should do it asap. But this raises the question,

should we continue to support classic /?
should we change the way we print division to be //?

I think the floordivision in Python is less well known, and even unknown to people coming from different modeling languages. So perhaps we should 1. keep / but maybe throw a deprecationwarning that on integer varaibles \\ should be used, and 2. indeed change our printing of div to //?
@IgnaceBleukx @JoD @Wout4 opinions?

It makes a lot of sense to have the same notation for int() as for intvar(), and since we only support floor division on intvar we should probably use '//' here. keeping / with a warning seems ok to me.
And if someone want's to have a float constant like 7 / 3 that still stays possible, although I'm not sure there is a use case for that.

I think we can keep both, a deprication warning might be good. We did the same for the camel-cased IntVar and non-camel-cased alldifferent I think. This raises the question: do we actually stop supporting / when we do a stable release?
We should definitely change the printing to //


Added the To-Do React application

Pull Request Type
What kind of change does this PR introduce?
[x] Solved an issue/task
[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:
Issue Number: #1109
What is the new behavior?
In this code, the useEffect hook is used for loading and saving todos to localStorage. The addTodo, updateTodo, and deleteTodo functions handle adding, updating, and deleting tasks respectively.

Other information

Merged

This is an automated message from Fork, Commit, Merge [BOT].

Thank you for your contribution! Your pull request has been merged. The files have been reset for the next contributor.
What's next?
If you're looking for more ways to contribute, I invite you to check out my other projects. Just click here to find more. These projects contain real issues that you can help resolve. You can also check out the Influences section in the README to find more projects similar to this one.
Also please leave a star to this project if you feel it helped you, i would really appreciate it.
I look forward to seeing your contributions!


problems recompiling application after installation of 1.8 beta

Hi all, I have vs 2015 update 1 with ts 1.8. I just tried to reopen an asp.net 5 application with angular 1 and the usual angular.d.ts files.
After the installation of the installation of 1.8 beta I cannot compile it anymore:
with 1.8 beta installed I received a lot of errors: Build: cannot find namespace 'ng':
uninstalling it (I have both 1.8 beta and 1.7.6 installed I have a single error: Unable to get property 'compilerOptions' of undefined or null reference.
repairing the ts 1.7 installation I obtain this error message: Option 'project' cannot be mixed with source files on a command line.
I worked with another asp.net 4 project and angular without problems.
this is my tsconfig.json
{
    "compilerOptions": {
        "noImplicitAny": false,
        "noEmitOnError": true,
        "removeComments": false,
        "target": "es5",
        "outFile": "wwwroot/js/application.js",
        "inlineSourceMap": true,
        "inlineSources": true
    },
    "exclude": [
        "node_modules",
        "wwwroot"
    ]
}

Am I misiing something about the changes in ts 1.8?

the error message Unable to get property 'compilerOptions' of undefined or null reference. is a bug in TS 1.7 that was fixed in https://github.com/Microsoft/TypeScript/pull/5589.
 Build: cannot find namespace 'ng': is a different issue, can you share your project?

Since is the project of a customer I just sent the link to you via email.
about the #5589, there is any workaround to make it work again? the project was working with 1.7 before.

The 1.7 issue was caused by a missing tsconfig.json file or one with unknown properties. yours look fine to me, so i am guessing it is something with the file location. i will need to see the build logs.

where can I find the logs? If I look in the output windows I see just this:
2>------ Build started: Project: Trace, Configuration: Debug Any CPU ------
2>VSTSC : tsc.js(31087, 13) JavaScript runtime error : Unable to get property 'compilerOptions' of undefined or null reference
========== Build: 1 succeeded or up-to-date, 1 failed, 0 skipped ==========
anyway checking out the same project in my laptop where I have ts 1.7.6 installed the project compiles without problems.

OK. i see the issue now. it should be fixed in the next release, or in the nightly NuGet package.

To clarify, the issue is specific to tsc.exe, enumerating directories looking for .d.ts files.

node tsc.js should work.

thank you very much, how can I find more infos on using nuget packages in my asp.net 5 project? I had similar problems just opening a few angular 2 and aurelia projects, so I would like to check if this fix them too.

here is the info: https://github.com/Microsoft/TypeScript/wiki/Nightly-drops

I'm trying to foolow the indications: since the xproj files doesn't contain the import of the task I left it untouched, Yesterday I added the nuget source in nuget configuration and the **1.8.20160203.1-beta **version of both the packages, but same problem.
Now I see that the 1.8.20160204.1-beta is available: updated the project.json rebuilt the solution but I have this message

What am I missing?

i just tried locally and i do not see this error, i actually used the UI. so righ-click, manage my Nuget Packages, removed exiting TS package, Added myget to package source, reloaded VS, and it seems to work on your project.

Thanks, I updated but I have the problem. _ have checked better and I looks like that at least now the problem is now.
declare var angular: angular.IAngularStatic;
// Support for painless dependency injection
interface Function {
$inject?: string[];
}
from angular.d.ts

// Collapse angular into ng
import ng = angular;
// Support AMD require
declare module 'angular' {
export = angular;
}

the problem is the import ng that is not working
If in my code I replace ng.IHttpService with angular.IHttpService and so on the error disappear, but I don't know if this is not working.


Add constant for NATS default URL

Purpose

$title

Remarks
https://github.com/ballerina-platform/ballerina-lang/issues/20493
https://groups.google.com/forum/#!topic/ballerina-dev/47dGfyiz1QY/discussion
Check List

[x] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Codecov Report

Merging #20494 into release-stage will not change coverage.
The diff coverage is n/a.

@@              Coverage Diff               @@
##           release-stage   #20494   +/-   ##
==============================================
  Coverage          15.21%   15.21%
==============================================
  Files                 50       50
  Lines               1341     1341
  Branches             208      208
==============================================
  Hits                 204      204
  Misses              1121     1121
  Partials              16       16

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 db8f307...be41b52. Read the comment docs.

I think we need to change the base to master

Shouldn't we update the examples too, to demonstrate the URL is optional?


feat: make index.html a little more self hosting friendly

Yes, I'm using replaceAll, but that's because this entire project is about embracing modern javascript ;)

lgtm, thanks


Can't run foundation-apps watch command after application creation

After installing the Foundation-CLI, running foundation-apps new magnolia-lite, changing into the magnolia-lite directory, and running foundation-apps watch I am getting an error.
Current environment:
Mac OS X 10.10.3, Node v0.12.2, NPM 2.7.5, Foundation CLI version 1.1.0
Full error:
➜ magnolia-lite     foundation-apps watch

><EMAIL_ADDRESS>start /Users/devanb/Desktop/magnolia-lite
> gulp ""

[10:08:28] Using gulpfile ~/Desktop/magnolia-lite/gulpfile.js
Error<EMAIL_ADDRESS>start: `gulp ""`
Exit status 1
    at EventEmitter.<anonymous> (/usr/local/lib/node_modules/foundation-cli/node_modules/npm/lib/utils/lifecycle.js:213:16)
    at EventEmitter.emit (events.js:110:17)
    at ChildProcess.<anonymous> (/usr/local/lib/node_modules/foundation-cli/node_modules/npm/lib/utils/spawn.js:14:12)
    at ChildProcess.emit (events.js:110:17)
    at maybeClose (child_process.js:1015:16)
    at Process.ChildProcess._handle.onexit (child_process.js:1087:5)

Can you try running npm start and see if that works?

npm start does work and is what I've been using. Is the Zurb documentation incorrect and I should be using npm start instead?

On Apr 16, 2015, at 15:55, Geoff Kimball<EMAIL_ADDRESS>wrote:
Can you try running npm start and see if that works?
—
Reply to this email directly or view it on GitHub.

npm start is what the CLI runs in the background, so until we get this fixed you can use that command and it'll work just fine.
What versions of Node and npm are you running? Use node -v and npm -v to find out.

@quook What version of Node are you on? Maybe it's an issue with 0.12; most of us here are still running 0.10.

Thanks for the information @gakimball
I'll leave the issue in your all hands then.

@gakimball Node v0.12.2 (new machine, fresh install so latest version of everything). I can run the gulpfile directly with no trouble.

Same error for me, node 0.12.2

Alright, I was able to recreate it in Node 0.12.2, so it's an issue with Node 0.12.x.

Just published version 1.1 of the CLI which addresses this issue. Run npm update -g foundation-cli to get it.


ReferenceError: Can't find variable: lang

After installing the package, i attempted to use the component
<IntlPhoneInput
defaultCountry="VC"
lang="EN"
onChangeText={({ dialCode, unmaskedPhoneNumber }) =>
setPhoneNumber(dialCode + unmaskedPhoneNumber)
}
/>
To reproduce the issue:
Install the package
Attempt to change the country's flag by searching for country's name
Error:
ReferenceError: Can't find variable: lang

this issue solved at version of "1.2.18"


just: 1.31.0 -> 1.32.0

Signed-off-by: Muhammad Falak R Wani<EMAIL_ADDRESS>Description of changes
Diff: https://github.com/casey/just/compare/refs/tags/1.31.0...1.32.0
Changelog: https://github.com/casey/just/blob/1.32.0/CHANGELOG.md

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

@mfrw I’d encourage you to become a maintainer of this package. You’ve updated it a number of times recently and it could use another maintainer as I’ve stepped down.