Python interface: enable use of literal labels

In IRIS, it is possible to use literal labels, which get collected automatically from the rules and added to lexreps. It would be very helpful to have that functionality in Python interface as well.

Literal labels work for words in a Western language, so it's not a general problem. Can you specify which labels you tried?

Literal labels work for words in a Western language, so it's not a general problem. Can you specify which labels you tried?

Sorry, this problem is solved with the adaptations I made to the language compiler last year. Literal labels are extracted from the rules.csv file, and added "add runtime". This was released November 20 (https://github.com/intersystems/iknow/commit/737e984be501ba220a5720304958043dfac9c04e), If Masako can confirm, the issue can be closed.

Sorry, this problem is solved with the adaptations I made to the language compiler last year. Literal labels are extracted from the rules.csv file, and added "add runtime". This was released November 20 (https://github.com/intersystems/iknow/commit/737e984be501ba220a5720304958043dfac9c04e), If Masako can confirm, the issue can be closed.

@JosDenysGitHub - I recall still having issues with using "(" ")" as literal labels in Japanese sometime in November, but I'm not sure if it's before or after your fix. I'll give it a try (both the special characters and more generic Japanese characters) next time I work with the Python interface and report back here. It may be a few days. Stay tuned.

@JosDenysGitHub - I recall still having issues with using "(" ")" as literal labels in Japanese sometime in November, but I'm not sure if it's before or after your fix. I'll give it a try (both the special characters and more generic Japanese characters) next time I work with the Python interface and report back here. It may be a few days. Stay tuned.

I haven't tried using "(" and ")" as literal labels with iknowpy yet, but that didn't work in IRIS in December. So, my guess is that literal labels can be used now, with some exceptions that also exist in IRIS.

I haven't tried using "(" and ")" as literal labels with iknowpy yet, but that didn't work in IRIS in December. So, my guess is that literal labels can be used now, with some exceptions that also exist in IRIS.

I'm quite sure that "(" and ")" as Literal Labels worked in IRIS back in the fall when I used "(" and ")" in rules. However, you are correct, they no longer do anything in rules. Jos, did the work you released in Python on November 20th possibly remove this capability from IRIS by any chance? I personally think they (and other common symbols) should work as literal labels. If not, at least we should get an error message - currently there is no warning to indicate that.

I'm quite sure that "(" and ")" as Literal Labels worked in IRIS back in the fall when I used "(" and ")" in rules. However, you are correct, they no longer do anything in rules. Jos, did the work you released in Python on November 20th possibly remove this capability from IRIS by any chance? I personally think they (and other common symbols) should work as literal labels. If not, at least we should get an error message - currently there is no warning to indicate that.

I did not remove any capability, they should work, but you will not find a "Lit_(" because it is rewritten (str_subsitute(labelName, string("("), string("lbrack"));)
It is called "Lit_lbrack", because of the symbol "(" being used in rules specification.
I'll investigate...

I did not remove any capability, they should work, but you will not find a "Lit_(" because it is rewritten (str_subsitute(labelName, string("("), string("lbrack"));)
It is called "Lit_lbrack", because of the symbol "(" being used in rules specification.
I'll investigate...

I did a small test using "de":
First add 2 extra rules :
650;1;"(";SBegin;force ( to SBegin
651;1;")";SEnd;force ) to SEnd
Rebuild, and then index following text: Index("( morgen )"),"de", true);
Then inspect the traces:
[0]	"LexrepCreated:<lexrep id=3 type=Nonrelevant value="(" index="(" labels="Punctuation;" />;"
[1]	"LexrepCreated:<lexrep id=4 type=Unknown value="morgen" index="morgen" labels="DECon;" />;"
[2]	"LexrepCreated:<lexrep id=5 type=Nonrelevant value=")" index=")" labels="Punctuation;" />;"
[3]	"SentenceFound:<sentence kb="de" ali="0.000000" lang="de" text="( morgen )" />;"
[4]	"UserDictionaryMatch:<lexrep id=1 type=Nonrelevant value="" index="B" labels="SBegin;" />;"
[5]	"UserDictionaryMatch:<lexrep id=3 type=Nonrelevant value="(" index="(" labels="Punctuation;" />;"
[6]	"UserDictionaryMatch:<lexrep id=4 type=Unknown value="morgen" index="morgen" labels="DECon;" />;"
[7]	"UserDictionaryMatch:<lexrep id=5 type=Nonrelevant value=")" index=")" labels="Punctuation;" />;"
[8]	"UserDictionaryMatch:<lexrep id=2 type=Nonrelevant value="" index="E" labels="SEnd;" />;"
[9]	"LexrepIdentified:<lexrep id=1 type=Nonrelevant value="" index="B" labels="SBegin;" />;"
[10]	"LexrepIdentified:<lexrep id=3 type=Nonrelevant value="(" index="(" labels="Lit_lbrack;" />;"
[11]	"LexrepIdentified:<lexrep id=4 type=Unknown value="morgen" index="morgen" labels="DEAdv;DEAdvTime;DEConIfCap;" />;"
[12]	"LexrepIdentified:<lexrep id=5 type=Nonrelevant value=")" index=")" labels="Lit_);" />;"
[13]	"LexrepIdentified:<lexrep id=2 type=Nonrelevant value="" index="E" labels="SEnd;" />;"
[14]	"RuleApplication:rule_id=0;match_length=1;lexrep_match=;<lexrep id=3 type=Nonrelevant value="(" index="(" labels="Lit_lbrack;" />;rule_input="Lit_lbrack;" rule_output="SBegin;" rule_phase=1;"
[15]	"RuleApplicationResult:rule_id=0;match_length=1;<lexrep id=3 type=Nonrelevant value="(" index="(" labels="Lit_lbrack;SBegin;" />;"
[16]	"RuleApplication:rule_id=1;match_length=1;lexrep_match=;<lexrep id=5 type=Nonrelevant value=")" index=")" labels="Lit_);" />;rule_input="Lit_);" rule_output="SEnd;" rule_phase=1;"
[17]	"RuleApplicationResult:rule_id=1;match_length=1;<lexrep id=5 type=Nonrelevant value=")" index=")" labels="Lit_);SEnd;" />;"
[18]	"RuleApplication:rule_id=205;match_length=1;lexrep_match=;<lexrep id=4 type=Unknown value="morgen" index="morgen" labels="DEAdv;DEAdvTime;DEConIfCap;" />;rule_input="DEConIfCap;" rule_output="-DEConIfC...
[19]	"RuleApplicationResult:rule_id=205;match_length=1;<lexrep id=4 type=Unknown value="morgen" index="morgen" labels="DEAdv;DEAdvTime;" />;"
[20]	"RuleApplication:rule_id=244;match_length=1;lexrep_match=;<lexrep id=4 type=Unknown value="morgen" index="morgen" labels="DEAdv;DEAdvTime;" />;rule_input="DEAdvTime;" rule_output="DEAdvTime;" rule_phas...
[21]	"RuleApplicationResult:rule_id=244;match_length=1;<lexrep id=4 type=Unknown value="morgen" index="morgen" labels="DEAdvTime;" />;"
[22]	"RuleApplication:rule_id=249;match_length=1;lexrep_match=;<lexrep id=4 type=Unknown value="morgen" index="morgen" labels="DEAdvTime;" />;rule_input="DEAdvDirection:DEAdvManner:DEAdvModality:DEAdvNonrel...

This looks like normal behaviour to me ?

I did a small test using "de":
First add 2 extra rules :
650;1;"(";SBegin;force ( to SBegin
651;1;")";SEnd;force ) to SEnd
Rebuild, and then index following text: Index("( morgen )"),"de", true);
Then inspect the traces:
[0]	"LexrepCreated:<lexrep id=3 type=Nonrelevant value="(" index="(" labels="Punctuation;" />;"
[1]	"LexrepCreated:<lexrep id=4 type=Unknown value="morgen" index="morgen" labels="DECon;" />;"
[2]	"LexrepCreated:<lexrep id=5 type=Nonrelevant value=")" index=")" labels="Punctuation;" />;"
[3]	"SentenceFound:<sentence kb="de" ali="0.000000" lang="de" text="( morgen )" />;"
[4]	"UserDictionaryMatch:<lexrep id=1 type=Nonrelevant value="" index="B" labels="SBegin;" />;"
[5]	"UserDictionaryMatch:<lexrep id=3 type=Nonrelevant value="(" index="(" labels="Punctuation;" />;"
[6]	"UserDictionaryMatch:<lexrep id=4 type=Unknown value="morgen" index="morgen" labels="DECon;" />;"
[7]	"UserDictionaryMatch:<lexrep id=5 type=Nonrelevant value=")" index=")" labels="Punctuation;" />;"
[8]	"UserDictionaryMatch:<lexrep id=2 type=Nonrelevant value="" index="E" labels="SEnd;" />;"
[9]	"LexrepIdentified:<lexrep id=1 type=Nonrelevant value="" index="B" labels="SBegin;" />;"
[10]	"LexrepIdentified:<lexrep id=3 type=Nonrelevant value="(" index="(" labels="Lit_lbrack;" />;"
[11]	"LexrepIdentified:<lexrep id=4 type=Unknown value="morgen" index="morgen" labels="DEAdv;DEAdvTime;DEConIfCap;" />;"
[12]	"LexrepIdentified:<lexrep id=5 type=Nonrelevant value=")" index=")" labels="Lit_);" />;"
[13]	"LexrepIdentified:<lexrep id=2 type=Nonrelevant value="" index="E" labels="SEnd;" />;"
[14]	"RuleApplication:rule_id=0;match_length=1;lexrep_match=;<lexrep id=3 type=Nonrelevant value="(" index="(" labels="Lit_lbrack;" />;rule_input="Lit_lbrack;" rule_output="SBegin;" rule_phase=1;"
[15]	"RuleApplicationResult:rule_id=0;match_length=1;<lexrep id=3 type=Nonrelevant value="(" index="(" labels="Lit_lbrack;SBegin;" />;"
[16]	"RuleApplication:rule_id=1;match_length=1;lexrep_match=;<lexrep id=5 type=Nonrelevant value=")" index=")" labels="Lit_);" />;rule_input="Lit_);" rule_output="SEnd;" rule_phase=1;"
[17]	"RuleApplicationResult:rule_id=1;match_length=1;<lexrep id=5 type=Nonrelevant value=")" index=")" labels="Lit_);SEnd;" />;"
[18]	"RuleApplication:rule_id=205;match_length=1;lexrep_match=;<lexrep id=4 type=Unknown value="morgen" index="morgen" labels="DEAdv;DEAdvTime;DEConIfCap;" />;rule_input="DEConIfCap;" rule_output="-DEConIfC...
[19]	"RuleApplicationResult:rule_id=205;match_length=1;<lexrep id=4 type=Unknown value="morgen" index="morgen" labels="DEAdv;DEAdvTime;" />;"
[20]	"RuleApplication:rule_id=244;match_length=1;lexrep_match=;<lexrep id=4 type=Unknown value="morgen" index="morgen" labels="DEAdv;DEAdvTime;" />;rule_input="DEAdvTime;" rule_output="DEAdvTime;" rule_phas...
[21]	"RuleApplicationResult:rule_id=244;match_length=1;<lexrep id=4 type=Unknown value="morgen" index="morgen" labels="DEAdvTime;" />;"
[22]	"RuleApplication:rule_id=249;match_length=1;lexrep_match=;<lexrep id=4 type=Unknown value="morgen" index="morgen" labels="DEAdvTime;" />;rule_input="DEAdvDirection:DEAdvManner:DEAdvModality:DEAdvNonrel...

This looks like normal behaviour to me ?

For me (in IRIS Japanese), using "(" and ")" in rules (without the escape character) results in an error "Break // cannot continue" - I think it's because it conflicts with one of the lexreps. I think I've always used "(" and ")" to work around it.
At any rate, your German case may work because "(" and ")" are not associated with any other label. For me, the symbols have labels, but I need the certain rules to fire only for the particular symbols. In the trace, I see:
Lexrep("(")=BracketOpen+JPPlusMinus
This seems to indicate that the literal label is not being added. Is that right?

For me (in IRIS Japanese), using "(" and ")" in rules (without the escape character) results in an error "Break // cannot continue" - I think it's because it conflicts with one of the lexreps. I think I've always used "(" and ")" to work around it.
At any rate, your German case may work because "(" and ")" are not associated with any other label. For me, the symbols have labels, but I need the certain rules to fire only for the particular symbols. In the trace, I see:
Lexrep("(")=BracketOpen+JPPlusMinus
This seems to indicate that the literal label is not being added. Is that right?

I tried removing the lexrep that gives the 2 labels. But the trace reveals that the Literal label is still not being picked up:
Lexrep("(")=Punctuation
So I guess my theory about German working was wrong. Perhaps the problem is specific to Japanese...?

I tried removing the lexrep that gives the 2 labels. But the trace reveals that the Literal label is still not being picked up:
Lexrep("(")=Punctuation
So I guess my theory about German working was wrong. Perhaps the problem is specific to Japanese...?

If you get:
Lexrep("(")=BracketOpen+JPPlusMinus
This indeed means the literal label is not assigned, so this might indeed be a Japanese speciality :-)
I'll investigate...

If you get:
Lexrep("(")=BracketOpen+JPPlusMinus
This indeed means the literal label is not assigned, so this might indeed be a Japanese speciality :-)
I'll investigate...

I added the same (dummy) rules as specified above, and then indexed following text : "( 資源第一本部長 )".
From the traces I get :
| Name | Value | Type
-- | -- | -- | --
▶ | [26] | "LexrepIdentified:<lexrep id=3 type=Unknown value="(" index="(" labels="BracketOpen;JPPlusMinus;JPParenOpen;Lit_lbrack;" />;" | std::string
| Name | Value | Type
-- | -- | -- | --
▶ | [34] | "LexrepIdentified:<lexrep id=13 type=Unknown value=")" index=")" labels="BracketClose;JPParenClose;Lit_);" />;" | std::string
As expected.
Can you show me the rules that result in an error, that will be the real problem.

I added the same (dummy) rules as specified above, and then indexed following text : "( 資源第一本部長 )".
From the traces I get :
| Name | Value | Type
-- | -- | -- | --
▶ | [26] | "LexrepIdentified:<lexrep id=3 type=Unknown value="(" index="(" labels="BracketOpen;JPPlusMinus;JPParenOpen;Lit_lbrack;" />;" | std::string
| Name | Value | Type
-- | -- | -- | --
▶ | [34] | "LexrepIdentified:<lexrep id=13 type=Unknown value=")" index=")" labels="BracketClose;JPParenClose;Lit_);" />;" | std::string
As expected.
Can you show me the rules that result in an error, that will be the real problem.

I did some experiments today and discovered the problems...
I currently have the rule:
4608;2;typeConcept|JPParenOpen|JPKatakana|JPParenClose;|JPCon-BracketOpen-JPPlusMinus|Join|Join;;
This was actually a workaround for the originally intended rule:
;2;typeConcept|"("|JPKatakana|")";|JPCon-BracketOpen-JPPlusMinus|Join|Join;;
This rule results in IRIS, with error:  93 zInsertLiterals+40^Delve.Model.1 ^||%DELVE(")する",1)      Break // cannot continue zParseLanguageModelData+170^Delve.Model.1
I assume this means "(" conflicts with some (not all) of the lexreps that include ")". There are 11 such lexreps that IRIS complained about, so I temporarily commented them out. I then am able to index a sentence such as "アドビル（イブプロフェン）を服用。" and get the expected lexreps identification:
Lexrep("(")=BracketOpen+JPPlusMinus+Lit_lbrack
Lexrep(")")=BracketClose+Lit_)
So, I have two questions:

In the lexreps file, the error causing lexreps were all multi-lexreps. If it's a single-label lexrep, the escaped lexreps (such as "(土)") works without any problem. Perhaps other languages do not have such multi-lexreps? Is there a way to create multi-lexreps that would not conflict with the literal labels?
In the rules file, I thought I worked around the error by using "(" and ")" instead of "(" and ")" in rules. Obviously, that wasn't a workaround -  it didn't cause the error, but it was looking literally for "(" and ")" with the backslashes. Do we ever escape any character in the rules file?

I did some experiments today and discovered the problems...
I currently have the rule:
4608;2;typeConcept|JPParenOpen|JPKatakana|JPParenClose;|JPCon-BracketOpen-JPPlusMinus|Join|Join;;
This was actually a workaround for the originally intended rule:
;2;typeConcept|"("|JPKatakana|")";|JPCon-BracketOpen-JPPlusMinus|Join|Join;;
This rule results in IRIS, with error:  93 zInsertLiterals+40^Delve.Model.1 ^||%DELVE(")する",1)      Break // cannot continue zParseLanguageModelData+170^Delve.Model.1
I assume this means "(" conflicts with some (not all) of the lexreps that include ")". There are 11 such lexreps that IRIS complained about, so I temporarily commented them out. I then am able to index a sentence such as "アドビル（イブプロフェン）を服用。" and get the expected lexreps identification:
Lexrep("(")=BracketOpen+JPPlusMinus+Lit_lbrack
Lexrep(")")=BracketClose+Lit_)
So, I have two questions:

In the lexreps file, the error causing lexreps were all multi-lexreps. If it's a single-label lexrep, the escaped lexreps (such as "(土)") works without any problem. Perhaps other languages do not have such multi-lexreps? Is there a way to create multi-lexreps that would not conflict with the literal labels?
In the rules file, I thought I worked around the error by using "(" and ")" instead of "(" and ")" in rules. Obviously, that wasn't a workaround -  it didn't cause the error, but it was looking literally for "(" and ")" with the backslashes. Do we ever escape any character in the rules file?

The literal insert does not understand the "escape" symbol :
USER 4e1>zwrite ^||%DELVE(")する")
USER 4e1>zwrite ^||%DELVE(")する")
^||%DELVE(")する")=$lb("BracketClose","JPVerb;Join;")
^||%DELVE(")する",1)=2
^||%DELVE(")する",1,1)=$lb(")",$lb("BracketClose"))
^||%DELVE(")する",1,2)=$lb("する",$lb("JPVerb","Join"))
This is why it is failing on IRIS, I'll fix it.

The literal insert does not understand the "escape" symbol :
USER 4e1>zwrite ^||%DELVE(")する")
USER 4e1>zwrite ^||%DELVE(")する")
^||%DELVE(")する")=$lb("BracketClose","JPVerb;Join;")
^||%DELVE(")する",1)=2
^||%DELVE(")する",1,1)=$lb(")",$lb("BracketClose"))
^||%DELVE(")する",1,2)=$lb("する",$lb("JPVerb","Join"))
This is why it is failing on IRIS, I'll fix it.

An neither does HTML, this is what should be displayed:
USER 4e1>zwrite ^||%DELVE("\)する")
USER 4e1>zwrite ^||%DELVE(")する")
^||%DELVE(")する")=$lb("BracketClose","JPVerb;Join;")
^||%DELVE(")する",1)=2
^||%DELVE(")する",1,1)=$lb(")",$lb("BracketClose"))
^||%DELVE(")する",1,2)=$lb("する",$lb("JPVerb","Join"))
USER 4e1>`

An neither does HTML, this is what should be displayed:
USER 4e1>zwrite ^||%DELVE("\)する")
USER 4e1>zwrite ^||%DELVE(")する")
^||%DELVE(")する")=$lb("BracketClose","JPVerb;Join;")
^||%DELVE(")する",1)=2
^||%DELVE(")する",1,1)=$lb(")",$lb("BracketClose"))
^||%DELVE(")する",1,2)=$lb("する",$lb("JPVerb","Join"))
USER 4e1>`

I've been testing the Japanese fix in IRIS, as well as looking at the behaviors of literal labels in iknowpy.

fix in IRIS together with updated CSV files → good
use the CSV files generated by IRIS in iknowpy → good

One question remains. When the shared memory model loads, some of the literal labels get re-written by the DELVE code, i.g.:
/**** Rewritten by DELVE, ;;たところ(;;JPta;-;JPPartAdvNOUN;JPEndRelation;Join;Join;-;BracketOpen;
;;たところ(;;JPta;-;JPPartAdvNOUN;JPEndRelation;Join;Join;-;BracketOpen;Lit_lbrack
If a new literal label gets added to the rules file in iknowpy, no such re-writing occurs, i.e., "Lit_lbrack" above does not get added to the multi-lexreps that include the literal label. Is that not necessary? I recall there was a reason why this re-writing was needed in IRIS. Wasn't there?

After reviewing the history of literal labels implementation (thank you Jos) & validating in IRIS & standalone iKnow, I confirm that the current state of literal labels is as per expectation in both. Closing this issue.


Damage Tracking

Hello,
I'm currently implementing the wlr-screencopy protocol within a compositor and I've noticed that damage doesn't seem to be taken into account, (in copy_with_damage requests). For instance, if I only copy the damaged regions to the wf-recorder buffers (both SHM and DMA), the resulting video exhibits the typical buffer tracking error glitches. Interestingly, this issue doesn't occur if I perform a full copy, and it works fine even if I don't send the correct damaged region.
So, is damage considered? and does wf-recorder require the compositor to always perform a full copy to the buffers?
Thank you.
Tested version: 0.4.1

The compositor is always required to do a full copy with wlr-screencopy-v1. This is addressed by ext-screencopy-v1: https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/124

Thank you!


Fails to generate code for the gitea API

Describe the bug
openapi-python-generator does not like the API definition of gitea and bugs out during code generation:
❯ poetry run openapi-python-generator --library requests https://gitea.opensuse.org/swagger.v1.json gitea/
Generating data from https://gitea.opensuse.org/swagger.v1.json
Error in service adminCronList: invalid syntax (<string>, line 1)
Error in service adminCronRun: invalid syntax (<string>, line 1)
Error in service adminGetAllOrgs: invalid syntax (<string>, line 1)
Error in service adminUnadoptedList: invalid syntax (<string>, line 1)
Error in service adminAdoptRepository: invalid syntax (<string>, line 1)
Error in service adminDeleteUnadoptedRepository: invalid syntax (<string>, line 1)
Error in service adminGetAllUsers: invalid syntax (<string>, line 1)
Error in service adminDeleteUser: invalid syntax (<string>, line 1)
Error in service adminEditUser: invalid syntax (<string>, line 1)
Error in service adminCreatePublicKey: invalid syntax (<string>, line 1)
Error in service adminDeleteUserPublicKey: invalid syntax (<string>, line 1)
Error in service adminCreateOrg: invalid syntax (<string>, line 1)
Error in service adminCreateRepo: invalid syntax (<string>, line 1)
Error in service notifyGetList: invalid syntax (<string>, line 1)
Error in service notifyReadList: invalid syntax (<string>, line 1)
Error in service notifyGetThread: invalid syntax (<string>, line 1)
Error in service notifyReadThread: invalid syntax (<string>, line 1)
Error in service createOrgRepoDeprecated: invalid syntax (<string>, line 1)
Error in service orgGetAll: invalid syntax (<string>, line 1)
Error in service orgGet: invalid syntax (<string>, line 1)
Error in service orgDelete: invalid syntax (<string>, line 1)
Error in service orgEdit: invalid syntax (<string>, line 1)
Error in service orgListHooks: invalid syntax (<string>, line 1)
Error in service orgCreateHook: invalid syntax (<string>, line 1)
Error in service orgGetHook: invalid syntax (<string>, line 1)
Error in service orgDeleteHook: invalid syntax (<string>, line 1)
Error in service orgEditHook: invalid syntax (<string>, line 1)
Error in service orgListLabels: invalid syntax (<string>, line 1)
Error in service orgCreateLabel: invalid syntax (<string>, line 1)
Error in service orgGetLabel: invalid syntax (<string>, line 1)
Error in service orgDeleteLabel: invalid syntax (<string>, line 1)
Error in service orgEditLabel: invalid syntax (<string>, line 1)
Error in service orgListMembers: invalid syntax (<string>, line 1)
Error in service orgIsMember: invalid syntax (<string>, line 1)
Error in service orgDeleteMember: invalid syntax (<string>, line 1)
Error in service orgListPublicMembers: invalid syntax (<string>, line 1)
Error in service orgIsPublicMember: invalid syntax (<string>, line 1)
Error in service orgPublicizeMember: invalid syntax (<string>, line 1)
Error in service orgConcealMember: invalid syntax (<string>, line 1)
Error in service orgListRepos: invalid syntax (<string>, line 1)
Error in service createOrgRepo: invalid syntax (<string>, line 1)
Error in service orgListTeams: invalid syntax (<string>, line 1)
Error in service orgCreateTeam: invalid syntax (<string>, line 1)
Error in service teamSearch: invalid syntax (<string>, line 1)
Error in service listPackages: invalid syntax (<string>, line 1)
Error in service getPackage: invalid syntax (<string>, line 1)
Error in service deletePackage: invalid syntax (<string>, line 1)
Error in service listPackageFiles: invalid syntax (<string>, line 1)
Error in service issueSearchIssues: invalid syntax (<string>, line 1)
Error in service repoSearch: invalid syntax (<string>, line 1)
Error in service repoGet: invalid syntax (<string>, line 1)
Error in service repoDelete: invalid syntax (<string>, line 1)
Error in service repoEdit: invalid syntax (<string>, line 1)
Error in service repoGetArchive: invalid syntax (<string>, line 1)
Error in service repoGetAssignees: invalid syntax (<string>, line 1)
Error in service repoListBranchProtection: invalid syntax (<string>, line 1)
Error in service repoCreateBranchProtection: invalid syntax (<string>, line 1)
Error in service repoGetBranchProtection: invalid syntax (<string>, line 1)
Error in service repoDeleteBranchProtection: invalid syntax (<string>, line 1)
Error in service repoEditBranchProtection: invalid syntax (<string>, line 1)
Error in service repoListBranches: invalid syntax (<string>, line 1)
Error in service repoCreateBranch: invalid syntax (<string>, line 1)
Error in service repoGetBranch: invalid syntax (<string>, line 1)
Error in service repoDeleteBranch: invalid syntax (<string>, line 1)
Error in service repoListCollaborators: invalid syntax (<string>, line 1)
Error in service repoCheckCollaborator: invalid syntax (<string>, line 1)
Error in service repoAddCollaborator: invalid syntax (<string>, line 1)
Error in service repoDeleteCollaborator: invalid syntax (<string>, line 1)
Error in service repoGetRepoPermissions: invalid syntax (<string>, line 1)
Error in service repoGetAllCommits: invalid syntax (<string>, line 1)
Error in service repoGetCombinedStatusByRef: invalid syntax (<string>, line 1)
Error in service repoListStatusesByRef: invalid syntax (<string>, line 1)
Error in service repoGetContentsList: invalid syntax (<string>, line 1)
Error in service repoGetContents: invalid syntax (<string>, line 1)
Error in service repoCreateFile: invalid syntax (<string>, line 1)
Error in service repoUpdateFile: invalid syntax (<string>, line 1)
Error in service repoDeleteFile: invalid syntax (<string>, line 1)
Error in service repoApplyDiffPatch: invalid syntax (<string>, line 1)
Error in service repoGetEditorConfig: invalid syntax (<string>, line 1)
Error in service listForks: invalid syntax (<string>, line 1)
Error in service createFork: invalid syntax (<string>, line 1)
Error in service GetBlob: invalid syntax (<string>, line 1)
Error in service repoGetSingleCommit: invalid syntax (<string>, line 1)
Error in service repoDownloadCommitDiffOrPatch: invalid syntax (<string>, line 1)
Error in service repoGetNote: invalid syntax (<string>, line 1)
Error in service repoListAllGitRefs: invalid syntax (<string>, line 1)
Error in service repoListGitRefs: invalid syntax (<string>, line 1)
Error in service GetAnnotatedTag: invalid syntax (<string>, line 1)
Error in service GetTree: invalid syntax (<string>, line 1)
Error in service repoListHooks: invalid syntax (<string>, line 1)
Error in service repoCreateHook: invalid syntax (<string>, line 1)
Error in service repoListGitHooks: invalid syntax (<string>, line 1)
Error in service repoGetGitHook: invalid syntax (<string>, line 1)
Error in service repoDeleteGitHook: invalid syntax (<string>, line 1)
Error in service repoEditGitHook: invalid syntax (<string>, line 1)
Error in service repoGetHook: invalid syntax (<string>, line 1)
Error in service repoDeleteHook: invalid syntax (<string>, line 1)
Error in service repoEditHook: invalid syntax (<string>, line 1)
Error in service repoTestHook: invalid syntax (<string>, line 1)
Error in service repoGetIssueTemplates: invalid syntax (<string>, line 1)
Error in service issueListIssues: invalid syntax (<string>, line 1)
Error in service issueCreateIssue: invalid syntax (<string>, line 1)
Error in service issueGetRepoComments: invalid syntax (<string>, line 1)
Error in service issueGetComment: invalid syntax (<string>, line 1)
Error in service issueDeleteComment: invalid syntax (<string>, line 1)
Error in service issueEditComment: invalid syntax (<string>, line 1)
Error in service issueGetCommentReactions: invalid syntax (<string>, line 1)
Error in service issuePostCommentReaction: invalid syntax (<string>, line 1)
Error in service issueDeleteCommentReaction: invalid syntax (<string>, line 1)
Error in service issueGetIssue: invalid syntax (<string>, line 1)
Error in service issueDelete: invalid syntax (<string>, line 1)
Error in service issueEditIssue: invalid syntax (<string>, line 1)
Error in service issueGetComments: invalid syntax (<string>, line 1)
Error in service issueCreateComment: invalid syntax (<string>, line 1)
Error in service issueDeleteCommentDeprecated: invalid syntax (<string>, line 1)
Error in service issueEditCommentDeprecated: invalid syntax (<string>, line 1)
Error in service issueEditIssueDeadline: invalid syntax (<string>, line 1)
Error in service issueGetLabels: invalid syntax (<string>, line 1)
Error in service issueAddLabel: invalid syntax (<string>, line 1)
Error in service issueReplaceLabels: invalid syntax (<string>, line 1)
Error in service issueClearLabels: invalid syntax (<string>, line 1)
Error in service issueRemoveLabel: invalid syntax (<string>, line 1)
Error in service issueGetIssueReactions: invalid syntax (<string>, line 1)
Error in service issuePostIssueReaction: invalid syntax (<string>, line 1)
Error in service issueDeleteIssueReaction: invalid syntax (<string>, line 1)
Error in service issueDeleteStopWatch: invalid syntax (<string>, line 1)
Error in service issueStartStopWatch: invalid syntax (<string>, line 1)
Error in service issueStopStopWatch: invalid syntax (<string>, line 1)
Error in service issueSubscriptions: invalid syntax (<string>, line 1)
Error in service issueCheckSubscription: invalid syntax (<string>, line 1)
Error in service issueAddSubscription: invalid syntax (<string>, line 1)
Error in service issueDeleteSubscription: invalid syntax (<string>, line 1)
Error in service issueGetCommentsAndTimeline: invalid syntax (<string>, line 1)
Error in service issueTrackedTimes: invalid syntax (<string>, line 1)
Error in service issueAddTime: invalid syntax (<string>, line 1)
Error in service issueResetTime: invalid syntax (<string>, line 1)
Error in service issueDeleteTime: invalid syntax (<string>, line 1)
Error in service repoListKeys: invalid syntax (<string>, line 1)
Error in service repoCreateKey: invalid syntax (<string>, line 1)
Error in service repoGetKey: invalid syntax (<string>, line 1)
Error in service repoDeleteKey: invalid syntax (<string>, line 1)
Error in service issueListLabels: invalid syntax (<string>, line 1)
Error in service issueCreateLabel: invalid syntax (<string>, line 1)
Error in service issueGetLabel: invalid syntax (<string>, line 1)
Error in service issueDeleteLabel: invalid syntax (<string>, line 1)
Error in service issueEditLabel: invalid syntax (<string>, line 1)
Error in service repoGetLanguages: invalid syntax (<string>, line 1)
Error in service repoGetRawFileOrLFS: invalid syntax (<string>, line 1)
Error in service issueGetMilestonesList: invalid syntax (<string>, line 1)
Error in service issueCreateMilestone: invalid syntax (<string>, line 1)
Error in service issueGetMilestone: invalid syntax (<string>, line 1)
Error in service issueDeleteMilestone: invalid syntax (<string>, line 1)
Error in service issueEditMilestone: invalid syntax (<string>, line 1)
Error in service repoMirrorSync: invalid syntax (<string>, line 1)
Error in service notifyGetRepoList: invalid syntax (<string>, line 1)
Error in service notifyReadRepoList: invalid syntax (<string>, line 1)
Error in service repoListPullRequests: invalid syntax (<string>, line 1)
Error in service repoCreatePullRequest: invalid syntax (<string>, line 1)
Error in service repoGetPullRequest: invalid syntax (<string>, line 1)
Error in service repoEditPullRequest: invalid syntax (<string>, line 1)
Error in service repoDownloadPullDiffOrPatch: invalid syntax (<string>, line 1)
Error in service repoGetPullRequestCommits: invalid syntax (<string>, line 1)
Error in service repoPullRequestIsMerged: invalid syntax (<string>, line 1)
Error in service repoMergePullRequest: invalid syntax (<string>, line 1)
Error in service repoCancelScheduledAutoMerge: invalid syntax (<string>, line 1)
Error in service repoCreatePullReviewRequests: invalid syntax (<string>, line 1)
Error in service repoDeletePullReviewRequests: invalid syntax (<string>, line 1)
Error in service repoListPullReviews: invalid syntax (<string>, line 1)
Error in service repoCreatePullReview: invalid syntax (<string>, line 1)
Error in service repoGetPullReview: invalid syntax (<string>, line 1)
Error in service repoSubmitPullReview: invalid syntax (<string>, line 1)
Error in service repoDeletePullReview: invalid syntax (<string>, line 1)
Error in service repoGetPullReviewComments: invalid syntax (<string>, line 1)
Error in service repoDismissPullReview: invalid syntax (<string>, line 1)
Error in service repoUnDismissPullReview: invalid syntax (<string>, line 1)
Error in service repoUpdatePullRequest: invalid syntax (<string>, line 1)
Error in service repoGetRawFile: invalid syntax (<string>, line 1)
Error in service repoListReleases: invalid syntax (<string>, line 1)
Error in service repoCreateRelease: invalid syntax (<string>, line 1)
Error in service repoGetReleaseByTag: invalid syntax (<string>, line 1)
Error in service repoDeleteReleaseByTag: invalid syntax (<string>, line 1)
Error in service repoGetRelease: invalid syntax (<string>, line 1)
Error in service repoDeleteRelease: invalid syntax (<string>, line 1)
Error in service repoEditRelease: invalid syntax (<string>, line 1)
Error in service repoListReleaseAttachments: invalid syntax (<string>, line 1)
Error in service repoCreateReleaseAttachment: invalid syntax (<string>, line 1)
Error in service repoGetReleaseAttachment: invalid syntax (<string>, line 1)
Error in service repoDeleteReleaseAttachment: invalid syntax (<string>, line 1)
Error in service repoEditReleaseAttachment: invalid syntax (<string>, line 1)
Error in service repoGetReviewers: invalid syntax (<string>, line 1)
Error in service repoSigningKey: invalid syntax (<string>, line 1)
Error in service repoListStargazers: invalid syntax (<string>, line 1)
Error in service repoListStatuses: invalid syntax (<string>, line 1)
Error in service repoCreateStatus: invalid syntax (<string>, line 1)
Error in service repoListSubscribers: invalid syntax (<string>, line 1)
Error in service userCurrentCheckSubscription: invalid syntax (<string>, line 1)
Error in service userCurrentPutSubscription: invalid syntax (<string>, line 1)
Error in service userCurrentDeleteSubscription: invalid syntax (<string>, line 1)
Error in service repoListTags: invalid syntax (<string>, line 1)
Error in service repoCreateTag: invalid syntax (<string>, line 1)
Error in service repoGetTag: invalid syntax (<string>, line 1)
Error in service repoDeleteTag: invalid syntax (<string>, line 1)
Error in service repoListTeams: invalid syntax (<string>, line 1)
Error in service repoCheckTeam: invalid syntax (<string>, line 1)
Error in service repoAddTeam: invalid syntax (<string>, line 1)
Error in service repoDeleteTeam: invalid syntax (<string>, line 1)
Error in service repoTrackedTimes: invalid syntax (<string>, line 1)
Error in service userTrackedTimes: invalid syntax (<string>, line 1)
Error in service repoListTopics: invalid syntax (<string>, line 1)
Error in service repoUpdateTopics: invalid syntax (<string>, line 1)
Error in service repoAddTopic: invalid syntax (<string>, line 1)
Error in service repoDeleteTopic: invalid syntax (<string>, line 1)
Error in service repoTransfer: invalid syntax (<string>, line 1)
Error in service acceptRepoTransfer: invalid syntax (<string>, line 1)
Error in service rejectRepoTransfer: invalid syntax (<string>, line 1)
Error in service repoCreateWikiPage: invalid syntax (<string>, line 1)
Error in service repoGetWikiPage: invalid syntax (<string>, line 1)
Error in service repoDeleteWikiPage: invalid syntax (<string>, line 1)
Error in service repoEditWikiPage: invalid syntax (<string>, line 1)
Error in service repoGetWikiPages: invalid syntax (<string>, line 1)
Error in service repoGetWikiPageRevisions: invalid syntax (<string>, line 1)
Error in service generateRepo: invalid syntax (<string>, line 1)
Error in service repoGetByID: invalid syntax (<string>, line 1)
Error in service orgGetTeam: invalid syntax (<string>, line 1)
Error in service orgDeleteTeam: invalid syntax (<string>, line 1)
Error in service orgEditTeam: invalid syntax (<string>, line 1)
Error in service orgListTeamMembers: invalid syntax (<string>, line 1)
Error in service orgListTeamMember: invalid syntax (<string>, line 1)
Error in service orgAddTeamMember: invalid syntax (<string>, line 1)
Error in service orgRemoveTeamMember: invalid syntax (<string>, line 1)
Error in service orgListTeamRepos: invalid syntax (<string>, line 1)
Error in service orgListTeamRepo: invalid syntax (<string>, line 1)
Error in service orgAddTeamRepository: invalid syntax (<string>, line 1)
Error in service orgRemoveTeamRepository: invalid syntax (<string>, line 1)
Error in service topicSearch: invalid syntax (<string>, line 1)
Error in service userGetOauth2Application: invalid syntax (<string>, line 1)
Error in service userGetOAuth2Application: invalid syntax (<string>, line 1)
Error in service userDeleteOAuth2Application: invalid syntax (<string>, line 1)
Error in service userUpdateOAuth2Application: invalid syntax (<string>, line 1)
Error in service userCurrentListFollowers: invalid syntax (<string>, line 1)
Error in service userCurrentListFollowing: invalid syntax (<string>, line 1)
Error in service userCurrentCheckFollowing: invalid syntax (<string>, line 1)
Error in service userCurrentPutFollow: invalid syntax (<string>, line 1)
Error in service userCurrentDeleteFollow: invalid syntax (<string>, line 1)
Error in service userCurrentListGPGKeys: invalid syntax (<string>, line 1)
Error in service userCurrentGetGPGKey: invalid syntax (<string>, line 1)
Error in service userCurrentDeleteGPGKey: invalid syntax (<string>, line 1)
Error in service userCurrentListKeys: invalid syntax (<string>, line 1)
Error in service userCurrentGetKey: invalid syntax (<string>, line 1)
Error in service userCurrentDeleteKey: invalid syntax (<string>, line 1)
Error in service orgListCurrentUserOrgs: invalid syntax (<string>, line 1)
Error in service userCurrentListRepos: invalid syntax (<string>, line 1)
Error in service userCurrentListStarred: invalid syntax (<string>, line 1)
Error in service userCurrentCheckStarring: invalid syntax (<string>, line 1)
Error in service userCurrentPutStar: invalid syntax (<string>, line 1)
Error in service userCurrentDeleteStar: invalid syntax (<string>, line 1)
Error in service userGetStopWatches: invalid syntax (<string>, line 1)
Error in service userCurrentListSubscriptions: invalid syntax (<string>, line 1)
Error in service userListTeams: invalid syntax (<string>, line 1)
Error in service userCurrentTrackedTimes: invalid syntax (<string>, line 1)
Error in service userSearch: invalid syntax (<string>, line 1)
Error in service userGet: invalid syntax (<string>, line 1)
Error in service userListFollowers: invalid syntax (<string>, line 1)
Error in service userListFollowing: invalid syntax (<string>, line 1)
Error in service userCheckFollowing: invalid syntax (<string>, line 1)
Error in service userListGPGKeys: invalid syntax (<string>, line 1)
Error in service userGetHeatmapData: invalid syntax (<string>, line 1)
Error in service userListKeys: invalid syntax (<string>, line 1)
Error in service orgListUserOrgs: invalid syntax (<string>, line 1)
Error in service orgGetUserPermissions: invalid syntax (<string>, line 1)
Error in service userListRepos: invalid syntax (<string>, line 1)
Error in service userListStarred: invalid syntax (<string>, line 1)
Error in service userListSubscriptions: invalid syntax (<string>, line 1)
Error in service userGetTokens: invalid syntax (<string>, line 1)
Error in service userCreateToken: invalid syntax (<string>, line 1)
Error in service userDeleteAccessToken: invalid syntax (<string>, line 1)
Traceback (most recent call last):
  File "/home/dan/.cache/pypoetry/virtualenvs/scm-staging-UcbLi63M-py3.11/bin/openapi-python-generator", line 8, in <module>
    sys.exit(main())
             ^^^^^^
  File "/home/dan/.cache/pypoetry/virtualenvs/scm-staging-UcbLi63M-py3.11/lib/python3.11/site-packages/click/core.py", line 1130, in __call__
    return self.main(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/dan/.cache/pypoetry/virtualenvs/scm-staging-UcbLi63M-py3.11/lib/python3.11/site-packages/click/core.py", line 1055, in main
    rv = self.invoke(ctx)
         ^^^^^^^^^^^^^^^^
  File "/home/dan/.cache/pypoetry/virtualenvs/scm-staging-UcbLi63M-py3.11/lib/python3.11/site-packages/click/core.py", line 1404, in invoke
    return ctx.invoke(self.callback, **ctx.params)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/dan/.cache/pypoetry/virtualenvs/scm-staging-UcbLi63M-py3.11/lib/python3.11/site-packages/click/core.py", line 760, in invoke
    return __callback(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/dan/.cache/pypoetry/virtualenvs/scm-staging-UcbLi63M-py3.11/lib/python3.11/site-packages/openapi_python_generator/__main__.py", line 49, in main
    generate_data(source, output, library, env_token_name, use_orjson)
  File "/home/dan/.cache/pypoetry/virtualenvs/scm-staging-UcbLi63M-py3.11/lib/python3.11/site-packages/openapi_python_generator/generate_data.py", line 143, in generate_data
    write_data(result, output)
  File "/home/dan/.cache/pypoetry/virtualenvs/scm-staging-UcbLi63M-py3.11/lib/python3.11/site-packages/openapi_python_generator/generate_data.py", line 112, in write_data
    write_code(
  File "/home/dan/.cache/pypoetry/virtualenvs/scm-staging-UcbLi63M-py3.11/lib/python3.11/site-packages/openapi_python_generator/generate_data.py", line 33, in write_code
    formatted_contend = black.format_file_contents(
                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "src/black/__init__.py", line 926, in format_file_contents
  File "src/black/__init__.py", line 1073, in format_str
  File "src/black/__init__.py", line 1083, in _format_str_once
  File "src/black/parsing.py", line 127, in lib2to3_parse
black.parsing.InvalidInput: Cannot parse: 8:28: def createOrgRepoDeprecated(, body : CreateRepoOption = None, ) -> Repository:

I have tried using a different library (and ran into #6), but that does not appear to help.

I'll take a look. For posterities sake, this is the openapi.json.

According to the provided openapi.json, it is currently compliant with openapi v2, which this project does not support as stated in the docs.
This could maybe be a thing for the future if the interest is high enough, however as of now, this is no priority for me. I would be glad for a pull request if you want to make one :)

This should be fixed with the latest v0.3.10 release of the tool :)

Yes, this works now, thank you!!


Create-react-app failed to minify

Error message

Failed to minify the code from this file: ./node_modules/react-slideshow-image/lib/helpers.js:10

File
"use strict";

Object.defineProperty(exports, "__esModule", {
  value: true
});
exports.getUnhandledProps = getUnhandledProps;

function getUnhandledProps(ComponentProps, props) {
  const handledProps = Object.keys(ComponentProps);
  return Object.keys(props).reduce((acc, prop) => {
    if (handledProps.indexOf(prop) === -1) acc[prop] = props[prop];
    return acc;
  }, {});
}

Version
"react-slideshow-image": "^1.2.0",

package.json
{
  "name": "react-auth-template",
  "homepage": "name",
  "version": "0.1.0",
  "private": true,
  "dependencies": {
    "autoprefixer": "7.1.6",
    "axios": "^0.18.0",
    "bootstrap": "^4.3.1",
    "chalk": "1.1.3",
    "dotenv": "4.0.0",
    "dotenv-expand": "4.2.0",
    "each-async": "^1.1.1",
    "fs-extra": "3.0.1",
    "gh-pages": "^2.0.1",
    "object-assign": "4.1.1",
    "promise": "8.0.1",
    "raf": "3.4.0",
    "react": "^16.4.2",
    "react-background-slider": "^1.2.0",
    "react-bootstrap": "^1.0.0-beta.5",
    "react-dom": "^16.4.2",
    "react-router-dom": "^4.3.1",
    "react-slideshow-image": "^1.2.0",
    "resolve": "1.6.0",
    "url-loader": "0.6.2",
    "react-scripts": "2.0.0-next.3e165448"
  },
  "scripts": {
    "start": "node scripts/start.js",
    "build": "node scripts/build.js",
    "test": "node scripts/test.js --env=jsdom",
    "make-standard": "eslint --fix ./src;exit 0",
    "nag": "eslint ./src;exit 0",
    "deploy": "gh-pages -d build",
    "predeploy": "npm run build"
  },
  "jest": {
    "collectCoverageFrom": [
      "src/**/*.{js,jsx,mjs}"
    ],
    "setupFiles": [
      "<rootDir>/config/polyfills.js"
    ],
    "testMatch": [
      "<rootDir>/src/**/__tests__/**/*.{js,jsx,mjs}",
      "<rootDir>/src/**/?(*.)(spec|test).{js,jsx,mjs}"
    ],
    "testEnvironment": "node",
    "testURL": "http://localhost",
    "transform": {
      "^.+\\.(js|jsx|mjs)$": "<rootDir>/node_modules/babel-jest",
      "^.+\\.css$": "<rootDir>/config/jest/cssTransform.js",
      "^(?!.*\\.(js|jsx|mjs|css|json)$)": "<rootDir>/config/jest/fileTransform.js"
    },
    "transformIgnorePatterns": [
      "[/\\\\]node_modules[/\\\\].+\\.(js|jsx|mjs)$"
    ],
    "moduleNameMapper": {
      "^react-native$": "react-native-web"
    },
    "moduleFileExtensions": [
      "web.js",
      "js",
      "json",
      "web.jsx",
      "jsx",
      "node",
      "mjs"
    ]
  },
  "babel": {
    "presets": [
      "react-app"
    ]
  },
  "eslintConfig": {
    "extends": "react-app"
  },
  "devDependencies": {
    "ajv": "^5.5.2",
    "babel-core": "6.26.0",
    "babel-eslint": "^9.0.0",
    "babel-jest": "20.0.3",
    "babel-loader": "7.1.2",
    "babel-preset-react-app": "^3.1.1",
    "babel-runtime": "6.26.0",
    "case-sensitive-paths-webpack-plugin": "2.1.1",
    "css-loader": "0.28.7",
    "eslint": "^5.14.1",
    "eslint-config-react-app": "^3.0.7",
    "eslint-config-standard": "^12.0.0",
    "eslint-loader": "^2.1.2",
    "eslint-plugin-flowtype": "^2.50.3",
    "eslint-plugin-import": "^2.13.0",
    "eslint-plugin-jsx-a11y": "^6.2.1",
    "eslint-plugin-node": "^8.0.1",
    "eslint-plugin-promise": "^4.0.1",
    "eslint-plugin-react": "^7.12.0",
    "eslint-plugin-standard": "^4.0.0",
    "extract-text-webpack-plugin": "3.0.2",
    "file-loader": "1.1.5",
    "html-webpack-plugin": "2.29.0",
    "jest": "20.0.4",
    "node-sass": "^4.9.3",
    "postcss-flexbugs-fixes": "3.2.0",
    "postcss-loader": "2.0.8",
    "react-dev-utils": "^5.0.1",
    "sass-loader": "^7.1.0",
    "style-loader": "0.19.0",
    "sw-precache-webpack-plugin": "0.11.4",
    "webpack": "3.8.1",
    "webpack-dev-server": "2.9.4",
    "webpack-manifest-plugin": "1.3.2"
  }
}

@saeedalzahrani thanks for raising this issue. I'll take a look at it. 👍

@saeedalzahrani I'm guessing you did npm run eject. Did you make some changes to your configuration and what command do you run that generates this error? I'm trying to reproduce the bug but I couldn't

I am using react-gh-pages to deploy. https://github.com/gitname/react-gh-pages
Here is the full error message
Saeeds-MacBook-Pro:react-template saeedalzahrani$ npm run deploy

><EMAIL_ADDRESS>predeploy /Users/saeedalzahrani/Desktop/wdi/projects/final_project/react-template
> npm run build

><EMAIL_ADDRESS>build /Users/saeedalzahrani/Desktop/wdi/projects/final_project/react-template
> node scripts/build.js

Creating an optimized production build...
Failed to compile.

Failed to minify the code from this file:

 	./node_modules/react-slideshow-image/lib/helpers.js:10

Read more here: http://bit.ly/2tRViJ9

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>build: `node scripts/build.js`
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.

npm ERR!      /Users/saeedalzahrani/.npm/_logs/2019-07-31T14_28_08_479Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>predeploy: `npm run build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>predeploy script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!      /Users/saeedalzahrani/.npm/_logs/2019-07-31T14_28_08_560Z-debug.log

And the debug log
0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli   '/usr/local/Cellar/node/12.4.0/bin/node',
1 verbose cli   '/usr/local/bin/npm',
1 verbose cli   'run',
1 verbose cli   'deploy'
1 verbose cli ]
2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose run-script [ 'predeploy', 'deploy', 'postdeploy' ]
5 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>6 verbose lifecycle<EMAIL_ADDRESS>unsafe-perm in lifecycle true
7 verbose lifecycle<EMAIL_ADDRESS>PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/Users/saeedalzahrani/Desktop/wdi/projects/final_project/react-template/node_modules/.bin:/Users/saeedalzahrani/.rbenv/shims:/Library/Frameworks/Python.framework/Versions/3.7/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin
8 verbose lifecycle<EMAIL_ADDRESS>CWD: /Users/saeedalzahrani/Desktop/wdi/projects/final_project/react-template
9 silly lifecycle<EMAIL_ADDRESS>Args: [ '-c', 'npm run build' ]
10 silly lifecycle<EMAIL_ADDRESS>Returned: code: 1  signal: null
11 info lifecycle<EMAIL_ADDRESS>Failed to exec predeploy script
12 verbose stack Error<EMAIL_ADDRESS>predeploy: `npm run build`
12 verbose stack Exit status 1
12 verbose stack     at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:301:16)
12 verbose stack     at EventEmitter.emit (events.js:200:13)
12 verbose stack     at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
12 verbose stack     at ChildProcess.emit (events.js:200:13)
12 verbose stack     at maybeClose (internal/child_process.js:1021:16)
12 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5)
13 verbose pkgid<EMAIL_ADDRESS>14 verbose cwd /Users/saeedalzahrani/Desktop/wdi/projects/final_project/react-template
15 verbose Darwin 18.7.0
16 verbose argv "/usr/local/Cellar/node/12.4.0/bin/node" "/usr/local/bin/npm" "run" "deploy"
17 verbose node v12.4.0
18 verbose npm  v6.9.0
19 error code ELIFECYCLE
20 error errno 1
21 error<EMAIL_ADDRESS>predeploy: `npm run build`
21 error Exit status 1
22 error Failed at the<EMAIL_ADDRESS>predeploy script.
22 error This is probably not a problem with npm. There is likely additional logging output above.
23 verbose exit [ 1, true ]

This error also occurs when I run npm run build directly.
This is my repository if it is helpful to clone and reproduce https://github.com/salt-1/project-4-frontend

@saeedalzahrani the issue has been fixed now in this PR #40 and a new version has been released. Use the v1.2.1 in your package.json and you should be good to go. Thanks for the issue


HBASE-27514 Move some persistent states from zookeeper to master region

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m  7s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ master Compile Tests _

+0 :ok:
mvndep
0m 15s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m 51s
master passed

+1 :green_heart:
compile
3m 55s
master passed

+1 :green_heart:
checkstyle
1m  1s
master passed

+1 :green_heart:
spotless
0m 46s
branch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
3m  8s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 11s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 14s
the patch passed

-1 :x:
compile
1m 11s
hbase-server in the patch failed.

-0 :warning:
javac
1m 11s
hbase-server in the patch failed.

-0 :warning:
checkstyle
0m 15s
hbase-client: The patch generated 1 new + 17 unchanged - 0 fixed = 18 total (was 17)

-0 :warning:
checkstyle
0m 38s
hbase-server: The patch generated 3 new + 7 unchanged - 1 fixed = 10 total (was 8)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
13m  5s
Patch does not cause any errors with Hadoop 3.2.4 3.3.4.

+1 :green_heart:
spotless
1m  6s
patch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
4m 24s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 39s
The patch does not generate ASF License warnings.

48m 49s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4925/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/4925

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti spotless checkstyle compile

uname
Linux 3b10ad726759 5.4.0-1085-aws #92~18.04.1-Ubuntu SMP Wed Aug 31 17:21:08 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 8b4e134f8c

Default Java
Eclipse Adoptium-11.0.17+8

compile
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4925/1/artifact/yetus-general-check/output/patch-compile-hbase-server.txt

javac
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4925/1/artifact/yetus-general-check/output/patch-compile-hbase-server.txt

checkstyle
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4925/1/artifact/yetus-general-check/output/diff-checkstyle-hbase-client.txt

checkstyle
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4925/1/artifact/yetus-general-check/output/diff-checkstyle-hbase-server.txt

Max. process+thread count
79 (vs. ulimit of 30000)

modules
C: hbase-client hbase-zookeeper hbase-server U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4925/1/console

versions
git=2.34.1 maven=3.8.6 spotbugs=4.7.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 25s
Docker mode activated.

-0 :warning:
yetus
0m  3s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+0 :ok:
mvndep
0m 10s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
2m 20s
master passed

+1 :green_heart:
compile
1m 10s
master passed

+1 :green_heart:
shadedjars
3m 48s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 50s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 13s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m  9s
the patch passed

+1 :green_heart:
compile
1m  9s
the patch passed

+1 :green_heart:
javac
1m  9s
the patch passed

+1 :green_heart:
shadedjars
3m 42s
patch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 23s
hbase-server generated 1 new + 23 unchanged - 0 fixed = 24 total (was 23)

_ Other Tests _

+1 :green_heart:
unit
1m 17s
hbase-client in the patch passed.

+1 :green_heart:
unit
0m 34s
hbase-zookeeper in the patch passed.

-1 :x:
unit
205m 48s
hbase-server in the patch failed.

229m 22s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4925/1/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/4925

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux d58122ccb214 5.4.0-131-generic #147-Ubuntu SMP Fri Oct 14 17:07:22 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 8b4e134f8c

Default Java
Temurin-1.8.0_352-b08

javadoc
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4925/1/artifact/yetus-jdk8-hadoop3-check/output/diff-javadoc-javadoc-hbase-server.txt

unit
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4925/1/artifact/yetus-jdk8-hadoop3-check/output/patch-unit-hbase-server.txt

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4925/1/testReport/

Max. process+thread count
2641 (vs. ulimit of 30000)

modules
C: hbase-client hbase-zookeeper hbase-server U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4925/1/console

versions
git=2.34.1 maven=3.8.6

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m  8s
Docker mode activated.

-0 :warning:
yetus
0m  2s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+0 :ok:
mvndep
0m 14s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m 57s
master passed

+1 :green_heart:
compile
1m 35s
master passed

+1 :green_heart:
shadedjars
4m 28s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m  6s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 11s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 16s
the patch passed

+1 :green_heart:
compile
1m 40s
the patch passed

+1 :green_heart:
javac
1m 40s
the patch passed

+1 :green_heart:
shadedjars
4m 39s
patch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 28s
hbase-server generated 1 new + 96 unchanged - 0 fixed = 97 total (was 96)

_ Other Tests _

+1 :green_heart:
unit
1m 30s
hbase-client in the patch passed.

+1 :green_heart:
unit
0m 38s
hbase-zookeeper in the patch passed.

-1 :x:
unit
202m 16s
hbase-server in the patch failed.

232m  3s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4925/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/4925

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 2a01488bbe69 5.4.0-1085-aws #92~18.04.1-Ubuntu SMP Wed Aug 31 17:21:08 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 8b4e134f8c

Default Java
Eclipse Adoptium-11.0.17+8

javadoc
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4925/1/artifact/yetus-jdk11-hadoop3-check/output/diff-javadoc-javadoc-hbase-server.txt

unit
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4925/1/artifact/yetus-jdk11-hadoop3-check/output/patch-unit-hbase-server.txt

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4925/1/testReport/

Max. process+thread count
2682 (vs. ulimit of 30000)

modules
C: hbase-client hbase-zookeeper hbase-server U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4925/1/console

versions
git=2.34.1 maven=3.8.6

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 15s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ master Compile Tests _

+0 :ok:
mvndep
0m 15s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m 55s
master passed

+1 :green_heart:
compile
3m 58s
master passed

+1 :green_heart:
checkstyle
1m  1s
master passed

+1 :green_heart:
spotless
0m 45s
branch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
3m  4s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 11s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 10s
the patch passed

+1 :green_heart:
compile
3m 36s
the patch passed

+1 :green_heart:
javac
3m 36s
the patch passed

-0 :warning:
checkstyle
0m 14s
hbase-client: The patch generated 1 new + 17 unchanged - 0 fixed = 18 total (was 17)

-0 :warning:
checkstyle
0m 37s
hbase-server: The patch generated 1 new + 20 unchanged - 1 fixed = 21 total (was 21)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
13m 50s
Patch does not cause any errors with Hadoop 3.2.4 3.3.4.

+1 :green_heart:
spotless
0m 54s
patch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
4m 29s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 32s
The patch does not generate ASF License warnings.

50m 39s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4925/2/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/4925

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti spotless checkstyle compile

uname
Linux dc158a459765 5.4.0-1085-aws #92~18.04.1-Ubuntu SMP Wed Aug 31 17:21:08 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 8b4e134f8c

Default Java
Eclipse Adoptium-11.0.17+8

checkstyle
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4925/2/artifact/yetus-general-check/output/diff-checkstyle-hbase-client.txt

checkstyle
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4925/2/artifact/yetus-general-check/output/diff-checkstyle-hbase-server.txt

Max. process+thread count
78 (vs. ulimit of 30000)

modules
C: hbase-client hbase-zookeeper hbase-server U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4925/2/console

versions
git=2.34.1 maven=3.8.6 spotbugs=4.7.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m  3s
Docker mode activated.

-0 :warning:
yetus
0m  4s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+0 :ok:
mvndep
0m  8s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
2m 14s
master passed

+1 :green_heart:
compile
1m 11s
master passed

+1 :green_heart:
shadedjars
3m 48s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 52s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 14s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 13s
the patch passed

+1 :green_heart:
compile
1m 12s
the patch passed

+1 :green_heart:
javac
1m 12s
the patch passed

+1 :green_heart:
shadedjars
3m 48s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 50s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
1m  2s
hbase-client in the patch passed.

+1 :green_heart:
unit
0m 37s
hbase-zookeeper in the patch passed.

+1 :green_heart:
unit
213m 53s
hbase-server in the patch passed.

237m 48s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4925/2/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/4925

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 759628384a72 5.4.0-135-generic #152-Ubuntu SMP Wed Nov 23 20:19:22 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 8b4e134f8c

Default Java
Temurin-1.8.0_352-b08

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4925/2/testReport/

Max. process+thread count
2465 (vs. ulimit of 30000)

modules
C: hbase-client hbase-zookeeper hbase-server U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4925/2/console

versions
git=2.34.1 maven=3.8.6

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

PTAL again? @bbeaudreault Thanks.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
5m 16s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ master Compile Tests _

+0 :ok:
mvndep
0m 18s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m 28s
master passed

+1 :green_heart:
compile
3m 52s
master passed

+1 :green_heart:
checkstyle
1m  0s
master passed

+1 :green_heart:
spotless
0m 44s
branch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
3m  3s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 10s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 17s
the patch passed

+1 :green_heart:
compile
3m 47s
the patch passed

-0 :warning:
javac
2m 37s
hbase-server generated 1 new + 194 unchanged - 1 fixed = 195 total (was 195)

-0 :warning:
checkstyle
0m 15s
hbase-client: The patch generated 1 new + 17 unchanged - 0 fixed = 18 total (was 17)

-0 :warning:
checkstyle
0m 35s
hbase-server: The patch generated 1 new + 20 unchanged - 1 fixed = 21 total (was 21)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
13m 29s
Patch does not cause any errors with Hadoop 3.2.4 3.3.4.

+1 :green_heart:
spotless
1m  4s
patch has no errors when running spotless:check.

-1 :x:
spotbugs
2m 31s
hbase-server generated 1 new + 0 unchanged - 0 fixed = 1 total (was 0)

_ Other Tests _

+1 :green_heart:
asflicense
0m 30s
The patch does not generate ASF License warnings.

54m 18s

Reason
Tests

FindBugs
module:hbase-server

org.apache.hadoop.hbase.master.BooleanStateStore.get() is unsynchronized, org.apache.hadoop.hbase.master.BooleanStateStore.set(boolean) is synchronized  At BooleanStateStore.java:synchronized  At BooleanStateStore.java:[line 46]

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4925/3/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/4925

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti spotless checkstyle compile

uname
Linux ca526c5c656c 5.4.0-1085-aws #92~18.04.1-Ubuntu SMP Wed Aug 31 17:21:08 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 222ec684d6

Default Java
Eclipse Adoptium-11.0.17+8

javac
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4925/3/artifact/yetus-general-check/output/diff-compile-javac-hbase-server.txt

checkstyle
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4925/3/artifact/yetus-general-check/output/diff-checkstyle-hbase-client.txt

checkstyle
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4925/3/artifact/yetus-general-check/output/diff-checkstyle-hbase-server.txt

spotbugs
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4925/3/artifact/yetus-general-check/output/new-spotbugs-hbase-server.html

Max. process+thread count
79 (vs. ulimit of 30000)

modules
C: hbase-client hbase-zookeeper hbase-server U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4925/3/console

versions
git=2.34.1 maven=3.8.6 spotbugs=4.7.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
5m 20s
Docker mode activated.

-0 :warning:
yetus
0m  2s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+0 :ok:
mvndep
0m 19s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m 31s
master passed

+1 :green_heart:
compile
1m 38s
master passed

+1 :green_heart:
shadedjars
4m 29s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m  1s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 11s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 19s
the patch passed

+1 :green_heart:
compile
1m 41s
the patch passed

+1 :green_heart:
javac
1m 41s
the patch passed

+1 :green_heart:
shadedjars
4m 35s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 57s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
1m 48s
hbase-client in the patch passed.

+1 :green_heart:
unit
0m 39s
hbase-zookeeper in the patch passed.

+1 :green_heart:
unit
203m 39s
hbase-server in the patch passed.

237m 30s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4925/3/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/4925

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 8e9070b4636f 5.4.0-1085-aws #92~18.04.1-Ubuntu SMP Wed Aug 31 17:21:08 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 222ec684d6

Default Java
Eclipse Adoptium-11.0.17+8

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4925/3/testReport/

Max. process+thread count
2696 (vs. ulimit of 30000)

modules
C: hbase-client hbase-zookeeper hbase-server U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4925/3/console

versions
git=2.34.1 maven=3.8.6

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m  3s
Docker mode activated.

-0 :warning:
yetus
0m  3s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+0 :ok:
mvndep
0m 17s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
2m 12s
master passed

+1 :green_heart:
compile
1m 11s
master passed

+1 :green_heart:
shadedjars
3m 48s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 50s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 14s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 14s
the patch passed

+1 :green_heart:
compile
1m  9s
the patch passed

+1 :green_heart:
javac
1m  9s
the patch passed

+1 :green_heart:
shadedjars
3m 46s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 50s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
1m  0s
hbase-client in the patch passed.

+1 :green_heart:
unit
0m 36s
hbase-zookeeper in the patch passed.

+1 :green_heart:
unit
216m 16s
hbase-server in the patch passed.

240m 31s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4925/3/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/4925

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 87178faea604 5.4.0-135-generic #152-Ubuntu SMP Wed Nov 23 20:19:22 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 222ec684d6

Default Java
Temurin-1.8.0_352-b08

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4925/3/testReport/

Max. process+thread count
2536 (vs. ulimit of 30000)

modules
C: hbase-client hbase-zookeeper hbase-server U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4925/3/console

versions
git=2.34.1 maven=3.8.6

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 18s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ master Compile Tests _

+0 :ok:
mvndep
0m 19s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m 32s
master passed

+1 :green_heart:
compile
3m 58s
master passed

+1 :green_heart:
checkstyle
1m  0s
master passed

+1 :green_heart:
spotless
0m 43s
branch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
3m  8s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 11s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 12s
the patch passed

+1 :green_heart:
compile
3m 38s
the patch passed

+1 :green_heart:
javac
3m 38s
the patch passed

-0 :warning:
checkstyle
0m 14s
hbase-client: The patch generated 1 new + 17 unchanged - 0 fixed = 18 total (was 17)

-0 :warning:
checkstyle
0m 40s
hbase-server: The patch generated 1 new + 20 unchanged - 1 fixed = 21 total (was 21)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
13m 35s
Patch does not cause any errors with Hadoop 3.2.4 3.3.4.

+1 :green_heart:
spotless
0m 59s
patch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
4m 23s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 34s
The patch does not generate ASF License warnings.

50m 10s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4925/4/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/4925

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti spotless checkstyle compile

uname
Linux b4f95d3168f8 5.4.0-1085-aws #92~18.04.1-Ubuntu SMP Wed Aug 31 17:21:08 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 222ec684d6

Default Java
Eclipse Adoptium-11.0.17+8

checkstyle
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4925/4/artifact/yetus-general-check/output/diff-checkstyle-hbase-client.txt

checkstyle
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4925/4/artifact/yetus-general-check/output/diff-checkstyle-hbase-server.txt

Max. process+thread count
79 (vs. ulimit of 30000)

modules
C: hbase-client hbase-zookeeper hbase-server U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4925/4/console

versions
git=2.34.1 maven=3.8.6 spotbugs=4.7.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m  1s
Docker mode activated.

-0 :warning:
yetus
0m  2s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+0 :ok:
mvndep
0m 11s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
2m 17s
master passed

+1 :green_heart:
compile
1m 10s
master passed

+1 :green_heart:
shadedjars
3m 46s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 52s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 13s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 15s
the patch passed

+1 :green_heart:
compile
1m 10s
the patch passed

+1 :green_heart:
javac
1m 10s
the patch passed

+1 :green_heart:
shadedjars
3m 51s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 49s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
1m  1s
hbase-client in the patch passed.

+1 :green_heart:
unit
0m 36s
hbase-zookeeper in the patch passed.

+1 :green_heart:
unit
216m 43s
hbase-server in the patch passed.

240m 20s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4925/4/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/4925

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux afa9d6ebdf6c 5.4.0-135-generic #152-Ubuntu SMP Wed Nov 23 20:19:22 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 222ec684d6

Default Java
Temurin-1.8.0_352-b08

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4925/4/testReport/

Max. process+thread count
2496 (vs. ulimit of 30000)

modules
C: hbase-client hbase-zookeeper hbase-server U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4925/4/console

versions
git=2.34.1 maven=3.8.6

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.


The resource cannot be edited or deployed while it is in the Deploying state

Describe the bug
The resource cannot be edited or deployed while it is in the deploying state.
Steps to reproduce

Create a resource, click Save and Preview;
Click Apply after planned.

Result
When run fails, the resource is stuck in a deploying state, and cannot edit or deploy it.

Expected behavior
When run fails,  resource goes into DeployFailed state.
Environment

Walrus version: v0.6.0-rc1

This seems to be related to the issue that sometimes resources get stuck in a Deploying state https://github.com/seal-io/walrus/issues/814#issuecomment-1982279057.

Can not find a way to reproduce it, add log print to trace it.

Environment

Walrus version: main 61070fa9f82dd3630b4aadb8626245dcef93e722
UI version: dev-f26d810

Test Result: Reproduce in main.

2024-03-13T02:38:04.760Z	D	api	200 | HTTP/2.0 |     10 KiB |        0 B |   12.806525ms |       <IP_ADDRESS> | PUT     /v1/projects/504341382106710018/environments/504465041026711554/resources/504602230469427202/runs/504602230502981634/terraform-states
2024-03-13T02:38:05.424Z	D	task	executed	{"createBy": "ResourceComponentLabelApplyCronExpr", "duration": "5.409238732s"}
2024-03-13T02:38:07.047Z	D	signal.handler	reaped child process 1917
2024-03-13T02:38:08.074Z	I	k8sctrl.deployer.tf	succeed	{"resource-run": "504602230502981634"}
2024-03-13T02:38:08.082Z	D	resource-run.syncer	resource azure-redis "create" run<PHONE_NUMBER>02981634 status "Succeeded"
2024-03-13T02:38:08.082Z	D	resource-run.syncer	set resource azure-redis status to "Preparing"
2024-03-13T02:38:08.175Z	W	task	error executing: error get resource alicloud_vpc:vpc-wz9d6xjh8gvuljlma44m3 from<PHONE_NUMBER>32478722: not found; error get resource alicloud_vswitch:vsw-wz9ny5j4uk3on4n51gvvi from<PHONE_NUMBER>32478722: not found; error get resource alicloud_vpc:vpc-wz97672v87gi7n18g0mgi from<PHONE_NUMBER>32478722: not found; error get resource alicloud_vswitch:vsw-wz9042b6ayih7pm83bndo from<PHONE_NUMBER>32478722: not found	{"createBy": "ResourceComponentStatusSyncCronExpr"}
2024-03-13T02:38:30.014Z	D	task	executed	{"createBy": "ResourceRelationshipCheckCronExpr", "duration": "7.741175ms"}
2024-03-13T02:39:00.024Z	D	task	executed	{"createBy": "ResourceRelationshipCheckCronExpr", "duration": "8.36193ms"}
2024-03-13T02:39:04.746Z	D	task	executed	{"createBy": "ResourceComponentsDiscoverCronExpr", "duration": "4.730741321s"}

Environment

Walrus version: main 38a408d6aa9ad32b0aea13f4c5eec7849bb6a29e
UI version: dev-f7ec895

Test Result: Cannot be reproduced in main.


chore: add perf test for select widget

Description
Add perf test for select widget.
Actions included:

rendering options list.
selecting an option

New script to run a single test - start-single-test.sh
Type of change
Checklist:

[ ] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

Test coverage results :test_tube:
:white_circle: Total coverage has not changed
No changes to code coverage between the base branch and the head branch

/ok-to-test sha=e2e78ed

/ok-to-test sha=2f1f14b

/ok-to-test sha=2f1f14b

/ok-to-test sha=d23bc76

/ok-to-test sha=7a53ff2


Error in the sidekiq error handler.

ruby 2.3.6p384
sidekiq (4.2.5)
sentry-raven (2.7.2)
I'm seeing this error in our logs, indication an error in the error handler preventing them to be sent to sentry:
{"severity":"ERROR","message":"!!! ERROR HANDLER THREW AN ERROR !!!","@timestamp":"2018-03-07T09:52:08.423Z","@version":"1"}
{"severity":"ERROR","message":"no member 'wrapped' in struct","@timestamp":"2018-03-07T09:52:08.423Z","@version":"1"}
{"severity":"ERROR","message":"/applications/x/shared/bundle/ruby/2.3.0/gems/sentry-raven-2.7.2/lib/raven/integrations/sidekiq.rb:59:in `[]'\n/applications/x/shared/bundle/ruby/2.3.0/gems/sentry-raven-2.7.2/lib/raven/integrations/sidekiq.rb:59:in

So either context or job is sometimes a Struct ( https://github.com/mperham/sidekiq/blob/2ed92600fa71a9c275189d01df369ad4f8b9ca32/lib/sidekiq/fetch.rb#L10 ) and, therefor trying ta access 'wrapped' or 'class' isn't falsey it throws an error no member 'x' in struct.
We still get errors from sidekiq into sentry so this isn't completely broken, this might be only triggered when we use delayed job like jobs?
https://github.com/getsentry/raven-ruby/blob/master/lib/raven/integrations/sidekiq.rb#L59
def transaction_from_context(context)
  classname = (context["wrapped"] || context["class"] ||
                (context[:job] && (context[:job]["wrapped"] || context[:job]["class"]))
              )

So we need to change fetching the class name to make sure we don't run into an Struct.
I'm not sure but this could be caused by: #702

That’s a sidekiq bug, please upgrade


Remove version: Tableau.Desktop version 24.1.1132

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

URL: https://downloads.tableau.com/esdalt/2024.1.3/TableauDesktop-64bit-2024-1-3.exe
Response status code does not indicate success: 403 (Forbidden).
(Automated message - build 896)


[ASK] what is the best practice to create file helper for Open Database Connection?

What version of Go are you using (go version)?
1.10.1
Which database and its version are you using?
mariadb
What is the best practice to create single database file helper for Open Database Connection?

Open database connection once using singleton pattern, and never close it for every HTTP request?
Or
every HTTP request always open database connection and close it?

I am so confused

Based on my research while exploring golang, the first one is the best practice.
See this stackoverflow answer.

@albertonaperijr concerning this answer, unlike sql.Open, gorm.Open does call Ping.


Adaptive hide not working

Adaptive hide is not working for the spotify app. I have to refresh the skin to update the changes.

It's still not fixed.....


Cleaned up build scripts & added documentation on building

Build script changes:

Added clean.sh script, to clean out all of the installed dictionary files and output files
Changed the /bin/bash shebang to /bin/sh for portability purposes

README changes:

Added a new Building section, which documents how to build the yomichan binary, and create the JMdict dictionaries.

Note to self (will open this as an issue when the issues tab is created): We eventually want to rename everything here to yomitan. However, there are a few potential issues with this:

The go.mod file seems to specify various dependencies, and some of them are various other Foosoft archived repositories: https://github.com/FooSoft/jmdict and https://github.com/FooSoft/zero-epwing-go.
I'm not at all familiar with go, but I believe this package is uploaded somewhere as foosoft.net/projects/yomichan-import/yomichan. In order to rename yomichan to yomitan, we might need to upload this project, as well as the repositories above, as separate packages maintained by themoeway instead of foosoft.

I'm willing to look into all of this in the next week or two, since I wanted to learn go for a while anyways.

Hey, I know a bit of go so I'd hope you don't mind me chiming in on this.
The go.mod file states the URL that this package is accesible from, the go version used and the dependencies of the project.
The first line that starts with module declares the URL from which this program can be imported into other programs.
To change this over for use with Yomitan, you just simply need to change the first line to
module $NEWURL
$NEWURL being the new place the project will be hosted at.
I would suggest we store all these new yomitan versions on this organization, it would be pretty convient and it's pretty common practice to have Go packages stored on github.

Converted to draft (since #2 should be merged first). After #2 is merged and all outstanding errors are dealt with, I'll fix the merge conflicts and re-open the PR.


Phone checks at login.

-This should be a warning screen not just info screen.
-Text should be: Your phone does not have any secure entry like Pin or Biometric
-Add to it: “This may be a security risk to your funds on Hexa”

Warning like image change is remaining from design team

Need warning image for bottom sheet.

https://xd.adobe.com/view/181f3fd2-7aca-4284-61c7-3417e1fe6d8a-6e2e/screen/c0f38435-7018-41d2-befc-b470f0eabd63

There is a screen for this. We used the wrong image.

https://xd.adobe.com/view/181f3fd2-7aca-4284-61c7-3417e1fe6d8a-6e2e/screen/6d0301f2-ae43-439c-9c98-e2551cc098f4

-Need to do the changes as per the XD link

https://xd.adobe.com/view/0aef8043-d951-4d0a-9a97-b7b2e16ffdbc-5fbc/screen/f25f3e5c-89a1-4c73-b154-35559d94e368/
@ASN-BitHyve take a look at the content


Add osx-x86_64 netty-resolver-dns-native-macos dependency

Motivation: Unable to load io.netty.resolver.dns.macos.MacOSDnsServerAddressStreamProvider on M1 MAC
Same problem with netty's next problem.
https://github.com/netty/netty/issues/11020
Modifications: There is an osx-x86_64 in armeria, but no osx-aarch_64.
https://github.com/netty/netty/issues/11693

Thanks! @woohhan 😄


Update to Mailchimp API v3.0?

I noticed that Mailchimp has release version 3.0 of their API here.
Are you interested in updating Gibbon to for Mailchimp API v3.0?  I'd be happy to help if I can!  But first I wanted to make sure this was something you would be interested in.
Thanks!

Hi Nell. Yes, I am. I'm in the process of rethinking how Gibbon might work to support the new API right now. I'm not happy with how Gibbon is built at the moment.

For example, API 3 supports multiple HTTP verbs per endpoint. Thinking out loud, the syntax might look like:
gibbon.get.lists(list_id).interest_categories(category_id).interests(id)

Creating a new object might look like:
gibbon.post.campaigns(campaign)

It's weird to leak the http verb into the syntax. I'm not a fan of that and open to ideas to fix it. Still thinking on this.
Feedback or suggestions welcome.

I don't see much way around it and there are other libraries that have done the same. However, the verb tends to be at the end of the resource string, not the beginning. And, taking the Stripe Ruby library as an example, it uses the CRUD verbs rather than raw HTTP verbs
https://stripe.com/docs/api/ruby#create_card
So, your above example would be more like
gibbon.lists(list_id).interest_categories(category_id).interests(id).retrieve

gibbon.lists(list_id).interest_categories(category_id).interests(id).update(payload)

Cool. Thanks for sharing. That's very helpful. I'll make time to start working on this. Help testing would be especially appreciated, once I have something to share.

Absolutely!  Please send me a ping when you're ready for some testing :)

Just a heads up that I have started on this.

Huzzah!! :smile_cat:

Fetching lists works now. I need to test other resources and add actual tests, plus do a little more work to make sure errors from the http lib (switched rest-client but not sure it's best yet) are handled properly.

Usage looks a like this (currently):
g = Gibbon::Request.new(api_key: "mykey-us1")
g.lists.retrieve(params: {foo: "bar"}, headers: {headername: "value"})

Supports params, headers, and body depending on the HTTP verb so that'll cover things like filters, etc. Values that go in the url, like IDs, work as we discussed above.

Looking good!
When this is ready for testing, I'd be happy to both test and update the command examples in the README.

Take a look at https://github.com/amro/gibbon/tree/api_v3 when you have time. The tests are completely out of date/broken. Part of the readme has been updated. From "Fetching Campaigns" to  "Error Handling" needs to be updated. To be clear, the "Error Handling" section has been updated.
To be honest, I don't know what params are available on some of these calls to do things like filter, paginate, etc. I made my best effort to support headers, query params, and post body to cover that sort of thing. I think the API docs are not quite complete yet.
Please send any pull requests against the api_v3 branch. I do prefer a single squashed commit, if possible.

Ah, FYI, there's one issue I've not figured out yet. There are some internal methods in ::APIRequest. I still need to mark them private but I was having issues calling them from a public method on that class. I moved on in the interest of time but I will revisit it. Maybe later tonight.

Another update: I fixed some of the tests, commented the rest out for now. Examples in README (as mentioned above) still need to be updated and more tests need to be updated or replaced. Still working from the api_v3 branch.

Will take a look tonight!
On Thu, May 14, 2015 at 7:34 PM, Amro Mousa<EMAIL_ADDRESS>wrote:

Another update: I fixed some of the tests, commented the rest out for now.
Examples in README (as mentioned above) still need to be updated and more
tests need to be updated or replaced. Still working from the api_v3 branch.
—
Reply to this email directly or view it on GitHub
https://github.com/amro/gibbon/issues/118#issuecomment-102227783.

Partly through the README, updating as I go along.  Will continue tomorrow morning.

Awesome, thanks!

Here's an example of subscribing a user, if you've not already figured it out:
g.lists(list_id).members.create(body: {email_address: email_address, status: "subscribed"})

Thanks!  That's a big help, I was missing the "body" part :)

Hmm...that's giving me an error:
2.1.2 :018 > gb.lists(list_id).members.create({body: {email_address<EMAIL_ADDRESS>status: "subscribed"}})
Gibbon::MailChimpError: undefined method `bytesize' for<EMAIL_ADDRESS>:status=>"subscribed"}:Hash

Troubleshooting

I'm kind of stumped on this one.

Pull latest from the branch to fix that. I wasn't json encoding the body bc I thought Faraday would do that given the wording in its readme. Apologies!
Thanks,
Amro
Sent from my iPhone

On May 16, 2015, at 9:45 PM, Nell Shamrell-Harrington<EMAIL_ADDRESS>wrote:
I'm kind of stumped on this one.
—
Reply to this email directly or view it on GitHub.

Will do!

Works like a charm now :)

Sent an email to Mailchimp asking for some examples of creating a campaign and paginating responses to queries (even when using offset and count as detailed in this article http://kb.mailchimp.com/api/article/api-3-overview)
Will add those once I have working examples based on Mailchimp's examples :)

Thanks very much

Just heard back from MailChimp:
Thanks for reaching out. At this time, campaign creation methods aren't available in v3.0 of the API. You'll need to continue using the v2.0 endpoints for now to create campaigns, but it's on the roadmap for 3.0: https://apidocs.mailchimp.com/api/2.0/campaigns/create.php
To paginate using v3.0 of the API, you'll want to add the "count" and "offset" parameters as query strings to the endpoint URL. For example, if I wanted to grab campaigns 301-400, I'd make a GET request to the following endpoint:
https://usX.api.mailchimp.com/3.0/campaigns?count=100&offset=300
Will add some count and offset parameter examples as I have time.

Thanks Nell. Sounds good. I’ll keep testing and try to write a few more unit tests I get time as well.

Hi, I was wondering where the update is these days. Is the v3.0 branch ready to try out?

You can try out the api_v3 branch, yes. There are no known bugs but I'm waiting on some tests someone has graciously offered to contribute.
I intend to push one more release of Gibbon 1.x that will adds support. This was contributed recently by @fsluis.

Cool, I'll keep you guys posted.

I pushed a prerelease version of v2: just gem install gibbon --pre to get it
https://rubygems.org/gems/gibbon/versions/2.0.0.pre
I'll promote to prod once it's been out there for a little while.

Has anyone on this thread run into issues?

I've been using it for a simple list subscriptions and it's all good. Thanks for working on this!

@lachlanhardy Thanks for the feedback. It's super helpful. I'll release really soon.

I released v2

Yay, thanks! Now using it in production :)


Ihn/update maintainers

Checklist

[x] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly conda-forge automerge bot!
I considered the following status checks when analyzing this PR:

linter: passed
azure: passed

Thus the PR was passing and merged! Have a great day!


Fixed some documentation for #59, also fixed some broken markdown links

Fixed documentation according to  @kdubb changes in #59, also fixed some broken markdown links.

Like that?

Exactly like that :-)
Thanks for contribution @erilor!


Update rotating_tank.rst

Joins the start of section 4.2 with the remainder of the section in the docs

Thanks for pointing out the typos. We are in the process of adding and reviewing "Tutorial Baroclinic Gyre" and I've fixed these typos there, so will close this PR. We do want to keep the individual tutorial experiments in their own separate .rst files, else it starts to take too long for one's browser to render. (separate rst files was also done in PR #267)